Unsolved
This post is more than 5 years old
5 Posts
0
903
January 19th, 2010 00:00
Tape Read Open Errors
Hi,
Networker 7.4.4. Tape library Dell 6000 with 4 x LTO4 drives.
My backups all failed last night with the log reporting the following error messages when attemting to load a tape:
Tape read open error. Command completed successfully (drive status is 6532935). The drive serial number has changed.
The backup eventually times out and fails.
No config changes have been made that I am aware of. Inquire command reports all 4 drives OK.
How can I align the drive serial numbers correctly or do I need to delete the library and run JBCONFIG?
Thank-you in advance.
BGuevara
1 Rookie
•
101 Posts
1
January 19th, 2010 01:00
Hi, i just checked out that the bug was with 7.4.3 version so i would suggest to run a jbedit or jbconfig, also if you are running networker in a SAN environment, ou should configure persisting binding in the HBA's.
Regards.
BGuevara
1 Rookie
•
101 Posts
0
January 19th, 2010 01:00
Hi Chaschaste,
I believe that there is a bug in 7.4.4 or 7.4.3 that trigger that error even though there have not been any hardware change, so try to install the last build for your networker version.
If that is not fix the issue, you can try running a jbedit or a jbconfig to reconfigure your library.
Regards.
chaschate
5 Posts
0
January 19th, 2010 02:00
You were right Mr Guevara. Due to a tape library power down, the HBA's lost their bindings. A rescan of devices detected 4 "new" devices and all is Ok now. Drives are happy and test backup completed Ok.
Thank-you for your input.
Jiju1
181 Posts
0
January 20th, 2010 03:00
Hi,
Is like Drive serial Number Changed or the Tape Volume has been Changed , if the drive Serial No has Changed then go the Library Console and Check whether both the serial number are same or not , If it same , Remove the T.L from the storage node and again add it using jbconfig again Check if the VOlume nam eof the tape is Changed then take the tape out and Check the Barcode . There might be problme with the Barcode , Because we have faced these kind of issue many times .
Rajesh S