As you can see my swap at /dev/sda7 has a different UUID in fstab than it does in blkid. This was, in my case, caused by another linux install repartitoning the swap
and causing the UUID to change. The boot delay is caused by the system trying to find the new UUID of the swap. To fix it, just copy the UUID in blkid that doesnt match to the fstab file then save.
If after restart the boot error is still there, you need to additionally edit your initramfs.conf file.
Do this by:
$ sudo nano /etc/initramfs-tools/conf.d/resume
Then either by making a new file, or editing the current resume file, write on the first line
RESUME=UUID=<< UUID of swap>>
For example, mine looks like
RESUME=UUID=d9539219-1c29-468f-bbd0-106663fdef59
Then run the below command to update your initramfs file.
Ive had this problem numerous times, and my solution works in all situations.
When running dsmeg, the error shows up as:
[CODE]
[ 6.382044] random: crng init done
[ 6.382048] random: 7 urandom warning(s) missed due to ratelimiting
[ 32.162934] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)[/CODE]
The solution is to:
First compare your fstab and blkid:
[CODE]$ blkid "1085d848- f8b9-45e2- a6be-087acb32a8 20" 23022FB" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID= "de399a3e- c832-4dca- a09d-f65789425b 89" 2511341" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID= "18feb4e1- 5770-4e13- 92b8-bb8ba80055 36" 98bf-4d40- b03e-e5e647163d 7e" TYPE="ext4" PARTLABEL="Arco Linux" PARTUUID= "3759200f- 6317-4487- 8b10-3a0140c67b d5" 61fa-4187- b11f-517c799f7c 94" TYPE="ext4" PARTLABEL="MX Linux" PARTUUID= "417c8cbd- 11b7-4fe6- 9b15-ac9082d744 60" 1c29-468f- bbd0-106663fdef 59" TYPE="swap" PARTLABEL="Swap" PARTUUID= "fefe3061- bf7b-4a26- 8c20-08e209acc2 8e"
/dev/sda1: UUID="C0C0-7641" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID=
/dev/sda3: LABEL="Windows" UUID="8662302C6
/dev/sda4: LABEL="Windows RE tools" UUID="226251396
/dev/sda5: UUID="81a474ab-
/dev/sda6: LABEL="rootMX17" UUID="7bae9e4d-
/dev/sda7: UUID="d9539219-
$ sudo nano /etc/fstab
# /etc/fstab: static file system information
#
# Created by make-fstab on Mon Nov 19 17:10:30 EST 2018
# <file system> <mount point> <type> <$
#-> /dev/sda6 label=rootMX17 61fa-4187- b11f-517c799f7c 94 / ext4 d$ b6e1-4d57- 9a3a-2ad9108625 79 swap swap d$[/CODE]
UUID=7bae9e4d-
#-> /dev/sda1
UUID=C0C0-7641 /boot/efi vfat d$
#-> /dev/sda7
UUID=42e5a9cd-
As you can see my swap at /dev/sda7 has a different UUID in fstab than it does in blkid. This was, in my case, caused by another linux install repartitoning the swap
and causing the UUID to change. The boot delay is caused by the system trying to find the new UUID of the swap. To fix it, just copy the UUID in blkid that doesnt match to the fstab file then save.
If after restart the boot error is still there, you need to additionally edit your initramfs.conf file.
Do this by:
$ sudo nano /etc/initramfs- tools/conf. d/resume
Then either by making a new file, or editing the current resume file, write on the first line
RESUME=UUID=<< UUID of swap>>
For example, mine looks like
RESUME= UUID=d9539219- 1c29-468f- bbd0-106663fdef 59
Then run the below command to update your initramfs file.
sudo update-initramfs -u
Then restart. The error will be gone