topic Re: startup errors in Operating System - Linux

startup errors

'chris' — Mon, 26 Jul 2004 04:10:43 GMT

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 ?

Re: startup errors

Mobeen_1 — Mon, 26 Jul 2004 04:22:50 GMT

Chris,
Check to see if the following link helps you

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

regards
Mobeen

Re: startup errors

Steven E. Protter — Mon, 26 Jul 2004 10:12:59 GMT

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

Re: startup errors

'chris' — Mon, 26 Jul 2004 11:55:14 GMT

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

Re: startup errors

dirk dierickx — Tue, 27 Jul 2004 01:12:17 GMT

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)