Re: Repeated problem: scsi: Device offlined - not ready after error recovery

[Stefan R. <st...@s5...>]

Joshua Daniel Franklin wrote:
> It seemed to work better forcing S100. It was writing to a 3ware RAID5 array.
> 
> Nov 13 20:03:14 vastus kernel: kjournald starting.  Commit interval 5 seconds
> Nov 13 20:03:14 vastus kernel: EXT3-fs: mounted filesystem with ordered data mode.
> Nov 13 20:07:24 vastus kernel: ieee1394: sbp2: aborting sbp2 command
> Nov 13 20:07:24 vastus kernel: sd 9:0:0:0:
> Nov 13 20:07:24 vastus kernel:         command: Read(10): 28 00 00 30 71 67 00 00 60 00
> Nov 13 20:07:26 vastus kernel: ieee1394: Error parsing configrom for node 0-00:1023
> Nov 13 20:07:27 vastus kernel: ieee1394: Error parsing configrom for node 0-01:1023
> Nov 13 20:07:27 vastus kernel: ieee1394: sbp2: reset requested
> Nov 13 20:07:27 vastus kernel: sd 9:0:0:0: scsi: Device offlined - not ready after error recovery

The "Error parsing configrom" during the SBP-2 error condition is a hint
on an electrically far too noisy bus.  Ditto the fact that S100 reduces
the frequency of errors.
-- 
Stefan Richter
-=====-=-=== =-== =-==-
http://arcgraph.de/sr/