[Solved] Fresh install booting to emergency mode

[bitdaddy]

This morning, I did a fresh install via http and for some reason, its booting to emergency mode. The system starts booting and then a few seconds after reaching the graphical splash everything hangs for a while and then I'm kicked to emergency mode. When I get to emergency mode, I'm able to start kde, but things like sound and networking are not working. I have a pretty generic system, with an A8-3850 APU, Gigabyte GA-A75-UD4H main board, 8 GB RAM & no expansion cards.

I can provide the entire output of the journalctl -xb if needed, but I think I found where the issue is, I just have no idea how to proceed:

Code: Select all

Apr 23 07:06:24 bitStorm kernel: EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: acl
Apr 23 07:07:50 bitStorm systemd[1]: Job dev-disk-by\x2duuid-1CF0\x2d0E53.device/start timed out.
Apr 23 07:07:50 bitStorm systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-1CF0\x2d0E53.device.
-- Subject: Unit dev-disk-by\x2duuid-1CF0\x2d0E53.device has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit dev-disk-by\x2duuid-1CF0\x2d0E53.device has failed.
--
-- The result is timeout.
Apr 23 07:07:50 bitStorm systemd[1]: Dependency failed for /mnt/hd.
-- Subject: Unit mnt-hd.mount has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mnt-hd.mount has failed.
--
-- The result is dependency.
Apr 23 07:07:50 bitStorm systemd[1]: Dependency failed for Local File Systems.
-- Subject: Unit local-fs.target has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit local-fs.target has failed.
--
-- The result is dependency.
Apr 23 07:07:50 bitStorm systemd[1]: Dependency failed for Mark the need to relabel after reboot.
-- Subject: Unit fedora-autorelabel-mark.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit fedora-autorelabel-mark.service has failed.
--
-- The result is dependency.
Apr 23 07:07:50 bitStorm systemd[1]: Dependency failed for Relabel all filesystems, if necessary.
-- Subject: Unit fedora-autorelabel.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit fedora-autorelabel.service has failed.
--
-- The result is dependency.
Apr 23 07:07:50 bitStorm systemd[1]: Triggering OnFailure= dependencies of local-fs.target.
Apr 23 07:07:50 bitStorm systemd[1]: Starting Save boot dmesg content...
-- Subject: Unit mandriva-save-dmesg.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--


Everything before that seems to start OK, and everything after is just services shutting down and going into emergency mode.

[bitdaddy]

OK, I figued it out. After looking at it a bit more, I thought it might be something related to the flash drive mount. So, I plugged in my flash drive and everything booted fine. Removing an entry for the flash drive that was placed in the fstab file fixed the problem.

[doktor5000]

Did you maybe install Mageia with the flash drive plugged in?
Hopefully this will be fixed for Mageia 5 as it's quite nasty: https://bugs.mageia.org/show_bug.cgi?id=12631

[bitdaddy]

Yes, that was it. I booted from the flash drive and then started a net install. Thanks for pointing out that bug report, that was my problem exactly.