[SOLVED] fail resume device '/dev/disk/by-uuid/...': No such file

ruppfv · 2024-04-21 19:17:10

I see this message on the initialization it's been weeks,

Failed to stat resume device `/dev/disk/by-uuid/b0aacBab-2d0c-4ce7-97ec-811055fcdf25': No such file or directory

but it always started normally after this message disappeared. Yesterday I added

GTK_IM_MODULE=xim

on

/etc/environment

, and suddenly, when I rebooted my arch, it got stuck on this error message at the initialization. I booted a live USB and removed this line from /etc/environment, as I thought it was the main problem, but it still doesn't boot, and is still stuck at this message. I'm not sure if the problem is what the message says itself or if it's a remnant from the line I added on environment.

blkid output:

/dev/mapper/ventoy: BLOCK_SIZE="2048" UUID="2024-02-16-18-43-32-00" LABEL="Lubuntu 22.04.4 LTS amd64" TYPE="iso9660" PTUUID="b898b0c3-ed82-4099-a75a-c2c1fa62c573" PTTYPE="gpt"                                                                                             
/dev/loop1: BLOCK_SIZE="131072" TYPE="squashfs"                                                                                       
/dev/sdb1: LABEL="Ventoy" UUID="4E21-0000" BLOCK_SIZE="512" TYPE="exfat" PARTUUID="ca2c5098-01"
/dev/loop6: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop4: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop2: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop0: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/sda4: BLOCK_SIZE="512" UUID="8E0A85270A850D81" TYPE="ntfs" PARTUUID="fac80c67-12b8-4e1f-b840-32115f9e7ad9"
/dev/sda2: PARTLABEL="Microsoft reserved partition" PARTUUID="918891c4-7673-43d1-b0d3-e6f36ed2356e"
/dev/sda7: UUID="5c21dcfd-d733-4555-913d-5ff888984932" TYPE="swap" PARTUUID="34e3492a-3740-4513-b62e-461a1b8459d8"
/dev/sda5: LABEL_FATBOOT="NO_LABEL" LABEL="NO_LABEL" UUID="6BE3-EDCE" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="13814770-c10b-c84c-8663-20a6a834c6e5"
/dev/sda3: BLOCK_SIZE="512" UUID="0C0C924C0C923126" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="78428d20-2388-43c4-b490-8462d8c3521a"
/dev/sda1: UUID="E68F-2CCB" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="0c6124c4-13ca-4f92-923c-78b1a618e2bb"
/dev/sda6: UUID="f6e6ee1c-d1b1-412f-ac00-a05051154f72" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="6b108003-444a-034b-b83a-29d42c2507f9"
/dev/zram0: UUID="51ba6e38-8eff-4637-a590-5c9531fe8742" TYPE="swap"
/dev/loop5: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop3: BLOCK_SIZE="131072" TYPE="squashfs"

my 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>
UUID=6BE3-EDCE                            /boot/efi      vfat    umask=0077 0 2
UUID=f6e6ee1c-d1b1-412f-ac00-a05051154f72 /              ext4    defaults,noatime 0 1
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0
UUID=5c21dcfd-d733-4555-913d-5ff888984932 none swap defaults 0 0

Last edited by ruppfv (2024-04-28 04:04:15)

seth · 2024-04-21 21:10:14

Yesterday I added

This didn't cause the spurious resume-attempts.

Add "noresume" to your kernel commandline to prevent this.
Do you otherwise actually use https://wiki.archlinux.org/title/Power_ … ibernation ?

ruppfv · 2024-04-21 21:41:14

I ran

sudo arch-chroot /mnt sysctl -w resume=noresume

to modify the value, but it returned the error

sysctl: cannot stat /proc/sys/resume: No such file or directory

. I am pretty sure I am not missing anything. Any idea?

Last edited by ruppfv (2024-04-21 21:42:01)

seth · 2024-04-21 21:42:11

https://wiki.archlinux.org/title/Kernel_parameters
Edit: and literally "noresume", not! "resume=noresume"

Last edited by seth (2024-04-21 21:43:00)

ruppfv · 2024-04-21 22:12:53

Thank you Seth! It worked, I appreciate your help.

The error message disappeared at the initialization, but it still doesn't start and get in the system. This makes me think the problem really was the changes in

/etc/environment

. I wonder if I might create a new topic for that.

Last edited by ruppfv (2024-04-21 22:14:22)

seth · 2024-04-21 22:19:30

Can you boot the multi-user.target (2nd link below)?
Setting the GTK_IM_MODULE won't have broken anything, even if you corrupted /etc/environment "somehow", I doubt that had any impact.

If you can't even boot the multi-user.target, try to reboot from the failed boot using the https://wiki.archlinux.org/title/Keyboa … el_(SysRq) to preserve the journal so you can inspect it from the iso to see what actually failed.

ruppfv · 2024-04-22 00:30:25

Yes, I can boot it like that normally

seth · 2024-04-22 06:48:51

Only the GUI target fails, if you

# systemctl start graphical.target; sleep 60; systemctl isolate multi-user.target

the system should™ try to start the GUI and after a minute return to the multi-user.target - the system journal will then likely tell you what's wrong and you can also upload it

sudo journalctl -b | curl -F 'file=@-' 0x0.st

What is your graphical.target? GDM, SDDM, ligthdm, startx, …?

ruppfv · 2024-04-22 15:26:16

my graphical manager is SDDM.

I doesn't seem like the GUI started, and it didn't even came back after 60 seconds. I had to turn it off and on again.

journal:
https://0x0.st/XodL.txt

seth · 2024-04-22 19:21:15

The journal of that boot never reached the graphcial.target?

abr 22 12:16:52 ruppfv login[448]: LOGIN ON tty1 BY ruppfv
…
abr 22 12:17:24 ruppfv sudo[799]:   ruppfv : TTY=tty1 ; PWD=/home/ruppfv ; USER=root ; COMMAND=/usr/bin/journalctl -b

But inbetween there isn't eg. you running "sudo systemctl start graphcial.target" - the "#" indicates "do this as root" (in contrast to "$")

ruppfv · 2024-04-22 21:53:52

When I run

# systemctl start graphical.target; sleep 60; systemctl isolate multi-user.target

I have to turn my computer off before running journal because when I run "systemctl ..." I get sent to a black terminal with nothing written on it, where I can't type anything. I turned it off between the code and the journal, my bad.

But how could I run journal without turning it off, since I can't get out of that terminal?

seth · 2024-04-22 22:01:15

Boot the regular graphical target, reboot using https://wiki.archlinux.org/title/Keyboa … el_(SysRq) (not the power button) and then into the multi-user.target and post the journal of the previous boot ("-1") from there.

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

ruppfv · 2024-04-22 23:59:45

edit: I got it after modifying journald.conf field "Storage=auto" to "Storage=persistent"

journal:
https://0x0.st/Xo7w.txt

Last edited by ruppfv (2024-04-23 00:23:04)

seth · 2024-04-23 06:15:26

SDDM, X11 simply fails

abr 22 21:16:23 ruppfv sddm[682]: Failed to read display number from pipe
abr 22 21:16:23 ruppfv sddm[682]: Display server stopping...
abr 22 21:16:23 ruppfv sddm[682]: Attempt 1 starting the Display server on vt 2 failed
abr 22 21:16:25 ruppfv sddm[682]: Display server starting...
abr 22 21:16:25 ruppfv sddm[682]: Writing cookie to "/run/sddm/xauth_XhtJkg"
abr 22 21:16:25 ruppfv sddm[682]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_XhtJkg -noreset -displayfd 16
abr 22 21:16:25 ruppfv sddm[682]: Failed to read display number from pipe
abr 22 21:16:25 ruppfv sddm[682]: Display server stopping...
abr 22 21:16:25 ruppfv sddm[682]: Attempt 2 starting the Display server on vt 2 failed
abr 22 21:16:27 ruppfv sddm[682]: Display server starting...
abr 22 21:16:27 ruppfv sddm[682]: Writing cookie to "/run/sddm/xauth_XhtJkg"
abr 22 21:16:27 ruppfv sddm[682]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_XhtJkg -noreset -displayfd 16
abr 22 21:16:27 ruppfv sddm[682]: Failed to read display number from pipe
abr 22 21:16:27 ruppfv sddm[682]: Display server stopping...
abr 22 21:16:27 ruppfv sddm[682]: Attempt 3 starting the Display server on vt 2 failed
abr 22 21:16:27 ruppfv sddm[682]: Could not start Display server on vt 2

Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General

ruppfv · 2024-04-23 15:28:33

Hey, I got it. The problem was in etc/X!!/Xorg.conf.d/10-evdev.conf!

Almost all the quotation marks (") were 'corrupted' I'd say. There was a little square where all these should be.

After fixing this I could run

start graphical.target

and it would work normally. Thank you seth!!

Last edited by ruppfv (2024-04-23 15:30:10)

V1del · 2024-04-23 15:41:41

What are you doing in that file and what are it's contents? It should probably not exist in the first place. evdev has long been deprecated and replaced with libinput.

ruppfv · 2024-04-27 01:40:08

I don't remember. After that I updated my system and it was no longer there.

I don't know how this happened since I update my system almost every week, so, for how long it has been deprecated?

seth · 2024-04-27 06:56:03

https://man.archlinux.org/man/extra/xf8 … evdev.4.en is't *really* deprecated but the default is https://archlinux.org/packages/extra/x8 … t-libinput

At some point in the past you had https://archlinux.org/packages/extra/x8 … put-evdev/ which ships usr/share/X11/xorg.conf.d/10-evdev.conf
Then you removed it, but the config stayed behind where it did mostly nothing until a systemd-provide update hook triggered udevadm

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

ruppfv · 2024-04-28 04:04:54

Done. Thank you for the advice

Arch Linux

#1 2024-04-21 19:17:10

[SOLVED] fail resume device '/dev/disk/by-uuid/...': No such file

#2 2024-04-21 21:10:14

Re: [SOLVED] fail resume device '/dev/disk/by-uuid/...': No such file

#3 2024-04-21 21:41:14

Re: [SOLVED] fail resume device '/dev/disk/by-uuid/...': No such file

#4 2024-04-21 21:42:11

Re: [SOLVED] fail resume device '/dev/disk/by-uuid/...': No such file

#5 2024-04-21 22:12:53

Re: [SOLVED] fail resume device '/dev/disk/by-uuid/...': No such file

#6 2024-04-21 22:19:30

Re: [SOLVED] fail resume device '/dev/disk/by-uuid/...': No such file

#7 2024-04-22 00:30:25

Re: [SOLVED] fail resume device '/dev/disk/by-uuid/...': No such file

#8 2024-04-22 06:48:51

Re: [SOLVED] fail resume device '/dev/disk/by-uuid/...': No such file

#9 2024-04-22 15:26:16

Re: [SOLVED] fail resume device '/dev/disk/by-uuid/...': No such file

#10 2024-04-22 19:21:15

Re: [SOLVED] fail resume device '/dev/disk/by-uuid/...': No such file

#11 2024-04-22 21:53:52

Re: [SOLVED] fail resume device '/dev/disk/by-uuid/...': No such file

#12 2024-04-22 22:01:15

Re: [SOLVED] fail resume device '/dev/disk/by-uuid/...': No such file

#13 2024-04-22 23:59:45

Re: [SOLVED] fail resume device '/dev/disk/by-uuid/...': No such file

#14 2024-04-23 06:15:26

Re: [SOLVED] fail resume device '/dev/disk/by-uuid/...': No such file

#15 2024-04-23 15:28:33

Re: [SOLVED] fail resume device '/dev/disk/by-uuid/...': No such file

#16 2024-04-23 15:41:41

Re: [SOLVED] fail resume device '/dev/disk/by-uuid/...': No such file

#17 2024-04-27 01:40:08

Re: [SOLVED] fail resume device '/dev/disk/by-uuid/...': No such file

#18 2024-04-27 06:56:03

Re: [SOLVED] fail resume device '/dev/disk/by-uuid/...': No such file

#19 2024-04-28 04:04:54

Re: [SOLVED] fail resume device '/dev/disk/by-uuid/...': No such file

Board footer