There's nothing in your `mt status` that says what tape drive it's talking to. My guess is that your SCSI devices got renumbered somehow. I think the nst* devices are issued in the order they're found, and if the device that was nst0 is gone, nst1 is now nst0.
Try `mt -f /dev/nst0 status` and `mt -f /dev/nst1 status` and see which one looks like your tape drive. > -----Original Message----- > From: Paul Miller [mailto:paul@;fxtech.com] > Sent: Tuesday, November 12, 2002 11:03 AM > To: [EMAIL PROTECTED] > Subject: ERROR: /devb/nst1: no tape online > > > Can anyone tell me what this means? > > I recently moved a linux system from a tower case to a rack case. > Everything was wired up the way it was, and everything is > working, except > amanda. For some reason, it doesn't think there are tapes in > the drive (a > DLT4000). > > I'm getting this error: > > bash-2.04$ /usr/sbin/amcheck Daily > Amanda Tape Server Host Check > ----------------------------- > Holding disk /amanda: 1714756 KB disk space available, using 666180 KB > ERROR: /dev/nst1: no tape online > (expecting tape Daily05 or a new tape) > NOTE: skipping tape-writable test > Server check took 0.002 seconds > > mt seems to work: > > bash-2.04$ mt status > SCSI 2 tape drive: > File number=0, block number=0, partition=0. > Tape block size 0 bytes. Density code 0x1a (unknown to this mt). > Soft error count since last status=0 > General status bits on (41010000): > BOT ONLINE IM_REP_EN > > > Could this be a messed up compression setting? I could really > use some advice! >
