|
Re: amtapetype problems
2006-09-08 15:03:54
On Fri, 8 Sep 2006 at 1:31pm, Nick Jones wrote
[root@localhost ~]# mt -f /dev/nst0 status
SCSI 2 tape drive:
File number=-1, block number=-1, partition=0.
Tape block size 0 bytes. Density code 0x0 (default).
Soft error count since last status=0
General status bits on (50000):
DR_OPEN IM_REP_EN
[root@localhost ~]# mt -f /dev/nst0 offline
/dev/nst0: Input/output error
[root@localhost ~]# mt -f /dev/nst0 load
/dev/nst0: Input/output error
[root@localhost ~]# mt -f /dev/st0 status
SCSI 2 tape drive:
File number=-1, block number=-1, partition=0.
Tape block size 0 bytes. Density code 0x0 (default).
Soft error count since last status=0
General status bits on (50000):
DR_OPEN IM_REP_EN
[root@localhost ~]# mt -f /dev/st0 load
/dev/st0: Input/output error
Here's what the log says
Sep 8 13:30:50 localhost kernel: st0: Error with sense data: <6>st0:
Current: sense key: Not Ready
Sep 8 13:30:50 localhost kernel: Additional sense: Medium not present
Any ideas?
Err, there's no tape in the drive?
Read through 'man mtx' and 'man mt', and understand them. In brief, you
use 'mtx' to manipulate the loaders robotics -- e.g. telling it to move
the tape in slot 10 into drive 1. You use 'mt' to talk to the tape drive,
e.g. to get the status. 'mtx' talks to the generic SCSI device associated
with the loader, while 'mt' talks to the SCSI tape device associated with,
well, the tape device.
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
|
|
|
