On Dec 28, 2013, at 2:42 PM, Patrick Dupre <pdu...@gmx.com> wrote: > Hello Chris, > > More information. This what I get until the first FAILED > > kvm: disabled by bios
Seems like this BIOS always disables virtualization so unless your other root doesn't have this message I don't know why it's relevant. > started Configure read-only root support Normal, so why are you including this? > Starting Load Random Seed > Started Load Random Seed > scsi > sd > sd [sdb] > World regulatory domain > (start_freq - end_freq @ > > Calling CRDA for country > > systemd-udevd[390]: renamed > > [ OK ] Found device ST9500420AS > Activating swap /dev/disk/by-uuid/026838a7-740a-4630-bb7d-b8b7e74657c0 > Adding 3077840k swap on /dev/sda5 > [ OK ] Activated swap /dev > [ OK ] Reached target Swap > [ OK ] Started Monitoring of LVM2 mirrors, > [ OK ] Found device ST9500420AS > Starting File System on /dev/sda16 > > [ OK ] Found device /dev/mapper/VolGrpSys3-usr_src > Starting File System Check on /dev/mapper/VolGrpSys3-usr_src > [ OK ] Started File System on /dev/sda16. > [ OK ] Started File System on /dev/mapper/VolGrpSys3-usr_src > Mounting /usr/src.... > Mounting /boot > [ OK ] Found device /dev/mapper/VolGrpSys3-tmp. > Starting File System Check on /dev/mapper/VolGrpSys3-tmp. > Mounting FUSE Control File System > [ OK ] Mounted FUSE Control File System > [ OK ] Mounted /usr/src > EXT4-fs (sda16): mounted > [ OK ] Started File System on /dev/mapper/VolGrpSys3-tmp. > Mounting /tmp > [ OK ] Mounted /boot > > [ OK ] Mounted /tmp > [ OK ] Found device /dev/mapper/VolGrpSys3-usr_local > Starting File System Check on /dev/mapper/VolGrpSys3-usr_local > Mounting /usr/local > [ OK ] Found device /dev/disk/by-uuid/225d0e0d-3fd0-4757-88be-ae4862470358. > Starting Cryptography Setup for > luks-225d0e0d-3fd0-4757-88be-ae4862470358.. > [ OK ] Listening on Journal Service... > [FAILED] Failed to start Journal Service. > See `systemctl status system-journal.service' for details. Do you get a prompt? Have you tried issuing systemctl status system-journal.service to find out why it wasn't started? Something isn't being mounted correctly is what it sounds like to me. Like either fstab is wrong, or cryptab is wrong. Basically you'll have to look at dracut and systemd troubleshooting, get them into debug mode, and find out where the problem is. https://fedoraproject.org/wiki/How_to_debug_Dracut_problems http://freedesktop.org/wiki/Software/systemd/Debugging/ Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
