I decided to check the information in /etc/fstab. The UUID of swap was
incorrect. Gparted did not see the swap partition, so it had no UUID. I
corrected that and entered the correct UUID in fstab and now it boots
fine. Maybe it is caused because I share the swap partition with other
Linux installations.
~$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @9.993s
└─multi-user.target @9.993s
└─kerneloops.service @9.900s +17ms
└─network-online.target @9.899s
└─network.target @3.198s
└─NetworkManager.service @2.147s +1.050s
└─basic.target @2.144s
└─sockets.target @2.144s
└─uuidd.socket @2.144s
└─sysinit.target @2.142s
└─networking.service @1.520s +621ms
└─apparmor.service @1.390s +128ms
└─local-fs.target @1.389s
└─run-vmblock\x2dfuse.mount @9.984s
└─local-fs-pre.target @1.346s
└─systemd-remount-fs.service @1.338s +7ms
└─systemd-fsck-root.service @1.278s +58ms
└─systemd-fsckd.socket @202ms
└─-.slice @195ms
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1448134
Title:
boot hangs on vmblock fuse mount
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1448134/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
