RAID Does Not Stay Mounted

[mhwittek]

Greetings All,
I have been having an issue with A RAID0 staying mounted. Every time I restart my computer, the RAID0 is no longer mounted. I have found a work around, but it requires me to keep reformatting drive (non destructive), reallocate the partition (non destructive0, and mount the partition with the Disks software. Though not well versed in the process, I tried, unsuccessfully, to make changes in FSTAB file. Occasional, I get an the following error during the reallocate-the-partition process:

Error wiping newly created partition /dev/dm-0p1:Failed to open the device ‘/dev/dm-0p1’ (udisks-error-quark,0)

To start this troubleshooting process, I have supplied my system information below. Thank you in advance for your help with this on going issue.

mike@derSchlaefer:~$ sudo inxi -Famxz
[sudo] password for mike:
System:
Kernel: 5.15.0-76-generic x86_64 bits: 64 compiler: gcc v: 11.3.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.15.0-76-generic
root=UUID=b386fa7b-dbf3-4aec-a3a2-1c39aedc8d93 ro intel_iommu=off
amd_iommu=off quiet splash vt.handoff=7
Desktop: MATE 1.26.0 info: mate-panel wm: marco 1.26.0 dm: LightDM 1.30.0
Distro: Ubuntu 22.04.3 LTS (Jammy Jellyfish)
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: N/A
Mobo: ASUSTeK model: ROG STRIX Z590-E GAMING WIFI v: Rev 1.xx
serial: UEFI: American Megatrends v: 0605 date: 03/11/2021
Memory:
RAM: total: 31.18 GiB used: 2.77 GiB (8.9%)
Array-1: capacity: 64 GiB slots: 4 EC: None max-module-size: 16 GiB
note: est.
Device-1: Controller0-ChannelA-DIMM0 size: No Module Installed
Device-2: Controller0-ChannelA-DIMM1 size: 16 GiB speed: spec: 2667 MT/s
actual: 2666 MT/s type: DDR4 detail: synchronous bus-width: 64 bits
total: 64 bits manufacturer: Crucial Technology
part-no: BL16G32C16U4B.16FE serial:
Device-3: Controller0-ChannelB-DIMM0 size: No Module Installed
Device-4: Controller0-ChannelB-DIMM1 size: 16 GiB speed: spec: 2667 MT/s
actual: 2666 MT/s type: DDR4 detail: synchronous bus-width: 64 bits
total: 64 bits manufacturer: Crucial Technology
part-no: BL16G32C16U4B.16FE serial:
CPU:
Info: model: 11th Gen Intel Core i9-11900K socket: LGA1200 bits: 64
type: MT MCP arch: Rocket Lake family: 6 model-id: 0xA7 (167) stepping: 1
microcode: 0x57
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 640 KiB desc: d-8x48 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
L3: 16 MiB desc: 1x16 MiB
Speed (MHz): avg: 800 high: 801 min/max: 800/5100:5300
base/boost: 3465/12000 scaling: driver: intel_pstate governor: powersave
volts: 0.9 V ext-clock: 100 MHz cores: 1: 801 2: 801 3: 801 4: 800 5: 801
6: 801 7: 801 8: 800 9: 800 10: 801 11: 801 12: 801 13: 801 14: 801
15: 800 16: 800 bogomips: 112128
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: retbleed mitigation: Enhanced 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: Enhanced IBRS, IBPB: conditional, RSB
filling, PBRSB-eIBRS: SW sequence
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
vendor: XFX Pine driver: amdgpu v: kernel pcie: gen: 3 speed: 8 GT/s
lanes: 8 link-max: lanes: 16 ports: active: DP-1,HDMI-A-1
empty: DP-2,DP-3,DVI-D-1 bus-ID: 01:00.0 chip-ID: 1002:67df
class-ID: 0300
Device-2: EMEET HD Webcam C960 type: USB driver: snd-usb-audio,uvcvideo
bus-ID: 1-10.1:6 chip-ID: 328f:003f class-ID: 0102 serial:
Display: server: X.Org v: 1.21.1.4 compositor: marco v: 1.26.0 driver: X:
loaded: amdgpu,ati unloaded: fbdev,modesetting,vesa gpu: amdgpu
display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x285mm (40.0x11.2")
s-diag: 1055mm (41.5")
Monitor-1: DisplayPort-0 mapped: DP-1 pos: primary,left
model: Sceptre F24 serial: built: 2021 res: 1920x1080 hz: 60
dpi: 94 gamma: 1.2 size: 520x320mm (20.5x12.6") diag: 611mm (24.1")
ratio: 16:10 modes: max: 1920x1080 min: 640x480
Monitor-2: HDMI-A-0 mapped: HDMI-A-1 pos: right model: Sceptre F24
serial: built: 2021 res: 1920x1080 hz: 60 dpi: 94 gamma: 1.2
size: 520x320mm (20.5x12.6") diag: 611mm (24.1") ratio: 16:10 modes:
max: 1920x1080 min: 640x480
OpenGL: renderer: AMD Radeon RX 590 Series (polaris10 LLVM 15.0.7 DRM
3.42 5.15.0-76-generic)
v: 4.6 Mesa 22.2.5-0ubuntu0.1~22.04.3 direct render: Yes
Audio:
Device-1: Intel Tiger Lake-H HD Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel alternate: snd_sof_pci_intel_tgl bus-ID: 00:1f.3
chip-ID: 8086:43c8 class-ID: 0403
Device-2: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]
vendor: XFX Pine driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s
lanes: 8 link-max: lanes: 16 bus-ID: 01:00.1 chip-ID: 1002:aaf0
class-ID: 0403
Device-3: EMEET HD Webcam C960 type: USB driver: snd-usb-audio,uvcvideo
bus-ID: 1-10.1:6 chip-ID: 328f:003f class-ID: 0102 serial:
Device-4: ASUSTek USB Audio type: USB
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-14:7 chip-ID: 0b05:1996
class-ID: 0300
Sound Server-1: ALSA v: k5.15.0-76-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
Device-1: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel pcie:
gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: 0f:00.0 chip-ID: 8086:15f3
class-ID: 0200
IF: enp15s0 state: down mac:
Device-2: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: 10:00.0
chip-ID: 8086:15f3 class-ID: 0200
IF: enp16s0 state: down mac:
Device-3: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi
v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 11:00.0
chip-ID: 8086:2725 class-ID: 0280
IF: wlp17s0 state: up mac:
Bluetooth:
Device-1: Intel AX210 Bluetooth type: USB driver: btusb v: 0.8
bus-ID: 1-2:2 chip-ID: 8087:0032 class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 0 state: up address:
Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff
link-mode: peripheral accept
service-classes: rendering, capturing, object transfer, audio, telephony
RAID:
Hardware-1: Intel Device driver: ahci v: 3.0 port: 7020 bus-ID: 00:17.0
chip-ID: 8086:43d6 rev: N/A class-ID: 0104
Hardware-2: HighPoint Device driver: hptnvme v: 1.5.1 port: 5000
bus-ID: 0a:00.0 chip-ID: 1103:7103 rev: N/A class-ID: 0104
Drives:
Local Storage: total: 1.82 TiB used: 444.28 GiB (23.8%)
SMART Message: Required tool smartctl not installed. Check --recommends
ID-1: /dev/sda maj-min: 8:0 vendor: Crucial model: CT1000MX500SSD1
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B
speed: 6.0 Gb/s type: SSD serial: rev: 033
ID-2: /dev/sdb maj-min: 8:16 vendor: Crucial model: CT1000MX500SSD1
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B
speed: 6.0 Gb/s type: SSD serial: rev: 033
Partition:
ID-1: / raw-size: 930.94 GiB size: 915.25 GiB (98.31%)
used: 304.4 GiB (33.3%) fs: ext4 block-size: 4096 B dev: /dev/hptblock0n0p2
maj-min: 259:2
ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
used: 6.1 MiB (1.2%) fs: vfat block-size: 512 B dev: /dev/hptblock0n0p1
maj-min: 259:1
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2
file: /swapfile
Sensors:
System Temperatures: cpu: 27.8 C mobo: N/A gpu: amdgpu temp: 47.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 2
Info:
Processes: 422 Uptime: 11m wakeups: 0 Init: systemd v: 249 runlevel: 5
tool: systemctl Compilers: gcc: 11.4.0 alt: 11/12 Packages: 3066 apt: 3036
lib: 1579 flatpak: 0 snap: 30 Shell: Sudo (sudo) v: 1.9.9 default: Bash
v: 5.1.16 running-in: mate-terminal inxi: 3.3.13

[ugnvs]

Hello!

Regarding "udisks-error-quark,0": it looks like a well-known error and

Unable to format USB drive with Disks (udisks-error-quark, 0)

claims it to be a long- living bug.

[ugnvs]

The next things to start troubleshooting could be:

1. Ensure that fstab contains mounting option for raid device when raid is up and mounted manually.
2. Ensure that raid device is up and ready after OS startup.

Good luck in troubleshooting that issue!

[tkn]

I may be mistaken, but according to your input I guess you have both software raid and hardware raid enabled at the same time which is asking for problems.

If you have both software and hardware raid enabled, please disable your (consumer grade) hardware raid mode in the BIOS.

If that works you might want to re-enable the iommu (which you have deliberatly disabled, probably as part of troubleshooting).

Some background info why i think this way:

1. '/dev/dm-0p1 ' seems to be a device mapper which is used in LVM and software raid.
2. your hardware listing recognizes a hardware (or rather, hybrid) raid controller.

Using software raid and hardware assisted raid at the same time on the same disks is asking for troubles, especially when the "hardware raid" is consumer grade (=not real hardware raid because the need of kernel drivers instead of being fully transparent)
You might therefor want to disable the (semi)-hardware raid in the BIOS, especially when it is an intel product.

Again: I might be mistaken
Be aware that I'm just a simple user (I also started out with MS-DOS 3.3 in 1988 after I used QNX for a few years, I switched to Linux in 2002, distrohopping until I settled on Ubuntu 6.06 dapper drake )

@ricmarques however, is a IT pro and I hope he'll doublecheck this post on any errors of my side.

P.S. If you use consumer grade hardware raid, make sure that neither your UEFI nor your bootimage are stored on those disks to prevent a chicken-and-egg problem (can't get the raid drivers because they are on the raid partition which can only be read with....raid drivers).

[ricmarques]

Hi, @mhwittek (Mike Whittek)

To try to troubleshoot the issue you're having - and supplementing the good answers that @ugnvs (Eugene) and @tkn (thom) have already given you in this topic - could you please run the following 3 commands in your computer and report the output of each command (naturally, if part of the output contains what you consider to be private or sensitive information, feel free to omit it or "mask" it):

1st command - To list the block devices, excluding the "squashfs" devices (the -e7 switch serves to exclude the "squashfs" / "loop" devices from the output):

$ lsblk -o NAME,LABEL,FSTYPE,SIZE,TYPE,MOUNTPOINT -e7

2nd command - To list the uncommented lines in the "fstab":

$ grep ^[^#] /etc/fstab

3rd command - To list the block device attributes:

$ blkid -o full

[mhwittek]

Hello @ricmarques, @tkn, and @ugnvs,
Thank you all for your responses. By the way Ric, 'h' is my middle initial and last name is Wittek. I too have been working on computer since DOS 3.11 on a Panasonic Business Partner Turbo XT days. However, Linux is a whole lot new for me, and I am working on my Linux+ certification, and I know enough to be dangerous. You know monkey with a grenade thing? @ricmarques, I have supplied you with the information that you want below. Just to inform you, I do have a professional grade NVM Raid1 controller that the OS sits on( much voodoo-black-magic went into to setting it up), and the RAID 0 which I am using the on board controller to set up a pair of SSD being used a storage tank. I have been working on and off with this issue since January '23. I am not sure when this started but it was after an update. I found a workaround, but not a satisfactory one. As noted above, I try to make a change to the FSTAB file, and I made it so the computer did not boot properly.

1st Command Results:

mike@derSchlaefer:~$ lsblk -o NAME,LABEL,FSTYPE,SIZE,TYPE,MOUNTPOINT -e7
NAME LABEL FSTYPE SIZE TYPE MOUNTPOINT
sda isw_raid_mem 931.5G disk
└─isw_bcchhhadda_Volume1 1.8T dmraid
└─isw_bcchhhadda_Volume1p1 RAID0 ext4 1.8T part /run/timeshift/bac
sdb isw_raid_mem 931.5G disk
└─isw_bcchhhadda_Volume1 1.8T dmraid
└─isw_bcchhhadda_Volume1p1 RAID0 ext4 1.8T part /run/timeshift/bac
sr0 1024M rom
hptblock0n0p 931.4G disk
├─hptblock0n0p1 vfat 512M part /boot/efi
└─hptblock0n0p2 ext4 930.9G part /

2nd Command Results:

mike@derSchlaefer:~$ grep ^[^#] /etc/fstab
UUID=b386fa7b-dbf3-4aec-a3a2-1c39aedc8d93 / ext4 errors=remount-ro 0 1
UUID=019F-17E8 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
LABEL=RAID0 /mnt/RAID0 ext4 nosuid,nodev,nofail,x-gvfs-show 0 0

3rd Command Results:

mike@derSchlaefer:~$ blkid -o full
/dev/hptblock0n0p2: UUID="b386fa7b-dbf3-4aec-a3a2-1c39aedc8d93" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="e65d4831-f43c-4dad-861b-be35d54ee724"

[ugnvs]

Hello again!

I'd like to add a couple of possible reasons for drive mounting failure.
First: software (OS level) raid does not work, because its configuration is not saved and/or service does not start.
Second: configuration file format and/or options changed after upgrade and configuration raid record is not valid anymore.
And the last: your fstab addresses raid device using 'label=...'. It is possible to try address it using device name or UUID.

[ricmarques]

Hi again, @mhwittek (Mike Wittek )... and please forgive me for having made a typo while writing your last name in my previous post. Thanks for the correction

I don't work with Software RAID and/or Fake RAID ("fakeraid") configurations myself. The RAID configurations that I do work with are the (Hardware) RAID Controllers in Server Hardware and in Storage Arrays. So, I'm afraid I can't help you much in your setup Having said that and from what I gathered from your posts, it seems to me that:

• your Operating System is mounted on a Hardware RAID 1 setup (over two 1 TB devices) and that's running well ...
• ... and your Timeshift backups (I also don't have experience with Timeshift) are running in a Software RAID or in a Fake RAID, in a RAID 0 configuration, and that's what you're having problems mounting. Right?

I saw references in the "inxi" output in your first post to "isw_raid_mem" associated with "dmraid". Some web searches mention that "isw" refers to "Intel Software RAID" and the relation with the command "dmraid" in Ubuntu. The manpage for "dmraid" for Ubuntu Jammy (22.04) - "Ubuntu Manpage: dmraid - discover, configure and activate software (ATA)RAID" mentions the following in the "EXAMPLES" section:

   "dmraid  -l"  lists  all  supported  metadata  formats  with  their  names along with some
       descriptive information, eg:
       hpt37x : (+) Highpoint HPT37X
       hpt45x : (+) Highpoint HPT45X
       isw    : (+) Intel Software RAID
       lsi    : (0) LSI Logic MegaRAID
       nvidia : (+) NVidia RAID
       pdc    : (+) Promise FastTrack
       sil    : (+) Silicon Image(tm) Medley(tm)
       via    : (+) VIA Software RAID
       dos    : (+) DOS partitions on SW RAIDs
       (0): Discover, (+): Discover+Activate

       "dmraid -ay" activates all software RAID sets discovered.

       "dmraid -an" deactivates all active software RAID sets which are  not  open  (eg,  mounted
       filesystem on them).

       "dmraid -ay -f pdc" (pdc looked up from "dmraid -l") activates all software RAID sets with
       Promise format discovered and ignores all other supported formats.

       "dmraid -r" discovers all software RAID devices supported on your system, eg:
       /dev/dm-46: hpt45x, "hpt45x_chidjhaiaa-0", striped, ok, 320172928 sectors, data@ 0
       /dev/dm-50: hpt45x, "hpt45x_chidjhaiaa-0", striped, ok, 320172928 sectors, data@ 0
       /dev/dm-54: hpt45x, "hpt45x_chidjhaiaa-1", striped, ok, 320172928 sectors, data@ 0
       /dev/dm-58: hpt45x, "hpt45x_chidjhaiaa-1", striped, ok, 320172928 sectors, data@ 0

As I'm NOT familiar with these configurations, please take my following suggestion with a "grain of salt" as I may be wrong and I don't want you to damage your system! It may be worth a try to:

1 - Run the following command to show the properties of the RAID sets in your system:
$ sudo dmraid -s

2 - Then run the following command to discover all the software RAID devices supported on your system:
$ sudo dmraid -r

3 - Then, depending on the output of the previous commands and IF you're "feeling particularly brave" (read: IF you have good backups stored elsewhere that you know are in good condition to be restored in case something goes terribly wrong!) you could then consider running the following command to activate all the software RAID sets in your system:
$ sudo dmraid -ay

[mhwittek]

Hello @ugnvs ,
While I dig up the RAID information for @ricmarques, let us look at your first idea. Configurations is not being saved by the DISKS app? Or a service is not starting. How would I verify the saving part? Is there a specific file that I would look for? Which daemon would I want to look for with it is starting or not? Can that be found in the system log files?

As I stated earlier, I use DISKS to configure the RAID0 every time I reboot my computer. When I shutdown the computer, it does not remount the RAID0 automatically.

[mhwittek]

Hello @ricmarques ,
Okay hear are some of the infomation requested. I have not backed up the RAID0 yet, so I have given you all but the SUDO DMRAID -R command. I will do that tomorrow.

A list:

mike@derSchlaefer:~$ sudo dmraid -l
asr : Adaptec HostRAID ASR (0,1,10)
ddf1 : SNIA DDF1 (0,1,4,5,linear)
hpt37x : Highpoint HPT37X (S,0,1,10,01)
hpt45x : Highpoint HPT45X (S,0,1,10)
isw : Intel Software RAID (0,1,5,01)
jmicron : JMicron ATARAID (S,0,1)
lsi : LSI Logic MegaRAID (0,1,10)
nvidia : NVidia RAID (S,0,1,10,5)
pdc : Promise FastTrack (S,0,1,10)
sil : Silicon Image(tm) Medley(tm) (0,1,10)
via : VIA Software RAID (S,0,1,10)
dos : DOS partitions on SW RAIDs

1:

mike@derSchlaefer:~$ sudo dmraid -s
[sudo] password for mike:
*** Group superset isw_bcchhhadda
--> Active Subset
name : isw_bcchhhadda_Volume1
size : 3907039744
stride : 128
type : stripe
status : ok
subsets: 0
devs : 2
spares : 0

2:

mike@derSchlaefer:~$ sudo dmraid -r
/dev/sda: isw, "isw_bcchhhadda", GROUP, ok, 1953525166 sectors, data@ 0
/dev/sdb: isw, "isw_bcchhhadda", GROUP, ok, 1953525166 sectors, data@ 0

[ugnvs]

Hello @mhwittek ,
When you have mounted your partition via DISKS, you can select that partition and invoke extra options menu.

'Edit mount options' menu entry shows a dialog window containing 'mount
at system startup' checkbox. If you set that option DISKS modifies /etc/fstab.

Finally, just verify that fstab still contains the entry for newly mounted partition after DISKS app is closed.

Hopefully, that would help a bit.

[mhwittek]

Hello @ricmarques ,
I just was wondering what this command does before I initiate it, do to the back up warning?

3 - Then, depending on the output of the previous commands and IF you're "feeling particularly brave" (read: IF you have good backups stored elsewhere that you know are in good condition to be restored in case something goes terribly wrong!) you could then consider running the following command to activate all the software RAID sets in your system:
$ sudo dmraid -ay

Thanks again for your help.

[mhwittek]

Hello @ugnvs,
Here is a screenshot of my Disk mount options.

Below is my FSTAB file:

#/etc/fstab: static file system information.

#Use 'blkid' to print the universally unique identifier for a
#device; this may be used with UUID= as a more robust way to name devices
#that works even if disks are added and removed. See fstab(5).

#/ was on /dev/hptblock8n0p2 during installation
UUID=b386fa7b-dbf3-4aec-a3a2-1c39aedc8d93 / ext4 errors=remount-ro 0 1
#/boot/efi was on /dev/hptblock8n0p1 during installation
UUID=019F-17E8 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
#/dev/disk/by-uuid/c3fda098-4963-4035-beb7-1797fa8a55fd /mnt/c3fda098-4963-4035-beb7-1797fa8a55fd auto nosuid,nodev,nofail,x-gvfs-show 0 0
#/dev/disk/by-uuid/c6f5a106-e72d-4530-b29f-22119681c1f9 /mnt/c6f5a106-e72d-4530-b29f-22119681c1f9 auto nosuid,nodev,nofail,x-gvfs-show 0 0

#/dev/disk/by-uuid/c6f5a106-e72d-4530-b29f-22119681c1f9 /mnt/RAID0 ext4 0 0
LABEL=RAID0 /mnt/RAID0 ext4 nosuid,nodev,nofail,x-gvfs-show 0 0

Thanks sir!

[ricmarques]

Hello @mhwittek,

As far as I understand, sudo dmraid -ay is expected to activate all your software RAID sets. I think that should be reasonably safe, but your setup looks to me to be somewhat involved, and so it seems better to be "safe than sorry".

By the way: you could add a '-v' (verbose) switch to that command to get more verbose output:
$ sudo dmraid -ay -v

... or, to get extra verbose output, you could run the same command with -vvv and with -d (which stands for "debug"):

From the web page "FakeRaidDebug - Community Help Wiki" (https://help.ubuntu.com/community/FakeRaidDebug) :

" (...)
1. First run the comand "dmraid -ay -vvv -d". If errors show up here, that probably indicates that other problems outside of dmraid exist with your disk.
> 2. Run the command "dmraid -b" and make sure that dmraid can see your block devices. (...)"

According to the manpage of "dmraid" the -b switch has the following meaning:

{-b|--block_devices} [device-path...]
List all or particular discovered block devices with their properties (size, serial number).

After running those commands, I would run "$ sudo blkid" again to see if you get extra block devices in that command output from the activation of the RAID sets (I think that, if things run well, you will get at least an extra block device that stands for the RAID set). Please, keep us posted

[ugnvs]

Hello @mhwittek,

I am afraid I can not tell you much regarding the situation
Well, your disks app settings and fstab file look to be healthy. But LABEL=RAID0 option looks suspicious to me... The next assumption to verify is whether your raid device is not mounted because it is not found by your system.
At first I'd suggest to verify that the raid device is present in lsblk -f output. Next, you can try to mount the raid device manually using mount command to see its output for errors, if any. Do not hesitate to re-read man mount output. I'd suggest to try mounting the raid device using label, uuid and direct device name for its identification. If mount command works succesfully using uuid or device name identification, substitute LABEL option it fstab with uuid or device name.

Good luck!