13.01.2016 02:20, Stefan Seyfried пишет:
Hypothesis 3 (backed by experience): This happens when creating a "monster initrd" with mkinitrd. Then
dracut is configured to create hostonly initrd by default; mkinitrd does not disable it. So the question is where it comes from.
multipath and other features are included and you can be happy if the system boots at all. And if it does, the devices are named "strange".
Well ... that somehow conflicts with intention to have universal initrd that "just works". ... Hmm ... actually it is not that simple. In-initrd multipath is activated only if /etc/multipath.conf in initrd exists. And by default there is no /etc/multipath.conf at all; dracut builds one only if installed in hostonly mode and system is already using multipath. @Felix: do you have /etc/multipath.conf on your system? Do you have it in initrd that exhibits this problem? Could you show content of both?
Been there, experienced that, when trying to prepare a system for a "hardware change" (actually trying to change a KVM guest from virtio to virtio-scsi).
It's a shame that this is nowadays easier in windows than in Linux, just sysprep your machine before exchanging the hardware.
In linux you need to know exactly what hardware you'll need at next boot or have a rescue medium ready.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org