Sander wrote:
I've applied the patch against 2.6.16-git4. I'm sorry to say the
messages are still there:
That's okay. I have an alternate theory about those messages,
to be addressed in a later patch.
[ 1038.536894] kjournald starting. Commit interval 5 seconds
[ 1038.555040] EXT3 FS on md0, internal journal
[ 1038.555072] EXT3-fs: mounted filesystem with writeback data mode.
[ 1418.639290] ata11: status=0x50 { DriveReady SeekComplete }
[ 1418.639356] ata11: error=0x50 { UncorrectableError SectorIdNotFound }
[ 1418.639418] sdh: Current: sense key=0x0
[ 1418.639448] ASC=0x0 ASCQ=0x0
[ 1418.639481] Info fld=0x505050
[ 1684.727367] ata9: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
[ 1684.727420] ata9: status=0xd0 { Busy }
[ 2223.664107] ata6: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
[ 2223.664162] ata6: status=0xd0 { Busy }
[ 2381.589354] ata11: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
[ 2381.589416] ata11: status=0xd0 { Busy }
[ 2511.238690] ata9: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
[ 2511.238753] ata9: status=0xd0 { Busy }
[ 2990.792908] ata7: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
[ 2990.792960] ata7: status=0xd0 { Busy }
[ 4672.691569] ata8: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
[ 4672.691623] ata8: status=0xd0 { Busy }
[ 4988.884663] ata6: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
[ 4988.884717] ata6: status=0xd0 { Busy }
Could the ata11/sdh message be bogus? I re-create the raid5 and fs every
reboot.
Hard to tell. It would be far more helpful if those messages included
info as to what was going on at the time.
Cheers
-
: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
