This content has been marked as final. Show 3 replies
What OS are you running?1 person found this helpful
It sounds like the device attach points have moved. If this is a Linux system then you can do "obtool lsdev -l" to see what /dev/sg entry your devices are looking at, and then do "sg_map -x -i" to see what /dev/sg your devices are really using. Then you can update the device attach points to point to the correct entry using "obtool chdev -a"
For example :
obtool lsdev -l
Device type: tape
Serial number: 882E70020M
In service: yes
Query frequency: [undetermined]
Debug mode: no
Blocking factor: 512
Max blocking factor: 512
Current tape: [unknown]
Use list: all
Drive usage: 2 months, 1 week
Cleaning required: no
Raw device: /dev/sg2
sg_map -x -i
/dev/sg0 0 0 32 0 13 DP BACKPLANE 1.05
/dev/sg1 0 2 0 0 0 /dev/sda DELL PERC 6/i 1.22
/dev/sg2 1 0 0 0 5 /dev/scd0 TEAC DVD-ROM DV28EV D.AE
/dev/sg3 3 0 0 1 1 /dev/nst0 IBM ULTRIUM-TD2 333K
obtool chdev -a dukdaa01:/dev/sg3 Drive0
Thanks for the suggestion Rich. Since we'd never had a problem with our library or drives changing attach points with this install I assumed that because I was getting the "Unsupported device type" error in OSB that it was an OSB problem. Running sg_map -i -x showed that the OS wasn't even aware the devices were there anymore.
It turned out to be a hardware issue. A SCSI cable had gone bad after drive 1 causing the OS to not see drives 2 and 3. I replaced the cable and all is well.
This was not an OSB issue.
We have the same problem, but on Solaris, so the sg_map commant is not working.
Can somebody help us ?
Thank you and regards,