Am 12.01.2016 um 23:50 schrieb Jan Engelhardt:
Hypothesis 1. Your /dev/sda{11..23} in the old kernel were actually dm_mod devices in the first place, created by the kpartx(8) utility, and something in kpartx changed.
Hypothesis 2. Your /dev/sda{11..23} in the old kernel were driven by CONFIG_EFI_PARTITION / CONFIG_MSDOS_PARTITION, and you have disabled these config options in a new custom kernel (so it cannot read partition tables), causing udev to invoke kpartx(8) to read the partition table ANYWAY, giving the partitions new device names.
Hypothesis 3 (backed by experience): This happens when creating a "monster initrd" with mkinitrd. Then 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". 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. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org