disk-manager crashes [Solved]

[roundup976]

Code: Select all

System:    Kernel: 5.10.0-21-amd64 [5.10.162-1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-21-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.18.1 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.18.0 vt: 7 
           dm: LightDM 1.26.0 Distro: MX-21.3_x64 Wildflower April 9  2022 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop System: HP product: HP Z2 SFF G4 Workstation v: N/A serial: <filter> 
           Chassis: type: 3 serial: <filter> 
           Mobo: HP model: 8456 v: KBC Version 07.D4.00 serial: <filter> UEFI: HP 
           v: Q50 Ver. 01.06.03 date: 11/18/2019 
CPU:       Info: 6-Core model: Intel Core i5-8600 bits: 64 type: MCP arch: Kaby Lake note: check 
           family: 6 model-id: 9E (158) stepping: A (10) microcode: F0 cache: L2: 9 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 37199 
           Speed: 4138 MHz min/max: 800/4300 MHz Core speeds (MHz): 1: 4138 2: 4141 3: 4184 
           4: 4197 5: 4185 6: 4114 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled 
           Type: mds mitigation: Clear CPU buffers; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: mmio_stale_data mitigation: Clear CPU buffers; SMT disabled 
           Type: retbleed mitigation: IBRS 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: IBRS, IBPB: conditional, RSB filling, PBRSB-eIBRS: Not affected 
           Type: srbds mitigation: Microcode 
           Type: tsx_async_abort mitigation: Clear CPU buffers; SMT disabled 
Graphics:  Device-1: NVIDIA GP107GL [Quadro P400] vendor: Hewlett-Packard driver: nouveau 
           v: kernel bus-ID: 01:00.0 chip-ID: 10de:1cb3 class-ID: 0300 
           Display: x11 server: X.Org 1.20.11 compositor: xfwm4 v: 4.18.0 driver: 
           loaded: modesetting unloaded: fbdev,vesa display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") 
           s-diag: 582mm (22.9") 
           Monitor-1: DP-2 res: 1920x1080 hz: 60 dpi: 104 size: 470x300mm (18.5x11.8") 
           diag: 558mm (22") 
           OpenGL: renderer: NV137 v: 4.3 Mesa 20.3.5 direct render: Yes 
Audio:     Device-1: Intel Cannon Lake PCH cAVS vendor: Hewlett-Packard driver: snd_hda_intel 
           v: kernel alternate: snd_soc_skl,snd_sof_pci bus-ID: 00:1f.3 chip-ID: 8086:a348 
           class-ID: 0403 
           Device-2: NVIDIA GP107GL High Definition Audio vendor: Hewlett-Packard 
           driver: snd_hda_intel v: kernel bus-ID: 01:00.1 chip-ID: 10de:0fb9 class-ID: 0403 
           Sound Server-1: ALSA v: k5.10.0-21-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Intel Ethernet I219-LM vendor: Hewlett-Packard driver: e1000e v: kernel 
           port: efa0 bus-ID: 00:1f.6 chip-ID: 8086:15bb class-ID: 0200 
           IF: eth2 state: down mac: <filter> 
           Device-2: Intel I350 Gigabit Network driver: igb v: kernel port: 3000 bus-ID: 02:00.0 
           chip-ID: 8086:1521 class-ID: 0200 
           IF: eth0 state: down mac: <filter> 
           Device-3: Intel I350 Gigabit Network driver: igb v: kernel port: 3000 bus-ID: 02:00.1 
           chip-ID: 8086:1521 class-ID: 0200 
           IF: eth1 state: up speed: 1000 Mbps duplex: full mac: <filter> 
RAID:      Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 port: 4020 
           bus-ID: 00:17.0 chip-ID: 8086.2822 rev: 10 class-ID: 0104 
           Supported mdraid levels: linear multipath raid0 raid1 raid6 raid5 raid4 raid10 
           Device-1: md126 maj-min: 9:126 type: mdraid level: mirror status: active 
           size: 465.76 GiB 
           Info: report: 2/1 _U blocks: 488383488 chunk-size: N/A 
           Components: Online: 
           0: sdb maj-min: 8:16 size: 465.76 GiB 
           Device-2: md127 type: mdraid level: N/A status: inactive size: N/A 
           Info: report: N/A blocks: 3096 chunk-size: N/A 
           Components: Online: N/A Spare: 
           0: sdb maj-min: 8:16 size: 465.76 GiB state: S 
Drives:    Local Storage: total: raw: 1.82 TiB usable: 1.36 TiB used: 11.4 GiB (0.8%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD5000AZLX-60K2TA1 
           size: 465.76 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD 
           rpm: 7200 serial: <filter> rev: 1A03 scheme: GPT 
           ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD5000AZLX-60K2TA1 
           size: 465.76 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD 
           rpm: 7200 serial: <filter> rev: 1A03 
           ID-3: /dev/sdc maj-min: 8:32 vendor: SanDisk model: SSD PLUS 1000GB size: 931.51 GiB 
           block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> 
           rev: 04RL scheme: GPT 
Partition: ID-1: / raw-size: 97.66 GiB size: 95.56 GiB (97.86%) used: 9.5 GiB (9.9%) fs: ext4 
           dev: /dev/sdc4 maj-min: 8:36 
           ID-2: /boot/efi raw-size: 600 MiB size: 598.8 MiB (99.80%) used: 17.5 MiB (2.9%) 
           fs: vfat dev: /dev/sdc1 maj-min: 8:33 
           ID-3: /home raw-size: 597.49 GiB size: 587.04 GiB (98.25%) used: 1.88 GiB (0.3%) 
           fs: ext4 dev: /dev/sdc6 maj-min: 8:38 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 1.95 GiB used: 0 KiB (0.0%) priority: -2 
           dev: /dev/sdc5 maj-min: 8:37 
Sensors:   System Temperatures: cpu: 52.0 C mobo: N/A gpu: nouveau temp: 41.0 C 
           Fan Speeds (RPM): N/A gpu: nouveau fan: 1640 
Repos:     Packages: 2066 note: see --pkg apt: 2061 lib: 1022 flatpak: 5 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list 
           1: deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye main non-free
Info:      Processes: 252 Uptime: 27m wakeups: 1 Memory: 31.21 GiB used: 1.72 GiB (5.5%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: UEFI

Starting Disk Manager out of the application menu has issues ( at least on my system ). Sometimes nothing happens, sometimes it asked for a root password and then nothing happens. I ran it from the terminal to get more info:

Code: Select all

$ sudo disk-manager
[sudo] password for : 
['/usr/sbin', '/usr/lib/python39.zip', '/usr/lib/python3.9', '/usr/lib/python3.9/lib-dynload', '/usr/local/lib/python3.9/dist-packages', '/usr/lib/python3/dist-packages', '/usr/lib/python3.9/site-packages']
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/DiskManager/Fstab/DiskInfo.py", line 251, in __getitem__
    return list.__getitem__(self, self.search(item)[0])
IndexError: list index out of range

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/sbin/disk-manager", line 97, in <module>
    main(args, opts)
  File "/usr/sbin/disk-manager", line 70, in main
    app = DiskManager()
  File "/usr/lib/python3/dist-packages/DiskManager/DiskManager.py", line 84, in __init__
    check = SanityCheck(parent = self.window_main, conf = self.conf)
  File "/usr/lib/python3/dist-packages/DiskManager/Dialogs.py", line 410, in __init__
    self.fstab = MntFile(FSTAB)
  File "/usr/lib/python3/dist-packages/DiskManager/Fstab/Fstab.py", line 396, in __init__
    i = info.search_device(entry[0], ignored = False)
  File "/usr/lib/python3/dist-packages/DiskManager/Fstab/DiskInfo.py", line 306, in search_device
    return self.search_reverse(entry, ignored)
  File "/usr/lib/python3/dist-packages/DiskManager/Fstab/DiskInfo.py", line 290, in search_reverse
    self.load_database()
  File "/usr/lib/python3/dist-packages/DiskManager/Fstab/DiskInfo.py", line 116, in load_database
    self[i] = self._get_device_info(devices[i])
  File "/usr/lib/python3/dist-packages/DiskManager/Fstab/ToolsBackend.py", line 73, in _get_device_info
    dev["PARENT"] = self[drive]["DEV"]
  File "/usr/lib/python3/dist-packages/DiskManager/Fstab/DiskInfo.py", line 253, in __getitem__
    raise NotInDatabase("Can't find %s in the database" % item)
DiskManager.Fstab.FstabError.NotInDatabase: Can't find 'Can't find md in the database' in the database

I was looking through the python and see it is maintained by MX Linux, specifically by Nite Coder. Now I have no issues editing fstab myself as I always have done, but I believe a shipped utility should at least give a pop-up failure when run from the GUI. My main question here is to sort out if this is due to some irregularity on my system or an actual bug. If it is really a bug then I will move to filling a bug report.

I have three drives on the system, Windows(500GB Hdd), MX19(500GB Hdd), MX21 and Fedora(1TB SSD) containing four operating systems as well as a 500GB NVMe drive that has the oddity of only Fedora recognizing.

I think I will go back and see how MX19 runs disk-manager, but I need to reboot and what not so I will update this after that.


[UPDATE]
Running MX19:

Disk Manager runs fine other than the two warnings output below.

Code: Select all

$ sudo disk-manager
[sudo] password for : 
WARNING : python-notify is not installed, disable notification
WARNING : python-notify is too old, disable notification

Quick System Info from MX19:

Code: Select all

System:    Kernel: 5.10.0-15mx-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-15mx-amd64 root=UUID=<filter> ro quiet 
           splash 
           Desktop: KDE Plasma 5.14.5 tk: Qt 5.11.3 wm: kwin_x11 vt: 7 dm: SDDM 
           Distro: MX-19.4_KDE_x64 patito feo November 11 2020 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop System: HP product: HP Z2 SFF G4 Workstation v: N/A serial: <filter> Chassis: type: 3 
           serial: <filter> 
           Mobo: HP model: 8456 v: KBC Version 07.D4.00 serial: <filter> UEFI: HP v: Q50 Ver. 01.06.03 date: 11/18/2019 
CPU:       Info: 6-Core model: Intel Core i5-8600 bits: 64 type: MCP arch: Kaby Lake note: check family: 6 model-id: 9E (158) 
           stepping: A (10) microcode: F0 cache: L2: 9 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 37199 
           Speed: 800 MHz min/max: 800/4300 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled 
           Type: mds mitigation: Clear CPU buffers; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: disabled, RSB filling 
           Type: srbds mitigation: Microcode 
           Type: tsx_async_abort mitigation: Clear CPU buffers; SMT disabled 
Graphics:  Device-1: NVIDIA GP107GL [Quadro P400] vendor: Hewlett-Packard driver: nvidia v: 470.141.03 bus-ID: 01:00.0 
           chip-ID: 10de:1cb3 class-ID: 0300 
           Display: x11 server: X.Org 1.20.10 compositor: kwin_x11 driver: loaded: nvidia 
           unloaded: fbdev,modesetting,nouveau,vesa alternate: nv display-ID: :0 screens: 1 
           Screen-1: 0 s-res: 1920x1080 s-dpi: 103 s-size: 473x301mm (18.6x11.9") s-diag: 561mm (22.1") 
           Monitor-1: DP-0 res: 1920x1080 hz: 60 dpi: 104 size: 470x300mm (18.5x11.8") diag: 558mm (22") 
           OpenGL: renderer: Quadro P400/PCIe/SSE2 v: 4.6.0 NVIDIA 470.141.03 direct render: Yes 
Audio:     Device-1: Intel Cannon Lake PCH cAVS vendor: Hewlett-Packard driver: snd_hda_intel v: kernel 
           alternate: snd_soc_skl,snd_sof_pci bus-ID: 00:1f.3 chip-ID: 8086:a348 class-ID: 0403 
           Device-2: NVIDIA GP107GL High Definition Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel 
           bus-ID: 01:00.1 chip-ID: 10de:0fb9 class-ID: 0403 
           Sound Server-1: ALSA v: k5.10.0-15mx-amd64 running: yes 
           Sound Server-2: PulseAudio v: 12.2 running: yes 
Network:   Device-1: Intel Ethernet I219-LM vendor: Hewlett-Packard driver: e1000e v: kernel port: efa0 bus-ID: 00:1f.6 
           chip-ID: 8086:15bb class-ID: 0200 
           IF: eth2 state: down mac: <filter> 
           Device-2: Intel I350 Gigabit Network driver: igb v: kernel port: 3000 bus-ID: 02:00.0 chip-ID: 8086:1521 
           class-ID: 0200 
           IF: eth0 state: down mac: <filter> 
           Device-3: Intel I350 Gigabit Network driver: igb v: kernel port: 3000 bus-ID: 02:00.1 chip-ID: 8086:1521 
           class-ID: 0200 
           IF: eth1 state: up speed: 1000 Mbps duplex: full mac: <filter> 
RAID:      Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 port: 4020 bus-ID: 00:17.0 chip-ID: 8086.2822 
           rev: 10 class-ID: 0104 
Drives:    Local Storage: total: 1.82 TiB used: 253.45 GiB (13.6%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD5000AZLX-60K2TA1 size: 465.76 GiB block-size: 
           physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: 1A03 scheme: GPT 
           ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD5000AZLX-60K2TA1 size: 465.76 GiB block-size: 
           physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: 1A03 
           ID-3: /dev/sdc maj-min: 8:32 vendor: SanDisk model: SSD PLUS 1000GB size: 931.51 GiB block-size: physical: 512 B 
           logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 04RL scheme: GPT 
Partition: ID-1: / raw-size: 50.78 GiB size: 49.68 GiB (97.84%) used: 23.83 GiB (48.0%) fs: ext4 dev: /dev/sda2 maj-min: 8:2 
           ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 387 KiB (0.1%) fs: vfat dev: /dev/sda1 maj-min: 8:1 
           ID-3: /home raw-size: 50.78 GiB size: 49.68 GiB (97.84%) used: 44.72 GiB (90.0%) fs: ext4 dev: /dev/sda3 
           maj-min: 8:3 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 32.23 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda4 maj-min: 8:4 
Sensors:   System Temperatures: cpu: 53.0 C mobo: N/A gpu: nvidia temp: 43 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 34% 
Repos:     Packages: note: see --pkg apt: 3241 lib: 1741 flatpak: 0 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/asbru-cm-release.list 
           1: deb [signed-by=/usr/share/keyrings/asbru-cm-release-archive-keyring.gpg] https://dl.cloudsmith.io/public/asbru-cm/release/deb/debian buster main
           2: deb-src [signed-by=/usr/share/keyrings/asbru-cm-release-archive-keyring.gpg] https://dl.cloudsmith.io/public/asbru-cm/release/deb/debian buster main
           Active apt repos in: /etc/apt/sources.list.d/atom.list 
           1: deb [arch=amd64] https://packagecloud.io/AtomEditor/atom/any/ any main
           Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list 
           1: deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ buster main non-free
           2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ buster ahs
           Active apt repos in: /etc/apt/sources.list.d/teams.list 
           1: deb [arch=amd64] https://packages.microsoft.com/repos/ms-teams stable main
           Active apt repos in: /etc/apt/sources.list.d/teamviewer.list 
           1: deb https://linux.teamviewer.com/deb stable main
           No active apt repos in: /etc/apt/sources.list.d/various.list 
           Active apt repos in: /etc/apt/sources.list.d/vscode.list 
           1: deb [arch=amd64] https://packages.microsoft.com/repos/vscode stable main
Info:      Processes: 243 Uptime: 8m wakeups: 1 Memory: 31.21 GiB used: 1.9 GiB (6.1%) Init: SysVinit v: 2.93 runlevel: 5 
           default: 5 tool: systemctl Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in default: Bash v: 5.0.3 
           running-in: quick-system-in inxi: 3.3.06 

[fehlix]

I have three drives on the system, Windows(500GB Hdd), MX19(500GB Hdd), MX21 and Fedora(1TB SSD) containing four operating systems as well as a 500GB NVMe drive that has the oddity of only Fedora recognizing.

That's probably related to enabled Intel RST RAID with UEFI System Setup as the Intel RAID's are known to introduce issues within the kernel drive handling. Suggest to change from RAID to SATA/AHCI with UEFI/BIOS PC System setup.
(Note on Windows you would need some extra hops to change from RAID to SATA/AHCI driver.
OTOH, the crash should not happen, so I guess an adjustment to capture of those unknow-in-db crashs might be worth to consider.

[roundup976]

@fehlix based on your last comment would you then recommend a bug report instead?

[fehlix]

@fehlix based on your last comment would you then recommend a bug report instead?

It's fine if you keep this within this thread
The raised exception is probably done in this way as the original author may not have foreseen that such a constellation would occur.

So some questions:
Would you post the /etc/fstab ( as text-wrapped with code-tags. )
and also the list of drives / partitions as seen by lsblk e.g. with
lsblk -f

And also, if you switch from RAID to SATA/AHCI within UEFI System Setup
would disk-manger terminate also.

[roundup976]

Code: Select all

# Pluggable devices are handled by uDev, they are not in fstab
UUID=e869b8c6-6a47-4fce-baa7-c1fbf3274efe / ext4 discard,noatime 0 1
UUID=e26dcd3e-6c4b-4c70-aa48-465a4c57f286 /home ext4 noatime 0 2
UUID=da8dc875-5cf8-4c84-9162-e7400c35090a swap swap noatime 1 2
UUID=17DD-3778 /boot/efi vfat noatime,dmask=0002,fmask=0113 0 0

Code: Select all

$ lsblk -f
NAME   FSTYPE LABEL                 UUID                                 FSAVAIL FSUSE% MOUNTPOINT
sda                                                                                     
├─sda1 vfat                         6931-C33C                             251.7M     0% /boot/efi
├─sda2 ext4   rootMX19              c16f0150-1918-40a9-8387-41be89e04cfa   22.8G    49% /
├─sda3 ext4   homeMX                c683f38d-b9e7-4ab8-9c6b-9af76a0fd418    2.4G    90% /home
├─sda4 swap                         65c7c59e-f1f1-4eb0-9bf4-5959dd6e6bf7                [SWAP]
└─sda5 ext4   Data                  fe16dc03-99b4-4c06-9d7e-45e34a5a4c18    124G    57% /media/ryan/Data
sdb                                                                                     
sdc                                                                                     
├─sdc1 vfat                         17DD-3778                                           
├─sdc2 ext4                         c672d5d6-fa7f-4224-a9ce-5ce2b5865932                
├─sdc3 btrfs  fedora_localhost-live e67b0d96-9542-4896-b953-34551b31b591                
├─sdc4 ext4   rootMX21              e869b8c6-6a47-4fce-baa7-c1fbf3274efe                
├─sdc5 swap   mx21swap              da8dc875-5cf8-4c84-9162-e7400c35090a                
└─sdc6 ext4   mx21home              e26dcd3e-6c4b-4c70-aa48-465a4c57f286                
sr0 

Here is /etc/fstab
also, this does work fine with MX19 on the same setup. (just FYI if you missed that in the large post). I will look into switching the EFI settings.

[roundup976]

I changed from the RAID and no longer have a grub entry or an UEFI boot entry for MX21. I need to take care of that issue now, not sure what went wrong or how that happened. The RAID disk was not even the one with MX21 on it.

[Mauser]

@roundup976 , It's been my experience that disk mangers won't work correctly when you are running a RAID. There is no fix for it.

[roundup976]

Ok, added the entry back into grub for MX21 and booted it up. The screenshot shows disk-manager working but removing some drives from the list, presumably related to the RAID disk?

Opening it a second time after the removal there were no pop-ups and it works as expected. What I failed to catch was that the UUID's listed were for MX21. So when I rebooted I got stuck in a loop
in the login screen. I rebuilt the fstab from MX19 and got logged in.

Checked disk-manager and again gives the pop-up that the devices are unrecognized. Hitting cancel it does go back into the main dialog. So, problem mostly solved? Now I am unclear why it fails
to recognize the devices it has mounted for the OS. Anyway, I caused some of my own pain with the deleting of UIID's from fstab but at least that one was easy.

[roundup976]

@roundup976 , It's been my experience that disk mangers won't work correctly when you are running a RAID. There is no fix for it.

Looks like it, but MX19 had no issues. Still, the RAID was a hold over from the original Windows setup and I had long ago broke the RAID but never removed it. It was not in use. I should have deleted it years ago when I first converted the MX19 drive from Windows.

[timkb4cq]

@roundup976 , It's been my experience that disk mangers won't work correctly when you are running a RAID. There is no fix for it.

Looks like it, but MX19 had no issues.

In MX-19 disk-manager was provided by debian and was the original abandoned python2 version. Since it couldn't be built anymore for MX-21 Nite Coder forked it to convert it to python3. It's not surprising an issue from a somewhat rare configuration was not encountered before now. You can't fix what hasn't been seen or reported.