Hello,

On 1/19/2006 10:42 PM, Lance Brown wrote:
Arno Lehmann wrote:
...
BUT I'd suggest that you do the following:
- Check the system log for any tape or SCSI related errors. Use tapeinfo
to see the tape drive's status.


Oh joy....  I missed this when I looked last time:

Here is a cut of the SCSI related kernel syslog messages starting with a
reboot of the server.  After it came up, I tried to follow your
directions below.  An attempt to 'mt -f /dev/nst1 eod' has hung up,
apparently forever.
...
 [ Attempted to 'mt -f /dev/nst1 eod' at this point]

Jan 19 15:41:21 what kernel: Attached scsi generic sg1 at scsi2, channel
0, id 0, lun 0,  type 8
Jan 19 15:41:21 what kernel: Attached scsi generic sg3 at scsi2, channel
0, id 2, lun 0,  type 8
Jan 19 15:41:22 what kernel: sym53c895-0-<2,*>: target did not report SYNC.
Jan 19 15:41:22 what kernel: sym53c895-0-<2,*>: target did not report SYNC.
Jan 19 15:41:32 what kernel: sym53c895-0-<3,*>: FAST-40 WIDE SCSI 80.0
MB/s (25.0 ns, offset 31)
Jan 19 15:42:12 what kernel: st1: Block limits 1 - 16777215 bytes.
Jan 19 15:44:05 what kernel: st1: Mode 0 options: buffer writes: 1,
async writes: 1, read ahead: 1
Jan 19 15:44:05 what kernel: st1:    can bsr: 0, two FMs: 0, fast mteom:
0, auto lock: 0,
Jan 19 15:44:05 what kernel: st1:    defs for wr: 0, no block limits: 0,
partitions: 0, s2 log: 0
Jan 19 15:44:05 what kernel: st1:    sysv: 0 nowait: 0
Jan 19 15:47:04 what kernel: scsi : aborting command due to timeout :
pid 4801, scsi2, channel 0, id 3, lun 0 Inquiry 00 00 00 38 00
Jan 19 15:47:04 what kernel: sym53c8xx_abort: pid=4801
serial_number=4802 serial_number_at_timeout=4802
Jan 19 15:47:34 what kernel: scsi : aborting command due to timeout :
pid 4831, scsi2, channel 0, id 3, lun 0 Inquiry 00 00 00 38 00
Jan 19 15:47:34 what kernel: sym53c8xx_abort: pid=4831
serial_number=4832 serial_number_at_timeout=4832
Jan 19 15:48:04 what kernel: scsi : aborting command due to timeout :
pid 4840, scsi2, channel 0, id 3, lun 0 Inquiry 00 00 00 38 00
Jan 19 15:48:04 what kernel: sym53c8xx_abort: pid=4840
serial_number=4841 serial_number_at_timeout=4841
Jan 19 15:48:34 what kernel: scsi : aborting command due to timeout :
pid 4850, scsi2, channel 0, id 3, lun 0 Inquiry 00 00 00 38 00
Jan 19 15:48:34 what kernel: sym53c8xx_abort: pid=4850
serial_number=4851 serial_number_at_timeout=4851
Jan 19 15:50:18 what kernel: sym53c895-0:3: message 6 sent on bad
reselection.

I expect the
Jan 19 15:41:22 what kernel: sym53c895-0-<2,*>: target did not report SYNC.
Jan 19 15:41:22 what kernel: sym53c895-0-<2,*>: target did not report SYNC.

entries and the aborts at the end are a Bad Thing(TM).

Definitely.

Tried a cold restart of all hardware and got the same errors trying to
go to EOD on this volume (Monthly-004)
...
I'm really starting to think I have a bad tape on my hands, since btape
with a different tape succeeds in all respects.

Good for you - replacing one tape is rather simple :-)

Arno

--[Lance]

--
IT-Service Lehmann                    [EMAIL PROTECTED]
Arno Lehmann                  http://www.its-lehmann.de


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to