Andrei Borzenkov composed on 2015-11-18 06:51 (UTC+0300):
Felix Miata composed:
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?
https://bugzilla.opensuse.org/show_bug.cgi?id=935993#c50 could be related (skipping to the relevant comment for you).
I'm unable to recognize a connection between that bug and what happened here. I grep'd raid output of lsinitrd on both original and freshly working initrds, then diff'd, and the only difference is in timestamps. /etc/modules-load.d is empty. Timestamps on /usr/lib/udev/rules.d/ 63-md-raid-arrays.rules and 64-md-raid-assembly.rules' timestamps predate the old initrd. That bug is TW, while this is about 13.2, so that report could be about since changed behavior. Now that this trouble is behind me I'm going to proceed to try the offline upgrade from 32 bit to 64 bit that surfaced this obstacle in preparation for. -- "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