Is my system dying or is something with the kernel?

[MasterX]

When I boot the system, we see the message checking all filesystems and if we have boot the system several times then it is likely that we have reached the maximum number of times that a filesystem can be mounted without being checked. When this happens fsck runs to check the filesystem and although it finishes without any errors/warnings the boot process stops and I get the message where it says that I should give the root's password to check the filesystem or to press ctrl+d to continue.

Am I doomed? Is there something wrong with the system? or something is wrong with the kernel?
I have this problem several months now, but I do not really remember when, I think it happened after I updated a program. When I installed Gentoo I did not have this problem.

Also, sometimes when I reboot the system, the system can not find the scripts and it gives me a warning for each script that was supposed to be loaded. I logged in, and I went to /etc/init.d folder and all the scripts were 0 bytes. If I press ctrl+alt+del to reboot the system it will behave like nothing has happened.

What is going on here? Any idea?

I have 2.6.0-bk3 kernel and hdparm is enabled during boot. Also dmesg prints the following message
blk: queue dfd53800, I/O limit 4095Mb (mask 0xffffffff)
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }
blk: queue dfd53400, I/O limit 4095Mb (mask 0xffffffff)
hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hdb: drive_cmd: error=0x04 { DriveStatusError }
hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hdc: drive_cmd: error=0x04Aborted Command
hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hdc: drive_cmd: error=0x04Aborted Command
hdd: Speed warnings UDMA 3/4/5 is not functional.
hdd: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hdd: drive_cmd: error=0x04Aborted Command

hdc and hdd are the dvd player and the cdwriter


Thank you

[ectospasm]

This is only a guess, but it looks like your IDE controller for your motherboard is dying. I find it hard to believe that all of those devices (hda, hdb, etc.) would fail at the same time, but stranger things have happened. Unfortunately you probably need another barebones system just to make sure all of those devices are working properly.
_________________
Join the adopt an unanswered post initiative today
Join the EFF!
Join the Drug Policy Alliance!

[MasterX]

The erros that i am getting when I run dmesg, are because of hdparm.
I boot the system without running the hdparm script and dmesg did not show any error related to hd*.
The commands hdparm -tT /dev/hda and hdparm /dev/hda gave the following output:

[webnoelle]

did you ever solve this masterX?

[oumpah-pah]

I had this problem once, and it turned out to be jfs fault. The program that checks jfs filesystem has got return values that differ from the other filesystems utilities. So the script just thinks that something went wrong, but in fact everything was just fine. So the question is : do you use jfs ?

[webnoelle]

I have a similar problem but I am using ext3. I believe it is my hard drive though because I tried to run e2fsck or whatever it is, with the 'badblocks' flag so it will flag badblocks and not use them, and it keeps hanging on certain blocks. I let it run for over an hour and no results.

I already ordered a new hard drive (I was just looking for an excuse to replace it anyway ) So hopefully that will fix my problem.

[mekong]

I had this problem too once. It was a faulty IDE cable. I replaced it and it was fixed.

[webnoelle]

That's interesting, I was actually planning on replacing that cable as well Thanks for the info though, it makes me not feel dumb for trying it!