On Tue, 8 Jan 2002, Matthew Dickinson wrote:
>
> more error messages are present: it's just a small selection...
>
> Dec 30 15:17:34 jaguar kernel: hda: write_intr error1: nr_sectors=1,
> stat=0x70
> Dec 30 15:17:34 jaguar kernel: hda: write_intr: status=0x70 { DriveReady
> DeviceFault SeekComplete }
> Dec 30 15:37:58 jaguar kernel: hda: write_intr error1: nr_sectors=188,
> stat=0x78
> Dec 31 17:00:40 jaguar kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
> Dec 31 17:00:40 jaguar kernel: hda: drive not ready for command
> Dec 31 17:00:40 jaguar kernel: hda: status error: status=0x58 { DriveReady
> SeekComplete DataRequest }
> Dec 31 17:00:40 jaguar kernel: hda: drive not ready for command
Hi Matt!
This is definitely a hardware error, not an ext3 problem. IBM DTLA Drive,
i presume? A e2fsck -c should at least mark the badblocks so that no new
data gets written on them, but in the long run i would suggest that you
replace the drive.
best regards,
michael
