cancel
Showing results for 
Search instead for 
Did you mean: 

startup errors

SOLVED
Go to solution
'chris'
Super Advisor

startup errors

hi

I have SUSE 9.1 prof. and get each each time at startup following errors:

hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }
hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hdb: drive_cmd: error=0x04 { DriveStatusError }
Non-volatile memory driver v1.2
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0

knows someone why ?
4 REPLIES
Mobeen_1
Esteemed Contributor

Re: startup errors

Chris,
Check to see if the following link helps you

http://lists.suse.com/archive/suse-linux-e/2004-Feb/0006.html

regards
Mobeen
Steven E. Protter
Exalted Contributor
Solution

Re: startup errors

What you do not state is whether or not the drive actually works.

It would seem that your diskette drive is quite dead. I'd check power and cable connectons on that. There appears to be something wrong with the hard disks as well.

Might want to check bios configuration and run disk check utilities on them.

Does the system boot?

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
'chris'
Super Advisor

Re: startup errors

hi steven

diskette drive and linux system works well

I have Maxtor DiamondMax Plus 9 80GB ATA/133 harddiscs

at other linux server with SUSE 8.2 (other hardware, but the same harddisc) I have this error as well:

hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }
hda: cache flushing failed. disable write back cacheing for journalled file systems
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }
hda: cache flushing failed. disable write back cacheing for journalled file systems

greetings
chris
dirk dierickx
Honored Contributor

Re: startup errors

this is a known issue with (new) maxtor drives. their implementation of the cache does not follow the standard correctly.
the problem has been resolved with newer kernels, so if you can and know how to roll your own you can give that a try. although these errors are _non_ critical, meaning that they cause no harm and no data will be lost (beware, because sometimes a timeout can occur which could slow down the system for several seconds at random)