Sometime during some hardware changes and upgrades, I now have a 90 second delay in booting my computer while it waits for a UUID that does not exist. The message is:
“A start job is running for /dev/disk/by-uuid” followed by a UUID that does not appear in either /etc/fstab or /etc/crypttab.
Where else can I look to find out why it is searching for this UUID. How can I fix it so that this 90 second delay is removed? I have asked this question on fedoraforum but had not success. I regenerated the /boot/grub2/grub.cfg, the /boot/efi/EFI/grub.cfg, ran dracut -f, ran grub2-install /dev/sda to reinstall grub to the MBR, double and triple checked the fstab and crypttab files to make sure that this UUID isn’t there. Since all my partitions are accounted for, this must be some old artifact. However, I can’t figure out how to eliminate it. I would appreciate any help that would fix this issue and stop the 90 second wait.
To where should that be added? The link seems to be to add it to the fstab, but the UUID does not exist in either file. The lsblk and head commands do not show any UUID matching the one in the start job so there is nowhere to add the nofail or timeout change.
I also do not see that UUID in any of the /dev/disk/by-uuid entries
vgdisplay; sudo pvdisplay; sudo lvdisplay
/dev/sdf: open failed: No medium found
/dev/sdg: open failed: No medium found
/dev/sdh: open failed: No medium found
/dev/sdi: open failed: No medium found
/dev/sdj: open failed: No medium found
vgmknodes -vvvv --refresh
I’m not going to paste the results of vgmknodes -vvv --refresh or vgck -vvvv since they would be way too long. Suffice it to say that the UUID that is causing the delay is not in the results either. I do not use lvm, having been burned twice by it so all my partitions are standard partitions.
Edit: I rebooted after doing the grub.cfg and dracut regenerations. No change. It is still waiting for the non-existing UUID.