On Tuesday, 11.05.2004 at 11:24 +0200, Stefan G. Weichinger wrote: > >>> [...] kernel: ASC=15 ASCQ= 2 > >>> [...] kernel: Raw sense data:0xf0 0x00 0x03 0x00 0x00 0x00 0x01 0x16 0x00 0x00 > >>> +0x4f 0xc8 0x15 0x02 0x00 0x00 0x00 0x00 0x82 0x01 0x55 0x00 > >>> 0x00 0x25 0x3b 0x00 0x96 0x32 0x50 0x00 > >>> [...] kernel: st0: Error on write filemark. > > DE> What looks like the problem here? The drive itself? The SCSI > DE> controller? We have a HP DLT-40 drive on an Adaptec 29160 controller. > DE> There have been no configuration changes to the server. > > Sounds like a SCSI-problem to me. > > Try to communicate with the drive outside of AMANDA. > > What does > > mt -f /dev/st0 status
blackhole: ~ # mt -f /dev/st0 status drive type = Generic SCSI-2 tape drive status = 1073741824 sense key error = 0 residue count = 0 file number = 0 block number = 0 Tape block size 0 bytes. Density code 0x40 (unknown). Soft error count since last status=0 General status bits on (41010000): BOT ONLINE IM_REP_EN Anything odd there? > tell you? (You did not mention the OS, but the message points to > Linux). Yeah, sorry - it's running a vanilla Debian Woody installation. > Check cabling, sometimes it is enough to just reconnect everything > (after shutdown ;-) ). > > I am not sure if this could also happen with a bad tape ... as it > tells you the device is failing to write a filemark. > > Maybe try another tape, but as you said that this happens since 2 days > (and 2 tapes, I assume, or is it still the same?) the scsi-system > seems to be responsible. Appears to have affected two tapes now ... so I'm guessing it's not the tapes. Will try playing with the connectors and perhaps reseat the controller card, that sort of thing. This system can afford downtime, since it doesn't do anything other than run the backups overnight ... Thanks for the suggestions ... Dave. -- Dave Ewart [EMAIL PROTECTED] Computing Manager, Epidemiology Unit, Oxford Cancer Research UK PGP: CC70 1883 BD92 E665 B840 118B 6E94 2CFD 694D E370
