[SOLVED] Timeout waiting to mount /dev/disk-uuid

marol · 2024-03-17 13:26:29

I know there are topics with the same, similar theme. I read some of them, but it didn't work for me.
I installed vanila arch (btrfs, secure boot). After installation I rebooted, entered passphrase and got this:

 [TIME] Timed out waiting for device /dev/diskby-uuid/37c1e87c-ee39-4655-8495-82cbb04ac895.
[DEPEND] Dependency failed for Resume from hibernation.

 cat /etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/mapper/disk
UUID=56a50349-96c2-4a03-8655-32f5536d052b	/         	btrfs     	rw,noatime,compress=zstd:1,ssd,discard=async,space_cache=v2,autodefrag,subvol=/@	0 0

# /dev/mapper/disk
UUID=56a50349-96c2-4a03-8655-32f5536d052b	/home     	btrfs     	rw,noatime,compress=zstd:1,ssd,discard=async,space_cache=v2,autodefrag,subvol=/@home	0 0

# /dev/mapper/disk
UUID=56a50349-96c2-4a03-8655-32f5536d052b	/.snapshots	btrfs     	rw,noatime,compress=zstd:1,ssd,discard=async,space_cache=v2,autodefrag,subvol=/@snapshots	0 0

# /dev/mapper/disk
UUID=56a50349-96c2-4a03-8655-32f5536d052b	/var/log  	btrfs     	rw,noatime,compress=zstd:1,ssd,discard=async,space_cache=v2,autodefrag,subvol=/@var_log	0 0

# /dev/nvme0n1p1
UUID=7E76-E05A      	/efi      	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro	0 2

# /dev/nvme0n1p2
/dev/mapper/swap				none      	swap      	defaults  	0 0

lsblk -f
NAME        FSTYPE      FSVER LABEL     UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
nvme0n1                                                                                     
├─nvme0n1p1 vfat        FAT32           7E76-E05A                             314.1M    39% /efi
├─nvme0n1p2 ext2        1.0   cryptswap 5edf6d96-1b50-46a3-beb9-c4c375eea0ba                
│ └─swap    swap        1     swap      c0b3b8af-6717-4576-87bc-dfb4abfa692b                [SWAP]
└─nvme0n1p3 crypto_LUKS 2               4636c268-b6b2-41d9-9a03-abd426cfb555                
  └─disk    btrfs                       56a50349-96c2-4a03-8655-32f5536d052b  363.2G    19% /var/log
                                                                                            /home
                                                                                            /.snapshots
                                                                                            /

 blkid
/dev/mapper/swap: LABEL="swap" UUID="c0b3b8af-6717-4576-87bc-dfb4abfa692b" TYPE="swap"
/dev/nvme0n1p3: UUID="4636c268-b6b2-41d9-9a03-abd426cfb555" TYPE="crypto_LUKS" PARTUUID="388360b9-a4f9-48db-850c-92ee7f8ba67f"
/dev/nvme0n1p1: UUID="7E76-E05A" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="d1c29728-9c13-4245-8a1b-140ec3ed36f4"
/dev/nvme0n1p2: LABEL="cryptswap" UUID="5edf6d96-1b50-46a3-beb9-c4c375eea0ba" BLOCK_SIZE="1024" TYPE="ext2" PARTUUID="a6b4866f-aa32-42fa-b713-197694e56aab"
/dev/mapper/disk: UUID="56a50349-96c2-4a03-8655-32f5536d052b" UUID_SUB="7f214d3d-e799-4e07-908d-cb8cd2670e6f" BLOCK_SIZE="4096" TYPE="btrfs"

I looked through journalctl -xb, also read few topics at this forum and some other sites, but nothing worked for me. I tried to rebuild initramfs, problem still remains.
I'm confused and don't understand what mistake I did during installation? I followed the same script and commands, installing arch on my laptop. It's booting and working flowlessly.

Please, help me to find, what is the problem and fix it.

Last edited by marol (2024-03-22 08:28:04)

Head_on_a_Stick · 2024-03-17 13:32:09

Please share your full bootloader configuration.

marol wrote:

I followed the same script and commands

Which script did you follow?

marol · 2024-03-17 13:47:17

Head_on_a_Stick wrote:

Please share your full bootloader configuration.
marol wrote:
I followed the same script and commands

 /etc/kernel/cmdline
root=/dev/mapper/disk rootfstype=btrfs rootflags=subvol=/@ rw quiet splash modprobe.blacklist=pcspkr zswap.enabled=0

Head_on_a_Stick wrote:

...
Which script did you follow?

This one.

Head_on_a_Stick · 2024-03-17 14:15:18

Does /etc/crypttab contain the correct swap UUID?

Reference: https://wiki.archlinux.org/title/Dm-cry … _and_LABEL

marol · 2024-03-17 14:38:04

 blkid /dev/nvme0n1p2
/dev/nvme0n1p2: LABEL="cryptswap" UUID="5edf6d96-1b50-46a3-beb9-c4c375eea0ba" BLOCK_SIZE="1024" TYPE="ext2" PARTUUID="a6b4866f-aa32-42fa-b713-197694e56aab"

Head_on_a_Stick · 2024-03-17 14:45:20

Probably best to share the full journal contents then. I'm not much good with encryption though, unfortunately.

marol · 2024-03-17 15:56:46

https://pastebin.com/tz5gH7AW

Raynman · 2024-03-17 16:20:27

Journal confirms no resume= parameter, but there's

Mar 17 17:01:33 archlinux systemd-hibernate-resume-generator[177]: Reported hibernation image: ID=arch kernel=6.5.7-arch1-1 UUID=37c1e87c-ee39-4655-8495-82cbb04ac895 offset=0

According to the man page, the only other possibility is the EFI variable HibernateLocation, so I'd start by checking/removing that (did you have a previous Arch install on this motherboard?): https://wiki.archlinux.org/title/Unifie … _variables

See also https://wiki.archlinux.org/title/Power_ … _initramfs

marol · 2024-03-17 22:07:07

Raynman wrote:

Journal confirms no resume= parameter, but there's
Mar 17 17:01:33 archlinux systemd-hibernate-resume-generator[177]: Reported hibernation image: ID=arch kernel=6.5.7-arch1-1 UUID=37c1e87c-ee39-4655-8495-82cbb04ac895 offset=0
According to the man page, the only other possibility is the EFI variable HibernateLocation, so I'd start by checking/removing that (did you have a previous Arch install on this motherboard?): https://wiki.archlinux.org/title/Unifie … _variables
See also https://wiki.archlinux.org/title/Power_ … _initramfs

 efivar --list
...
8cf2644b-4b0b-428f-9387-6d876050dc67-HibernateLocation
...

So, what should I do? To add this UUID 8cf2644b-4b0b-428f-9387-6d876050dc67 to efistab?

Raynman wrote:

...
(did you have a previous Arch install on this motherboard?)

Yes, I did. There was arch luks2 brtfs.

seth · 2024-03-18 08:55:38

No, remove the entry from the efivars. The partition doesn't exist (anymore) according to the provided data.

marol · 2024-03-18 09:28:30

Thank you, seth. I opened /sys/firmware/efi/efivars and tried to delete HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67, but I've got warning:

 /sys/firmware/efi/efivars [RO]
**warning** (netrw) delete(/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67) failed!
NetrwMessage [RO]

May be I don't understand something... During bootloading there's notification to /dev/disk-uuid-37c1e87c-ee39-4655-8495-82cbb04ac895 but I should remove HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67 ????

seth · 2024-03-18 14:06:29

The filesystem is probably immuted by default, "lsattr /sys/firmware/efi/efivars", "chattr -i" to remove that.
USE WITH OUTMOST CARE! You can brick your system this way!

Have you checked the contents of the file?

cat /sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67

To (hopefully) boot the system w/o fumbling w/ the UEFI, add "noresume" to the https://wiki.archlinux.org/title/Kernel_parameters

Head_on_a_Stick · 2024-03-18 15:32:18

I think it would be safer to just attempt to manually specify the hibernate location.

Deleting random EFI variables sounds unwise.

seth · 2024-03-18 16:02:03

Afaiu the OP doesn't hibernate at all, so that would be the "noresume" approach (idk whether systemd will otherwise still try to get the hibernation image b/c of the efivar) and 8cf2644b-4b0b-428f-9387-6d876050dc67 isn't a present UUID in any regard.

But yes, w/o looking at it I'd not touch anything in there ("brick")

marol · 2024-03-18 16:14:56

seth wrote:

...
Have you checked the contents of the file?
cat /sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67
To (hopefully) boot the system w/o fumbling w/ the UEFI, add "noresume" to the https://wiki.archlinux.org/title/Kernel_parameters

cat /sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67
{"uuid":"8b2cab04-7bdd-4509-a493-026bf1b81928","offset":0,"kernelVersion":"6.7.9-arch1-1","osReleaseId":"arch"}%

marol · 2024-03-18 16:25:33

seth wrote:

Afaiu the OP doesn't hibernate at all, so that would be the "noresume" approach (idk whether systemd will otherwise still try to get the hibernation image b/c of the efivar) and 8cf2644b-4b0b-428f-9387-6d876050dc67 isn't a present UUID in any regard.
But yes, w/o looking at it I'd not touch anything in there ("brick")

You are right, I don't use hebernation. I don't worry about brcking system - I worry about bricking my desktop. I did

lsattr /sys/firmware/efi/efivars

and I've got a list of data along with /sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67
So, now I can enter this command

chattr -i /sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67

right?

Last edited by marol (2024-03-18 16:28:08)

seth · 2024-03-18 16:28:54

"bricking system" means you can turn your notebook into a paperweight to use to balance a chair.
Do not wing anything here!

Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
Post the actual outputs you're getting, both from the lsattr as well as "efivar --list"
ALL of them.

You can feed them into 0x0.st, see the 1st link below.

For context: https://bbs.archlinux.org/viewtopic.php?id=290990

marol · 2024-03-18 22:05:57

I'm sorry, seth. I'm not new in Linux, but feeling myself a noob. I had no intention to wing or twist something. I'm only for clearance and transparency.
I'm going to edit cmdline. Should I add this ?

/etc/kernel/cmdline
root=/dev/mapper/disk rootfstype=btrfs rootflags=subvol=/@ rw quiet splash [b]resume=UUID=8cf2644b-4b0b-428f-9387-6d876050dc67[/b] modprobe.blacklist=pcspkr zswap.enabled=0

Later I wil post all actual outputs from the lsattr as well as "efivar --list" as you recommended.

seth · 2024-03-18 22:28:53

You don't have to be sorry, I just wanted you to understand that you can cause some serious and permanent damage here.

The other tags don't work inside code tags
And no, the parameter to test would still be "noresume" - there's no partition w/ the UUID 8cf2644b-4b0b-428f-9387-6d876050dc67 and we also don't know where this is coming from.

marol · 2024-03-19 07:04:30

Thank you very much, seth! So, code should be this -

/etc/kernel/cmdline
root=/dev/mapper/disk rootfstype=btrfs rootflags=subvol=/@ rw quiet splash noresume modprobe.blacklist=pcspkr zswap.enabled=0

Last edited by marol (2024-03-19 07:04:54)

seth · 2024-03-19 07:06:16

Yes, and probably also remove the "splash" and "quiet" paramters for more boot messages.

marol · 2024-03-19 08:51:38

So, I edited cmdline

/etc/kernel/cmdline
root=/dev/mapper/disk rootfstype=btrfs rootflags=subvol=/@ rw quiet splash noresume modprobe.blacklist=pcspkr zswap.enabled=0

After reboot nothing changed, except UUID in that [TIMEOUT] warning.

[TIME] Timed out waiting for device /dev/diskby-uuid/8b2cab04-7bdd-a493-026bf1b81928.
[DEPEND] Dependency failed for Resume from hibernation.

Here is the link to logs - https://0x0.st/XruV.txt
and to lsattr - https://0x0.st/XrS-.txt

In logs I found first mention about this UUID

Mar 17 21:23:33 marol systemd-makefs[859]: /dev/mapper/swap successfully formatted as swap (label "swap", uuid 8b2cab04-7bdd-4509-a493-026bf1b81928)

Before it was "uuid 37c1e87c...". And this uuid remains in logs. I don't understand what's going on with this hibernation.

Last edited by marol (2024-03-19 10:55:22)

seth · 2024-03-19 18:18:32

Mar 19 10:37:13 archlinux kernel: Command line: root=/dev/mapper/disk rootfstype=btrfs rootflags=subvol=/@ rw quiet splash modprobe.blacklist=pcspkr zswap.enabled=0

"noresume" is not in that commandline?
How did you supposingly change it?

The hibernation UUID changed

Mar 17 17:03:33 archlinux systemd[1]: systemd-hibernate-resume.service: Job systemd-hibernate-resume.service/start failed with result 'dependency'.
Mar 17 21:21:31 archlinux systemd-hibernate-resume-generator[177]: Reported hibernation image: ID=arch kernel=6.5.7-arch1-1 UUID=37c1e87c-ee39-4655-8495-82cbb04ac895 offset=0
Mar 17 21:23:31 archlinux systemd[1]: Dependency failed for Resume from hibernation.
Mar 17 21:23:31 archlinux systemd[1]: systemd-hibernate-resume.service: Job systemd-hibernate-resume.service/start failed with result 'dependency'.
Mar 18 09:51:51 archlinux systemd-hibernate-resume-generator[178]: Reported hibernation image: ID=arch kernel=6.7.9-arch1-1 UUID=8b2cab04-7bdd-4509-a493-026bf1b81928 offset=0
Mar 18 09:53:51 archlinux systemd[1]: Dependency failed for Resume from hibernation.
Mar 18 09:53:51 archlinux systemd[1]: systemd-hibernate-resume.service: Job systemd-hibernate-resume.service/start failed with result 'dependency'.

so

/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67

is the relevant variable that currently causes this timeout.

marol · 2024-03-19 21:14:48

seth wrote:

Mar 19 10:37:13 archlinux kernel: Command line: root=/dev/mapper/disk rootfstype=btrfs rootflags=subvol=/@ rw quiet splash modprobe.blacklist=pcspkr zswap.enabled=0
"noresume" is not in that commandline?
How did you supposingly change it?
.

Yes, it is there. And "quier splash" deleted, but arch is booting as it is not.

seth wrote:

The hibernation UUID changed
Mar 17 17:03:33 archlinux systemd[1]: systemd-hibernate-resume.service: Job systemd-hibernate-resume.service/start failed with result 'dependency'.
Mar 17 21:21:31 archlinux systemd-hibernate-resume-generator[177]: Reported hibernation image: ID=arch kernel=6.5.7-arch1-1 UUID=37c1e87c-ee39-4655-8495-82cbb04ac895 offset=0
Mar 17 21:23:31 archlinux systemd[1]: Dependency failed for Resume from hibernation.
Mar 17 21:23:31 archlinux systemd[1]: systemd-hibernate-resume.service: Job systemd-hibernate-resume.service/start failed with result 'dependency'.
Mar 18 09:51:51 archlinux systemd-hibernate-resume-generator[178]: Reported hibernation image: ID=arch kernel=6.7.9-arch1-1 UUID=8b2cab04-7bdd-4509-a493-026bf1b81928 offset=0
Mar 18 09:53:51 archlinux systemd[1]: Dependency failed for Resume from hibernation.
Mar 18 09:53:51 archlinux systemd[1]: systemd-hibernate-resume.service: Job systemd-hibernate-resume.service/start failed with result 'dependency'.
so
/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67
is the relevant variable that currently causes this timeout.

What I can or should do now? To "chattr -i"? I thought to use shred command and reinstall arch. Which is better - shred or scrub? dd didn't work in my case.

seth · 2024-03-19 21:17:29

Not in *any* of the journals you posted.

seth wrote:

How did you supposingly change it?

What *exactly* did you do?

Arch Linux

#1 2024-03-17 13:26:29

[SOLVED] Timeout waiting to mount /dev/disk-uuid

#2 2024-03-17 13:32:09

Re: [SOLVED] Timeout waiting to mount /dev/disk-uuid

#3 2024-03-17 13:47:17

Re: [SOLVED] Timeout waiting to mount /dev/disk-uuid

#4 2024-03-17 14:15:18

Re: [SOLVED] Timeout waiting to mount /dev/disk-uuid

#5 2024-03-17 14:38:04

Re: [SOLVED] Timeout waiting to mount /dev/disk-uuid

#6 2024-03-17 14:45:20

Re: [SOLVED] Timeout waiting to mount /dev/disk-uuid

#7 2024-03-17 15:56:46

Re: [SOLVED] Timeout waiting to mount /dev/disk-uuid

#8 2024-03-17 16:20:27

Re: [SOLVED] Timeout waiting to mount /dev/disk-uuid

#9 2024-03-17 22:07:07

Re: [SOLVED] Timeout waiting to mount /dev/disk-uuid

#10 2024-03-18 08:55:38

Re: [SOLVED] Timeout waiting to mount /dev/disk-uuid

#11 2024-03-18 09:28:30

Re: [SOLVED] Timeout waiting to mount /dev/disk-uuid

#12 2024-03-18 14:06:29

Re: [SOLVED] Timeout waiting to mount /dev/disk-uuid

#13 2024-03-18 15:32:18

Re: [SOLVED] Timeout waiting to mount /dev/disk-uuid

#14 2024-03-18 16:02:03

Re: [SOLVED] Timeout waiting to mount /dev/disk-uuid

#15 2024-03-18 16:14:56

Re: [SOLVED] Timeout waiting to mount /dev/disk-uuid

#16 2024-03-18 16:25:33

Re: [SOLVED] Timeout waiting to mount /dev/disk-uuid

#17 2024-03-18 16:28:54

Re: [SOLVED] Timeout waiting to mount /dev/disk-uuid

#18 2024-03-18 22:05:57

Re: [SOLVED] Timeout waiting to mount /dev/disk-uuid

#19 2024-03-18 22:28:53

Re: [SOLVED] Timeout waiting to mount /dev/disk-uuid

#20 2024-03-19 07:04:30

Re: [SOLVED] Timeout waiting to mount /dev/disk-uuid

#21 2024-03-19 07:06:16

Re: [SOLVED] Timeout waiting to mount /dev/disk-uuid

#22 2024-03-19 08:51:38

Re: [SOLVED] Timeout waiting to mount /dev/disk-uuid

#23 2024-03-19 18:18:32

Re: [SOLVED] Timeout waiting to mount /dev/disk-uuid

#24 2024-03-19 21:14:48

Re: [SOLVED] Timeout waiting to mount /dev/disk-uuid

#25 2024-03-19 21:17:29

Re: [SOLVED] Timeout waiting to mount /dev/disk-uuid

Board footer