Arch Linux

stephenboston

Banned

Registered: 2020-09-27

Posts: 46

after install using systemd-boot : reboot into emergency shell

After installation and reboot:

:: running early hook [udev]
     Starting version 240.3-2-arch
     :: running hook [udev]
     :: Triggering uevents
     ERROR: device '' not found. Skipping fsck.
     :: mount '' on real root
     mount: /new_root: no filesystem type specified
     You are now being dropped into an emergency shell
    [rootfs]#

From here I cannot find my boot directory or anything i recognize from the installation process.

For example, during install I explicitly created /etc/hostname but that file does not exist now.

Last edited by stephenboston (2021-05-22 21:57:59)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,729

Re: after install using systemd-boot : reboot into emergency shell

Looks to me like you didn't configure systemd-boot correctly, or at all.

stephenboston

Banned

Registered: 2020-09-27

Posts: 46

Re: after install using systemd-boot : reboot into emergency shell

Aye. Looks like that, I know, and thank you very much,  but using here

https://wiki.archlinux.org/title/Systemd-boot

as a guide, and then :

bootctl --path=/boot install
Created "/boot/EFI".
Created "/boot/EFI/systemd".
Created "/boot/EFI/BOOT".
Created "/boot/loader".
Created "/boot/loader/entries".
Created "/boot/EFI/Linux".
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/boot/EFI/systemd/systemd-bootx64.efi".
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/boot/EFI/BOOT/BOOTX64.EFI".
Random seed file /boot/loader/random-seed successfully written (512 bytes).
Not installing system token, since we are running in a virtualized environment.
Created EFI boot entry "Linux Boot Manager".

cd boot
[root@archiso boot]# ls
initramfs-linux-fallback.img  initramfs-linux.img  loader  vmlinuz-linux

loader.conf

  default  arch.conf
  timeout  4
  console-mode max
  editor   no
 

loader/arch.conf

  title   Arch Linux
  linux   /vmlinuz-linux
  initrd  /initramfs-linux.img
  options root="LABEL=arch_os" rw
 
:
I get what looks to be nothing.

Where have these files gone?

Last edited by stephenboston (2021-05-22 22:44:03)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,729

Re: after install using systemd-boot : reboot into emergency shell

Are you getting confused on what's inside the chroot and what's outside?

stephenboston

Banned

Registered: 2020-09-27

Posts: 46

Re: after install using systemd-boot : reboot into emergency shell

Are you getting confused on what's inside the chroot and what's outside?

I followed the instructions in https://wiki.archlinux.org/title/Installation_guide

In the above snippet I had  issued the arch-chroot  just before issuing bootctl.

How would I know that I have made the error you're suggesting?

loqs

Member

Registered: 2014-03-06

Posts: 19,011

Re: after install using systemd-boot : reboot into emergency shell

Systemd-boot#Adding_loaders

systemd-boot will automatically check at boot time for Windows Boot Manager at the location /EFI/Microsoft/Boot/Bootmgfw.efi, UEFI shell /shellx64.efi and EFI Default Loader /EFI/BOOT/bootx64.efi, as well as specially prepared kernel files found in /EFI/Linux/. When detected, corresponding entries with titles auto-windows, auto-efi-shell and auto-efi-default, respectively, will be generated. These entries do not require manual loader configuration. However, it does not auto-detect other EFI applications (unlike rEFInd), so for booting the Linux kernel, manual configuration entries must be created.

Emphasis added.

GeorgeJP

Member

From: Czech Republic

Registered: 2020-01-28

Posts: 190

Re: after install using systemd-boot : reboot into emergency shell

loader.conf

  default  arch.conf
  timeout  4
  console-mode max
  editor   no
 

loader/arch.conf

  title   Arch Linux
  linux   /vmlinuz-linux
  initrd  /initramfs-linux.img
  options root="LABEL=arch_os" rw

Paths should be:

loader/loader.conf
loader/entries/arch.conf

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,729

Re: after install using systemd-boot : reboot into emergency shell

You do realize that "arch_os" is just a placeholder, right? You put in the actual label you used.

stephenboston

Banned

Registered: 2020-09-27

Posts: 46

Re: after install using systemd-boot : reboot into emergency shell

Oops sorry. I was cutting from the instructions I followed.

Here are the actual files :

cat loader.conf

  default arch.conf
  timeout 4 
  console-mode max

cat entries/arch.conf
  title Arch Linux
  linux /vmlinuz-linux
  initrd /initramfs-linux.img
  options root=PARTUUID=22f819bc-50bb-c14a-v458-649b34444aa2 

where the partuuid is taken from

blkid -s PARTUUID -o value /dev/sda2

and /dev/sda2 will be mounted to /

I must have botched something along the way. I will run through the installation again. I'm getting pretty quick at it.

Thanks for your response.

Last edited by stephenboston (2021-05-23 02:44:20)

stephenboston

Banned

Registered: 2020-09-27

Posts: 46

Re: after install using systemd-boot : reboot into emergency shell

loader.conf

  default  arch.conf
  timeout  4
  console-mode max
  editor   no
 

loader/arch.conf

  title   Arch Linux
  linux   /vmlinuz-linux
  initrd  /initramfs-linux.img
  options root="LABEL=arch_os" rw

Paths should be:

loader/loader.conf

loader/entries/arch.conf

Thanks. Yes. I did have the files in the correct directories. It is my post that is wrong.

GeorgeJP

Member

From: Czech Republic

Registered: 2020-01-28

Posts: 190

Re: after install using systemd-boot : reboot into emergency shell

Post output of lsblk -f