Loading Initial Ramdisk Fail......

[stevea]

"single" on the grub line probably doesn't work anymore - you need to add ....

"systemd.unit=rescue.target" or "1"
or else
"systemd.unit=emergency.target" to get right to the shell.

--

You need to debug systemd ....
http://fedoraproject.org/wiki/How_to...stemd_problems

[Carfax]

Originally Posted by secipolla

This won't help in this issue. But I'm new to Fedora and I think that it's adopting grub2 only now.
I can go into edit mode but the cursor appears misaligned to its actual place and I couldn't edit what I wanted. Another custom entry I added (for Puppy Linux frugal mode) just made the system reboot without grub giving any errors.
I'm using in-development F17 but I'm thinking that maybe your errors are GRUB's fault. So if you could by means of a live-CD install GRUB legacy maybe it would work.

I noticed that Fedora's grub2 uses some quite different configuration to Debian's, like it has a bunch of settings in its boot line. So while I used grub2 since almost when it came out, I haven't understood yet how Fedora configures it.

P.S. but the difference may come from the LVM setup that I never used before.

I use an LVM setup so i guess maybe those are the differences. However i think i'll still wait around a bit for any other advice someone might have before reinstalling GRUB legacy. Thanks a lot for the help though

[Carfax]

Originally Posted by stevea

"single" on the grub line probably doesn't work anymore - you need to add ....

"systemd.unit=rescue.target" or "1"
or else
"systemd.unit=emergency.target" to get right to the shell.

--

You need to debug systemd ....
http://fedoraproject.org/wiki/How_to...stemd_problems

I'm afraid neither single or systemd.unit work for me. Is there any possible way I can reinstall the Os without losing my files and settings, like in windows?

[Gareth Jones]

Originally Posted by Carfax

Is there any possible way I can reinstall the Os without losing my files and settings, like in windows?

Did you create a separate home partition when you first installed? It's a good idea to, and this in one of the benefits: you can tell the installation program to mount the existing home partition on /home without reformatting it. Then, as long as you keep the same user names, and create them in the same order, it should work fine.

If you haven't got a separate home partition though, it's more difficult.

[Carfax]

Unfortunately I didn't create a seperate partition.. I'm kinda doomed I guess. And btw I finally got acces to rescue, what would be the next advised step please?

[goodfella]

If you downloaded the ISO image for dvd:
boot from the dvd and try the repair option.

What I would do is boot from the dvd and get into recovery mode. You can probe
around see what does not look right. To my knowledge the 3.3 kernel was never
marked stable at kernel.org. But I have used it with out any problems.

[Carfax]

Originally Posted by goodfella

If you downloaded the ISO image for dvd:
boot from the dvd and try the repair option.

What I would do is boot from the dvd and get into recovery mode. You can probe
around see what does not look right. To my knowledge the 3.3 kernel was never
marked stable at kernel.org. But I have used it with out any problems.

I'd really really be grateful if you could let me know a few commands that might repair or sort out this issue

[goodfella]

boot the Fedora ISO dvd and try the repair mode.
If that fails then boot to a command prompt and type "startx".
If you get a failure message you might be able to look in some
log files to see what the problem is. Get ready for an education.

BTW, kernel 3.3.1 has been marked stable as of yesterday.

[pslusarczyk]

What command should I do i repair mode?
Cause i have simillar, few days ago my pc with F16 hang up, so i poweroff my pc. After that i can't boot in any kernel.
During starting service system freeze. I already tried using fsck and it show that everything is fine, and i also tried boot pc with options noacpi, nolapic etc. I can boot pc in rescue mode.
On my pc kernel is in v 3.3.0.4

[Carfax]

Originally Posted by pslusarczyk

What command should I do i repair mode?
Cause i have simillar, few days ago my pc with F16 hang up, so i poweroff my pc. After that i can't boot in any kernel.
During starting service system freeze. I already tried using fsck and it show that everything is fine, and i also tried boot pc with options noacpi, nolapic etc. I can boot pc in rescue mode.
On my pc kernel is in v 3.3.0.4

Same question I've been waiting for someone to answer all this while. I gave up anyway. Will just wait for the final Fc17 release and then reinstall

[stejfish]

Carfax, I had a similar problem with Fedora 16 not booting after the upgrade to the 3.3.0 kernel, though I was able to continue booting the system using the previous kernel (3.2.9). Not an expert on this, but it seems the problem was that the ramdisk (initramfs-*) file in /boot was not created for the 3.3.0 kernel when the update was performed using yum. to fix it, I ran the dracut command as root in /boot directory as follows:

dracut initramfs-3.3.0-4.fc16.x86_64.img 3.3.0-4.fc16.x86_64

not sure if it's necessary, but I ran the following after the dracut command:

grub2-mkconfig -o /boot/grub2/grub.cfg

after running these commands, the 3.3.0 kernel was able to boot.

Now you said that you were not able to boot the system using the previous kernels (by default, fedora keeps previous two kernels), so before running the above commands, obviously you have to figure out how to get your system running, perhaps you can use a LiveCD to boot the system.

IIRC, the update to the 3.3.1 kernel through yum worked without having to do the above.

hope that helps,
stejfish

[goodfella]

Eaiser way:

#su -
#/sbin/mkinitrd /boot/initrd-3.3.0-4.fc16.x86_64.img 3.3.0-4

[pslusarczyk]

The same error after using new ramdisk. I think it can't help cause after one hang up, from any of three kernel i can't boot so i is not releated with one kernel or ramdisk.

I also wait till relase F17 Beta