Monthly Backup and Restore Test has "a job has started for" for 1 minute 30 seconds

After restoring as usual there is a new “a start job is running for dev-disk-by\more numbers” for 1 minute 30 seconds.

blkid does not show the device - /etc/fstab is exactly like entries from blkid.

mkinitrd and grub2-install does not change the problem.

Since it does boot up correctly after the timeout - Is there a way to change the timeout to 30 seconds?

This is the disk that timesout on the boot - I see this in the journalctl every so often - where is this coming from?

Jan 24 12:04:46 LLR1 systemd[1]: dev-disk-by\x2duuid-9cbad955\x2d9531\x2d4ece\x2db6fd\x2de4cf8ca26b8a.device: Job dev-disk-by\x2duuid-9cbad955\x2d9531\x2d4ece\x2db6fd\x2de4cf8ca26b8a.device/start timed out.
Jan 24 12:04:46 LLR1 systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-9cbad955\x2d9531\x2d4ece\x2db6fd\x2de4cf8ca26b8a.device.
Jan 24 12:04:46 LLR1 systemd[1]: Dependency failed for /dev/disk/by-uuid/9cbad955-9531-4ece-b6fd-e4cf8ca26b8a.
Jan 24 12:04:46 LLR1 systemd[1]: dev-disk-by\x2duuid-9cbad955\x2d9531\x2d4ece\x2db6fd\x2de4cf8ca26b8a.swap: Job dev-disk-by\x2duuid-9cbad955\x2d9531\x2d4ece\x2db6fd\x2de4cf8ca26b8a.swap/start failed with result 'dependency'.
Jan 24 12:04:46 LLR1 systemd[1]: dev-disk-by\x2duuid-9cbad955\x2d9531\x2d4ece\x2db6fd\x2de4cf8ca26b8a.device: Job dev-disk-by\x2duuid-9cbad955\x2d9531\x2d4ece\x2db6fd\x2de4cf8ca26b8a.device/start failed with result 'timeout'.

Hi
Check grub and the resume= entry… likely swap… (I don’t resume/hibernate, so it’s deleted…).


cat /etc/default/grub | grep GRUB_CMDLINE_LINUX_DEFAULT

Post:

blkid
cat /etc/fstab
cat /etc/mtab

You mention this, thus you probably think it may be important. But in fact you tell nothing about it. Or do you think that we all know how you “restore as usual”?

When this is about a system restore after a disaster, it may be that you restored that /dev/disk/by-uuid/9cbad955-9531-4ece-b6fd-e4cf8ca26b8a as a string in some configuration.

Maybe

cd /etc
grep 9cbad955-9531-4ece-b6fd-e4cf8ca26b8a *

And of course, you talk about blkid ands /etc/fstab, but you show nothing! To say it bluntly: we do not believe you, we only believe what the computer shows.

I was still looking for the source - It is the swap file but it is not starting at boot - I have to swapon /dev/nvmen0p3 for it to show and it is not there on a reboot.

I was doing my monthly bare iron restore - I put a new nvme drive in and make a gpt and the 3 files system and change the UUID’s for the ext4 and swap mount the new filesystems as /mnt and create the missing directories not backed up (dev run sys tmp proc boot and boot/efi ) and tar xvf the backup - I have done this every month for 15 years - this is the first time anything different has happened. I see that /boot/efi/EFI/boot has different files than the last time I restored a backed up. I do not have secureboot - just opensuse - so I have to grub2-install anytime I use the recovery USB that has a built 15.2 with MATE.

LLR1:~ # blkid
/dev/nvme0n1p1: UUID="5BC0-FC11" TYPE="vfat" PARTUUID="573cecd2-56d0-4d5d-958a-b812ea1ab285"
/dev/nvme0n1p2: UUID="75837315-86e5-4e19-af88-621f330d2be5" TYPE="ext4" PARTUUID="786db11a-034d-4099-943d-c6d38663e699"
/dev/nvme0n1p3: UUID="9bcad955-9531-4ece-6bfd-e4cf8ca26b8a" TYPE="swap" PARTUUID="45fc8e26-9f28-4400-a7bd-5a367899229a"
/dev/sda1: LABEL="LLR1_U" UUID="9588fdd5-0c3d-4664-bd2e-6236b6ffd45c" TYPE="ext4" PARTUUID="539494fe-fd4a-44e4-a867-74d8ffde5bb6"
/dev/sdb1: LABEL="LLR1_T" UUID="aec9a02c-9d32-412f-80be-1e1587e786bb" TYPE="ext4" PARTUUID="eee15a67-a8ca-4a8b-980e-0081798f16ac"
/dev/sdc1: LABEL="LLR1_O" UUID="7b809416-35cb-4560-88e0-187849a25d43" TYPE="ext4" PARTUUID="e6575d36-85cc-480e-b1eb-2ee6a2c13e29"
/dev/sdd1: LABEL="LLR1_P" UUID="50641663-0199-491e-9114-82e1eb9d4a70" TYPE="ext4" PARTUUID="93b7d61d-f961-4d7e-b382-6039574d1b17"
/dev/sde1: LABEL="LLR1_BK" UUID="730b7e52-5edd-4f2b-8e5e-933c16192a21" TYPE="ext4" PARTUUID="3aed1e4c-9ef9-4495-8faf-81b7c50f540e"
/dev/nvme0n1: PTUUID="9d7221c4-e0e2-4b39-989b-b1cfc67a58f8" PTTYPE="gpt"
LLR1:~ # cat /etc/fstab
UUID=9cbad955-9531-4ece-b6fd-e4cf8ca26b8a swap                 swap       defaults              0 0
UUID=75837315-86e5-4e19-af88-621f330d2be5 /                    ext4       acl,user_xattr        1 1
UUID=5BC0-FC11                            /boot/efi            vfat       utf8=true             0 0

LLR1:~ # cat /etc/default/grub | grep GRUB_CMDLINE_LINUX_DEFAULT
#GRUB_CMDLINE_LINUX_DEFAULT="splash=verbose showopts nouveau.modeset=0 net.ifnames=0 usb-storage.quirks=0bc2:3323:u usbcore.autosuspend=-1"
GRUB_CMDLINE_LINUX_DEFAULT="splash=verbose showopts nouveau.modeset=0 net.ifnames=0 usb-storage.quirks=152d:0562:u,0bc2:3323:u usbcore.autosuspend=-1"
LLR1:~ # cd /etc
LLR1:/etc # grep -R 9cbad955-9531-4ece-b6fd-e4cf8ca26b8a *
grep: boto.cfg: No such file or directory
grep: boto.cfg.rpmsave: No such file or directory
fstab:UUID=9cbad955-9531-4ece-b6fd-e4cf8ca26b8a swap                 swap       defaults              0 0
grep: mpv/scripts/mpris.lua: No such file or directory
LLR1:/etc # swapon -v
NAME           TYPE       SIZE USED PRIO
/dev/nvme0n1p3 partition 32.2G   0B   -2
LLR1:/etc #

I remove the swap from /etc/fstab and the issue went away but no swap file until I do the swapon /dev/nvmen0p3.

Any Idea why swap entry in /etc/fstab is causing this problem?

Honestly, that suggests that the “fstab” entry for swap was bad. But, as Henk says, you have not shown us the details so we can only guess.

fstab entry is in the previous code.

repeated with color

LLR1:~ # blkid
/dev/nvme0n1p1: UUID="5BC0-FC11" TYPE="vfat" PARTUUID="573cecd2-56d0-4d5d-958a-b812ea1ab285"
/dev/nvme0n1p2: UUID="75837315-86e5-4e19-af88-621f330d2be5" TYPE="ext4" PARTUUID="786db11a-034d-4099-943d-c6d38663e699"
/dev/nvme0n1p3: UUID="9bcad955-9531-4ece-6bfd-e4cf8ca26b8a" TYPE="swap" PARTUUID="45fc8e26-9f28-4400-a7bd-5a367899229a"
/dev/sda1: LABEL="LLR1_U" UUID="9588fdd5-0c3d-4664-bd2e-6236b6ffd45c" TYPE="ext4" PARTUUID="539494fe-fd4a-44e4-a867-74d8ffde5bb6"
/dev/sdb1: LABEL="LLR1_T" UUID="aec9a02c-9d32-412f-80be-1e1587e786bb" TYPE="ext4" PARTUUID="eee15a67-a8ca-4a8b-980e-0081798f16ac"
/dev/sdc1: LABEL="LLR1_O" UUID="7b809416-35cb-4560-88e0-187849a25d43" TYPE="ext4" PARTUUID="e6575d36-85cc-480e-b1eb-2ee6a2c13e29"
/dev/sdd1: LABEL="LLR1_P" UUID="50641663-0199-491e-9114-82e1eb9d4a70" TYPE="ext4" PARTUUID="93b7d61d-f961-4d7e-b382-6039574d1b17"
/dev/sde1: LABEL="LLR1_BK" UUID="730b7e52-5edd-4f2b-8e5e-933c16192a21" TYPE="ext4" PARTUUID="3aed1e4c-9ef9-4495-8faf-81b7c50f540e"
/dev/nvme0n1: PTUUID="9d7221c4-e0e2-4b39-989b-b1cfc67a58f8" PTTYPE="gpt"
LLR1:~ # cat /etc/fstab
UUID=9cbad955-9531-4ece-b6fd-e4cf8ca26b8a swap                 swap       defaults              0 0
UUID=75837315-86e5-4e19-af88-621f330d2be5 /                    ext4       acl,user_xattr        1 1
UUID=5BC0-FC11 

Those two are different. Perhaps a typo somewhere.

I guess I looked at it with a dyslexic eye.

Good catch. Thanks.

Always copy from command output and paste into editor.:wink:

**erlangen:~ #** lsblk -f /dev/sdb 
NAME   FSTYPE FSVER LABEL    UUID                                 FSAVAIL FSUSE% MOUNTPOINT 
sdb                                                                               
└─sdb1 ext4         Home-SSD 5605f149-34a7-4301-9bf3-f1f177e35ed6    493G    68% /home-SSD 
**erlangen:~ #**