I don't actually know what BOOT_DEBUG does -- I've never seen it before, it does not appear anywhere in my yakkety system, and it's for sure not something the kernel, initramfs-tools, or systemd look at. My best guess is that this is a debian-installer specific debug flag.
So from what I can tell, the readlink path issue is merely a red herring -- it's good to fix it of course, but it's unrelated to the boot failure. Since this is a heisenbug, it rather seems to me that this is some timing issue -- any extra debugging, or time spent with changing boot parameters in the boot loader will change the behaviour (e. g. make the detection of network devices by the hardware finish earlier). ATM I'm afraid there isn't enough useful information here yet to understand what's going on -- indeed having a screen output where the problem does happen would be helpful. dmesg logs and "udevadm info -e" as well, as Steve says. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615021 Title: Unable to network boot Ubuntu 16.04 installer normally on Briggs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1615021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
