Hi.
I just upgraded my system using yay. The system recommended my to reboot since “core” packages were upgraded (linux kernel) and so I did.
But on booting all I see is; a start job is running for /dev/disk-by-uuid/3b2fa9a7-9b9b-444c-aa78-5787cf0e868c. I wait for a few minutes but nothing happens.
I’m running EndeavourOS Gallileo Neo (new install) along with dracut and refind as boot manager.
Here’s what I’ve done till now;
arch-chroot from a Live USB
pacman -Syu: No updates to install
sudo dracut-rebuild: Results in no errors that I can see. Can share the logs if needed.
Checked that UUID of the disk is the same in /etc/fstab and what shows in fdisk -l
Result of fdisk -l
The error occurs when booting from nvme1 disks endeavourOS.
Note that I have another EOS installation on the second disk that I’m writing from.
❯ sudo fdisk -l
Disk /dev/nvme1n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: WD Blue SN580 2TB
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 3D153D11-4706-4444-9F5B-A5037EF172C0
Device Start End Sectors Size Type
/dev/nvme1n1p1 4096 2052095 2048000 1000M EFI System
/dev/nvme1n1p2 2052096 3888569126 3886517031 1.8T Linux filesystem
/dev/nvme1n1p3 3888569127 3907024064 18454938 8.8G Linux swap
Disk /dev/nvme0n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: Micron_2450_MTFDKBA1T0TFK
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 9CAF4CBF-217B-4550-BF9E-45ACF829C282
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 534527 532480 260M EFI System
/dev/nvme0n1p2 534528 567295 32768 16M Microsoft reserved
/dev/nvme0n1p3 567296 974845951 974278656 464.6G Microsoft basic data
/dev/nvme0n1p4 974845952 976494591 1648640 805M Windows recovery environment
/dev/nvme0n1p5 976496640 1228154879 251658240 120G Linux filesystem
/dev/nvme0n1p6 1228154880 1902096383 673941504 321.4G Linux filesystem
/dev/nvme0n1p7 1902096384 1952428031 50331648 24G Linux swap
/dev/nvme0n1p8 1953861632 1999998975 46137344 22G Microsoft basic data
/dev/nvme0n1p9 1999998976 2000408575 409600 200M Windows recovery environment
Disk /dev/sda: 15.23 GiB, 16357785600 bytes, 31948800 sectors
Disk model: Flash Disk
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x4e4305b5
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 64 5069119 5069056 2.4G 0 Empty
/dev/sda2 5069120 5390655 321536 157M ef EFI (FAT-12/16/32)
Here’s what I use to arch-chroot from the Live USB
sudo mount /dev/nvme1n1p2 /mnt
sudo mount -t proc /proc /mnt/proc
sudo mount -t sysfs /sys /mnt/sys
sudo mount -o bind /dev /mnt/dev
sudo mount -o bind /run /mnt/run
sudo mount /dev/nvme0n1p1 /mnt/boot/efi
sudo arch-chroot /mnt
Here’s the contents of fstab
As I said in the first post, the UUID is the same from lsblk so I’m quite confused as to what’s wrong here.
❯ cat /mnt/etc/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=7016-0637 /efi vfat fmask=0137,dmask=0027 0 2
UUID=3b2fa9a7-9b9b-444c-aa78-5787cf0e868c / ext4 noatime 0 1
UUID=def17d23-50d4-4105-9114-bb4d0a6390dc swap swap defaults 0 0
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
i can reproduce this error aswell only if i boot into the LTS 6.12.26 and 27 kernel picking the normal 6.14 or one of the (Fallbacks even the lts) i go trough normaly
