On 15:28 Mon 03 Sep , Michael Yao wrote:
> Hi
>
> Looks like a disk I/O error to me.
> As I can remember, after kernel 2.6.16, raid1 read error will be auto-corrected.
>
> I think do a filesystem check might help.
>
> Michael
Nope. It is not fsck problem.
Unfortunately, I had been remiss in running fsck, so I did on all of the filesystems. They
are in great shape now!
However I still get the error below on shutdown -h now.
Any other ideas??
> > "
> > md stopping all md devices
> > Synchronizing SCSI cache from disk sdg:
> > ata8: command timeout
> > ata8: no sense translation for status:0x40
> > ata8: translated ATA status/error 0x40/00 to SCSI SK/ASC/ASCQ 0xb/00/00
> > ata8: Status =0x40{DriveReady}
> > ata8: command timeout
> > ata8: no sense translation for Status:0x40
> > ata8: translated ATA Status/error 0x40/00 to SCSI SK/ASC/ASCQ 0xb/00/00
> > ata8: Status =0x40{DriveReady}
> > ata8: no sense translation for Status:0x40
> > ata8: translated ATA Status/error 0x40/00 to SCSI SK/ASC/ASCQ 0xb/00/00
> > ata8: Status =0x40{DriveReady}
> > Failed
> > status=1, message=00, host=0, drive=08
> > <6>sd: Current: sense key: Aborted Command
> > Additional sense no additional sense information
> >
> >
> > Synchronizing SCSI cache from disk sdf:
> > ata6: command timeout
> > ata6: no sense translation for status:0x40
> > ata6: translated ATA status/error 0x40/00 to SCSI SK/ASC/ASCQ 0xb/00/00
> > ata6: Status =0x40{DriveReady}
> > ata6: command timeout
> > ata6: no sense translation for Status:0x40
> > ata6: translated ATA Status/error 0x40/00 to SCSI SK/ASC/ASCQ 0xb/00/00
> > ata6: Status =0x40{DriveReady}
> > ata6: no sense translation for Status:0x40
> > ata6: translated ATA Status/error 0x40/00 to SCSI SK/ASC/ASCQ 0xb/00/00
> > ata6: Status =0x40{DriveReady}
> > Failed
> > status=1, message=00, host=0, drive=08
> > <6>sd: Current: sense key: Aborted Command
> > Additional sense no additional sense information
Mitchell Laks
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
