YaST sometimes can't find root partition

English Hardware
1

I first encountered this problem when trying to upgrade to Leap 15.3. Now I notice that it sometimes happens while using Leap 15.2. In YaST, some operations result in this error:

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:

device not found, name:/dev/md126p3

I have a RAID1 on ISW.
This error prevented me from upgrading to Leap 15.3
How can I fix it?

2

Did you try upgrading with zypper? I never have upgrade trouble from RAID with zypper.

Does that UUID belong to a valid current filesystem?

Does that UUID match anything in /etc/mdadm.conf?

Did you try using standard Linux software RAID instead of ISW fake RAID? ISW devices are supposed to use DM RAID devices. Linux RAID uses MD RAID devices.

3

No I tried the offline DVD image. I’m afraid of borking the works if I try to do a distribution upgrade with zypper.

blkid reports

/dev/md126p3: UUID="01330ce7-d819-40e9-b947-cc8c7a874339" UUID_SUB="4a663114-f21c-41d4-b8ea-27f85f34717c" TYPE="btrfs" PTTYPE="dos" PARTLABEL="primary" PARTUUID="d02de483-4cc6-4a83-b948-6b9397d0396c"

No, but I would expect it wouldn’t since this is handled by dmraid instead of mdadm. Or am I wrong on that? The contents of /etc/mdadm.conf is:

DEVICE containers partitions
ARRAY metadata=imsm UUID=3a3a541a:48e50d2b:b91a666f:004607fc
ARRAY /dev/md/Volume1_0 container=3a3a541a:48e50d2b:b91a666f:004607fc member=0 UUID=c5af2e40:393921db:eec6cb93:21ddf5cf

Not yet. I’m planning to get an SSD to put boot and root on, then tear down the ISW RAID and build a new one with mdadm with only home.