Maxtor / status=0x51 { DriveReady SeekComplete Error }
I get a "status=0x51 / error=0x04" error during bootup. (see part of dmesg below) I found a lot of topics on the web, but I still don't know what's up. However, I don't think it's related to hardware damage. A lot of people posting this issue seem to have Maxtor (Diamond Plus 9??) However, I don't know if this is significant. - I get the error only for my Maxtor 6Y080P0. - I don't get this error for my IBM TLA-307030 - I get this error for journaled ReiserFS and journaled XFS - I get this error as master, slave, or single drive. - I use udma5-mode (ATA100) - I get that error on an ASUS P4PE (Intel 82801) and P4P800 (Intel ICH5) - I saw the same error on another Maxtor 80G at work (AFAIR a 6Y080 and 82801, don't remember the MoBo) - the IBM tells (hdparm) : rive conforms to: ATA/ATAPI-5 T13 1321D revision 1: - the Maxtor tells: Drive conforms to: (null): - SMART is enabled for both drives in the BIOS. I run SuSE 9.0, kernel 2.4.21 ---- MY QUESTIONS: ? Can someone expain what this error really means? ? Does this affect data integrity, i.e. is there a change of data corruption under certain cirsumstances due to faulty cache flushing, etc. ? ? Does anybody observe this error with a NEW drive but NO Maxtor 6YxxxP0? ? Is this a (known) specific Maxtor problem? ? Is this a (known) specific driver problem? ? Is this a (known) specific chip-set problem? ? How can I avoid this error? (I won't switch off DMA or journal) ? What means "PIIX-4: not 100% native mode: will probe irqs later" (dmesg)? ? Should I ignore the error OR should I be worried and replace the disk? ------------------------------------------------------------- /begin dmesg ... PCI: Probing PCI hardware (bus 00) PCI: Ignoring BAR0-3 of IDE controller 00:1f.1 Transparent bridge - Intel Corp. 82801BA/CA/DB/EB PCI Bridge ... PIIX-4: IDE controller at PCI slot 00:1f.1 PIIX-4: chipset revision 2 PIIX-4: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:pio ... hda: IBM-DTLA-307030, ATA DISK drive hdb: Maxtor 6Y080P0, ATA DISK drive blk: queue c03bc8e0, I/O limit 4095Mb (mask 0xffffffff) blk: queue c03bca3c, I/O limit 4095Mb (mask 0xffffffff) hdc: SAMSUNG CDRW/DVD SM-348B, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 ... hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error } hdb: drive_cmd: error=0x04 { DriveStatusError } hdb: cache flushing failed. disable write back cacheing for journalled file systems hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error } hdb: drive_cmd: error=0x04 { DriveStatusError } hdb: cache flushing failed. disable write back cacheing for journalled file systems /end dmesg ===============================================================
Haiml, Markus wrote:
I get a "status=0x51 / error=0x04" error during bootup. (see part of dmesg below)
I have two maxtor drives, SuSE 9.0, and I get the same error messages, though my system works fine. However, there's a line suggesting to disable write back cahing, which I haven't tried yet: it might solve the problem. <4>hda: Maxtor 6Y080L0, ATA DISK drive <4>hdb: Maxtor 6Y060L0, ATA DISK drive <4>hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error } <4>hda: drive_cmd: error=0x04 { DriveStatusError } <4>hda: cache flushing failed. disable write back cacheing for journalled file systems <4>hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error } <4>hdb: drive_cmd: error=0x04 { DriveStatusError } <4>hdb: cache flushing failed. disable write back cacheing for journalled file systems FXF -- ______________________ Courtesy of SuSE Linux http://www.nibz.org
You only need to disable the writeback cache on your motherboard (in the <DEL> whe the system starts up). It's there as windows uses it to make you think it runs faster as far as i can see. It's not really a linux problem just an oversmart motherboard as many are nowadays. regards scsijon At 09:54 PM 24/02/2004, Haiml, Markus wrote:
I get a "status=0x51 / error=0x04" error during bootup. (see part of dmesg below)
I found a lot of topics on the web, but I still don't know what's up. However, I don't think it's related to hardware damage. A lot of people posting this issue seem to have Maxtor (Diamond Plus 9??) However, I don't know if this is significant.
- I get the error only for my Maxtor 6Y080P0. - I don't get this error for my IBM TLA-307030 - I get this error for journaled ReiserFS and journaled XFS - I get this error as master, slave, or single drive. - I use udma5-mode (ATA100) - I get that error on an ASUS P4PE (Intel 82801) and P4P800 (Intel ICH5) - I saw the same error on another Maxtor 80G at work (AFAIR a 6Y080 and 82801, don't remember the MoBo) - the IBM tells (hdparm) : rive conforms to: ATA/ATAPI-5 T13 1321D revision 1: - the Maxtor tells: Drive conforms to: (null): - SMART is enabled for both drives in the BIOS.
I run SuSE 9.0, kernel 2.4.21
----
MY QUESTIONS: ? Can someone expain what this error really means? ? Does this affect data integrity, i.e. is there a change of data corruption under certain cirsumstances due to faulty cache flushing, etc. ? ? Does anybody observe this error with a NEW drive but NO Maxtor 6YxxxP0? ? Is this a (known) specific Maxtor problem? ? Is this a (known) specific driver problem? ? Is this a (known) specific chip-set problem? ? How can I avoid this error? (I won't switch off DMA or journal) ? What means "PIIX-4: not 100% native mode: will probe irqs later" (dmesg)? ? Should I ignore the error OR should I be worried and replace the disk? ------------------------------------------------------------- /begin dmesg ... PCI: Probing PCI hardware (bus 00) PCI: Ignoring BAR0-3 of IDE controller 00:1f.1 Transparent bridge - Intel Corp. 82801BA/CA/DB/EB PCI Bridge ... PIIX-4: IDE controller at PCI slot 00:1f.1 PIIX-4: chipset revision 2 PIIX-4: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:pio ... hda: IBM-DTLA-307030, ATA DISK drive hdb: Maxtor 6Y080P0, ATA DISK drive blk: queue c03bc8e0, I/O limit 4095Mb (mask 0xffffffff) blk: queue c03bca3c, I/O limit 4095Mb (mask 0xffffffff) hdc: SAMSUNG CDRW/DVD SM-348B, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 ... hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error } hdb: drive_cmd: error=0x04 { DriveStatusError } hdb: cache flushing failed. disable write back cacheing for journalled file systems hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error } hdb: drive_cmd: error=0x04 { DriveStatusError } hdb: cache flushing failed. disable write back cacheing for journalled file systems /end dmesg ===============================================================
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Wed, Feb 25, 2004 at 09:20:02AM +1100, scsijon wrote:
You only need to disable the writeback cache on your motherboard (in the <DEL> whe the system starts up). It's there as windows uses it to make you think it runs faster as far as i can see.
This is too misleading. Writeback cache on the disk drive has nothing to do with cache on the motherboard. The error is caused by a missing feature in Maxtor drives. I interpret it as an informative message that kernel will not use writeback cache on the disk drive. Please see my other post on this topic: http://lists.suse.com/archive/suse-linux-e/2004-Feb/0017.html
It's not really a linux problem just an oversmart motherboard as many are nowadays.
Again, motherboard has nothing to do with it, it's a Maxtor disk drive missing feature. Regards, -Kastus
You may be right but: I wish this was so, i've found that some of the new motherboards with firmware and sata on board with revisions after dec 2003 are "too smart for their britches" and are controlling all devices via ata and sata. scsijon At 02:45 PM 24/02/2004, Kastus wrote:
On Wed, Feb 25, 2004 at 09:20:02AM +1100, scsijon wrote:
You only need to disable the writeback cache on your motherboard (in the <DEL> whe the system starts up). It's there as windows uses it to make you think it runs faster as far as i can see.
This is too misleading. Writeback cache on the disk drive has nothing to do with cache on the motherboard.
The error is caused by a missing feature in Maxtor drives. I interpret it as an informative message that kernel will not use writeback cache on the disk drive.
Please see my other post on this topic: http://lists.suse.com/archive/suse-linux-e/2004-Feb/0017.html
It's not really a linux problem just an oversmart motherboard as many are nowadays.
Again, motherboard has nothing to do with it, it's a Maxtor disk drive missing feature.
Regards, -Kastus
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Hi scsijon,
I wish this was so, i've found that some of the new motherboards with firmware and sata on board with revisions after dec 2003 are "too smart for their britches" and are controlling all devices via ata and sata.
- The latest P4PE bios is from nov. 26, 2003 (before dec. 2003) - I get the same messages from a Maxtor 6Y080L0 on an older MoBo (GA-8SIMLH with SiS 651 chipset) -> It seems that my 'writeback' messages are not related to the MoBo settings. - What's wrong about a controller that controls an ATA100 drive via ata?
You only need to disable the writeback cache on your motherboard (in the <DEL> whe the system starts up). It's there as windows uses it to make you think it runs faster as far as i can see.
If this is the case, can you please tell me how to 'deactivate writeback' in the BIOS? I don't find a feature like that on the Asus-P4PE-BIOS. What would be the name of the BIOS-entry to deactivate? many thanks Markus
Kastus, thanks for your help.
Writeback cache on the disk drive has nothing to do with cache on the motherboard.
The error is caused by a missing feature in Maxtor drives. I interpret it as an informative message that kernel will not use writeback cache on the disk drive.
Do I understand you correctly? http://lists.suse.com/archive/suse-linux-e/2004-Feb/0017.html The 8 MB cache on the Maxtor will be used and managed by the Maxtor's firmware, _however_ the linux kernel cannot flush the cache. It's up to the disk drive when to flush its cache. ? Is this correct ? If the above is correct so far: Could there be a problem (i.e. at shutdown) when the kernel cannot flush the cache and the drive will not flush the cache yet. If I completely misunderstand 'write back cacheing', can you explain in two sentences what 'write back cacheing' does? many thanks Markus
participants (5)
-
FX Fraipont -
Haiml, Markus -
Kastus -
Markus Haiml
-
scsijon