search

bluerider / liveroot

Initcpio hooks for overlayfs ontop of root
BSD 3-Clause "New" or "Revised" License
79 stars 13 forks source link

Nest resolve device call to assign root variable #1

Closed ghost closed 9 years ago

ghost commented 9 years ago 
Bug: fsck fails on root
    Error: root is mounted cannot continue
Bug: systemd-machine-id-commit.service fails
    Error: Failed to unmount transient /etc/machine-id file in
        our private namespace: Invalid Argument
    Error: Failed to start Commit a transient machine-id on disk
bluerider commented 9 years ago

https://wiki.archlinux.org/index.php/Arch_Boot_Process https://wiki.archlinux.org/index.php/Init

Also check the contents of /usr/lib/initcpio/init to see how init actually works.

bluerider commented 9 years ago

I've set up a similar setup to yours on qemu. It seems part of the issue is in the way zram is loaded (at least for me). As part of the oroot script, zram is loaded with a certain number of devices. It seems if zram is added directly to the modules array in /etc/mkinitcpio.conf this is ignored. Hence, as a temporary solution, I suggest removing zram from the modules array of mkinitcpio.conf and then loading the initramfs-linux-fallback.img at all times.

bluerider commented 9 years ago

I think most of these issues are solved in 0fc895221ba5ed487a8c7d7a63e1e26ec2ea10d4