Networker server version 7.2 running on Windows 2000 OS.
StorageTek L80 with 3 LT01 drives SCSI attached directly to Networker server. 1 drive that was faulty has been replaced, and the firmware upgraded, and server rebooted. As a result the drive ordering changed, so jukebox had to be deleted in Networker.
The inquire output showed all 3 drives, but 1 drive (not the one that was replaced, but showed the serial number and drive type) showed no tape symbolic name- found out that the driver wasn't installed on the OS looking at device manager, so this has been re-installed.
Inquire output now shows the tape symbolic name (\\.\Tape2) and same scsidev number but no serial number (scsidev numbers haven't changed) but still picks it up as an Ultrium- TD1 drive.
When running a jbconfig, and specifying the drive path for this element (\\.\Tape2) it says:
stat error: device `\\.\Tape2' does not exist.
Pathname '\\.\Tape2' is not valid. Please try again.
However this shows in inquire, but with no S/N. I'm thinking a reboot of the server may repopulate the inquire output.
In the meantime, as the other 2 drives \\.\Tape0 and \\.\Tape1 are ok, can jbconfig be configured to skip the problem drive and just use the 2 working drives?
Obviously nsrjb shows nothing as no jukebox has been configured yet. Is there a fix for this aside from setting persistent binding on the HBAs in the future?
I would suggest delete all drivers, reboot the box, scan for devices and install drivers to the latest version, reboot the box again and see if that resolves things.
Also 7.2 is out of support now, I would suggest you update from this (I'm guessing you have stuck with this as your server is still on Windows 2000?)
Thanks Hormigo, I will give this a try and let you know how it goes.
Do you know if jbconfig allows you to configure x drives out of y available drives in Networker i.e. if there is a problem drive that you know about and you need to delete and rebuild the jukebox? I'm thinking there probably isn't as jbconfig scans all devices available via the autochanger and only if we physically removed the drive would we be able to configure it without the problem drive then re-add via jbedit.
Also, is there any documentation on setting persistent binding? Is this an OS setting or HBA setting?
install_exclusive.exe should be used by applications (such as Tivoli Storage Manager) requiring the driver to issue automatic reserves on open and also preventing multiple open handles from a host to a drive to exist at the same time.
Note: This option replaces the previous default installation of install.exe
install_nonexclusive.exe:
install_nonexclusive.exe should be used by applications (such as Microsoft Data Protection Manager or Microsoft Removable Storage Manager) permitting multiple open handles from a host to a drive to exist at the same time.
Note: This option replaces the previous command line installation of install.exe -n
To install the Windows 200x IBMTape Device Drivers:
Double click on install_exclusive.exe or install_nonexclusive.exe to start the drivers installation or use the command line options as follows:
c = install only the changer drivers t = install only the tape drivers d = output debug information to debug.txt s = silent mode (suppress IBM driver pop-ups) r = disable the RSM service f = disable DPF h = print usage information
DavidHampson
2 Intern
•
1080 Posts
1108
0
Posted August 7th, 2009 05:00
Also 7.2 is out of support now, I would suggest you update from this (I'm guessing you have stuck with this as your server is still on Windows 2000?)