I'm experiencing boot errors after a recent install of Multiple OSes. I noticed the long boot times watching the boot loading code go by and getting apparently stuck on a start job that takes 90 seconds before finally kicking out to a fail that says [Timed] and [delay], hard to read the whole line as it runs off the screen continuing to boot. Its a delay on nearly all OSes on the machine during boot.
I ran journalctl -p err
and found the following:
Jan 03 12:37:48 z-Inspiron-N5010 systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-d85dac55\x2d2393\x2d412a\x2d8080\x2d8cb24061f7b0.device.
Jan 03 12:42:51 z-Inspiron-N5010 systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-d85dac55\x2d2393\x2d412a\x2d8080\x2d8cb24061f7b0.device.
Jan 03 12:48:34 z-Inspiron-N5010 systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-d85dac55\x2d2393\x2d412a\x2d8080\x2d8cb24061f7b0.device.
Jan 03 13:06:28 z-Inspiron-N5010 systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-d85dac55\x2d2393\x2d412a\x2d8080\x2d8cb24061f7b0.device.
z@z-Inspiron-N5010:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda14 during installation
UUID=a78d855d-8b99-4920-8cf6-16dea3ff5d56 / ext4 errors=remount-ro 0 1
# /home was on /dev/sda15 during installation
UUID=9c7b545a-642c-44ee-b9e6-f440b5aec755 /home ext4 defaults 0 2
# swap was on /dev/sda5 during installation
UUID=d85dac55-2393-412a-8080-8cb24061f7b0 none swap sw 0 0
z@z-Inspiron-N5010:~$
After parsing the Timed Out Device dev-disk-by\x2duuid-d85dac55\x2d2393\x2d412a\x2d8080\x2d8cb24061f7b0.device.
Extracting the x2d from each separated by "\" I come up with:
UUID=d85dac55-2393-412a-8080-8cb24061f7b0
Comparing that with the fstab file it is easy to see the device related to the error is /dev/sda5
.
I then ransudo blkid /dev/sda5
and determined that partition actually is assigned UUID=bb3c892f-7584-42a3-a35a-0f0dfd517222
I realized the last OS installed was Debian 10 on Jan 03 2020. I also remembered the installer asked me to confirm that the partitions I defined /
and /home
were going to be formatted but it added swap
on the list as well.
I booted into the Debian OS and ran blkid as well as looked at the Debian fstab file as shown below two swaps are defined - not manually, the installer made some error.
root@debian:/home/x# cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda14 during installation
UUID=199f052c-ccf7-4b75-874c-de83d1c37300 / ext4 errors=remount-ro 0 1
# /home was on /dev/sda15 during installation
UUID=ab46faec-c492-403d-8452-c6cd79af1ca1 /home ext4 defaults 0 2
/dev/mapper/fedora_localhost--live-swap none swap sw 0 0
# swap was on /dev/sda5 during installation
UUID=bb3c892f-7584-42a3-a35a-0f0dfd517222 none swap sw 0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
root@debian:/home/x#
Somehow Fedora swap
and the shared /dev/sda5 swap
are in Debian's fstab? All systems boot, all are delayed by 90 secs just on the swap timeout. I am playing around with a few distros since Ubuntu 16.04.6 is nearing ESM. Once I decide which OSes to keep and remove I may still have problems. Any technical help would be appreciated and thanks.