2
systemd-boot not finding an initrd, but finding a different one which is in the same place, what to do?(self.archlinux)
Hello!
The following is my arch linux entry file (/boot/efi/loader/entries/arch.conf) in systemd-...
since 3 years ago
3 of 3
Tip Reveddit Real-Time can notify you when your content is removed.
your account history
Tip Check if your account has any removed comments.
view my removed comments you are viewing a single comment's thread.
view all comments
lsblk will output something like this:
bash lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 2.7T 0 disk └─sda1 8:1 0 2.7T 0 part /shared zram0 254:0 0 4G 0 disk [SWAP] nvme1n1 259:0 0 465.8G 0 disk /home/user nvme0n1 259:1 0 232.9G 0 disk ├─nvme0n1p1 259:2 0 232.6G 0 part / ├─nvme0n1p2 259:3 0 8M 0 part └─nvme0n1p3 259:4 0 300M 0 part /bootbasically if you mounted something during system setup over root/boot it might be writing your initrd to a different disk that isn't available during boot. so you update the package get a new initrd and its stored somewhere that isn't mounted until much later in the boot process.
you can also check cat /etc/fstab
the only filesystems that are actually mounted are the ESP (/boot/efi) and the root partition (/) nothing else, fstab (which i made with genfstab) also only shows those two and correct me if im wrong but arent they both available during boot?
yeah i was just making a guess for something you should check. not that 100% would be the problem about a billion things could be causing this depending what you did. =)