can't remove device

[GuidoLenk]

Hi,

since i'm having trouble with my libraries, i want to re-setup them.... but i can't remove one of them... i did delete the jukebox, but when i'm trying to delete the device, it says i have to unmount it first.... when i try this i get device is idle!

Please help...

 

[605]

Restart the NetWorker server to release it. Unmounting should be possible at all times and under all conditions.

 

[GuidoLenk]

with 'networker stop' and '...start'?

 

[Chacalinc]

yessssss }

 

[GuidoLenk]

ok did it.... but now after rejbconfiged my first lib, i get read open error i/o error

the second lib i can't rejbconfig because it says there is something wrong with my drivers?? before it asks me if i installed driver package..... never had that before.... both lib's where running till a few days ago....

 

[Chacalinc]

hmmm... may be your libraries should be reseted.. make the engineering's typical solution, power off and on the libraries and try again.

 

[GuidoLenk]

i did already.... more than once ....

 

[Chacalinc]

are your libraries connected through a SCSI or FC card? do you have some other device in the same channel? I'm thinking that the problem could be the SCSI card or the cable.

Cheers.

 

[GuidoLenk]

SCSI.... i'll check cables...

 

[605]

Read I/O errors usually point to the fact that you talk to the wrong device. This may especially happen under Windows when it auto-reconfigures the tapes. You may check this by loading a media in a device and then run tapeexercise for each device at a time.

Also make sure - if it is on Windows, a drive rescan may have re-enabled the Removable Storage Manager. DISABLE IT!

 

[NWNinja]

Use the "inquire" command to have a look at the scsi chain, make sure all devices have correct drive mappings, i.e \\.\Tape0 or /dev/rmt/0cbn for example. Try mounting a tape into one device, then use the "mt" command to check if the tape was loaded into the correct drive. I think the syntax should be: mt -f \\.\Tape0 status

First you get a bunch of info regarding the drives features.
At the very bottom you should have info if a tape is loaded or not. Like 605 said, usually you have a problem on the scsi chain, which might cause NW to load a tape into what it thinks is Tape0, but is infact Tape1.