DriveReady SeekComplete Error...hd broken?
Hello everybody, when booting my Suse 9.0 I get the following messages in the bootlog, that I do not knwo what to do with. The hd is just about half a year old. Cheers, Sven <4>reiserfs: found format "3.6" with standard journal <4>reiserfs: enabling write barrier flush mode <4>reiserfs: using ordered data mode <4>reiserfs: checking transaction log (device ide0(3,2)) ... <4>for (ide0(3,2)) <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>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>Using r5 hash to sort names <4>VFS: Mounted root (reiserfs filesystem) readonly. <5>Trying to move old root to /initrd ... failed <5>Unmounting old root <5>Trying to free ramdisk memory ... okay <6>Freeing unused kernel memory: 176k freed <6>md: Autodetecting RAID arrays. <6>md: autorun ... <6>md: ... autorun DONE. <4>reiserfs: enabling write barrier flush mode <6>lvm-mp: allocating 42 lowmem entries at c233a000 <6>LVM version 1.0.5+(mp-v6c)(22/07/2002) module loaded <4>reiserfs: enabling write barrier flush mode <6>Adding Swap: 1036184k swap-space (priority 42) <4>reiserfs: enabling write barrier flush mode <4>reiserfs: enabling write barrier flush mode <4>reiserfs: found format "3.6" with standard journal <4>reiserfs: enabling write barrier flush mode <4>reiserfs: using ordered data mode <4>reiserfs: checking transaction log (device ide0(3,4)) ... <4>for (ide0(3,4)) <4>Using r5 hash to sort names <4>reiserfs: found format "3.6" with standard journal <4>reiserfs: enabling write barrier flush mode <4>reiserfs: using ordered data mode <4>reiserfs: checking transaction log (device ide0(3,5)) ... <4>for (ide0(3,5)) <4>Using r5 hash to sort names <4>reiserfs: found format "3.6" with standard journal <4>reiserfs: enabling write barrier flush mode <4>reiserfs: using ordered data mode <4>reiserfs: checking transaction log (device ide0(3,67)) ...
On Saturday 31 January 2004 01:32, Sven Burmeister wrote:
Hello everybody,
when booting my Suse 9.0 I get the following messages in the bootlog, that I do not knwo what to do with. The hd is just about half a year old.
Cheers,
Sven
<4>reiserfs: found format "3.6" with standard journal <4>reiserfs: enabling write barrier flush mode <4>reiserfs: using ordered data mode <4>reiserfs: checking transaction log (device ide0(3,2)) ... <4>for (ide0(3,2)) <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>hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error } <4>hda: drive_cmd: error=0x04 { DriveStatusError } 3,67)) ...
Some stuff here: http://lists.terrasoftsolutions.com/yellowdog-general/November01/0325.html -- _____________________________________ John Andersen
On Sat, Jan 31, 2004 at 11:32:36AM +0100, Sven Burmeister wrote:
when booting my Suse 9.0 I get the following messages in the bootlog, that I do not knwo what to do with. The hd is just about half a year old.
What brand is your HD?
<4>reiserfs: found format "3.6" with standard journal <4>reiserfs: enabling write barrier flush mode <4>reiserfs: using ordered data mode <4>reiserfs: checking transaction log (device ide0(3,2)) ... <4>for (ide0(3,2)) <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>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
Please note, that the error happens just once on system boot. It never happens after, on a running system. I got the same errors on Maxtor 6Y080L0 with firmware YAR41BW0. SMART does not show any degradation of the drive. I don't see these errors on MAXTOR 6L080L4 (firmware A93.0500) and FUJITSU MPG3409AT. What's interesting, both Fujitsu and Maxtor 6L080L4 are ATA/ATAPI-5 drives, while Maxtor 6Y080L0 is ATA/ATAPI-7. I suspect this error is caused by the difference in ATAPI standards and the way reiserfs accesses the drive. So in my understanding, reserfs attmpts to use some feature on the disk, fails on it, and disables it. Regards, -Kastus
Kastus schrieb:
On Sat, Jan 31, 2004 at 11:32:36AM +0100, Sven Burmeister wrote:
I got the same errors on Maxtor 6Y080L0 with firmware YAR41BW0. SMART does not show any degradation of the drive.
Him I got a Maxtor 6Y080P0 with exactly the same firmware, smart does not show anything either. And my other maxtor does not complain, so i guess we are having the same issue here.
I don't see these errors on MAXTOR 6L080L4 (firmware A93.0500) and FUJITSU MPG3409AT.
What's interesting, both Fujitsu and Maxtor 6L080L4 are ATA/ATAPI-5 drives, while Maxtor 6Y080L0 is ATA/ATAPI-7.
I suspect this error is caused by the difference in ATAPI standards and the way reiserfs accesses the drive. So in my understanding, reserfs attmpts to use some feature on the disk, fails on it, and disables it.
Ok, so this does not mean it is going to die soon. That's all I want to hear. Do you know if I only have to worry if smart tells me to, or if it can happen that smart tells me everything is ok when it is not? Thanks for the reply! Sven
The Monday 2004-02-02 at 01:53 +0100, Sven Burmeister wrote:
Ok, so this does not mean it is going to die soon. That's all I want to hear. Do you know if I only have to worry if smart tells me to, or if it can happen that smart tells me everything is ok when it is not?
Unfortunately, smart can not catch everything. There are "sudden deaths" that can not be forecasted. Backup always! :-) -- Cheers, Carlos Robinson
have not watched this thread, so someone might have said this, but here it goes: check the early stages of your boot log, around the discovery of the ide system on the mobo. do you see any notes about not 100% compatibility? If yes, it's the chipset on your mobo. it will work, without dma and who knows what else. i had that problem, used the board for almost a year, eventually changed it. i should have done it earlier. Dimitris On Monday 02 February 2004 13:28, Carlos E. R. wrote:
The Monday 2004-02-02 at 01:53 +0100, Sven Burmeister wrote:
Ok, so this does not mean it is going to die soon. That's all I want to hear. Do you know if I only have to worry if smart tells me to, or if it can happen that smart tells me everything is ok when it is not?
Unfortunately, smart can not catch everything. There are "sudden deaths" that can not be forecasted.
Backup always! :-)
-- Cheers, Carlos Robinson
participants (5)
-
Carlos E. R. -
John Andersen -
Kastus -
plain -
Sven Burmeister