Messages in this thread |  | | Date | Thu, 1 Feb 2007 17:10:33 -0700 | From | "Eric D. Mudama" <> | Subject | Re: [PATCH 1/1] filesystem: Disk Errors at boot-time caused by probe of partitions |
| |
On 2/1/07, TJ <linux@tjworld.net> wrote: > ---- short extract --- > DC202XX: Primary channel reset. > ide2: reset: success > hde: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest > Error } > hde: task_in_intr: error=0x04 { DriveStatusError } > ide: failed opcode was: unknown > end_request: I/O error, dev hde, sector 238276076 > printk: 8 messages suppressed. > Buffer I/O error on device hde2, logical block 47279294 > hde: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest > Error } > hde: task_in_intr: error=0x04 { DriveStatusError } > ide: failed opcode was: unknown > hde: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest > Error } ... > The Model number is Maxtor 6Y060L0.
In the log you posted, the drive posted 51/04 to your out-of-bounds request, but these are 59/04, do they span the end of the device or something?
I'd be surprised if the drive clunked because of an out of range command, that model of drive used a very mature interface firmware with many generations of testing and qualification. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |