Hello,
Surely this booting (subject) can be done and has been done:: iff you believe what has been posted. Here is one solution (patch) [1] from an interesting discussion:: albeit dated. [2] I think this subject is worth exploring because I do not believe that these booting issues are all related to btrfs issues. I think they are sometimes transient and are affected by other combinations of hardware and kernel and file system configurations. Let's also face the fact that the kernel codes are undergoing massive and frequent changes:: now we can " live patching the kernel code" so the need for more robust tools and methods are warranted; even exasperated if you do not reboot a given system frequently. [3] Paul Tobias's recent post " Adding "rootdelay=30" to the kernel command line" is but the latest example. Parsing out some of these threads on gentoo user does suggest a general booting problem, exasperated by more complex installations (not exclusively btrfs) and thus worth the focus to nail down these issue and the potential work around(s); that they should end up well documented and in the gentoo wiki, imho. As I have mentioned in several threads, I think the available of "netconsole" for fine grain debugging will be useful, as long as we can find a way to setup the ethernet interface as quickly as possible in the sequence of boot events or a way to buffer that boot info (in ram?) and then transmitt it remotely as soon as possible for remote install monitoring and debugging. ALL thoughts and comments are most welcome, James [1] https://gist.github.com/the8lack8ox/2706705 [2] https://forums.gentoo.org/viewtopic-p-7275724.html [3] http://kernelnewbies.org/Linux_4.0#head-6e2ee9e5b7cfdb480861fda324a804734dc14f89
