Bug 967321

Where does it fail?  Please try the instructions at:
   http://freedesktop.org/wiki/Software/systemd/Debugging/
and attach what output you can get.

Created attachment 754530 [details]
log files from root command line console (emergency mode)

I reach only the emergency console. Crtl-D to continue does not help. 
Login as root is working. If I edit fstab, remove the two lines (commenting out) and shutdown for restart it boots fine. 
From the root shell after crash i have created the attached log files. 
If you need more then let me know what and how i can get this as root command line shell user.

From the systemd viewpoint, this is not a bug (filesystem failed to mount, local-fs.target cannot be reached, enter emergency mode). Add ",nofail" at the end of options in fstab if you don't want the boot to fail when the filesystems cannot be mounted.

Why the mounting fails in the first place?
> kernel: vboxguest: module verification failed: signature and/or required key missing - tainting kernel
> mount[540]: /sbin/mount.vboxsf: mounting failed with the error: No such device
> mount[539]: /sbin/mount.vboxsf: mounting failed with the error: No such device
I haven't had much experience with vbox, but I guess that this means there's some configuration error or maybe the vboxsf module is not getting loaded. Can you mount the shared folder manually?

Hm, are you using kmod-VirtualBox from rpmfusion? If so, they haven't released kmod-VirtualBox-3.9.4 yet. Consider switching to open-vm-tools which is part of Fedora now.

THe same configuration works in the previous kernel. 
Manual mount works in both cases. 

I don't see a reason why the mount works in the previous kernel and not now anymore. If there is a configuration error it should not have worked in the previous kernel version. 

The emergency screen offers Ctrl-D to continue. This doesn't work in the sense that it reboots and stops at the same point again. It should finalize startup if the problem is a minor one as you described. 

I'm using this 
http://download.virtualbox.org/virtualbox/4.2.12/VirtualBox-4.2.12-84980-Win.exe
to run fedora as guest. 

The guest additions are these:
http://download.virtualbox.org/virtualbox/4.2.12/VBoxGuestAdditions_4.2.12.iso

The shared folders are folders of the Windows 8 64bit host. I installed the fedora 32bit version in virtulbox. (64 bit performace is not so good and there is a compatibility issues with apache, php etc.)

The behaviour is a little odd. I was doing a yum distribution-synchronization and after this I got the problem.
Selection in the boot menu the previous kernel was removing the problem.

(In reply to wweigelt-07 from comment #4)
> The emergency screen offers Ctrl-D to continue. This doesn't work in the
> sense that it reboots and stops at the same point again.
That's the designed behaviour of systemd: when you quit the emergency session,
it attempts to reach the default target, which means that it'll attempt to
mount all the filesystems in /etc/fstab that haven't been mounted yet.

Could you boot with systemd.log_level=debug on the kernel command line,
and attach the output of journalctl -b ?

Created attachment 757924 [details]
journal-b

I haved added the debug command to the boot line before booting. I don't know if I have done this correctly

>That's the designed behaviour of systemd: when you quit the emergency session,
>it attempts to reach the default target, which means that it'll attempt to
>mount all the filesystems in /etc/fstab that haven't been mounted yet.

That designed behaviour is really fine for programmers and for Linux experts. 
For simple users running their applications like a spreadsheet or email etc. this is fatal because they will never figure out what has gone wrong. 
Helpful would be at least to show in the emergency screen always an error message. In case of not system relevant errors it should boot up normally and show always after log on an error message. But this is my opinion only ...

So I am not sure I can do much about this. virtualbox is not part of fedora is it?

I am not sure how virtualbox does its shared folder stuff, but it's probably up to them to get this right.

The two vbox specific mount commands fail:

> mount[540]: /sbin/mount.vboxsf: mounting failed with the error: No such device
> mount[539]: /sbin/mount.vboxsf: mounting failed with the error: No such device

So this really indicates a problem with vbox' own code. 

Please file a bug on the virtualbox bug tracker, they need to fix this. I really don't see what we can do in systemd/Fedora about this.

>So I am not sure I can do much about this. virtualbox is not part of fedora is >it?
Fedora runs as virtual machine within VIRTUALBOX. 
Simply a FEDORA UPDATE OF THE KERNEL was bringing up the problem. 
MANUAL MOUNT WORKS

I'm really pretty sure that this is a Fedora bug.

I'm sure you've moved on from this issue, but just in case anyone else is reading this and having the same problem, the issue is likely due to the vboxsf module not being loaded at the time fstab is processed during boot.

With Fedora 21 server, adding a file in /etc/sysconfig/modules with the following contents:

> /usr/sbin/modprobe vboxsf > /dev/null 2>&1

fixes the issue for me.

(Note for anyone reading, the file must be made executable, and from what I've read it probably also needs to have the extension ".modules")