System Partition Not Found During Upgrade From Leap 15.2 to 15.3

I have a RAID1 configuration for boot, root, and home. No problems booting and using the system. However when I try to upgrade from Leap 15.2 to to 15.3 using offline upgrade media, I get the following error:

YaST2

Probing file system with UUID 01330ce7-d819-40e9-b947-cc8c7a874339 failed

Unexpected situation found in the system.

Click below to see more details (English only).

Continue despite the error?

When I click on details it says:

YaST2

device not found, name:/dev/md126p3

If I click on Continue, the next page shows no partitions. If I click on “show all partitions” it lists everything except the root partition.

I have seen some inconsistent naming of the partitions in the RAID at various times, sometimes md126p_, sometimes md127p_, and /dev/md/Volume1_0p_ (with _ being a partition number) in Disks (Gnome Disk Utility).

Could there be a misconfiguration somewhere that is causing the inconsistencies?

When Leap 15.2 is running /dev/md126p3 is mounted:

/dev/md126p3 on /.snapshots type btrfs (rw,relatime,space_cache,subvolid=275,subvol=/.snapshots)
/dev/md126p3 on /var/opt type btrfs (rw,relatime,space_cache,subvolid=268,subvol=/var/opt)
/dev/md126p3 on /var/crash type btrfs (rw,relatime,space_cache,subvolid=263,subvol=/var/crash)
/dev/md126p3 on /var/lib/mailman type btrfs (rw,relatime,space_cache,subvolid=264,subvol=/var/lib/mailman)
/dev/md126p3 on /var/lib/named type btrfs (rw,relatime,space_cache,subvolid=265,subvol=/var/lib/named)
/dev/md126p3 on /var/lib/pgsql type btrfs (rw,relatime,space_cache,subvolid=266,subvol=/var/lib/pgsql)
/dev/md126p3 on /tmp type btrfs (rw,relatime,space_cache,subvolid=261,subvol=/tmp)
/dev/md126p3 on /var/lib/machines type btrfs (rw,relatime,space_cache,subvolid=1325,subvol=/var/lib/machines)
/dev/md126p3 on /opt type btrfs (rw,relatime,space_cache,subvolid=259,subvol=/opt)
/dev/md126p3 on /var/log type btrfs (rw,relatime,space_cache,subvolid=267,subvol=/var/log)
/dev/md126p3 on /srv type btrfs (rw,relatime,space_cache,subvolid=260,subvol=/srv)
/dev/md126p3 on /boot/grub2/x86_64-efi type btrfs (rw,relatime,space_cache,subvolid=258,subvol=/boot/grub2/x86_64-efi)
/dev/md126p3 on /usr/local type btrfs (rw,relatime,space_cache,subvolid=262,subvol=/usr/local)
/dev/md126p3 on /boot/grub2/i386-pc type btrfs (rw,relatime,space_cache,subvolid=257,subvol=/boot/grub2/i386-pc)
/dev/md126p3 on /var/spool type btrfs (rw,relatime,space_cache,subvolid=269,subvol=/var/spool)
/dev/md126p3 on /var/tmp type btrfs (rw,relatime,space_cache,subvolid=270,subvol=/var/tmp)

Why? Is there any reason to do it offline?

Probing file system with UUID 01330ce7-d819-40e9-b947-cc8c7a874339 failed
Unexpected situation found in the system.
Click below to see more details (English only).
Continue despite the error?

device not found, name:/dev/md126p3

Open bug report.

After looking into this further, it appears that inconsistent naming of RAID partitions is a separate and unrelated issue. From looking at the listed partitions in the installer, it looks like it is not even recognizing the RAID:


System               Partition    Architecture   File System          Label
Unknown Linux        /dev/sda4    Unknown        xfs
Unknown Linux        /dev/sdb4    Unknown        xfs
Unknown Linux        /dev/sdc1    Unknown        btrfs                Downloads
Unknown Linux        /dev/sdc2    Unknown        xfs                  Media
Unknown Linux        /dev/sdd2    Unknown        xfs
Unknown or Non-Linux /dev/sda1    Unknown        EFI System Partition
Unknown or Non-Linux /dev/sdb1    Unknown        EFI System Partition
Unknown or Non-Linux /dev/sdd1    Unknown        NTFS Partition
Unknown or Non-Linux /dev/sde1    Unknown        EFI System Partition
Unknown or Non-Linux /dev/sde2    Unknown        0x17                 openSUSE-Leap-15.3-DVD-x86_64160

sda and sdb are the hard disks in the RAID. It sees them as separate disks rather than a RAID. Is there a boot option or something that has to be used for it to recognize the RAID? I don’t recall having this issue with previous upgrades.

I’ve run into this same problem. Interestingly my ext4 /home partition was recognised, but not my btrfs root and spare partitions.

I’ve only been doing online upgrades (with zypper) on all my RAID1 systems since somewhere back around 11.4 or before. All my fstabs are written using LABELS for mounting. /etc/mdadm.conf keeps md device names consistent, e.g.:

# cat /etc/mdadm.conf
HOMEHOST <ignore>
DEVICE containers partitions
ARRAY /dev/md0 metadata=1.0 name=myhost:0tmp UUID=...
ARRAY /dev/md1 metadata=1.0 name=myhost:1usrl UUID=...
ARRAY /dev/md2 metadata=1.0 name=myhost:2srv UUID=...
ARRAY /dev/md3 metadata=1.0 name=myhost:3hom UUID=...
ARRAY /dev/md4 metadata=1.0 name=myhost:4pub UUID=...
ARRAY /dev/md5 metadata=1.0 name=myhost:5iso UUID=...