Forum Discussion

Carlos_V's avatar
Carlos_V
Level 6
16 years ago
Solved

Tapes in status frozen, after maked the backup tape

Hi, i have the next problem, NB mount the tape to make a Backup, when the tape end use is in frozen state, then NOM send me an alert. I need to solve why our media server put on the tape in status frozen, please see the next message when i execute the command bperror

12/16/2009 10:07:54 crcgesms03 -  TapeAlert Code: 0x27, Type: Warning, Flag:
                    DIAGNOSTICS REQ., from drive STK.T10000B.001 (index 4),
                    Media Id 036184
12/16/2009 10:07:54
crcgesms03 -  TapeAlert Code: 0x34, Type: Critical, Flag:
                    SYSTEM AREA WRITE FAILURE, from drive STK.T10000B.001
                    (index 4), Media Id 036184
12/16/2009 10:07:54
crcgesms03 -  TapeAlert Code: 0x3a, Type: Warning, Flag:
                    FIRMWARE FAILURE, from drive STK.T10000B.001 (index 4),
                    Media Id 036184

Anybody have a idea?

I need to be sure the problem is in the drive

Regards...

  • 350 0x27
        351 Diagnostics required
        352 Warning
        353 The tape drive may have a hardware fault. Run extended diagnostics\
        354 to verify and diagnose the problem. Check the tape drive users\
        355 manual for device specific instructions on running extended\
        356 diagnostics tests.
        357 The drive may have a hardware fault that may be identified by\
        358 extended diagnostics (i.e. SEND DIAGNOSTIC command).


      471 0x34
        472 Tape system area write failure
        473 Critical
        474 The tape just unloaded could not write its system area\
        475 successfully:\
        476 1. Copy data to another tape cartridge.\
        477 2. Discard the old cartridge.
        478 Write errors while writing the system area on unload.


      542 0x3a
        543 Firmware failure
        544 Warning
        545 The tape drive has reset itself due to a detected firmware fault. If\
        546 problem persists, call the supplier help line.
        547 Firmware bug.


    you can find these on the web

    src.opensolaris.org/source/xref/samqfs/samqfs/src/utility/tapealert/tapealert.text
  • Thanks, but the drives and the cartridge are new, the model is  relatively new T10000B. 

    The operating system of media server is AIX, will have something to do this?


    Regards!
  • Well it could be,

    "infant mortality"  some things just don't work right even when new.
    I got a new library and 2 of the drives did not work.

    if aix

    look in the errpt and see if you logged any errors on the drive.

    if it is a drive problem aix will log it

    you can also run diag on the aix server and have it check based on the errpt.
  • A 'relatively new' tape does not mean that it has the latest firmware - the drive could've been on a shelve for a year or two before it was sold to you... I would've logged a call with the SUN/STK reseller.
    The supported O/S and tested firmware versions are listed the Device Compatibility matrix.
    Judy - THANKS for the URL, I've been searching for something like this!!
  • Thank you. But we have installed the last version of firmware 1.44.208.

    Regards!
  • Hi All,

    I have same problem, I found error in C:\Program Files\Veritas\NetBackup\db\media>

    1/06/09 07:10:28 002060 2 TAPE_ALERT IBM.ULTRIUM-TD3.007 0x30001000 0x02000000
    1/10/09 01:16:26 002008 2 WRITE_ERROR IBM.ULTRIUM-TD3.007
    1/10/09 01:16:33 002008 2 TAPE_ALERT IBM.ULTRIUM-TD3.007 0x00800000 0x00000000
    1/10/09 01:27:22 002008 1 WRITE_ERROR IBM.ULTRIUM-TD3.006
    1/10/09 01:27:29 002008 1 TAPE_ALERT IBM.ULTRIUM-TD3.006 0x00800000 0x00000000
    1/10/09 02:01:38 002008 1 WRITE_ERROR IBM.ULTRIUM-TD3.006
    1/10/09 02:01:43 002008 1 TAPE_ALERT IBM.ULTRIUM-TD3.006 0x00800000 0x00000000
    1/19/09 17:51:11 002103 2 WRITE_ERROR IBM.ULTRIUM-TD3.007
    1/19/09 17:51:18 002103 2 TAPE_ALERT IBM.ULTRIUM-TD3.007 0x30001000 0x02000000
    2/09/09 02:26:08 002156 0 WRITE_ERROR IBM.ULTRIUM-TD3.000
    2/09/09 02:26:15 002156 0 TAPE_ALERT IBM.ULTRIUM-TD3.000 0x30001000 0x02000000
    2/21/09 02:04:20 002030 2 TAPE_ALERT IBM.ULTRIUM-TD3.002 0x00000000 0x02000000
    2/22/09 23:00:19 002063 3 WRITE_ERROR IBM.ULTRIUM-TD3.003
    2/22/09 23:00:25 002063 3 TAPE_ALERT IBM.ULTRIUM-TD3.003 0x30001000 0x02000000
    2/24/09 00:57:44 002240 4 WRITE_ERROR IBM.ULTRIUM-TD3.004
    2/24/09 00:57:52 002240 4 TAPE_ALERT IBM.ULTRIUM-TD3.004 0x30001000 0x02000000
    2/24/09 03:00:18 002237 3 WRITE_ERROR IBM.ULTRIUM-TD3.003
    2/24/09 03:00:24 002237 3 TAPE_ALERT IBM.ULTRIUM-TD3.003 0x30001000 0x02000000
    2/24/09 05:11:15 002251 2 TAPE_ALERT IBM.ULTRIUM-TD3.002 0x00000000 0x02000000
    2/25/09 01:11:25 002240 3 WRITE_ERROR IBM.ULTRIUM-TD3.003
    2/25/09 01:11:35 002240 3 TAPE_ALERT IBM.ULTRIUM-TD3.003 0x30001000 0x02000000
    2/25/09 04:29:45 002237 0 WRITE_ERROR IBM.ULTRIUM-TD3.000
    2/25/09 04:29:51 002237 0 TAPE_ALERT IBM.ULTRIUM-TD3.000 0x30001000 0x02000000
    2/25/09 05:30:20 002251 1 TAPE_ALERT IBM.ULTRIUM-TD3.001 0x00000000 0x02000000

    :\Program Files\Veritas\NetBackup\db\media>

    my library is PowerVault ML6000 Series
  • ... is almost a year ago!  :)

    Check the write-protect tab or replace the suspect media. 
  • Carlos,

    Start simple.
    Prove the tapedrive and tapes are good at the OS level.
    Use mt and tar, dd or whatever to write, read, mount, dismount  from several of the tapes.
    Do physical checks on the library and tape drive while doing this.
    Look in the system logs for events/errors.

    After you can prove that the tapedrives can both write and read from the cartridges then proceed to NetBackup.
    Make sure the drivers you are using are correct for the firmware installed on the tape drives.
    Follow the link that Marianne provided and check compatability.
    Make sure the robot and library is properly cconfigured and audited.

    Also, always remember, read/write errors can be the fault of I/O operations and not the physical media.