RAID 1 split after upgrade

Support System Updates
,
1

I finally managed to upgrade from 6.12.48-1-MANJARO to 6.12.90-1-MANJARO. This moves me from 25.x to ManjaroLinux 26.1.0-pre Bian-May. Since the upgrade, I’ve had a problem with my RAID1 array. This is hardware managed by an Intel driver on the MB, reporting no issues. I have the array set to auto mount using the System Settings → Disks & Cameras → Device Auto-Mount, not fstab. I see that the two drives making the array are listed individually in Dolphin / tools (see below). As this is sometimes just a UI issue, I put in a test file and confirmed it is not showing up on the other drive, they are out of sync.

Note: this is an old NTFS array from when I ran Windows way back. When I finally run out of space (nearly!) I’ll rebuild with the correct FS type.

Checking the boot log, I see the mount listing two entries:

May 25 11:34:49 victor ntfs-3g[1054]: Version 2022.10.3 external FUSE 29
May 25 11:34:49 victor ntfs-3g[1054]: Mounted /dev/sda2 (Read-Write, label "RAID", NTFS 3.1)
May 25 11:34:49 victor ntfs-3g[1054]: Cmdline options: rw,uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,windows_names
May 25 11:34:49 victor ntfs-3g[1054]: Mount options: uhelper=udisks2,nodev,nosuid,allow_other,nonempty,relatime,rw,default_permissions,fsname=/dev/sda2,blkdev,blksize=4096
May 25 11:34:49 victor ntfs-3g[1054]: Global ownership and permissions enforced, configuration type 7
May 25 11:34:49 victor ntfs-3g[1056]: Version 2022.10.3 external FUSE 29
May 25 11:34:49 victor ntfs-3g[1056]: Mounted /dev/sdb2 (Read-Write, label "RAID", NTFS 3.1)
May 25 11:34:49 victor ntfs-3g[1056]: Cmdline options: rw,uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,windows_names
May 25 11:34:49 victor ntfs-3g[1056]: Mount options: uhelper=udisks2,nodev,nosuid,allow_other,nonempty,relatime,rw,default_permissions,fsname=/dev/sdb2,blkdev,blksize=4096
May 25 11:34:49 victor ntfs-3g[1056]: Global ownership and permissions enforced, configuration type 7

I pulled up the prior log to compare:

May 25 10:11:22 victor ntfs-3g[1038]: Mounted /dev/md126p2 (Read-Write, label "RAID", NTFS 3.1)
May 25 10:11:22 victor ntfs-3g[1038]: Cmdline options: rw,uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,windows_names
May 25 10:11:22 victor ntfs-3g[1038]: Mount options: uhelper=udisks2,nodev,nosuid,allow_other,nonempty,relatime,rw,default_permissions,fsname=/dev/md126p2,blkdev,blksize=4096
May 25 10:11:22 victor ntfs-3g[1038]: Global ownership and permissions enforced, configuration type 7
May 25 10:11:22 victor udisksd[770]: Mounted /dev/md126p2 at /run/media/victor/RAID on behalf of uid 1000

Same mounting utility and version, so that didn’t upgrade.

I can confirm the drives are mounted separately:

lsblk -l
NAME      MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda         8:0    0   2.7T  0 disk 
sda1        8:1    0   128M  0 part 
sda2        8:2    0   2.7T  0 part /run/media/victor/RAID
sdb         8:16   0   2.7T  0 disk 
sdb1        8:17   0   128M  0 part 
sdb2        8:18   0   2.7T  0 part /run/media/victor/RAID1
sr0        11:0    1  1024M  0 rom  
nvme0n1   259:0    0 238.5G  0 disk 
nvme0n1p1 259:1    0   300M  0 part /boot/efi
nvme0n1p2 259:2    0 229.4G  0 part /var/log
                                    /home
                                    /var/cache
                                    /
nvme0n1p3 259:3    0   8.8G  0 part [SWAP]

sudo fdisk -l
The backup GPT table is not on the end of the device.
Disk /dev/sda: 2.73 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: ST3000DM008-2DM1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: C8F960E6-D73F-4FC5-BA10-51A081EE1583

Device      Start        End    Sectors  Size Type
/dev/sda1      34     262177     262144  128M Microsoft reserved
/dev/sda2  264192 5860526079 5860261888  2.7T Microsoft basic data

Partition 1 does not start on physical sector boundary.
The backup GPT table is not on the end of the device.


Disk /dev/sdb: 2.73 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: ST3000DM008-2DM1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: C8F960E6-D73F-4FC5-BA10-51A081EE1583

Device      Start        End    Sectors  Size Type
/dev/sdb1      34     262177     262144  128M Microsoft reserved
/dev/sdb2  264192 5860526079 5860261888  2.7T Microsoft basic data

Partition 1 does not start on physical sector boundary.


Disk /dev/nvme0n1: 238.47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: INTEL SSDPEKKW256G7                     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 80422C9C-46A6-422F-A3EE-C167B67B7615

Device             Start       End   Sectors   Size Type
/dev/nvme0n1p1      4096    618495    614400   300M EFI System
/dev/nvme0n1p2    618496 481663187 481044692 229.4G Linux filesystem
/dev/nvme0n1p3 481663188 500118125  18454938   8.8G Linux swap

I don’t have the older lsblk / fdisk output, would need to fall back to the prior snapshot to collect. I can provide it if needed.

inxi info for reference:

inxi --filter --verbosity=8 --color=0
System:
  Kernel: 6.12.90-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 16.1.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.12-x86_64
    root=UUID=f4addf64-b459-401c-8cec-c194cf8301b4 rw rootflags=subvol=@
    quiet splash resume=UUID=128c88d4-6db6-4ace-9804-be2b98cc0903
    udev.log_priority=3
  Desktop: KDE Plasma v: 6.6.5 tk: Qt v: N/A info: frameworks v: 6.26.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: TUF Z270 MARK 2 v: Rev 1.xx
    serial: <superuser required> part-nu: SKU uuid: <superuser required>
    Firmware: UEFI vendor: American Megatrends v: 0505 date: 11/08/2016
Battery:
  Device-1: hidpp_battery_0 model: Logitech M705 serial: <filter> charge: 15%
    rechargeable: yes status: discharging
Memory:
  System RAM: total: 16 GiB available: 15.55 GiB used: 4.34 GiB (27.9%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 64 GiB slots: 4 modules: 2 EC: None
    max-module-size: 16 GiB note: est.
  Device-1: ChannelA-DIMM1 type: no module installed
  Device-2: ChannelA-DIMM2 type: DDR4 detail: synchronous size: 8 GiB
    speed: 2133 MT/s volts: note: check curr: 1 min: 1 max: 1 width (bits):
    data: 64 total: 64 manufacturer: G-Skill part-no: F4-2400C15-8GVB
    serial: N/A
  Device-3: ChannelB-DIMM1 type: no module installed
  Device-4: ChannelB-DIMM2 type: DDR4 detail: synchronous size: 8 GiB
    speed: 2133 MT/s volts: note: check curr: 1 min: 1 max: 1 width (bits):
    data: 64 total: 64 manufacturer: G-Skill part-no: F4-2400C15-8GVB
    serial: N/A
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Core i5-6600K bits: 64 type: MCP arch: Skylake-S
    gen: core 6 level: v3 note: check built: 2015 process: Intel 14nm family: 6
    model-id: 0x5E (94) stepping: 3 microcode: 0xF0
  Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 smt: <unsupported> cache:
    L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
    L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 800 min/max: 800/3900 scaling: driver: intel_pstate
    governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 bogomips: 28009
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush
    clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
    dtherm dts epb erms est f16c flush_l1d fma fpu fsgsbase fxsr ht hwp
    hwp_act_window hwp_epp hwp_notify ibpb ibrs ida intel_pt invpcid lahf_lm
    lm mca mce md_clear mmx monitor movbe mpx msr mtrr nonstop_tsc nopl nx
    pae pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge pln pni popcnt pse pse36
    pti pts rdrand rdseed rdtscp rep_good sdbg sep smap smep ss ssbd sse sse2
    sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tsc tsc_adjust
    tsc_deadline_timer vme x2apic xgetbv1 xsave xsavec xsaveopt xsaves
    xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling status: Vulnerable: No microcode
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: KVM: VMX unsupported
  Type: l1tf mitigation: PTE Inversion
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT disabled
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: IBRS
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: IBRS; IBPB: conditional; STIBP: disabled;
    RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsa status: Not affected
  Type: tsx_async_abort mitigation: TSX disabled
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: NVIDIA GP106 [GeForce GTX 1060 3GB] vendor: EVGA driver: nouveau
    v: kernel non-free: 550-580.xx+ status: current (as of 2025-11;
    EOL~2026-12-xx) arch: Pascal code: GP10x process: TSMC 16nm
    built: 2016-2021 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3
    speed: 8 GT/s ports: active: HDMI-A-1 empty: DP-1, DP-2, DP-3, DVI-D-1
    bus-ID: 01:00.0 chip-ID: 10de:1c02 class-ID: 0300 temp: 51.0 C
  Display: wayland server: X.org v: 1.21.1.22 with: Xwayland v: 24.1.11
    compositor: kwin_wayland driver: X: loaded: modesetting
    alternate: fbdev,vesa dri: nouveau gpu: nouveau display-ID: 0
  Monitor-1: HDMI-A-1 model: Acer G257HU serial: <filter> built: 2018 res:
    mode: 2560x1440 hz: 60 scale: 100% (1) dpi: 118 gamma: 1.2 chroma: red:
    x: 0.663 y: 0.333 green: x: 0.302 y: 0.616 blue: x: 0.149 y: 0.059 white:
    x: 0.314 y: 0.329 size: 552x311mm (21.73x12.24") diag: 634mm (24.9")
    ratio: 16:9 modes: 2560x1440, 1920x1080, 1920x1080i, 1680x1050,
    1280x1024, 1440x900, 1280x960, 1280x800, 1152x864, 1280x720, 1024x768,
    832x624, 800x600, 720x576, 720x480, 640x480, 720x400
  API: EGL v: 1.5 hw: drv: nvidia nouveau platforms: device: 0 drv: nouveau
    device: 1 drv: swrast gbm: drv: nouveau surfaceless: drv: nouveau wayland:
    drv: nouveau x11: drv: nouveau
  API: OpenGL v: 4.5 compat-v: 4.3 vendor: mesa v: 26.0.6-arch1.1 glx-v: 1.4
    direct-render: yes renderer: NV136 device-ID: 10de:1c02 memory: 2.91 GiB
    unified: no display-ID: :1.0
  API: Vulkan v: 1.4.350 layers: 2 device: 0 type: discrete-gpu name: NVIDIA
    GeForce GTX 1060 3GB (NVK GP106) driver: mesa nvk v: 26.0.6-arch1.1
    device-ID: 10de:1c02 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel 200 Series PCH HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3
    chip-ID: 8086:a2f0 class-ID: 0403
  Device-2: NVIDIA GP106 High Definition Audio vendor: EVGA
    driver: snd_hda_intel v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 16
    link-max: gen: 3 speed: 8 GT/s bus-ID: 01:00.1 chip-ID: 10de:10f1
    class-ID: 0403
  API: ALSA v: k6.12.90-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: JACK v: 1.9.22 status: off tools: N/A
  Server-3: PipeWire v: 1.6.5 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15d6 class-ID: 0200
  IF: enp0s31f6 state: down mac: <filter>
  Device-2: Qualcomm Atheros AR93xx Wireless Network Adapter driver: ath9k
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 06:00.0
    chip-ID: 168c:0030 class-ID: 0280
  IF: wlp6s0 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  IF-ID-1: tun0 state: unknown speed: 10000 Mbps duplex: full mac: N/A
  IP v4: <filter> type: noprefixroute scope: global broadcast: <filter>
  IP v6: <filter> virtual: stable-privacy proto kernel_ll scope: link
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Message: No bluetooth data found.
Logical:
  Message: No logical block device data found.
RAID:
  Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 port: f020
    bus-ID: 00:17.0 chip-ID: 8086:2822 rev: class-ID: 0104
Drives:
  Local Storage: total: 8.42 TiB used: 7.51 TiB (89.1%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Intel model: SSDPEKKW256G7
    size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: PSF100C temp: 42.9 C
    scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST3000DM008-2DM166
    size: 2.73 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: CC26
  ID-3: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST3000DM008-2DM166
    size: 2.73 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: CC26
Partition:
  ID-1: / raw-size: 229.38 GiB size: 229.38 GiB (100.00%)
    used: 142.75 GiB (62.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: f4addf64-b459-401c-8cec-c194cf8301b4
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 664 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1 label: N/A
    uuid: CEAD-1D8B
  ID-3: /home raw-size: 229.38 GiB size: 229.38 GiB (100.00%)
    used: 142.75 GiB (62.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: f4addf64-b459-401c-8cec-c194cf8301b4
  ID-4: /run/media/victor/RAID raw-size: 2.73 TiB size: 2.73 TiB (100.00%)
    used: 2.61 TiB (95.6%) fs: ntfs dev: /dev/sda2 maj-min: 8:2 label: RAID
    uuid: 2E3C78203C77E16F
  ID-5: /run/media/victor/RAID1 raw-size: 2.73 TiB size: 2.73 TiB (100.00%)
    used: 2.61 TiB (95.6%) fs: ntfs dev: /dev/sdb2 maj-min: 8:18 label: RAID
    uuid: 2E3C78203C77E16F
  ID-6: /var/cache raw-size: 229.38 GiB size: 229.38 GiB (100.00%)
    used: 142.75 GiB (62.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: f4addf64-b459-401c-8cec-c194cf8301b4
  ID-7: /var/log raw-size: 229.38 GiB size: 229.38 GiB (100.00%)
    used: 142.75 GiB (62.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: f4addf64-b459-401c-8cec-c194cf8301b4
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: partition size: 8.8 GiB used: 768 KiB (0.0%)
    priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:3 label: swap
    uuid: 128c88d4-6db6-4ace-9804-be2b98cc0903
Unmounted:
  ID-1: /dev/sda1 maj-min: 8:1 size: 128 MiB fs: <superuser required>
    label: N/A uuid: N/A
  ID-2: /dev/sdb1 maj-min: 8:17 size: 128 MiB fs: <superuser required>
    label: N/A uuid: N/A
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 16 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 1-1:2 info: Logitech Internet 350 Keyboard type: keyboard,HID
    driver: hid-generic,usbhid interfaces: 2 rev: 1.1
    speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 100mA
    chip-ID: 046d:c313 class-ID: 0300
  Device-2: 1-5:3 info: Logitech Unifying Receiver type: keyboard,mouse,HID
    driver: logitech-djreceiver,usbhid interfaces: 3 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 98mA
    chip-ID: 046d:c52b class-ID: 0300
  Device-3: 1-6:4 info: JMicron / USA USB to ATA/ATAPI Bridge
    type: mass storage driver: usb-storage interfaces: 1 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 2mA
    chip-ID: 152d:2351 class-ID: 0806 serial: <filter>
  Hub-2: 2-0:1 info: super-speed hub ports: 10 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-4: 4-0:1 info: super-speed hub ports: 2 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 35.0 C mobo: N/A gpu: nouveau temp: 51.0 C
  Fan Speeds (rpm): N/A gpu: nouveau fan: 0
Repos:
  Packages: pm: pacman pkgs: 1534 libs: 395 tools: pamac pm: flatpak pkgs: 0
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://muug.ca/mirror/manjaro/stable/$repo/$arch
    2: https://volico.mm.fcix.net/manjaro/stable/$repo/$arch
    3: https://mirror.vinehost.net/manjaro/stable/$repo/$arch
    4: https://ftp.nluug.nl/pub/os/Linux/distr/manjaro/stable/$repo/$arch
    5: https://ftp.tsukuba.wide.ad.jp/Linux/manjaro/stable/$repo/$arch
    6: https://manjaro.mirror.garr.it/manjaro/stable/$repo/$arch
    7: https://mirror.xeonbd.com/manjaro/stable/$repo/$arch
    8: https://mirror.dc.uz/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 244
  1: cpu: 17.1% command: sdc2 started-by: mount.ntfs pid: 2903
    mem: 3.84 MiB (0.0%)
  2: cpu: 15.3% command: firefox pid: 3616 mem: 903.8 MiB (5.6%)
  3: cpu: 6.2% command: Terabyte started-by: dolphin pid: 2920
    mem: 519.3 MiB (3.2%)
  4: cpu: 5.4% command: kwin_wayland pid: 727 mem: 367.4 MiB (2.3%)
  5: cpu: 3.8% command: [kworker/u16:3-btrfs-endio] pid: 8770
    mem: 0.00 MiB (0.0%)
  Memory top: 5 of 244
  1: mem: 903.8 MiB (5.6%) command: firefox pid: 3616 cpu: 15.3%
  2: mem: 789.5 MiB (4.9%) command: firefox pid: 3846 cpu: 2.2%
  3: mem: 519.3 MiB (3.2%) command: Terabyte started-by: dolphin pid: 2920
    cpu: 6.2%
  4: mem: 444.3 MiB (2.7%) command: firefox pid: 5450 cpu: 0.6%
  5: mem: 444.2 MiB (2.7%) command: firefox pid: 4634 cpu: 1.2%
Info:
  Processes: 244 Power: uptime: 4h 40m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 6.11 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 260 default: graphical
    tool: systemctl
  Compilers: clang: 22.1.5 gcc: 16.1.1 alt: 14/15 Shell: Zsh v: 5.9
    default: Bash v: 5.3.9 running-in: konsole inxi: 3.3.40

I suspect the problem is in /usr/share/polkit-1/actions/org.freedesktop.UDisks2.policy as I have to fix this on every update and the good syslog entry shows udisksd performing the second mount. I normally only need to edit the org.freedesktop.udisks2.filesystem-mount-system section, set all three to ‘yes’.

<defaults>
  <allow_any>yes</allow_any>
  <allow_inactive>yes</allow_inactive>
  <allow_active>yes</allow_active>
</defaults>

Otherwise the auto mount fails and I have to manually mount with sudo, which defeats the purpose of auto mounting. Otherwise the file has default content. Perhaps org.freedesktop.udisks2.manage-md-raid?

Can you please assist me in getting my RAID back to a single sync’d mount?

2

Had no impact. Suggestions?

3

Don’t bump your issue - the forum is populated with volunteering members - so you need to exercise patience until someone with the required knowledge see your topic.

Disclaimer

While your use case may not be unique - I don’t know to assemble a raid from a main-board controller using a foreign file system. I am would expect such attempt to cause damage to the file system and/or the on-disk configuration.

So unless you are willing to use a native Linux mdraid implementation - which would of course not work when booted into Windows - there is not much I can offer to help.

EDIT :high_voltage: :warning:

Be sure to backup your data to external storage before you attempt to do anything related to assembling the RAID under Linux.

Because it is not a dedicated RAID controller and using NTFS there is a high risk of data-loss. What you want to do is not native Linux.

I don’t know what the issue might be but I am not surprised.

What you have is known as Fake Raid and it is well-known for causing varios issue on Linux. Especially when created for/with Windows.

Please see What is Fake Raid for more information and resources.

Thoughts

When the RAID has previously worked it might be worth checking the ntfs driver in use. Userspace ntfs-3g vs kernel ntfs3.

You are mounting it using Plasma’s automount your say?

This tells us that your disks were mounted using ntfs-3g. It is possible the kernels ntfs3 driver has been used to mount the devices before plasmas automount kicks in.

Before moving further down this comment - I suggest you test if blacklisting the kernels ntfs3 driver will work.

Create a file in /etc/modprobe.d/blacklist-ntfs3.conf

blacklist ntfs3

Reboot your system and check if the plasma automount work.

If it does not try then next section.

More thoughts

Check you file /etc/mdadm.conf - the active configuration is typically in the last few lines - I have server configured with mdraid

Sample output

 $ cat /etc/mdadm.conf
...

ARRAY /dev/md/data metadata=1.2 UUID=c59ea61f:60485382:34a2bc57:92e3ec7a

As suggested by @Molski below

Sample output

 # cat /proc/mdstat
Personalities : [raid10] 
md127 : active raid10 sdg1[1] sdd1[2](S) sde1[0]
      468717568 blocks super 1.2 512K chunks 2 far-copies [2/2] [UU]
      bitmap: 0/4 pages [0KB], 65536KB chunk

using mount units

I would rather suggest you setup a pair of systemd mount/automount units to ensure that the RAID is mounted - not the individual devices.

Filename depends on your mount point - do not use /run/media/... but create a dedicated mount point e.g. /a/raid

The create a file /etc/systemd/system/a-raid.mount

The Options has been extracted from your journal output quoted above

[Unit]
Description=Mount data raid

[Mount]
What=/dev/md126p2
Where=/a/raid
Type=ntfs
Options=,nodev,nosuid,allow_other,nonempty,relatime,rw,default_permissions,blkdev,blksize=4096,uid=1000,gid=1000,windows_names

[Install]
WantedBy=multi-user.target

And an automount unit /etc/systemd/system/a-raid.automount

[Unit]
Description=Automount RAID
ConditionPathExists=/a/raid

[Automount]
Where=/a/raid
TimeoutIdleSec=3600

[Install]
WantedBy=multi-user.target

ONLY activate the automount

sudo systemctl enable --now a-raid.automount
2 Likes
5

Hi linux-aarhus, thanks for responding!

Tested

I attempted this and saw no change in behavior.

This file is all comments except one default line:
DEVICE partitions

I executed mdadm -D --scan which returned nothing as well. I reverted to the old snapshot (more below) (same file content as above) and ran the same command which returned:

ARRAY /dev/md/imsm0 metadata=imsm UUID=1c8946ad:ff1e4ca1:a87d8e06:47580247
ARRAY /dev/md/RAID_0 container=/dev/md/imsm0 member=0 UUID=c850e72a:7fc6b853:c49abf3f:f226e972

Old image
While in the old image, ManjaroLinux 25.0.10 Zetar, I pulled up the details for the working RAID setup:

lsblk -l
NAME      MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
sda         8:0    0   2.7T  0 disk  
sdb         8:16   0   2.7T  0 disk  
md126       9:126  0   2.7T  0 raid1 
md127       9:127  0     0B  0       
sr0        11:0    1  1024M  0 rom   
nvme0n1   259:0    0 238.5G  0 disk  
nvme0n1p1 259:1    0   300M  0 part  /boot/efi
nvme0n1p2 259:2    0 229.4G  0 part  /var/log
                                     /var/cache
                                     /home
                                     /
nvme0n1p3 259:3    0   8.8G  0 part  [SWAP]
md126p1   259:4    0   128M  0 part  
md126p2   259:5    0   2.7T  0 part  /run/media/victor/RAID

sudo blkid
/dev/nvme0n1p3: LABEL="swap" UUID="128c88d4-6db6-4ace-9804-be2b98cc0903" TYPE="swap" PARTUUID="0334fe44-0746-44f1-9149-634028e561b1"
/dev/nvme0n1p1: UUID="CEAD-1D8B" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="1a124026-87bc-4252-a9e6-fb654ce5f617"
/dev/nvme0n1p2: UUID="f4addf64-b459-401c-8cec-c194cf8301b4" UUID_SUB="f6ba7625-0d21-44a0-a0ce-01254de02640" BLOCK_SIZE="4096" TYPE="btrfs" PARTLABEL="root" PARTUUID="799fed22-51c2-418e-9544-7560b2e0bcb0"
/dev/sdb: TYPE="isw_raid_member"
/dev/md126p2: LABEL="RAID" BLOCK_SIZE="512" UUID="2E3C78203C77E16F" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="b2c8b5d4-e1f4-40e0-8511-c361b1e9e101"
/dev/md126p1: PARTLABEL="Microsoft reserved partition" PARTUUID="cc1563f5-c4ce-4790-bc73-819124294249"
/dev/sda: TYPE="isw_raid_member"

From this I ran udisksctl against everything:

udisksctl info -b /dev/sda
/org/freedesktop/UDisks2/block_devices/sda:
  org.freedesktop.UDisks2.Block:
    Configuration:              []
    CryptoBackingDevice:        '/'
    Device:                     /dev/sda
    DeviceNumber:               2048
    Drive:                      '/org/freedesktop/UDisks2/drives/ST3000DM008_2DM166_Z5048DHH'
    HintAuto:                   false
    HintIconName:               
    HintIgnore:                 false
    HintName:                   
    HintPartitionable:          true
    HintSymbolicIconName:       
    HintSystem:                 true
    Id:                         by-id-ata-ST3000DM008-2DM166_Z5048DHH
    IdLabel:                    
    IdType:                     isw_raid_member
    IdUUID:                     
    IdUsage:                    raid
    IdVersion:                  1.3.00
    MDRaid:                     '/'
    MDRaidMember:               '/'
    PreferredDevice:            /dev/sda
    ReadOnly:                   false
    Size:                       3000592982016
    Symlinks:                   /dev/disk/by-diskseq/1
                                /dev/disk/by-id/ata-ST3000DM008-2DM166_Z5048DHH
                                /dev/disk/by-id/wwn-0x5000c500a1bc294f
                                /dev/disk/by-path/pci-0000:00:17.0-ata-5
                                /dev/disk/by-path/pci-0000:00:17.0-ata-5.0
    UserspaceMountOptions:

udisksctl info -b /dev/sdb
/org/freedesktop/UDisks2/block_devices/sdb:
  org.freedesktop.UDisks2.Block:
    Configuration:              []
    CryptoBackingDevice:        '/'
    Device:                     /dev/sdb
    DeviceNumber:               2064
    Drive:                      '/org/freedesktop/UDisks2/drives/ST3000DM008_2DM166_Z504807S'
    HintAuto:                   false
    HintIconName:               
    HintIgnore:                 false
    HintName:                   
    HintPartitionable:          true
    HintSymbolicIconName:       
    HintSystem:                 true
    Id:                         by-id-ata-ST3000DM008-2DM166_Z504807S
    IdLabel:                    
    IdType:                     isw_raid_member
    IdUUID:                     
    IdUsage:                    raid
    IdVersion:                  1.3.00
    MDRaid:                     '/'
    MDRaidMember:               '/'
    PreferredDevice:            /dev/sdb
    ReadOnly:                   false
    Size:                       3000592982016
    Symlinks:                   /dev/disk/by-diskseq/2
                                /dev/disk/by-id/ata-ST3000DM008-2DM166_Z504807S
                                /dev/disk/by-id/wwn-0x5000c500a1b7b6b1
                                /dev/disk/by-path/pci-0000:00:17.0-ata-6
                                /dev/disk/by-path/pci-0000:00:17.0-ata-6.0
    UserspaceMountOptions:

udisksctl info -b /dev/md126p2
/org/freedesktop/UDisks2/block_devices/md126p2:
  org.freedesktop.UDisks2.Block:
    Configuration:              []
    CryptoBackingDevice:        '/'
    Device:                     /dev/md126p2
    DeviceNumber:               66309
    Drive:                      '/'
    HintAuto:                   false
    HintIconName:               
    HintIgnore:                 false
    HintName:                   
    HintPartitionable:          true
    HintSymbolicIconName:       
    HintSystem:                 true
    Id:                         by-id-md-uuid-c850e72a:7fc6b853:c49abf3f:f226e972-part2
    IdLabel:                    RAID
    IdType:                     ntfs
    IdUUID:                     2E3C78203C77E16F
    IdUsage:                    filesystem
    IdVersion:                  
    MDRaid:                     '/'
    MDRaidMember:               '/'
    PreferredDevice:            /dev/md/RAID_0p2
    ReadOnly:                   false
    Size:                       3000454086656
    Symlinks:                   /dev/disk/by-id/md-uuid-c850e72a:7fc6b853:c49abf3f:f226e972-part2
                                /dev/disk/by-label/RAID
                                /dev/disk/by-partuuid/b2c8b5d4-e1f4-40e0-8511-c361b1e9e101
                                /dev/disk/by-uuid/2E3C78203C77E16F
                                /dev/md/RAID_0p2
    UserspaceMountOptions:      uhelper=udisks2
  org.freedesktop.UDisks2.Filesystem:
    MountPoints:        /run/media/victor/RAID
    Size:               0
  org.freedesktop.UDisks2.Partition:
    Flags:              0
    IsContained:        false
    IsContainer:        false
    Name:               Basic data partition
    Number:             2
    Offset:             135266304
    Size:               3000454086656
    Table:              '/org/freedesktop/UDisks2/block_devices/md126'
    Type:               ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
    UUID:               b2c8b5d4-e1f4-40e0-8511-c361b1e9e101

udisksctl info -b /dev/md/imsm0                                                                                                                                          1 ✘ 
/org/freedesktop/UDisks2/block_devices/md127:
  org.freedesktop.UDisks2.Block:
    Configuration:              []
    CryptoBackingDevice:        '/'
    Device:                     /dev/md127
    DeviceNumber:               2431
    Drive:                      '/'
    HintAuto:                   false
    HintIconName:               
    HintIgnore:                 false
    HintName:                   
    HintPartitionable:          true
    HintSymbolicIconName:       
    HintSystem:                 true
    Id:                         by-id-md-uuid-1c8946ad:ff1e4ca1:a87d8e06:47580247
    IdLabel:                    
    IdType:                     
    IdUUID:                     
    IdUsage:                    
    IdVersion:                  
    MDRaid:                     '/org/freedesktop/UDisks2/mdraid/1c8946ad_ff1e4ca1_a87d8e06_47580247'
    MDRaidMember:               '/'
    PreferredDevice:            /dev/md/imsm0
    ReadOnly:                   false
    Size:                       0
    Symlinks:                   /dev/disk/by-id/md-uuid-1c8946ad:ff1e4ca1:a87d8e06:47580247
                                /dev/md/imsm0
    UserspaceMountOptions:

udisksctl info -b /dev/md/RAID_0
/org/freedesktop/UDisks2/block_devices/md126:
  org.freedesktop.UDisks2.Block:
    Configuration:              []
    CryptoBackingDevice:        '/'
    Device:                     /dev/md126
    DeviceNumber:               2430
    Drive:                      '/'
    HintAuto:                   false
    HintIconName:               
    HintIgnore:                 false
    HintName:                   
    HintPartitionable:          true
    HintSymbolicIconName:       
    HintSystem:                 true
    Id:                         by-id-md-uuid-c850e72a:7fc6b853:c49abf3f:f226e972
    IdLabel:                    
    IdType:                     
    IdUUID:                     
    IdUsage:                    
    IdVersion:                  
    MDRaid:                     '/org/freedesktop/UDisks2/mdraid/c850e72a_7fc6b853_c49abf3f_f226e972'
    MDRaidMember:               '/'
    PreferredDevice:            /dev/md/RAID_0
    ReadOnly:                   false
    Size:                       3000590401536
    Symlinks:                   /dev/disk/by-id/md-uuid-c850e72a:7fc6b853:c49abf3f:f226e972
                                /dev/md/RAID_0
    UserspaceMountOptions:      
  org.freedesktop.UDisks2.PartitionTable:
    Partitions:         /org/freedesktop/UDisks2/block_devices/md126p1
                        /org/freedesktop/UDisks2/block_devices/md126p2
    Type:               gpt

udisksctl info -b /dev/md/RAID_0p1
/org/freedesktop/UDisks2/block_devices/md126p1:
  org.freedesktop.UDisks2.Block:
    Configuration:              []
    CryptoBackingDevice:        '/'
    Device:                     /dev/md126p1
    DeviceNumber:               66308
    Drive:                      '/'
    HintAuto:                   false
    HintIconName:               
    HintIgnore:                 true
    HintName:                   
    HintPartitionable:          true
    HintSymbolicIconName:       
    HintSystem:                 true
    Id:                         by-id-md-uuid-c850e72a:7fc6b853:c49abf3f:f226e972-part1
    IdLabel:                    
    IdType:                     
    IdUUID:                     
    IdUsage:                    
    IdVersion:                  
    MDRaid:                     '/'
    MDRaidMember:               '/'
    PreferredDevice:            /dev/md/RAID_0p1
    ReadOnly:                   false
    Size:                       134217728
    Symlinks:                   /dev/disk/by-id/md-uuid-c850e72a:7fc6b853:c49abf3f:f226e972-part1
                                /dev/md/RAID_0p1
    UserspaceMountOptions:      
  org.freedesktop.UDisks2.Partition:
    Flags:              0
    IsContained:        false
    IsContainer:        false
    Name:               Microsoft reserved partition
    Number:             1
    Offset:             17408
    Size:               134217728
    Table:              '/org/freedesktop/UDisks2/block_devices/md126'
    Type:               e3c9e316-0b5c-4db8-817d-f92df00215ae
    UUID:               cc1563f5-c4ce-4790-bc73-819124294249

udisksctl info -b /dev/md/RAID_0p2
/org/freedesktop/UDisks2/block_devices/md126p2:
  org.freedesktop.UDisks2.Block:
    Configuration:              []
    CryptoBackingDevice:        '/'
    Device:                     /dev/md126p2
    DeviceNumber:               66309
    Drive:                      '/'
    HintAuto:                   false
    HintIconName:               
    HintIgnore:                 false
    HintName:                   
    HintPartitionable:          true
    HintSymbolicIconName:       
    HintSystem:                 true
    Id:                         by-id-md-uuid-c850e72a:7fc6b853:c49abf3f:f226e972-part2
    IdLabel:                    RAID
    IdType:                     ntfs
    IdUUID:                     2E3C78203C77E16F
    IdUsage:                    filesystem
    IdVersion:                  
    MDRaid:                     '/'
    MDRaidMember:               '/'
    PreferredDevice:            /dev/md/RAID_0p2
    ReadOnly:                   false
    Size:                       3000454086656
    Symlinks:                   /dev/disk/by-id/md-uuid-c850e72a:7fc6b853:c49abf3f:f226e972-part2
                                /dev/disk/by-label/RAID
                                /dev/disk/by-partuuid/b2c8b5d4-e1f4-40e0-8511-c361b1e9e101
                                /dev/disk/by-uuid/2E3C78203C77E16F
                                /dev/md/RAID_0p2
    UserspaceMountOptions:      uhelper=udisks2
  org.freedesktop.UDisks2.Filesystem:
    MountPoints:        /run/media/victor/RAID
    Size:               0
  org.freedesktop.UDisks2.Partition:
    Flags:              0
    IsContained:        false
    IsContainer:        false
    Name:               Basic data partition
    Number:             2
    Offset:             135266304
    Size:               3000454086656
    Table:              '/org/freedesktop/UDisks2/block_devices/md126'
    Type:               ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
    UUID:               b2c8b5d4-e1f4-40e0-8511-c361b1e9e101

udisksctl info -b /dev/md126
/org/freedesktop/UDisks2/block_devices/md126:
  org.freedesktop.UDisks2.Block:
    Configuration:              []
    CryptoBackingDevice:        '/'
    Device:                     /dev/md126
    DeviceNumber:               2430
    Drive:                      '/'
    HintAuto:                   false
    HintIconName:               
    HintIgnore:                 false
    HintName:                   
    HintPartitionable:          true
    HintSymbolicIconName:       
    HintSystem:                 true
    Id:                         by-id-md-uuid-c850e72a:7fc6b853:c49abf3f:f226e972
    IdLabel:                    
    IdType:                     
    IdUUID:                     
    IdUsage:                    
    IdVersion:                  
    MDRaid:                     '/org/freedesktop/UDisks2/mdraid/c850e72a_7fc6b853_c49abf3f_f226e972'
    MDRaidMember:               '/'
    PreferredDevice:            /dev/md/RAID_0
    ReadOnly:                   false
    Size:                       3000590401536
    Symlinks:                   /dev/disk/by-id/md-uuid-c850e72a:7fc6b853:c49abf3f:f226e972
                                /dev/md/RAID_0
    UserspaceMountOptions:      
  org.freedesktop.UDisks2.PartitionTable:
    Partitions:         /org/freedesktop/UDisks2/block_devices/md126p1
                        /org/freedesktop/UDisks2/block_devices/md126p2
    Type:               gpt

udisksctl info -b /dev/md127                                                                                                                                               ✔ 
/org/freedesktop/UDisks2/block_devices/md127:
  org.freedesktop.UDisks2.Block:
    Configuration:              []
    CryptoBackingDevice:        '/'
    Device:                     /dev/md127
    DeviceNumber:               2431
    Drive:                      '/'
    HintAuto:                   false
    HintIconName:               
    HintIgnore:                 false
    HintName:                   
    HintPartitionable:          true
    HintSymbolicIconName:       
    HintSystem:                 true
    Id:                         by-id-md-uuid-1c8946ad:ff1e4ca1:a87d8e06:47580247
    IdLabel:                    
    IdType:                     
    IdUUID:                     
    IdUsage:                    
    IdVersion:                  
    MDRaid:                     '/org/freedesktop/UDisks2/mdraid/1c8946ad_ff1e4ca1_a87d8e06_47580247'
    MDRaidMember:               '/'
    PreferredDevice:            /dev/md/imsm0
    ReadOnly:                   false
    Size:                       0
    Symlinks:                   /dev/disk/by-id/md-uuid-1c8946ad:ff1e4ca1:a87d8e06:47580247
                                /dev/md/imsm0
    UserspaceMountOptions:

And for completeness, the inxi output:

inxi --filter --verbosity=8 --color=0                                                                                                                                      ✔ 
System:
  Kernel: 6.12.48-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/timeshift-btrfs/snapshots/2026-05-25_10-12-47/@/boot/vmlinuz-6.12-x86_64
    root=UUID=f4addf64-b459-401c-8cec-c194cf8301b4 quiet splash
    resume=UUID=128c88d4-6db6-4ace-9804-be2b98cc0903 udev.log_priority=3
    rootflags=defaults,compress=zstd:1,subvol=timeshift-btrfs/snapshots/2026-05-25_10-12-47/@
  Desktop: KDE Plasma v: 6.3.6 tk: Qt v: N/A info: frameworks v: 6.18.0
    wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: TUF Z270 MARK 2 v: Rev 1.xx
    serial: <superuser required> part-nu: SKU uuid: <superuser required>
    Firmware: UEFI vendor: American Megatrends v: 0505 date: 11/08/2016
Battery:
  Device-1: hidpp_battery_0 model: Logitech M705 serial: <filter> charge: 20%
    rechargeable: yes status: discharging
Memory:
  System RAM: total: 16 GiB available: 15.55 GiB used: 1.9 GiB (12.2%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 64 GiB slots: 4 modules: 2 EC: None
    max-module-size: 16 GiB note: est.
  Device-1: ChannelA-DIMM1 type: no module installed
  Device-2: ChannelA-DIMM2 type: DDR4 detail: synchronous size: 8 GiB
    speed: 2133 MT/s volts: note: check curr: 1 min: 1 max: 1 width (bits):
    data: 64 total: 64 manufacturer: G-Skill part-no: F4-2400C15-8GVB
    serial: N/A
  Device-3: ChannelB-DIMM1 type: no module installed
  Device-4: ChannelB-DIMM2 type: DDR4 detail: synchronous size: 8 GiB
    speed: 2133 MT/s volts: note: check curr: 1 min: 1 max: 1 width (bits):
    data: 64 total: 64 manufacturer: G-Skill part-no: F4-2400C15-8GVB
    serial: N/A
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Core i5-6600K bits: 64 type: MCP arch: Skylake-S
    gen: core 6 level: v3 note: check built: 2015 process: Intel 14nm family: 6
    model-id: 0x5E (94) stepping: 3 microcode: 0xF0
  Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 smt: <unsupported> cache:
    L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
    L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 800 min/max: 800/3900 scaling: driver: intel_pstate
    governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 bogomips: 28009
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush
    clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
    dtherm dts epb erms est f16c flush_l1d fma fpu fsgsbase fxsr ht hwp
    hwp_act_window hwp_epp hwp_notify ibpb ibrs ida intel_pt invpcid lahf_lm
    lm mca mce md_clear mmx monitor movbe mpx msr mtrr nonstop_tsc nopl nx
    pae pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge pln pni popcnt pse pse36
    pti pts rdrand rdseed rdtscp rep_good sdbg sep smap smep ss ssbd sse sse2
    sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tsc tsc_adjust
    tsc_deadline_timer vme x2apic xgetbv1 xsave xsavec xsaveopt xsaves
    xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling status: Vulnerable: No microcode
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: KVM: VMX unsupported
  Type: l1tf mitigation: PTE Inversion
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT disabled
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: IBRS
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: IBRS; IBPB: conditional; STIBP: disabled;
    RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsa status: Not affected
  Type: tsx_async_abort mitigation: TSX disabled
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: NVIDIA GP106 [GeForce GTX 1060 3GB] vendor: eVga.com.
    driver: nouveau v: kernel non-free: 550-580.xx+ status: current (as of
    2025-11; EOL~2026-12-xx) arch: Pascal code: GP10x process: TSMC 16nm
    built: 2016-2021 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3
    speed: 8 GT/s ports: active: HDMI-A-1 empty: DP-1, DP-2, DP-3, DVI-D-1
    bus-ID: 01:00.0 chip-ID: 10de:1c02 class-ID: 0300 temp: 50.0 C
  Display: x11 server: X.Org v: 21.1.18 with: Xwayland v: 24.1.8
    compositor: kwin_x11 driver: X: loaded: modesetting alternate: fbdev,vesa
    dri: nouveau gpu: nouveau display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.65x15.00")
    s-diag: 777mm (30.58")
  Monitor-1: HDMI-A-1 mapped: HDMI-1 model: Acer G257HU serial: <filter>
    built: 2018 res: mode: 2560x1440 hz: 60 scale: 100% (1) dpi: 118 gamma: 1.2
    chroma: red: x: 0.663 y: 0.333 green: x: 0.302 y: 0.616 blue: x: 0.149
    y: 0.059 white: x: 0.314 y: 0.329 size: 552x311mm (21.73x12.24")
    diag: 634mm (24.9") ratio: 16:9 modes: 2560x1440, 1920x1080, 1920x1080i,
    1680x1050, 1280x1024, 1440x900, 1280x960, 1280x800, 1152x864, 1280x720,
    1024x768, 832x624, 800x600, 720x576, 720x480, 640x480, 720x400
  API: EGL v: 1.5 hw: drv: nvidia nouveau platforms: device: 0 drv: nouveau
    device: 1 drv: swrast gbm: drv: nouveau surfaceless: drv: nouveau x11:
    drv: nouveau inactive: wayland
  API: OpenGL v: 4.5 compat-v: 4.3 vendor: mesa v: 25.2.3-arch1.2 glx-v: 1.4
    direct-render: yes renderer: NV136 device-ID: 10de:1c02 memory: 2.91 GiB
    unified: no
  API: Vulkan Message: No Vulkan data available.
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel 200 Series PCH HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3
    chip-ID: 8086:a2f0 class-ID: 0403
  Device-2: NVIDIA GP106 High Definition Audio vendor: eVga.com.
    driver: snd_hda_intel v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 16
    link-max: gen: 3 speed: 8 GT/s bus-ID: 01:00.1 chip-ID: 10de:10f1
    class-ID: 0403
  API: ALSA v: k6.12.48-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.4.8 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15d6 class-ID: 0200
  IF: enp0s31f6 state: down mac: <filter>
  Device-2: Qualcomm Atheros AR93xx Wireless Network Adapter driver: ath9k
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 06:00.0
    chip-ID: 168c:0030 class-ID: 0280
  IF: wlp6s0 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  IF-ID-1: tun0 state: unknown speed: 10000 Mbps duplex: full mac: N/A
  IP v4: <filter> type: noprefixroute scope: global broadcast: <filter>
  IP v6: <filter> virtual: stable-privacy proto kernel_ll scope: link
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Message: No bluetooth data found.
Logical:
  Message: No logical block device data found.
RAID:
  Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 port: f020
    bus-ID: 00:17.0 chip-ID: 8086:2822 rev: class-ID: 0104
  Supported mdraid levels: raid1
  Device-1: md126 maj-min: 9:126 type: mdraid level: mirror status: active
    size: 2.73 TiB
  Info: report: 2/2 UU blocks: 2930264064 chunk-size: N/A
  Components: Online:
  0: sdb maj-min: 8:16 size: 2.73 TiB
  1: sda maj-min: 8:0 size: 2.73 TiB
  Device-2: md127 maj-min: 9:127 type: mdraid level: N/A status: inactive
    size: N/A
  Info: report: N/A blocks: 5040 chunk-size: N/A
  Components: Online: N/A Spare:
  0: sda maj-min: 8:0 size: 2.73 TiB state: S
  1: sdb maj-min: 8:16 size: 2.73 TiB state: S
Drives:
  Local Storage: total: 5.69 TiB used: 2.75 TiB (48.3%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Intel model: SSDPEKKW256G7
    size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: PSF100C temp: 42.9 C
    scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST3000DM008-2DM166
    size: 2.73 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: CC26
  ID-3: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST3000DM008-2DM166
    size: 2.73 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: CC26
  Optical-1: /dev/sr0 vendor: HL-DT-ST model: BD-RE WH10LS30 rev: 1.00
    dev-links: cdrom
  Features: speed: 40 multisession: yes audio: yes dvd: yes
    rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
Partition:
  ID-1: / raw-size: 229.38 GiB size: 229.38 GiB (100.00%)
    used: 143.09 GiB (62.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: f4addf64-b459-401c-8cec-c194cf8301b4
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 664 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1 label: N/A
    uuid: CEAD-1D8B
  ID-3: /home raw-size: 229.38 GiB size: 229.38 GiB (100.00%)
    used: 143.09 GiB (62.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: f4addf64-b459-401c-8cec-c194cf8301b4
  ID-4: /run/media/victor/RAID raw-size: 2.73 TiB size: 2.73 TiB (100.00%)
    used: 2.61 TiB (95.6%) fs: ntfs dev: /dev/md126p2 maj-min: 259:5 label: RAID
    uuid: 2E3C78203C77E16F
  ID-5: /var/cache raw-size: 229.38 GiB size: 229.38 GiB (100.00%)
    used: 143.09 GiB (62.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: f4addf64-b459-401c-8cec-c194cf8301b4
  ID-6: /var/log raw-size: 229.38 GiB size: 229.38 GiB (100.00%)
    used: 143.09 GiB (62.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: f4addf64-b459-401c-8cec-c194cf8301b4
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: partition size: 8.8 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p3 maj-min: 259:3 label: swap
    uuid: 128c88d4-6db6-4ace-9804-be2b98cc0903
Unmounted:
  ID-1: /dev/md126p1 maj-min: 259:4 size: 128 MiB fs: <superuser required>
    label: N/A uuid: N/A
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 16 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 1-1:2 info: Logitech Internet 350 Keyboard type: keyboard,HID
    driver: hid-generic,usbhid interfaces: 2 rev: 1.1
    speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 100mA
    chip-ID: 046d:c313 class-ID: 0300
  Device-2: 1-5:3 info: Logitech Unifying Receiver type: keyboard,mouse,HID
    driver: logitech-djreceiver,usbhid interfaces: 3 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 98mA
    chip-ID: 046d:c52b class-ID: 0300
  Hub-2: 2-0:1 info: super-speed hub ports: 10 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-4: 4-0:1 info: super-speed hub ports: 2 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 32.0 C mobo: N/A gpu: nouveau temp: 50.0 C
  Fan Speeds (rpm): N/A gpu: nouveau fan: 0
Repos:
  Packages: pm: pacman pkgs: 1482 libs: 373 tools: pamac pm: flatpak pkgs: 0
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://muug.ca/mirror/manjaro/stable/$repo/$arch
    2: https://volico.mm.fcix.net/manjaro/stable/$repo/$arch
    3: https://mirror.vinehost.net/manjaro/stable/$repo/$arch
    4: https://ftp.nluug.nl/pub/os/Linux/distr/manjaro/stable/$repo/$arch
    5: https://ftp.tsukuba.wide.ad.jp/Linux/manjaro/stable/$repo/$arch
    6: https://manjaro.mirror.garr.it/manjaro/stable/$repo/$arch
    7: https://mirror.xeonbd.com/manjaro/stable/$repo/$arch
    8: https://mirror.dc.uz/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 239
  1: cpu: 3.2% command: dolphin pid: 1253 mem: 272.3 MiB (1.7%)
  2: cpu: 2.7% command: mdadm.txt started-by: notepadqq-bin pid: 2327
    mem: 390.9 MiB (2.4%)
  3: cpu: 2.4% command: Xorg pid: 647 mem: 101.4 MiB (0.6%)
  4: cpu: 2.2% command: QtWebEngineProcess pid: 2489 mem: 115.2 MiB (0.7%)
  5: cpu: 2.0% command: kwin_x11 pid: 828 mem: 165.4 MiB (1.0%)
  Memory top: 5 of 239
  1: mem: 390.9 MiB (2.4%) command: mdadm.txt started-by: notepadqq-bin
    pid: 2327 cpu: 2.7%
  2: mem: 342.5 MiB (2.1%) command: plasmashell pid: 884 cpu: 1.3%
  3: mem: 272.3 MiB (1.7%) command: dolphin pid: 1253 cpu: 3.2%
  4: mem: 201.5 MiB (1.2%) command: thumbnail.so started-by: kioworker
    pid: 1273 cpu: 2.0%
  5: mem: 165.4 MiB (1.0%) command: kwin_x11 pid: 828 cpu: 2.0%
Info:
  Processes: 239 Power: uptime: 11m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 6.16 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
    tool: systemctl
  Compilers: clang: 20.1.8 gcc: 15.2.1 alt: 14 Shell: Zsh v: 5.9
    default: Bash v: 5.3.3 running-in: konsole inxi: 3.3.40

Thoughts
As to fake RAID or not, the MB isn’t marketed as fake RAID though the output above does suggest it is.

While I could create unit files, this again defeats the purpose of the built-in automount feature of the OS. The product has been working fine for years and the option is not listed as deprecated, so there should be no reason to work around it if it was functioning properly. I’d rather get the built-in utility working again if possible before abandoning it and doing something on my own which would be less likely to get any support.

Questions
A couple things are also not clear from your post.

  1. Why is /run/media/... a bad path? This is the default and has been working fine for years. All my configurations point to this.

  2. In your unit file sample, you indicate /dev/md126p2 should be mounted but this doesn’t exist. It is only in the old image, but not the upgraded one. If I could get that far, the mounting is fairly trivial as you’ve shown. How do I get from sda2 and sdb2 to md126p2?

What is the relevance of this? It seems disconnected from your prior statement. I do not have this file on my upgraded system. Forgot to check on the older image.

Closing
Thanks for your comments so far. I hope to hear back from you soon. At present my system is considered down as I cannot perform any write operation on my RAID as it would further desync the drives and potentially lead to data loss once they are sync’d again. Appreciate your time and understanding!

6

The relevance is that it is part of getting to understand your system configuration and the output is as stated examples of what to expect to see.

The fact that you do not see similar output is setting a direction.

The same goes for the content of your configuration in /etc/mdadm.conf

madm.conf

I assume the following is the last lines in the file /etc/mdadm.conf when you use a snapshot? Meaning before the update?

When these lines are part of your configuration before the update, something must have gone haywire during the update if the lines is no longer a part of your configuration.

Without diving into the why’s I am thinking that you should try adding the lines above at the end of the configuration file.

The configuration lines are essential for the kernel to be able to assemble the disk array.

After you added the lines - restart your system.

test for kernel regression

If this doesn’t get your RAID online, I am thinking that some back-ported security-fix has created a regression with kernel 6.12.48 and 6.12.90.

I am thinking you should sync the 6.18 kernel and reboot - before reboot - ensure the /etc/mdadm.conf contains the lines for configuring the disk array.

Notes

Plasma is not the OS - it is the desktop - whatever you configured is a user configuration and as such the /run/... tree is what is used for mounting.

The /run/... tree is a volatile structure which is populated when the system is running - hence the /run folder name.

A system wide disk configuration - which should be available in a non volatile location - will never point to a volatile location.

If you want to know more about Linux you can visit the kernel documentation RAID arrays — The Linux Kernel documentation

:thinking: indications

The inxi above - is when using Linux 6.12.48 - and it has been assembled correct.

As per your inxi output

RAID:
  Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 port: f020
    bus-ID: 00:17.0 chip-ID: 8086:2822 rev: class-ID: 0104
  Supported mdraid levels: raid1
  Device-1: md126 maj-min: 9:126 type: mdraid level: mirror status: active
    size: 2.73 TiB
  Info: report: 2/2 UU blocks: 2930264064 chunk-size: N/A
  Components: Online:
  0: sdb maj-min: 8:16 size: 2.73 TiB
  1: sda maj-min: 8:0 size: 2.73 TiB
  Device-2: md127 maj-min: 9:127 type: mdraid level: N/A status: inactive
    size: N/A
  Info: report: N/A blocks: 5040 chunk-size: N/A
  Components: Online: N/A Spare:
  0: sda maj-min: 8:0 size: 2.73 TiB state: S
  1: sdb maj-min: 8:16 size: 2.73 TiB state: S

And this must be the automounted partition - which at the time you ran inxi was not mounted - is that correct assumption?

Unmounted:
  ID-1: /dev/md126p1 maj-min: 259:4 size: 128 MiB fs: <superuser required>
    label: N/A uuid: N/A

Because you have these lines in /etc/mdadm.conf

ARRAY /dev/md/imsm0 metadata=imsm UUID=1c8946ad:ff1e4ca1:a87d8e06:47580247
ARRAY /dev/md/RAID_0 container=/dev/md/imsm0 member=0 UUID=c850e72a:7fc6b853:c49abf3f:f226e972

When you are using Linux 6.12.48 - what is the output from

cat /proc/mdstat

When you boot into the snapshot with Linux 6.12.90, I have understood that those lines is not present in /etc/mdadm.conf - is that correct?

I think and you can verify if - using Linux 6.12.90 - edit the file /etc/mdadm.conf to contain (at the bottom of the file) the lines

ARRAY /dev/md/imsm0 metadata=imsm UUID=1c8946ad:ff1e4ca1:a87d8e06:47580247
ARRAY /dev/md/RAID_0 container=/dev/md/imsm0 member=0 UUID=c850e72a:7fc6b853:c49abf3f:f226e972

Save the file and reboot using Linux 6.12.90

product or community

Your statement assumes that Manjaro is a product to consume, so I have to say - it is not.

Manjaro is not a product but a community built around a derivative of Arch Linux - each and everyone on the forum is part of this community.

Yes - one of the original founders created a consulting business named Manjaro which should not be mistaken for the community you find here.

That founder is also the one maintaining the kernels along with patches for quirks with some common consumer devices which has not yet received upstream kernel support.

That founder is also the one who manages when testing branch is safe to roll out on stable branch.

With relation to the system you are using - Manjaro is a community not a product.

What you do with your system is entirely your responsibility.

about raid

fake raid

A fake raid is a software implementation stored in your systems firmware.

real raid

An PCIe card with a CPU and a firmware and one or more disks attached - and the kernel will only ever see the disk(s) exposed by the controller.

disk maintenance - such as replacing a failing disk - often requires downtime for replacement and rebuilding.

mdraid

Linux mdraid is a software raid implemented as part of the kernel.

mdraid has several modes not offered by other implementations.

One of those is my favorite because it makes it possible to create a special raid with the performance of raid0 with the redundancy of raid1 on two disks.

I use this combined with a spare on my mirror server and it is rock solid.

The reason I mention this

  • It appears you are not dual-booting windows
  • I therefore assume that your NTFS formatted raid is a remnant
  • Why using a non-Linux file system on a Linux box
  • I believe it to be a much better solution

In the end it is your system - you can do anything you want - but keeping a reliance on NTFS using Linux system is bound to end bad at some point.

7

Edit
I may be encountering this issue. I have had need to set the dirty bit due to bad super block errors in the past. Was the black listing of ntfs3 mentioned previously an attempt to work around this problem?

Adding:

ARRAY /dev/md/imsm0 metadata=imsm UUID=1c8946ad:ff1e4ca1:a87d8e06:47580247
ARRAY /dev/md/RAID_0 container=/dev/md/imsm0 member=0 UUID=c850e72a:7fc6b853:c49abf3f:f226e972

To /etc/mdadm.conf had no impact. In my prior post, I indicated that my /etc/mdadm.conf file is empty on both the snapshot and upgraded versions. The output shown comes from the mdadm -D --scan command.

I got the /proc/mdstat from the old snapshot:

cat /proc/mdstat
Personalities : [raid1]
md126 : active (auto-read-only) raid1 sda[1] sdb[0]
      2930264064 blocks super external:/md127/0 [2/2] [UU]

md127 : inactive sdb[1](S) sda[0](S)
      5040 blocks super external:imsm

unused devices: <none>

For the kernels, my only lower options are:

  • 6.6.141-1
  • 6.6.135_rt74-1
  • 6.12.89_rt18-1

I do not have the version you indicated and see no way to add it. I tried with 6.6.141-1 including the mdadm.conf file change as requested and still see no difference.

Incorrect. The automounted partition is md126p2. The p1 variant is for a small Windows partition that doesn’t get used and does not need to be mounted. Never looked into why it doesn’t mount as it is unused.

I agree that NTFS is not a great choice for a file system on Linux. At the time it was created, NTFS was the only viable option. I have run into other issues with it, some sectors may be going bad, but nothing this problematic. I will change this when I can, I don’t have drives standing by in which I an easily perform backups nor rebuild. My only other drive of comparable size runs over USB 2.0, it would take days to move 3 TB over that connection. I’ll buy new drives that are larger and will move the data in time. That will take time.

Sadly I can’t even fully use the old snapshot. The update has changed things within the home directory (caches / settings) so parts of the old snapshot are now broke too. I’d need to use a mix of snapshots until the RAID can be rebuilt, not ideal.

Thanks for your comments so far. If you have any other suggestions, I’m willing to try.

8

If you have the dirty bit set then yes, probably this is the problem. The default driver is now ntfs3 and it won’t mount if the bit is set. On single drives “fixed” in fstab, on raid i have no idea.
If you are feeling adventurous you can test kernel 7.1 where an even newer driver is used.

9

That makes no sense - the content of the /proc/... tree is a volatile structure which only exist at runtime.

This is the command used to generate the information that goes into /etc/mdadm.conf (root context - no sudo)

mdadm --detail --scan >> /etc/mdadm.conf

Verify that you only have the lines generated - remove duplicates (if any)

Then assemble the array (root context or sudo)

mdadm --assemble --scan

Then check using

cat /proc/mdstat

To get the latest LTS kernel, you can execute (root context or sudo)

mhwd-kernel -i linux618

It may be an idea to remove unused kernels - if present - they will contribute to the size of an update even if they are never used.

Realtime kernels (-rt) - evaluate if you really need rt-kernel - as optimized kernel for e.g. music and video production or other high-precision requirement use-cases. More info → Realtime kernel - ArchWiki

In any case remove installed kernels below 6.12 as you may get issues with system >= 260.

To list installed kernels

mhwd-kernel -li

To list available kernels

mhwd-kernel -l
10

Sorry if my update was not clear. By “from the old snapshot” I mean I booted into the working image and then pulled this information. I did not dissect the image to pull this from the saved data, cause as you mentioned, this wouldn’t even be in there.

I did as instructed in regards to assembling mdadm:

su root
Password: 
[victor victor]# cat /etc/mdadm.conf
# mdadm configuration file
#
# mdadm will function properly without the use of a configuration file,
# but this file is useful for keeping track of arrays and member disks.
# In general, a mdadm.conf file is created, and updated, after arrays
# are created. This is the opposite behavior of /etc/raidtab which is
# created prior to array construction.
#
#
# the config file takes two types of lines:
#
#       DEVICE lines specify a list of devices of where to look for
#         potential member disks
#
#       ARRAY lines specify information about how to identify arrays so
#         so that they can be activated
#
# You can have more than one device line and use wild cards. The first
# example includes SCSI the first partition of SCSI disks /dev/sdb,
# /dev/sdc, /dev/sdd, /dev/sdj, /dev/sdk, and /dev/sdl. The second
# line looks for array slices on IDE disks.
#
#DEVICE /dev/sd[bcdjkl]1
#DEVICE /dev/hda1 /dev/hdb1
#
# If you mount devfs on /dev, then a suitable way to list all devices is:
#DEVICE /dev/discs/*/*
#
# The designation "partitions" will scan all partitions found in
# /proc/partitions
DEVICE partitions

# The AUTO line can control which arrays get assembled by auto-assembly,
# meaing either "mdadm -As" when there are no 'ARRAY' lines in this file,
# or "mdadm --incremental" when the array found is not listed in this file.
# By default, all arrays that are found are assembled.
# If you want to ignore all DDF arrays (maybe they are managed by dmraid),
# and only assemble 1.x arrays if which are marked for 'this' homehost,
# but assemble all others, then use
#AUTO -ddf homehost -1.x +all
#
# ARRAY lines specify an array to assemble and a method of identification.
# Arrays can currently be identified by using a UUID, superblock minor number,
# or a listing of devices.
#
#       super-minor is usually the minor number of the metadevice
#       UUID is the Universally Unique Identifier for the array
# Each can be obtained using
#
#       mdadm -D <md>
#
#ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371
#ARRAY /dev/md1 super-minor=1
#ARRAY /dev/md2 devices=/dev/hda1,/dev/hdb1
#
# ARRAY lines can also specify a "spare-group" for each array.  mdadm --monitor
# will then move a spare between arrays in a spare-group if one array has a failed
# drive but no spare
#ARRAY /dev/md4 uuid=b23f3c6d:aec43a9f:fd65db85:369432df spare-group=group1
#ARRAY /dev/md5 uuid=19464854:03f71b1b:e0df2edd:246cc977 spare-group=group1
#
# When used in --follow (aka --monitor) mode, mdadm needs a
# mail address and/or a program.  This can be given with "mailaddr"
# and "program" lines to that monitoring can be started using
#    mdadm --follow --scan & echo $! > /run/mdadm/mon.pid
# If the lines are not found, mdadm will exit quietly
#MAILADDR root@mydomain.tld
#PROGRAM /usr/sbin/handle-mdadm-events

ARRAY /dev/md/imsm0 metadata=imsm UUID=1c8946ad:ff1e4ca1:a87d8e06:47580247
ARRAY /dev/md/RAID_0 container=/dev/md/imsm0 member=0 UUID=c850e72a:7fc6b853:c49abf3f:f226e972
[victor victor]# mdadm --assemble --scan
[victor victor]# cat /proc/mdstat
cat: /proc/mdstat: No such file or directory
[victor victor]# exit

You can see that from root the mdadm.conf file has the two lines shown by the scan output from when I was booted into the working snapshot. I then ran the assemble command provided and still the /proc/mdstat file does not exist.

11

Just for the record, the Arch Wiki recommends dmraid instead of mdraid for FakeRAID arrays. mdraid is a Linux pure software RAID, and it requires that the FakeRAID is disabled in the BIOS or UEFI firmware setup.

12

Hmm - I didn’t spot that - I have never used fakeRAID only controller card raid.

:man_facepalming:

This explain a lot - I am asking the wrong questions - and I don’t have the same validation options as I have with the kernel implementation mdraid.

13

Same thing here; I have only ever used real hardware RAID — Adaptec controller cards. :wink:

14

Thank you all for your comments. As it looks like this was not something I could easily fix, I spent the last day and a half cloning my drives to a backup (which was a true hardware raid 5, also with ntfs). I have now recreated the array without FakeRaid using mdadm and SoftRaid and an ext4 file system. I am now in the process of cloning the data back.
I appreciate you trying to fix this for me.

3 Likes