boot broken (systemd)

Hi,

I have updated my cooker machine 3 days ago, and in the first time i
reboot after upgraded into cooker the book entered in console mode
promptiong to enter CTRL+D or root password, after some tries i didnt
managed to see what was the problem so i did a new clean isntall and
again after upgrading to cooker when rebooting the problem appeared
again....

So to be able to boot and to have X i had to edit /etc/fstab and
disable the windows partitons, the cdrom and another Ext4 partition.
The messages that i used to saw in boot were:

udevd[101]: exec of program '/bin/grep -qFw -e nokmsboot -e failsafe
/proc/cmdline' failed
...
udevd[407]: '/sbin/blkid -o udev -p /dev/sda2' [1400] terminated by
signal 15 (Terminated)

so after running fsck for the windows partitions and the Ext4
partition i was finally able to boot with the partitions enabled in
/etc/fstab.


The most strange was that to be able to have the cdrom entry in fstab
i needed to put a CD in the cdrom device and run fsck to it, then i
was able to boot with the cdrom enabled in fstab, go figure this
one...
But if i remove the CD from the cdrom device the boot hangs again and
it prompts this:

udevd[404]: '/sbin/modprobe -bv
pci:v00008086d00001c20sv00001558sd00001500bc04sc03i00' [615]
terminated by signal 15 (Termiinated)

I also notested that is i changed some in fstab the boot was broken
again (even with the cdrom entry disabed in fstab) and i was forced
again to run fsck for the windows and the Ext4 partitions to be able
to have them back enabled in /etc/fstab.

So something needs to be done to revert this "crazy" behaviour from
systemd and udev, but i think the problem remains only from systemd
since udev was not changed recently, only systemd was.

-- 
Salutem,
Zé