Won’t boot after update, stuck at Loading initial ramdisk

JohnAtl · July 25, 2024, 2:02am

Just did an uneventful update using yay.
Rebooted:

Loading Linux linux-lts
Loading initial ramdisk

That’s it.

Trying to boot my snapshots doesn’t work either. The log says it can’t mount root.

A couple of excerpts (ocred from photos of the screen):


[FAILEDI
Failed to start Remount Root and Kernel File Systems.
See
systemctl
status systend-remount-fs.service' for details.

Jul 24 20:09:15 beast systemd-remount-fs[1128]: /usr/bin/mount for / exited
with exit status 32.
Jul 24 20:09:16 beast systemd-remount-fs[1134]: mount: /: fsconfig system call failed: overlay: No changes allowed in reconfigure.
Jul 24 20:09:16 beast systemd-remount-fs[1134]:
dmesg(1) may have more information after failed mount system call.
Jul 24 20:09:15 beast systemd[1]: modprobe@configfs.service: Deactivated
successfully.

It stops and allows to to enter maintenance mode, or continue booting. I entered the admin password, and was able to mount the root partition to /mnt/root and list files.
Not sure where to go from here.

Dead in the water.

Any suggestions?

pebcak · July 25, 2024, 5:53am

Personally, I would try a couple of things from a live session:

run a filesystem check
chroot into the installed system, run the update again, rebuild initramfs, regenerate grub.cfg if Grub is used
check fstab and my kernel boot options to see if they look ok.

Cphusion · July 25, 2024, 7:09am

Have you tried booting from the fallback image?

JohnAtl · July 25, 2024, 10:50am

Thanks.
Yes, it also hangs at Loading initial ramdisk, as does the non-lts kernel.

It seems anything touched by the update hangs, and all snapshots fail to mount root (though I haven’t tried really old snapshots, which I might do now).

JohnAtl · July 25, 2024, 10:51am

Thanks.
Le sigh. I think you’re right.
Maybe I should start using ddrescue to mirror my drive before updating.

JohnAtl · July 25, 2024, 12:15pm

Ran btrfs check on the root partition, no errors found.

Booted a usb and created the chroot environment, did yay, a few packages were updated, including the lts kernel. No errors. Rebooted, and it failed to mount root again.

Follow up question:I always have a little doubt about where to mount the efi partition. I have both /efi and /boot/efi. I used /boot/efi when I chrooted (actually /mnt/boot/efi since the root partition was mounted at /mnt).

I’m doing a ddrescue backup of this drive as-is, since my home folder is on it too.
It feels like I might have to reinstall, which makes me sad, as having both Intel Arc and Nvidia GPUs can make things interesting.

pebcak · July 25, 2024, 12:29pm

In EnOS that really depends what bootloader you have chosen at the time of the installation.

If systemd-boot then ESP is mounted at /efi.

If Grub then it will be mounted at /boot/efi.

So I am not sure why you are having both an /efi and a /boot/efi directory.

Could you post the output of the following commands from the live session:

sudo parted -l

efibootmgr

If you have more than one disk in your system, indicate which one houses your EnOS.

JohnAtl · July 25, 2024, 12:46pm

Thanks for that info. I use grub.

other drives

[root@EndeavourOS ~]# parted -l
Model: ATA WDC WD161KRYZ-01 (scsi)
Disk /dev/sda: 16.0TB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                  Flags
 1      1049kB  16.0TB  16.0TB               zfs-8a3a445d8e242a23
 9      16.0TB  16.0TB  8389kB


Model: ATA WDC WD161KRYZ-01 (scsi)
Disk /dev/sdb: 16.0TB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                  Flags
 1      1049kB  16.0TB  16.0TB               zfs-58faff62f6271cff
 9      16.0TB  16.0TB  8389kB


Model: ATA WDC WD161KRYZ-01 (scsi)
Disk /dev/sdc: 16.0TB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                  Flags
 1      1049kB  16.0TB  16.0TB               zfs-78639b568f55ee69
 9      16.0TB  16.0TB  8389kB


Model: ATA WDC WD161KRYZ-01 (scsi)
Disk /dev/sdd: 16.0TB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                  Flags
 1      1049kB  16.0TB  16.0TB               zfs-d0b33e53166bed1e
 9      16.0TB  16.0TB  8389kB


Model: Sabrent  (scsi)
Disk /dev/sde: 1000GB
Sector size (logical/physical): 512B/2048B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name  Flags
 1      1049kB  1000GB  1000GB  btrfs


Model: CT2000P5PSSD8 (nvme)
Disk /dev/nvme0n1: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags: 

Number  Start  End     Size    File system  Flags
 1      0.00B  2000GB  2000GB  btrfs


Model: CT2000P5PSSD8 (nvme)
Disk /dev/nvme2n1: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags: 

Number  Start  End     Size    File system  Flags
 1      0.00B  2000GB  2000GB  btrfs


Model: PNY USB 3.2.1 FD (scsi)
Disk /dev/sdg: 31.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size   Type     File system  Flags
 2      2595MB  2760MB  165MB  primary  fat16        esp

The EOS drive:

Model: CT2000P5PSSD8 (nvme)
Disk /dev/nvme1n1: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name         Flags
 1      1049kB  538MB   537MB   fat32                     boot, esp
 2      538MB   385GB   384GB   btrfs        endeavouros
 4      385GB   2000GB  1616GB  btrfs

Output of efibootmgr:

[root@EndeavourOS ~]# efibootmgr 
BootCurrent: 0007
Timeout: 1 seconds
BootOrder: 0000,0006,0007
Boot0000* endeavouros   HD(1,GPT,495ce9d0-9b03-4f87-b09a-0eb40085ba90,0x800,0x100000)/File(\EFI\endeavouros\grubx64.efi)
Boot0006* debian        HD(1,GPT,495ce9d0-9b03-4f87-b09a-0eb40085ba90,0x800,0x100000)/File(\EFI\debian\shimx64.efi) File(.)
Boot0007* UEFI: PNY USB 3.2.1 FD PMAP   PciRoot(0x0)/Pci(0x14,0x0)/USB(9,0)/USB(3,0)/CDROM(1,0x4d5940,0x4ea98)0000424f

The debian entry is left over from long ago.

JohnAtl · July 25, 2024, 6:49pm

I reinstalled EOS and replaced the existing partition, so fallout was minimal.

I’m in the process of reinstalling everything now.

Thanks for the help!

system · July 29, 2024, 12:47pm

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.