Andrei Borzenkov composed on 2015-11-17 11:44 (UTC+0300):
Felix Miata wrote:
Finally I tried another chroot initrd build, this time with hostonly='no', and with add_drivers+="raid1 md_mod". It works, but I don't understand why the explicit addition of the two extra modules to the initrd was required, or
One reason could be that your chroot did not have /dev, /sys and /proc required for autodetection of kernel drivers.
For the second chroot dracut execution, I typed no commands. I used only most recent bash history and <ENTER>, both to initiate the chroot following the three bind mounts, and to run dracut.
why the failure with the comprehensive hostonly=no initrd. If this kind of clone can't be booted without all the fuss, how could a restored backup? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org