Jon LaBadie wrote:
Checking st.conf entries was going to be one suggestion.  Along with
what does "prtconf -v" report about the drive and what entry it chose
to use for the tape drive.

Now I see an entry for the tape:


st (driver not attached)
System software properties:
name <tape-config-list> length <60>
value 'EXABYTE IBM-8505' + 'Exabyte IBM-8505 8mm Helical Scan' + 'IBM-850
5'
name <IBM-8505> length <40>
value <0x0000000100000029000000000000ce390000000400000014000000150000008c
0000008c00000001>.


I guess that was probably empty before.

You 'should have been' able to avoid a reboot after by using devfsadm(1m).
That runs at boot time to check devices.  With arguments it can be made
to work on just a class of devices, like disk or tape or ...


Thanks, I'll keep that in mind for next time. Normally I hate rebooting to solve problems. At 2am though, its usually a lot faster :)


Thanks,

Andy




Reply via email to