Fedora Core2 boot problem due to unclean shut down
FedoraThis forum is for the discussion of the Fedora Project.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Fedora Core2 boot problem due to unclean shut down
Hi All,
I have fedora Core2, and recently I did an unclean shut down, and from then on, when I boot, fedora Core2, it asks me to do "System Integrity check", and after that, it freezes after "enabling swap space".
But the WIN XP boots fine and there's not another problem.
I have very very important data in Fedora and is there any way that I can recover my Fedora??
P4 2.4 GHz
512 MB DDR RAM
intel 865GBF mb
hda has Win 98 and win xp
hdb has FC2
The swap partition is hdb2, it's around 510MB.
I recently upgraded my RAM from 256MB to 512 MB. Fedora was working before the upgrade and it worked better after. I was worried that I should modify the swap partition to be twice the size of RAM.
Also, I modified my /etc/inittab file to choose a different run-level(just wanted to explore things), and rebooted, then it showed junk characters and command promt. All junk characters when I typed. Ctrl-d had no effect and neither did 'exit', So I decided to push the 'reset' button. And from then on, my fedora hangs after "enabling swap space".
Lesson No 1: Never tweak your system when you have important data in it.
The problem is not due to the unclean shut down, neither is it due to the swap partition.
When I edited the /etc/inittab file to choose different run-level, I made a spelling mistake at this line,
"id:5:initdefault:"
I actually booted in the rescue mode and did "chroot /mnt/sysimage" and then edited the /etc/inittab file to correct the mis-spelling and booted normally again The fedora was able to understand the run-level I have specified this time and it booted normally.
Perhaps you should explain your problem in detail before doing anything. It could be a different problem you know.
I have run into this problem and have yet to find a solution but I will offer up the hints that I have turned up so far.
This problem seems to have many potential causes:
1) hardware failure
- check your memory and cpu for errors using something like UBCD (the ultimate boot cd has lots of hardware checking tools on it)
2) bad blocks in swap partition
- boot the first disk of your Fedora installation media and go into rescue mode by typing "linux rescue" and then mount your current installation and chroot to it as instructed. You can try to fix the swap by typing the commands "swapoff -a" to turn the swap partition usage off and then "mkswap -c /dev/partition_where_your_swap_is" . Make sure you specify the right partition ... this could seriously hoop your other ones. Get partition info with fdisk -l /dev/hda
3) corrupted inittab
- fix problems in it using rescue mode like shashikanth mentions or you might be able to fix it my reinstalling the package responsible to putting it there in the first place. Find that out using "rpm -q --whatprovides /etc/inittab" I think
Unfortunately none of those things helped me. I have even upgraded from FC2 to FC3 and still have the same problem (although in FC2 it gave me an INIT: PANIC segmentation fault at .... error instead). I should look at inittab more closely and maybe remove the swap partition completely. Repetedly rebooting doesn't fix my problem either. Booting to a LiveCD works fine though.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.