LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Fedora - Installation (http://www.linuxquestions.org/questions/fedora-installation-39/)
-   -   Boot process dies during forced file system check (http://www.linuxquestions.org/questions/fedora-installation-39/boot-process-dies-during-forced-file-system-check-433477/)

mepaco 04-09-2006 06:40 PM

Boot process dies during forced file system check
 
I have been running Fedora Core 5 for about the last week and everything was fine. Today, I start it up and it gives me all these errors about how files are read only and froze during boot. I had to force it to shut down and now it gets about halfway through the file system check and then asks me for root password and throws me to a Repair Filesytem command prompt.

After reading aroung on the forums I tried some of the things suggested but I get:

fsck -t ext3 /dev/hda2
or
e2fsck -fp /dev/hda2

Bad magin number in super-block ...

The superblock could not be read or does not describe a correct ext2 filesystem ...


Is there anything I can do? I'm kind of a noob but I'm trying. Really, I don't care if I can't get it up and running again but there are a few files I really want off of it. How can I get it to mount a usb flash drive or can I get my Ubuntu live CD to recognize the HD?

Any help would be appreciated

Thanks,
Paco

unSpawn 04-11-2006 07:42 AM

start it up and it gives me all these errors about how files are read only and froze during boot.
When a filesystem contains errors (say "dirty" flag still set due to improper umounting) and when those are not repaired (man fsck) and Linux is set to do so (man tune2fs) it will protect them by not mounting it read-write.


I had to force it to shut down
Forced shutdowns are never good. If you can, and if "three finger salutes" (sysrq) are enabled (echo 1 > /proc/sys/kernel/sysrq), then you could use the key combo's: alt+printscreen+s (sync), alt+printscreen+u (umount), alt+printscreen+b (boot), (or alternatively "echo s > /proc/sysrq-trigger") to do a more "controlled" reboot.


Bad magin number in super-block
Being verbose and exact when posting error messages (it's magic) always helps.


Is there anything I can do?
If the system isn't that badly damaged, try booting it into runlevel 1 (search LQ for how to do that with your bootloader) and find the other superblocks for the device with mkfs.ext3 -n devicename (so: mkfs.ext3 -n /dev/hda1). Now supply one of the superblocks to fsck with the "-b" option until you find a usable one. If the system is badly damaged you may want to check booting your distribution's rescue disk instead, or use KNOPPIX. When this all is completed determine if you need a(n automated) backup mechanism to restore crucial data just in case.


All times are GMT -5. The time now is 05:32 PM.