Just some info to read. Might give some ideas?
Many thanks.
The problem is not that my PC won’t boot. The problem is that I have to intervene manually after reaching switch root. I don’t understand that
Strange.
BTW, have you compared the UUIDs of fstab to the output of command
lsblk -fm
?
2 Likes
It looks identical
❯ lsblk -fm
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS SIZE OWNER GROUP MODE
sda 931,5G root disk brw-rw----
└─sda1 ext4 1.0 Mediathek 9b940cbe-8123-4748-91f3-8116edd8bd43 246,7G 68% /srv/nfsv4/Share 931,5G root disk brw-rw----
/run/media/swh/Mediathek
sdb ext4 1.0 Stuff 70357a40-3800-404d-a68e-dc5b32c83377 268G 66% /srv/nfsv4/Filme 931,5G root disk brw-rw----
/run/media/swh/Stuff
sdc 223,6G root disk brw-rw----
└─sdc1 ext4 1.0 SSD d291ee0f-5b2c-4ea1-8fa9-193c8968f2be 199,6G 4% /srv/nfsv4/Handbrake 223,6G root disk brw-rw----
/run/media/swh/SSD
sdd 3,6T root disk brw-rw----
└─sdd1 ext4 1.0 NFS 1054c3d8-e9a8-4ef9-bafc-a61beb042571 2,2T 33% /srv/nfsv4/Mediathek 3,6T root disk brw-rw----
/run/media/swh/NFS
nvme0n1 232,9G root disk brw-rw----
├─nvme0n1p1 vfat FAT32 D3E2-C3D4 309M 38% /efi 500M root disk brw-rw----
└─nvme0n1p2 ext4 1.0 de0eeb1f-095d-408b-b6c3-ebda58df6d41 142,2G 32% / 232,4G root disk brw-rw----
nvme1n1 931,5G root disk brw-rw----
└─nvme1n1p1 ext4 1.0 74af6462-ba4b-48bf-993b-164ba88fbabb 679,4G 21% /home 931,5G root disk brw-rw----
Oh, looks like a mountpoint is assigned to sdb which is not a partition like others. I think it should be sdb1.
Edit: some places have two mountpoints, seems redundant (or wrong)?
2 Likes
I also have that bug that the boot process is stuck after switch root is started, there is a blinking cursor in the lower right screen corner. It continues without any delays after I hit enter in my case.
It’s not consistent across each boot process, sometimes it boots without that delay with no intervention required.
Strange, indeed. But luckily a small one.
2 Likes
Luckily, I am not the only one.
Exactly the same behavior as yours.
It’s really very strange, I just don’t understand why it’s like that. I think since an update a week ago
Hard to understand. This drive has been partitioned like this for almost 10 years and has been in operation with EOS for 4 years without any complications
❯ sudo lsblk
[sudo] Passwort für swh:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 931,5G 0 disk
└─sda1 8:1 0 931,5G 0 part /srv/nfsv4/Share
/run/media/swh/Mediathek
sdb 8:16 0 931,5G 0 disk /srv/nfsv4/Filme
/run/media/swh/Stuff
sdc 8:32 0 223,6G 0 disk
└─sdc1 8:33 0 223,6G 0 part /srv/nfsv4/Handbrake
/run/media/swh/SSD
sdd 8:48 0 3,6T 0 disk
└─sdd1 8:49 0 3,6T 0 part /srv/nfsv4/Mediathek
/run/media/swh/NFS
nvme0n1 259:0 0 232,9G 0 disk
├─nvme0n1p1 259:1 0 500M 0 part /efi
└─nvme0n1p2 259:3 0 232,4G 0 part /
nvme1n1 259:2 0 931,5G 0 disk
└─nvme1n1p1 259:4 0 931,5G 0 part /home
I am running these drives as a NFS drive so that I can access it with my Linux Sat-Box. It only contains movies, documentaries, concert recordings and stuff like that
With the difference that I’m using BTRFS instead of EXT4 on a single nvme
$ less /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=... /boot/efi vfat fmask=0137,dmask=0027 0 2
UUID=... / btrfs subvol=/@,noatime,compress=zstd 0 0
UUID=... /home btrfs subvol=/@home,noatime,compress=zstd 0 0
UUID=... /var/cache btrfs subvol=/@cache,noatime,compress=zstd 0 0
UUID=... /var/log btrfs subvol=/@log,noatime,compress=zstd 0 0
UUID=... swap swap defaults 0 0
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
edit: uuids removed for better readability.
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
nvme0n1 259:0 0 931.5G 0 disk
├─nvme0n1p1 259:1 0 1G 0 part /boot/efi
├─nvme0n1p2 259:2 0 896.1G 0 part /var/log
│ /var/cache
│ /home
│ /
└─nvme0n1p3 259:3 0 34.4G 0 part [SWAP]
1 Like
Ok, but I can assume that this will not cause a serious problem.
Thanks for your assessment!
Are you and @1093i3511 using systemd-boot?
I am using systemd dracut. Standard EOS installation
So that is systemd-boot? I see in @1093i3511 it looks like grub? Just wondering if the issue was only on one or other bootloader?
Edit: Because I don’t have it on grub.
That could be a systemd thing. I simply don’t know how a boot process with systemd or grub works and what the differences are. That’s where I completely reach my limits
I see an older post where downgrading systemd was the solution.
Edit: It’s very old though.
Edit2: I suppose one could try downgrading systemd maybe? 
I’m using grub.
The article is from 2017 and we are now at version 257-1
Would be a possibility but @1093i3511 has the same problem with grub. So I don’t think that’s the problem
EDIT: Maybe Ill try another kernel. Normally i am using zen
Additionally it’s not a failure of starting switch root, I’s just … delayed until the enter is pressed.
Also, not on every boot. I was just checking for orphaned packages and such, did a reboot and it went straight to the login prompt.
I’m using the zen kernel as well.
1 Like
I have never noticed this behavior during a reboot. As you say, every now and then during a boot