FedoraThis forum is for the discussion of the Fedora Project.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Hi, I'm still fairly new to linux, but this is what is happening:
I was having problems connecting to our linux box over the lan, so I rebooted with the following command:
"shutdown -r 0"
Upon reboot, I get:
/dev/md1 contains a file system with errors, check forced.
Then it gets to about 35% and just stops, no more output.
I tried changing to runlevel 3 and booting and the system runs the same file check, but when it gets to 35%, I get a bunch of output that I can't make much sense of. It gives a message, "Continuing in 120 seconds." then stops at "start_kernel". So, next, I booted the the Fedora CD, went in to the Recovery Mode, and when I got to a prompt, I ran:
"fsck -c -v /dev/md1"
It took about a half hour (I was never prompted for anything), and when it finished, it appeared to try and boot. It then got stuck at the same "start_kernel" line. I also tried going into Grub and adding "idle=poll" to the kernel, but nogo.
If anyone could point me in the right direction I would be forever grateful!!
Also, I tried just now using "e2fsck -c -v /dev/md1" instead, and it gets to "Pass 1: checking inodes, blocks, and sizes", then wigs out, puts me back to the prompt. But the last message I have says: Segmentation fault. Does this mean there is something physically wrong with the drive itself?
Fixed it! I downloaded the Maxtor bootable image that I burned to a cd and booted from, then ran a full test on the hard drive overnight and it passed. I then booted to the Fedora disc, ran memtest86, and to my delight, the ram was failing. I swapped out the 2 sticks with some spares, ended up having to run fsck once more, but then everything was back to normal... Woo Hoo!