View previous topic :: View next topic |
Author |
Message |
MasterX Veteran
Joined: 26 Jun 2003 Posts: 1165
|
Posted: Wed Jan 07, 2004 3:00 am Post subject: Is my system dying or is something with the kernel? |
|
|
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 |
|
Back to top |
|
|
ectospasm l33t
Joined: 19 Feb 2003 Posts: 711 Location: Mobile, AL, USA
|
Posted: Wed Jan 07, 2004 3:35 am Post subject: |
|
|
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! |
|
Back to top |
|
|
MasterX Veteran
Joined: 26 Jun 2003 Posts: 1165
|
Posted: Wed Jan 07, 2004 2:08 pm Post subject: |
|
|
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:
Code: |
hdparm -tT /dev/hda
/dev/hda:
Timing buffer-cache reads: 1896 MB in 2.00 seconds = 948.14 MB/sec
Timing buffered disk reads: 142 MB in 3.02 seconds = 46.95 MB/sec
hdparm /dev/hda
/dev/hda:
multcount = 16 (on)
IO_support = 0 (default 16-bit)
unmaskirq = 0 (off)
using_dma = 1 (on)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 256 (on)
geometry = 65535/16/63, sectors = 78165360, start = 0
|
Then I run the hdparm script, dmesg gave all the errors that I posted in my first post and hdparm -tT /dev/hda and hdparm /dev/hda gave the following output:
Code: |
hdparm /dev/hda
/dev/hda:
multcount = 16 (on)
IO_support = 1 (32-bit)
unmaskirq = 1 (on)
using_dma = 1 (on)
keepsettings = 1 (on)
readonly = 0 (off)
readahead = 256 (on)
geometry = 65535/16/63, sectors = 78165360, start = 0
hdparm -tT /dev/hda
/dev/hda:
Timing buffer-cache reads: 1920 MB in 2.00 seconds = 959.67 MB/sec
Timing buffered disk reads: 142 MB in 3.02 seconds = 47.01 MB/sec
|
It is relief to know that my system is not dying. The only thing that is left to do is to find out why when I run the hdparm script I get all these errors. |
|
Back to top |
|
|
webnoelle n00b
Joined: 06 Apr 2004 Posts: 50
|
Posted: Mon Jul 19, 2004 6:54 pm Post subject: |
|
|
did you ever solve this masterX? |
|
Back to top |
|
|
oumpah-pah Guru
Joined: 18 Jul 2004 Posts: 575 Location: Lausanne, Switzerland
|
Posted: Mon Jul 19, 2004 10:25 pm Post subject: |
|
|
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 ? |
|
Back to top |
|
|
webnoelle n00b
Joined: 06 Apr 2004 Posts: 50
|
Posted: Tue Jul 20, 2004 12:57 pm Post subject: |
|
|
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. |
|
Back to top |
|
|
mekong Tux's lil' helper
Joined: 23 Apr 2004 Posts: 93 Location: Rdam - NL - EU
|
Posted: Tue Jul 20, 2004 5:09 pm Post subject: |
|
|
I had this problem too once. It was a faulty IDE cable. I replaced it and it was fixed. |
|
Back to top |
|
|
webnoelle n00b
Joined: 06 Apr 2004 Posts: 50
|
Posted: Tue Jul 20, 2004 5:37 pm Post subject: |
|
|
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! |
|
Back to top |
|
|
|