[Solved] systemd-boot: Root device not found

lasombra · 2016-11-15 14:49:30

I setup a new box with Arch using systemd-boot but when booting the system I get an error and basically stuck in emergency mode:

[ TIME ] Timeout waiting for device dev-gpt\x2dauto\x2droot.device
[DEPEND] Dependency failed for Initrd Root Device
[DEPEND] Dependency failed for Root Partition
[DEPEND] Dependency failed for Initrd Root File System
[DEPEND] Dependency failed for Reload Configuration from the Real Root
[DEPEND] Dependency failed for File System Check on /dev/gpt-auto-root

I followed the instruction in the https://wiki.archlinux.org/index.php/Systemd-boot and my esp/loader/entries/arch.conf looks like this:

title          Arch Linux
linux          /vmlinuz-linux
initrd         /initramfs-linux.img
options        root=UUID=3952e295-b7v6-4ee9-be68-8f2b037fsbe0 rw

fstab looks like this

#/dev/sda2
UUID=3952e295-b7v6-4ee9-be68-8f2b037fsbe0    /      ext4   rw,relatime,data=ordered    0 1

#/dev/sda1 LABEL=ESP
UUID=3E22-B7AB                               /esp   vfat   rw,relatime,dmask=0022,codepage=437,iocharset=iso8859-1,errors=remount-ro  0 2
#/dev/sda3
UUID=243e23f2-c2de-40ad-b07c-9780b7ce140f    none    swap   defaults                  0 0

Any clue what I am doing wrong?

Last edited by lasombra (2016-11-22 10:50:20)

Scimmia · 2016-11-15 14:51:56

UUID and PARTUUID are two different things.

lasombra · 2016-11-15 18:09:58

Right, was a typo in my post - corrected. Issue still persists and still no clue what is wrong

pekka · 2016-11-15 20:08:30

typos

rw, relatime,dmask=0.... "white space"

ext4 / re,realtime,data=ordered 0 1 "/"

and
re " ro or rw "
realtime "relatime"

lasombra · 2016-11-15 22:29:16

Thanks to point out the typos but I just wrote it off bad. The original data is actually generate with genfstab so it's fine. Any other idea what could be the issue?

jasonwryan · 2016-11-15 22:33:18

lasombra wrote:

Thanks to point out the typos but I just wrote it off bad.

Please make more of an effort: this sort of thing just wastes people's time and goodwill. Rather than type things out by hand, use a paste service: https://wiki.archlinux.org/index.php/Li … in_clients

elkoraco · 2016-11-15 23:06:29

UUID=3E22-B7AB                               /esp   vfat   rw,relatime,dmask=0022,codepage=437,iocharset=iso8859-1,errors=remount-ro  0 2

this shouldn't be mounted as /esp but as /boot

lasombra · 2016-11-16 06:12:43

@jasonwryan: I understand and thanks for pointing it out. Unfortunately due to another issue I also do not have internet access with the affected computer.

@elkorako: According to https://wiki.archlinux.org/index.php/EF … unt_Points it can be mounted in another place than esp. Hover I changed it to see it makes any differences and it does not. I still run into the same issue. I believe it must have something to do with the systemd-gpt-auto-generator but that's only my guess and google does note help me any further with my error...

Head_on_a_Stick · 2016-11-16 07:50:21

Please post the output of:

# parted -l
# efibootmgr -v

These commands can be run from the Arch live ISO and a URL that can be posted here may be generated with a pastebin client, as noted by jasonwryan.

EDIT: sorry, I missed this bit:

I also do not have internet access with the affected computer

How do you expect to install Arch without an internet connection?

Last edited by Head_on_a_Stick (2016-11-16 07:51:43)

lasombra · 2016-11-16 08:19:35

I did the initial setup while I was using wifi-menu, which does not work anymore -as mentioned this is another issue which does not concern me much at the moment. First want to get the system booted correctly, then I can deal with the connection issue. Here is the parted -l output

Model: ATA LITEON CV1-8B256 (scsi)
Disk /dev/sda: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size    File system     Name                  Flags
 1      1049kB  106MB  105MB   fat32           EFI system partition  boot, esp
 2      106MB   222GB  222GB   ext4            Linux filesystem
 3      222GB   256GB  34.4GB  linux-swap(v1)  Linux swap


Model:   (scsi)
Disk /dev/sdb: 3898MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  3898MB  3897MB  primary  fat32        boot, lba

efibootmgr -v

BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0003,2001,0001,2002,2003
Boot0000* Linux Boot Manager	HD(1,GPT,b62e7883-65d2-41da-a104-2568ceb7d362,0x800,0x32000)/File(\EFI\systemd\systemd-bootx64.efi)
Boot0001* Command Linpus lite	HD(1,GPT,b62e7883-65d2-41da-a104-2568ceb7d362,0x800,0x32000)/File(\EFI\Boot\bootx64.efi)RC
Boot0002* USB HDD: Generic USB Storage	PciRoot(0x0)/Pci(0x14,0x0)/USB(1,0)/HD(1,MBR,0x61,0x800,0x742477)RC
Boot0003* SystemdBootx64	PciRoot(0x0)/Pci(0x17,0x0)/Sata(0,0,0)/HD(1,GPT,b62e7883-65d2-41da-a104-2568ceb7d362,0x800,0x32000)/File(\EFI\systemd\systemd-bootx64.efi)A01 ..
Boot0004* grub	HD(1,GPT,b62e7883-65d2-41da-a104-2568ceb7d362,0x800,0x32000)/File(\EFI\grub\grubx64.efi)
Boot2001* EFI USB Device	RC
Boot2002* EFI DVD/CDROM	RC
Boot2003* EFI Network	RC

Head_on_a_Stick · 2016-11-16 08:27:47

Did you create those "Command Linpus lite" and "SystemdBootx64" NVRAM entries yourself?

I think the message in the OP is from systemd itself so the bootmanager has already done it's job by then.

Just to be sure, you could try deleting the extraneous entries:

# efibootmgr -b 0003 -B
# efibootmgr -b 0001 -B

Then recreate the systemd-boot entry with:

# bootctl install
# bootctl update

lasombra · 2016-11-16 08:54:37

I did as Head_on_a_Stick suggested but unfortunately I still run into the same issue.

When I boot back to my Arch USB Stick I have these entries back -> so for some reason these entries you mentioned are created automatically.

pekka · 2016-11-16 19:44:14

lasombra wrote:

Model: (scsi)
Disk /dev/sdb: 3898MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 3898MB 3897MB primary fat32 boot, lba

What is dev/sdb , usb-stick.memory card ...
Get off that ?

Head_on_a_Stick · 2016-11-16 22:02:13

Try (re)moving /etc/fstab -- your partition configuration should boot without that file but systemd will mount the ESP to /boot -- will the system start normally then?

Also:

lasombra wrote:

basically stuck in maintenance mode

What exactly does this mean?

Cthulu201 · 2016-11-17 01:08:22

was /dev/sda1 mounted to /mnt/boot in arch-chroot before bootctl install was ran?

lasombra · 2016-11-17 06:10:36

@Head_on_a_stick: Already tried that but did not make any difference - I moved fstab away but still have the same issue. With "Maintenance Mode" I meant "Emergency mode"

@Cthulu201: yes it was.

lasombra · 2016-11-17 11:25:28

pekka wrote:

What is dev/sdb , usb-stick.memory card ...
Get off that ?

yes a memory stick

lasombra · 2016-11-19 10:10:56

I was playing around with mkinitcpio hooks. When I use systemd instead of udev then I run into the problem with the timeout.
When I use udev got the following error

ERROR: Device `` not found. Skipping fsck.
ERROR: Unable to find root device ``

Last edited by lasombra (2016-11-19 13:47:58)

Head_on_a_Stick · 2016-11-19 14:44:59

See if you can debug the startup of systemd:

https://freedesktop.org/wiki/Software/s … Debugging/

I'm pretty sure that systemd-boot had already done its job by the time the errors in the OP were printed.

Just to be sure, does direct EFI_STUB booting or GRUB work?

lasombra · 2016-11-22 10:50:06

Finally working. I started over and created the partitions from scratch and then followed the wiki and the suggestions within the thread:

1. boot with live usb and mount drives

mount /dev/sda2 /mnt
mount /dev/sda1 /mnt/boot

2. chroot and install boot loader

arch-chroot /mnt
bootctl install
bootctl update

3. create fstab with fstabgen and then modify fstab and remove entry for /

#<file system>	<dir>	<type>	<options>	<dump>	<pass>
UUID=3E22-B7AB      	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro	0 2

4. modify mkinitcpio.conf to use systemd

HOOKS="base systemd autodetect modconf block filesystems keyboard fsck"

5. build initramfs

mkinitcpio -p linux

6. Create /boot/loader/entries/arch.conf

title	Arch Linux (Standard)
linux	/EFI/arch/vmlinuz-linux
initrd	/EFI/arch/initramfs-linux.img
options	root=UUID=4c811cc5-3ca4-4cc3-aff1-44121a7ccaf1 rw

Arch Linux

#1 2016-11-15 14:49:30

[Solved] systemd-boot: Root device not found

#2 2016-11-15 14:51:56

Re: [Solved] systemd-boot: Root device not found

#3 2016-11-15 18:09:58

Re: [Solved] systemd-boot: Root device not found

#4 2016-11-15 20:08:30

Re: [Solved] systemd-boot: Root device not found

#5 2016-11-15 22:29:16

Re: [Solved] systemd-boot: Root device not found

#6 2016-11-15 22:33:18

Re: [Solved] systemd-boot: Root device not found

#7 2016-11-15 23:06:29

Re: [Solved] systemd-boot: Root device not found

#8 2016-11-16 06:12:43

Re: [Solved] systemd-boot: Root device not found

#9 2016-11-16 07:50:21

Re: [Solved] systemd-boot: Root device not found

#10 2016-11-16 08:19:35

Re: [Solved] systemd-boot: Root device not found

#11 2016-11-16 08:27:47

Re: [Solved] systemd-boot: Root device not found

#12 2016-11-16 08:54:37

Re: [Solved] systemd-boot: Root device not found

#13 2016-11-16 19:44:14

Re: [Solved] systemd-boot: Root device not found

#14 2016-11-16 22:02:13

Re: [Solved] systemd-boot: Root device not found

#15 2016-11-17 01:08:22

Re: [Solved] systemd-boot: Root device not found

#16 2016-11-17 06:10:36

Re: [Solved] systemd-boot: Root device not found

#17 2016-11-17 11:25:28

Re: [Solved] systemd-boot: Root device not found

#18 2016-11-19 10:10:56

Re: [Solved] systemd-boot: Root device not found

#19 2016-11-19 14:44:59

Re: [Solved] systemd-boot: Root device not found

#20 2016-11-22 10:50:06

Re: [Solved] systemd-boot: Root device not found

Board footer