[SOLVED] F13->F15 upgrade results in "Welcome to emergency mode". Won't boot.

[GregJo]

I have an F13 installation on a VirtualBox VM. I learned that I need more than 512MB of RAM to install, so I added more RAM to the VM.

I attempted the "preupgrade" route. That failed. As I boot into F15 I get the following messages:
Starting /share failed, see 'systemctl status share.mount' for details.
Starting Mark the need to relabel after reboot aborted because a dependency failed.
Starting Relabel all filesystems, if necessary aborted because a dependency failed.
Starting /boot aborted because a dependency failed.
Starting File System Check on /dev/disk/by-uuid/.... aborted because a dependency failed.
Starting Getty on tty6 aborted because a dependency failed.
....
Welcome to emergency mode. Use 'systemctl default" or ^D to activate default mode.
Give root password for maintenance
(or type Control-D to continue):

If I log in with the root password, and type "systemctl default", I get:
Failed to issue method call: Transaction is destructive.

If I issue 'systemctl status share.mount', I get the following:
share.mount - /share
Loaded: loaded
Active: failed since Fri, 01 Jul 2011....
Where: /share
What: vmshared
Process: 538 ExecMount=/bin/mount /share (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/share.mount


As I mentioned, I first attempted this with 'preupgrade'. I have the VM snapshotted, so I rolled back to F13, and this time I attempted to use the F15 installer, and got the same result as using 'preupgrade'. (But I failed much more quickly....because I had local media!)

So.....since I can roll back to F13 and try again, where can I start looking to solve this? Where can I look to see what dependency failed?

[jpollard]

You might try upgrading to F14 first. If that works, then try going to F15.

[GregJo]

The first time I tried just going to F14, it bombed out on some Xorg stuff. So I rolled back to F13. Then I removed VirtualBox guest additions. Then I patched F13 up all the way. Then I used the F14 ISO to update. It worked, although I had to fix my ethernet connection....eth0 got moved to eth2. Whatever. I got it working. Next I patched F14 all the way up. Then I used the F15 ISO to install that. But...same result as in my original post.

[GregJo]

Well, I finally found a work around because of this comment:
https://bugzilla.redhat.com/show_bug.cgi?id=708574#c5

There is an entry in fstab that I had previously added. So while in emergency mode, I went ahead and commented out my entry for 'share' in /etc/fstab. F15 will now boot. I'll now mark this post as SOLVED. But then I'll go back to digging to see why my volume won't mount in F15.

[jpollard]

The volume doesn't mount due to bugs in systemD.

It doesn't properly order the startup, and things that must be delayed (like anything depending on a network - such as NFS) will fail.

I think this will eventually be worked out, but for the time being...

[GregJo]

Thanks for that info. I went digging in bugzilla and came up with this entry:
https://bugzilla.redhat.com/show_bug.cgi?id=707409

This isn't quite what I'm experiencing, although it's close. From your experience, do you know of another bug number that more closely matches this problem? I'd just like to keep an eye on the issue.

[fregs]

ohh, thanks a lot for sharing this, I was going crazy trying to figure out whats broken...
removing the shared folder mount line solved it. (F17 virtualbox by now..