SUMMARY: DDS-3 drive configuration on Sol10

From: Bill Bradford <mrbill_at_mrbill.net>
Date: Tue May 01 2007 - 12:20:33 EDT
On Tue, May 01, 2007 at 10:28:39AM -0500, Bill Bradford wrote:
> Finally, I dug up these settings from an old shipped-with-solaris st.conf
> file circa 2003 (with product IDs changed to match the drive output):
> "ARCHIVE IBM-STD224000N!", "Seagate DAT", "ARCH_04106";
> ARCH_04106 = 1, 0x2C, 0, 0x09639, 4, 0x00, 0x8C, 0x8C, 0x8C, 3;
> Same result:
> root@bradford:/> mt -f /dev/rmt/0n status
> /dev/rmt/0n: no tape loaded or drive offline

The problem was that I was trying to use the wrong tape device.  
I'd been told that the tape was written to the "0mb" device on the origin
system.  Turns out I needed to use the "0lb" device to extract the data.

root@bradford:/> ls -al /dev/nrst*
lrwxrwxrwx   1 root     root           8 Apr 30 15:58 /dev/nrst12 ->
rmt/0mbn
lrwxrwxrwx   1 root     root           8 Apr 30 15:58 /dev/nrst20 ->
rmt/0hbn
lrwxrwxrwx   1 root     root           8 Apr 30 15:58 /dev/nrst28 ->
rmt/0cbn
lrwxrwxrwx   1 root     root           8 Apr 30 15:58 /dev/nrst4 ->
rmt/0lbn

Tried to use the 0mb device:

root@bradford:/tape> mt -f /dev/nrst12 status
/dev/nrst12: no tape loaded or drive offline

Tried the 0hb device for the heck of it:

root@bradford:/tape> mt -f /dev/nrst20 status
/dev/nrst20: no tape loaded or drive offline

but the 0lb device worked:

root@bradford:/tape> mt -f /dev/nrst4 status
Seagate DAT tape drive:
   sense key(0x5)= Illegal Request   residual= 0   retries= 0
   file no= 0   block no= 0

root@bradford:/tape> tar xvf /dev/nrst4
<files coming off the tape>

Bill

-- 
Bill Bradford 
Houston, Texas
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
Received on Tue May 1 12:20:47 2007

This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:44:05 EST