hansg
February 15, 2022, 3:58am
1
Some functions of yast such as boot loader configuration don’t work because I get the following dialog:
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?
Then on details I get:
device not found, name:/dev/md126p3
When I choose abort I get:
Error
Internal error. Please report a bug report with logs.
Run save_y2logs to get complete logs.
Caller: /usr/share/YaST2/lib/y2storage/storage_manager.rb:226:in `staging’
Details: Storage::Exception
The above UUID is the correct UUID for /dev/md126p3.
It might be related to this bug: https://bugzilla.opensuse.org/show_bug.cgi?id=1179061
but I don’t know and I can’t figure out how to fix it. yast in Leap 15.3 installer gives the same error so I can’t update the existing installation.
hcvv
February 15, 2022, 9:39am
2
But /dev/md126p3 is also not found. It seems as if the device is not there at all.
Can you check with
ls -l /dev/md*
and
ls -l /dev/disk/by-uuid/
And maybe explain what that disk is (being named md…, it is probably not a straight PCI connected device).
@hansg :
“lsblk --fs ” may well also shed some light on what’s going on here.
hansg
February 15, 2022, 8:45pm
4
/dev/md126p3 is currently mounted as /
ls -l /dev/md*:
[FONT=monospace]brw-rw---- 1 root disk 9, 126 Feb 14 19:45 **/dev/md126**
brw-rw---- 1 root disk 259, 0 Feb 14 19:45 **/dev/md126p1**
brw-rw---- 1 root disk 259, 1 Feb 14 19:45 **/dev/md126p2**
brw-rw---- 1 root disk 259, 2 Feb 14 19:45 **/dev/md126p3**
brw-rw---- 1 root disk 259, 3 Feb 14 19:45 **/dev/md126p4**
brw-rw---- 1 root disk 9, 127 Feb 14 19:45 **/dev/md127**
/dev/md:
total 0
lrwxrwxrwx 1 root root 8 Feb 14 19:45 Volume1 -> **../md126**
lrwxrwxrwx 1 root root 10 Feb 14 19:45 Volume1p1 -> **../md126p1**
lrwxrwxrwx 1 root root 10 Feb 14 19:45 Volume1p2 -> **../md126p2**
lrwxrwxrwx 1 root root 10 Feb 14 19:45 Volume1p3 -> **../md126p3**
lrwxrwxrwx 1 root root 10 Feb 14 19:45 Volume1p4 -> **../md126p4**
lrwxrwxrwx 1 root root 8 Feb 14 19:45 imsm0 -> **../md127**
[/FONT]
ls -l /dev/disk/by-uuid/:
total 0
lrwxrwxrwx 1 root root 13 Feb 14 19:45 01330ce7-d819-40e9-b947-cc8c7a874339 -> **../../md126p3**
lrwxrwxrwx 1 root root 15 Feb 14 19:45 0C70-40CF -> **../../nvme0n1p1**
lrwxrwxrwx 1 root root 10 Feb 14 19:45 1c7b8d4e-74c8-4f3f-83d4-8e5f9e7316c5 -> **../../sdc1**
lrwxrwxrwx 1 root root 10 Feb 14 19:45 1e471324-6f67-49af-abe0-8d014b3c562d -> **../../sdc2**
lrwxrwxrwx 1 root root 10 Feb 14 19:45 31600a0b-e130-4067-911d-50161578aa34 -> **../../sdd2**
lrwxrwxrwx 1 root root 15 Feb 14 19:45 694b4e64-e0d0-434e-9fa9-40c747bbcf04 -> **../../nvme0n1p2**
lrwxrwxrwx 1 root root 13 Feb 14 19:45 7dcbb740-c221-4c50-9be8-b09dd791c6b1 -> **../../md126p4**
lrwxrwxrwx 1 root root 10 Feb 14 19:45 B0B85D5FB85D255E -> **../../sdd1**
lrwxrwxrwx 1 root root 13 Feb 14 19:45 B83E-CB2B -> **../../md126p1**
lrwxrwxrwx 1 root root 13 Feb 14 19:45 f07fe3a8-5522-48ab-8c35-55b0975d6ae7 -> **../../md126p2
**
**lsblk --fs:
[FONT=monospace]NAME FSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
sda isw_raid_member
|-sda1 vfat B83E-CB2B
|-sda2 swap f07fe3a8-5522-48ab-8c35-55b0975d6ae7
|-sda3 btrfs 01330ce7-d819-40e9-b947-cc8c7a874339
|-sda4 xfs 7dcbb740-c221-4c50-9be8-b09dd791c6b1
`-md126
|-md126p1 vfat B83E-CB2B 147.9M 5% /boot/efi
|-md126p2 swap f07fe3a8-5522-48ab-8c35-55b0975d6ae7 [SWAP]
|-md126p3 btrfs 01330ce7-d819-40e9-b947-cc8c7a874339 6.9G 79% /boot/grub2/x86_64-efi
`-md126p4 xfs 7dcbb740-c221-4c50-9be8-b09dd791c6b1 550G 38% /home
sdb isw_raid_member
|-sdb1 vfat B83E-CB2B
|-sdb2 swap f07fe3a8-5522-48ab-8c35-55b0975d6ae7
|-sdb3 btrfs 01330ce7-d819-40e9-b947-cc8c7a874339
|-sdb4 xfs 7dcbb740-c221-4c50-9be8-b09dd791c6b1
`-md126
|-md126p1 vfat B83E-CB2B 147.9M 5% /boot/efi
|-md126p2 swap f07fe3a8-5522-48ab-8c35-55b0975d6ae7 [SWAP]
|-md126p3 btrfs 01330ce7-d819-40e9-b947-cc8c7a874339 6.9G 79% /boot/grub2/x86_64-efi
`-md126p4 xfs 7dcbb740-c221-4c50-9be8-b09dd791c6b1 550G 38% /home
sdc
|-sdc1 btrfs Downloads 1c7b8d4e-74c8-4f3f-83d4-8e5f9e7316c5 57.8G 36% /home/user/Downloads
`-sdc2 xfs Media 1e471324-6f67-49af-abe0-8d014b3c562d 1.4T 62% /home/user/Media
sdd
|-sdd1 ntfs B0B85D5FB85D255E 6.8G 84% /mnt/B0B85D5FB85D255E
`-sdd2 xfs 31600a0b-e130-4067-911d-50161578aa34
sr0
nvme0n1
|-nvme0n1p1 vfat 0C70-40CF
`-nvme0n1p2 btrfs 694b4e64-e0d0-434e-9fa9-40c747bbcf04
**[/FONT]
@hansg :
The UUID “01330ce7-d819-40e9-b947-cc8c7a874339” is a RAID member – ‘/dev/md126p3’ …
hansg
February 16, 2022, 11:30pm
6
cat /proc/mdstat
Personalities : [raid1]
md126 : active raid1 sda[1] sdb[0]
976759808 blocks super external:/md127/0 [2/2] [UU]
md127 : inactive sda[1](S) sdb[0](S)
5552 blocks super external:imsm
unused devices: <none>
Nothing ever reports an error accessing /dev/md126p3 other than yast. I can’t figure out what’s wrong.
In this case you should open bug report.
And please avoid colors when posting. I cannot see a single letter behind this yellow.
hansg
February 18, 2022, 7:18am
9
@dcurtisfra :
I don’t know what md127 is. I figured that imsm contains md127, and md127 contains md126. No?
@arvidjaar :
I just copied and pasted from the terminal where it was color coded. I sometimes forget that some people are still using white backgrounds.
md127 contains metadata for other arrays on these disks. It is not that md127 “contains” md126, rather md127 contains information where md126 is located on disks.