Ryan,
As discussed in IRC, I tweaked locations for testing in #11 and added all paths in #14.
Looks like after `mount -n -o move /dev ${rootmnt}/dev` ${rootmnt}/dev has the proper content (see the bcache rule as well)
https://paste.ubuntu.com/26082611/ == before == lrwxrwxrwx 1 13 /dev/bcache/by-uuid/aa04ab39-a42c-446f-aff5-addbd9c80e06 -> ../../bcache0 lrwxrwxrwx 1 13 /dev/bcache/by-uuid/835afacf-6213-48a9-864c-43733822668b -> ../../bcache3 lrwxrwxrwx 1 13 /dev/bcache/by-uuid/727212eb-0f0b-4d20-9191-f0577a38454e -> ../../bcache1 lrwxrwxrwx 1 13 /dev/bcache/by-uuid/2963855b-3d2b-4387-abd1-3ae788919de4 -> ../../bcache2
== after == lrwxrwxrwx 1 13 /root/dev/bcache/by-uuid/aa04ab39-a42c-446f-aff5-addbd9c80e06 -> ../../bcache0 lrwxrwxrwx 1 13 /root/dev/bcache/by-uuid/835afacf-6213-48a9-864c-43733822668b -> ../../bcache3 lrwxrwxrwx 1 13 /root/dev/bcache/by-uuid/727212eb-0f0b-4d20-9191-f0577a38454e -> ../../bcache1 lrwxrwxrwx 1 13 /root/dev/bcache/by-uuid/2963855b-3d2b-4387-abd1-3ae788919de4 -> ../../bcache2
So the problem must be further down.
And about the only thing I see in the init script is run-init from klibc:
# Chain to real filesystem exec run-init ${drop_caps} ${rootmnt} ${init} "$@" ${recovery:+--startup-event=recovery} <${rootmnt}/dev/console >${rootmnt}/dev/console 2>&1
So it's either somewhere in run-init code
https://git.launchpad.net/~usd-import-team/ubuntu/+source/klibc/tree/usr/kinit/run-init/runinitlib.c?h=applied/ubuntu/xenial-updates#n158
or in systemd.
Ryan,
As discussed in IRC, I tweaked locations for testing in #11 and added all paths in #14.
Looks like after `mount -n -o move /dev ${rootmnt}/dev` ${rootmnt}/dev has the proper content (see the bcache rule as well)
https:/ /paste. ubuntu. com/26082611/ by-uuid/ aa04ab39- a42c-446f- aff5-addbd9c80e 06 -> ../../bcache0 by-uuid/ 835afacf- 6213-48a9- 864c-4373382266 8b -> ../../bcache3 by-uuid/ 727212eb- 0f0b-4d20- 9191-f0577a3845 4e -> ../../bcache1 by-uuid/ 2963855b- 3d2b-4387- abd1-3ae788919d e4 -> ../../bcache2
== before ==
lrwxrwxrwx 1 13 /dev/bcache/
lrwxrwxrwx 1 13 /dev/bcache/
lrwxrwxrwx 1 13 /dev/bcache/
lrwxrwxrwx 1 13 /dev/bcache/
== after == bcache/ by-uuid/ aa04ab39- a42c-446f- aff5-addbd9c80e 06 -> ../../bcache0 bcache/ by-uuid/ 835afacf- 6213-48a9- 864c-4373382266 8b -> ../../bcache3 bcache/ by-uuid/ 727212eb- 0f0b-4d20- 9191-f0577a3845 4e -> ../../bcache1 bcache/ by-uuid/ 2963855b- 3d2b-4387- abd1-3ae788919d e4 -> ../../bcache2
lrwxrwxrwx 1 13 /root/dev/
lrwxrwxrwx 1 13 /root/dev/
lrwxrwxrwx 1 13 /root/dev/
lrwxrwxrwx 1 13 /root/dev/
So the problem must be further down.
And about the only thing I see in the init script is run-init from klibc:
# Chain to real filesystem +--startup- event=recovery} <${rootmnt} /dev/console >${rootmnt} /dev/console 2>&1
exec run-init ${drop_caps} ${rootmnt} ${init} "$@" ${recovery:
So it's either somewhere in run-init code
https:/ /git.launchpad. net/~usd- import- team/ubuntu/ +source/ klibc/tree/ usr/kinit/ run-init/ runinitlib. c?h=applied/ ubuntu/ xenial- updates# n158
or in systemd.