Open tilt12345678 opened 9 years ago
Hi tilt,
Good catch. I just pushed a fix to the vdev initramfs hook script to include it.
Can you send me a trace of exactly what happens prior to the vdev_pressed_run error? Exit 127 just means the shell couldn't find a command to execute, but I need to know which one :).
Thanks! -Jude
I'm sorry for my late reply.
I just retried. The hwdb is now there but fails to be mounted by losetup.
Here's a screenshot of the emergency shell where I try to verify that everything is where vdev.conf assumes it to be:
Here's a screenshot of trying to start vdevd manually, and then start the command that fails manually:
Here's a screenshot of me tracing dev-setup.sh where it fails to mount the hwdb.
Hi @tilt12345678,
Thank you for posting screenshots!
I encountered the same problems this past weekend. I just pushed a bunch of fixes to the master branch that should have fixed them. Can you confirm when you get a chance?
Thanks, Jude
testing the installation procedure, i am getting a vdev_preseed_run = 127 problem, the system being unable to boot because LVM devices are not found. more generally, vdev apparently completely fails to start.
i went through the entries in etc/vdev/vdevd.conf and suspect it due to the hwdb not being included with the initrd:
vdev# mkdir tmp ; cd tmp tmp# zcat ../example/initrd.img-4.1.0-1-amd64 | cpio -i tmp# grep hwdb etc/vdev/vdevd.conf hwdb=//lib/vdev/hwdb/hwdb.squashfs tmp# ls lib/vdev/hwdb/hwdb.squashfs ls: cannot access lib/vdev/hwdb/hwdb.squashfs: No such file or directory tmp#