Fedora Linux Support Community & Resources Center
Old 10th November 2008, 12:27 AM
Hlingler Offline
Join Date: Sep 2006
Location: Connellsville, PA, USA
Posts: 11,307
After PreUpgrade (F8=>F9): "Booting Has Failed"

Hello Fedora-Land:

Trying to get things upgraded in time for F10 release, I tried PreUpgrade on one of my F8 installs. All seemed to go well until it came time to reboot into F9. Then the melt-down:
vgchange     Wiping internal VG cache
Trying to resume from /dev/VolGroup00/LogVol01
Unable to access resume device (/dev/VolGroup00/LogVol01)
Creating root device.
Mounting root filesystem.
mount: error mounting /dev/root on /sysroot as ext3: No such file or directory
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Mount failed for selinuxfs on /selinux: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Booting has failed.
I can still boot (into text-mode only) with the remaining F8 kernel, but obviously this won't do. I'd like to try to fix this issue rather than scrap the whole OS. I searched but found little on PreUpgrade, and nothing of help on the above messages.

Any suggestions/ideas/help on how to fix this ?

Thanks and Regards,
Reply With Quote
Old 11th November 2008, 02:10 AM
stoat Offline
Registered User
Join Date: Jun 2006
Posts: 7,548
Hello Hlingler,

My aversion to Logical Volume Management is well documented in the record. But I have experienced failure to access the resume device before even with standard partitions. It had to do with me changing something about the swap partition. I forget, but it was probably its label or something like that. Anyway, it knocked the slats out of booting. I fixed it by teaching myself how to edit the initial ramdisk file and changed the name of the resume device in there. Other people have just used mkinitrd to generate a new initial ramdisk (easier). A kernel update probably fixes such things too for the same reason.

I feel like that /dev/VolGroup00/LogVol01 is the swap. Maybe the logical volume name in the pre-upgraded volume group and the initial ramdisk are different now, and it's doing what it always does when that happens. I found some support for this idea on the Internet with this search phrase: "Unable to access resume device (/dev/VolGroup00/LogVol01)". It's happened before, but I stopped reading after the first few when I remembered my own resume device encounter.

Can you do your LVM voodoo incantation things to find out the answer to that question about the swap and the logical volume names? The inital ramdisk is looking for /dev/VolGroup00/LogVol01. You can probably do it in the old kernel.

P.S.: Turns out I remembered my experience about the "Unable to access resume device" thing wrongly. My own earlier posts about this matter indicate that it did not stop the system from booting.

Last edited by stoat; 16th November 2008 at 03:56 PM.
Reply With Quote
Old 11th November 2008, 04:45 AM
Hlingler Offline
Join Date: Sep 2006
Location: Connellsville, PA, USA
Posts: 11,307
Hi stoat:

And many thanks for responding. And I'm beginning to share the aversion to LVM. I can say for sure that /dev/VolGroup00/LogVol01 is (and always was on this install) SWAP. I'm not sure what you're referring to: "LVM voodoo incantation thing" - most of my tricks are nothing more than smoke and mirrors.
I'll try disassembling both initrd images and compare the init files. And a kernel update I think is available, so I'll try that too.

Thanks Again,
Reply With Quote
Old 29th November 2008, 10:11 PM
Hlingler Offline
Join Date: Sep 2006
Location: Connellsville, PA, USA
Posts: 11,307
Still working on this, and still not fixed.

I have two kernels installed at this point: (which boots successfully, and no GUI/X11, but...), and, which fails as before. I've tried to make a new initrd file with mkinitrd, with same results. I have tried dis-assembling the initrd file and editing the init file, the only effect being failure on mount of system LVM instead of SWAP. Would very much like to find some fix/work-around before attempting on other F8 installs. Any other suggestions as to how to fix?

Reply With Quote

booting has failed, f8>f9, preupgrade

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
The "preupgrade" package seems to have corrupted my encrypted drive KenJackson Installation, Upgrades and Live Media 2 11th May 2009 10:11 AM
Folding@Home says "Error starting client thread" in FC10 PreUpgrade quantumburnz Alpha, Beta & Snapshots Discussions (Fedora 10 Only) 0 13th October 2008 11:42 PM
Fedora 9 "Booting has failed" ksr1973 Installation, Upgrades and Live Media 0 5th August 2008 06:20 AM
nvidiia: "Failed to load module "nvidia-1.0-9746" StefanJ Hardware & Laptops 7 25th February 2007 04:56 AM
Error:visibility arg must be one of "default", "hidden", "protected" or "internal" wangfeng Using Fedora 0 23rd May 2005 04:59 AM

Current GMT-time: 13:22 (Wednesday, 16-08-2017)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat