LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   booting file system errors => cannot run fsck (http://www.linuxquestions.org/questions/slackware-14/booting-file-system-errors-%3D-cannot-run-fsck-218249/)

snake_eye 08-16-2004 09:48 AM

booting file system errors => cannot run fsck
 
Hi,

Last night my slackware was running fine, and i had just got my head around editing lilo.conf (just installed few days ago, newbie).

This morning, turned my comp on ready to install nic, everything seems fine as it passes the lilo bootup screen and then begins to load/check all the stuff at the console. Then it come up with:

Code:

Checking root filesystem:
fsck 1.35 (28-Feb-2004)
/dev/hda1 contains a file system with errors, check forced.
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=386, sector=272
end_request: I/O error, dev 03:01 (hda), sector 272

...continues on for other sectors..

:eek: after this finishes, it then concludes:

Code:

/dev/hda1: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY.
(i.e.,without -a or -p options)

followed by a message in a box:

"An error occurred during the root filesystem check. You will now be given a chance to log into the system in single-user mode to fix the problem.

If you are using the ext2 filesystem, running 'e2fsck -v -y <partition>' might help."

The file system I am using is ext2.

:eek:
I am then given the option to press control-d to proceed with normal startup, or give the root password for system maintenance. When I type my root password in, system reboots, with the following lines:

Code:

Entering System Maintenance Mode

-bash: id: command not found

-bash: fortune: command not found

Unmounting file systems.
umount: usbfs: not found
umount: /dev/hda8: not mounted
umount: /dev/hda7: not mounted
umount: /dev/hda6: not mounted
Rebooting system.

:eek:
-I have tried booting up with the BOOT DISK created during install, but the same thing occurs.
-I have also tried booting from the CD1 (SW 10.0) but when "Verifying DMI Pool Data.." system hangs with the disc just spinning in the drive.


What the hell can I do to get linux running again? And could someone explain why this has happened? Could it be something to do with the way i shut down the comp? I usually logout of KDE, the type EXIT to log out of user, then press power button off. :confused:


Someone please help me sort this out! :cry: :( :cry:


snake_eye

320mb 08-16-2004 09:58 AM

Re: booting file system errors => cannot run fsck
 
Quote:

Originally posted by snake_eye
Hi,

Last night my slackware was running fine, and i had just got my head around editing lilo.conf (just installed few days ago, newbie).

what exactly did you enter in your lilo.conf

it appears your not booting to the right / partition.

snake_eye 08-16-2004 10:06 AM

Quote:

what exactly did you enter in your lilo.conf
All i did was change the default time from 1600 to 30. Then rebooted and it semmed to have worked. So I then went on to change the console to a Vesa resolution to 640x480 (old monitor), restarted, and that seemed to work.

Next morning, the options i changed are still working so i don't think it is anything i did in the lilo.conf (i may be wrong, i don't know anything about linux :p ).


snake_eye

snake_eye 08-16-2004 11:38 AM

Hi,

I just want some opinions. Do you think if I wait a little longer (maybe till midnight) I will eventually get a reply telling me the solution to my problem? I don't know if there are any elite linux users out there that are just at work and cannot reply to this, and so have to wait till they get off work, or if this is a problem people cannot deal with, and it is one of those computer mysteries that can never be solved, in which case leaving me to do a clean install.

Sorry if I sound a little angry, but I've tried everything I could, and if there is actually no cure, then i don't want to be wasting my time, and would rather carry on with learning how to use linux.

I've said it before and i'll say it again,

somtimes I hate computers...


snake_eye

snake_eye 08-16-2004 03:04 PM

OK, I've just tried re-installing slackware without writing out a new partition table, as in just using the table that i used for my previous install and pressing 'w' to write and exit. Now as soon as i try and format the root partition and I'm getting the same errors as before:



Code:

hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=386, sector=272
end_request: I/O error, dev 03:01 (hda), sector 272

except this time it seems to do this every 2 sectors up to sector 322, pauses for a while, and then backt to the partition format screen.


Does this have anything to do with me not writing out the partition table from scratch?
Or is my HDD totally f00ked up? How can I test this?

thanks


snake_eye


EDIT: Could it be something to do with the HDD mode set to LBA? I'm only assuming this from the code above having LBAsect=386, so it's a total guess, sorry for sounding stupid!

Goudaman 08-16-2004 04:49 PM

from the error message it appears your harddrive is foobared. Dont worry, nothing you or linux did caused it to happen -- it just was bad luck. to make sure you could try it in another computer or try installing another os. the "SeekComplete Error" often indicates mechanical failure

snake_eye 08-16-2004 05:17 PM

Dammit!! Oh well no problem. Just have to get a cheap one off eBay. I can't believe this tho, right after them errors I found out my CDROMs just stopped working. :P

I think my computers slowly melting away...

thanks


snake_eye

smgentry 08-26-2004 02:18 PM

Quote:

What the hell can I do to get linux running again? And could someone explain why this has happened? Could it be something to do with the way i shut down the comp? I usually logout of KDE, the type EXIT to log out of user, then press power button off.
Sounds to me like you are not shutting down the system before hitting the power button. Like typing "shutdown -h now" and waiting to turn off the power with the button if you need to. With ext2 you can corrupt partitions that way. ext3 is a bit more forgiving.


All times are GMT -5. The time now is 10:56 PM.