MX19 Raid5 Array not found after MX23 install

Help for Current Versions of MX
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
Message
Author
User avatar
RayJay62
Posts: 3
Joined: Thu Dec 06, 2018 3:45 pm

MX19 Raid5 Array not found after MX23 install

#1 Post by RayJay62 »

Hi All,

I did a manual upgrade from MX19 to MX21 then did a fresh install to get to MX23 per the migration information page.
Prior to MX23, I had a working Raid5 iRST Array.
After the MX23 install, the iRST shows all disks as not in an array and mdadm show 1 disk with a partition and the others with MBR Magic number.
The 4 disks for the Raid (sda/b/c/d) are spindles and the install disk is an SSD (sde).

My machine info is below.
Did I miss something a screw my Raid? Or is it still there and recoverable?
I am open to suggestions.

Thanks
Ray

Code: Select all

System:
  Kernel: 6.1.0-17-amd64 [6.1.69-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-17-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23.1_x64 Libretto October 15  2023 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Desktop Mobo: ASUSTeK model: P8Z68-V PRO GEN3 v: Rev 1.xx serial: <superuser required>
    BIOS: American Megatrends v: 3202 date: 02/17/2012
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse MX Master 3 serial: <filter> charge: 100%
    (should be ignored) rechargeable: yes status: discharging
CPU:
  Info: model: Intel Core i7-2600 bits: 64 type: MT MCP arch: Sandy Bridge gen: core 2 level: v2
    built: 2010-12 process: Intel 32nm family: 6 model-id: 0x2A (42) stepping: 7 microcode: 0x2F
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 256 KiB
    desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 1645 high: 1813 min/max: 1600/5900 scaling: driver: intel_cpufreq
    governor: ondemand cores: 1: 1605 2: 1605 3: 1600 4: 1600 5: 1626 6: 1813 7: 1600 8: 1713
    bogomips: 54580
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: retbleed status: Not affected
  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: Retpolines, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB
    filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: ASUSTeK
    driver: i915 v: kernel arch: Gen-6 code: Sandybridge process: Intel 32nm built: 2011 ports:
    active: none empty: DP-1, DP-2, DP-3, HDMI-A-1, HDMI-A-2, HDMI-A-3, VGA-1 bus-ID: 00:02.0
    chip-ID: 8086:0102 class-ID: 0380
  Device-2: NVIDIA GP104 [GeForce GTX 1070] vendor: PNY driver: nouveau v: kernel
    non-free: 530.xx+ status: current (as of 2023-03) arch: Pascal code: GP10x process: TSMC 16nm
    built: 2016-21 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s ports:
    active: DP-4,DP-5 empty: DP-6,DVI-D-1,HDMI-A-4 bus-ID: 01:00.0 chip-ID: 10de:1b81
    class-ID: 0300 temp: 46.0 C
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: nouveau gpu: nouveau display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x285mm (40.00x11.22")
    s-diag: 1055mm (41.54")
  Monitor-1: DP-4 pos: primary,left model: Acer H213H serial: <filter> built: 2009 res: 1920x1080
    hz: 60 dpi: 92 gamma: 1.2 size: 531x299mm (20.91x11.77") diag: 551mm (21.7") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  Monitor-2: DP-5 pos: right model: LG (GoldStar) FULL HD serial: <filter> built: 2018
    res: 1920x1080 hz: 60 dpi: 102 gamma: 1.2 size: 480x270mm (18.9x10.63") diag: 551mm (21.7")
    ratio: 16:9 modes: max: 1920x1080 min: 720x400
  API: OpenGL v: 4.3 Mesa 22.3.6 renderer: NV134 direct-render: Yes
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: ASUSTeK 6
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1c20 class-ID: 0403
  Device-2: NVIDIA GP104 High Definition Audio vendor: PNY 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:10f0 class-ID: 0403
  API: ALSA v: k6.1.0-17-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel 82579V Gigabit Network vendor: ASUSTeK P8P67 Deluxe driver: e1000e v: kernel
    port: f080 bus-ID: 00:19.0 chip-ID: 8086:1503 class-ID: 0200
  IF: eth0 state: down mac: <filter>
  Device-2: Ralink RT2760 Wireless 802.11n 1T/2R driver: rt2800pci v: 2.3.0 modules: wl
    bus-ID: 07:01.0 chip-ID: 1814:0701 class-ID: 0280
  IF: wlan0 state: up mac: <filter>
Bluetooth:
  Device-1: ASUSTek Bluetooth Adapter type: USB driver: btusb v: 0.8 bus-ID: 4-1.7:6
    chip-ID: 0b05:179c class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 1 state: down bt-service: N/A rfk-block: hardware: no
    software: no address: <filter>
  Info: acl-mtu: 1022:8 sco-mtu: 121:3 link-policy: rswitch hold sniff
    link-mode: peripheral accept
RAID:
  Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 port: f060 bus-ID: 00:1f.2
    chip-ID: 8086:2822 rev: N/A class-ID: 0104
Drives:
  Local Storage: total: 4.09 TiB used: 15.23 GiB (0.4%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000NM0033-9ZM173 size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: SN04 scheme: MBR
  ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST1000NM0033-9ZM173 size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: SN04 scheme: MBR
  ID-3: /dev/sdc maj-min: 8:32 vendor: Seagate model: ST1000NM0033-9ZM173 size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: SN04 scheme: MBR
  ID-4: /dev/sdd maj-min: 8:48 vendor: Seagate model: ST1000NM0033-9ZM173 size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: SN04 scheme: MBR
  ID-5: /dev/sde maj-min: 8:64 vendor: Samsung model: SSD 850 EVO 500GB size: 465.76 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q
    scheme: MBR
Partition:
  ID-1: / raw-size: 465.76 GiB size: 457.38 GiB (98.20%) used: 15.23 GiB (3.3%) fs: ext4
    dev: /dev/sde1 maj-min: 8:65
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 6 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 36.0 C mobo: N/A gpu: nouveau temp: 46.0 C
  Fan Speeds (RPM): N/A gpu: nouveau fan: 0
Repos:
  Packages: pm: dpkg pkgs: 2088 libs: 1053 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [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 bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://la.mxrepo.com/mx/repo/ bookworm main non-free
Info:
  Processes: 298 Uptime: 49m wakeups: 7 Memory: 31.24 GiB used: 2.48 GiB (7.9%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)

User avatar
CharlesV
Administrator
Posts: 8094
Joined: Sun Jul 07, 2019 5:11 pm

Re: MX19 Raid5 Array not found after MX23 install

#2 Post by CharlesV »

As I recall there is a mdadm config file that contains the information about your RAID array. I am not sure the differences in versions, but there was a difference for me with a RAID0 on mx19 when I went to mx21.

I was able to get back up onto my array, but I had some issues and just recreated it all in the end.

I would compare the two mdadm config files and see what the differences are as a starting place.

A note here - I have run RAID5 arrays for years and have found it to be FAR better to run twin SSD's in a RAID1 or move to a RAID10. RAID5 has some very serious drawbacks as well as speed issues (and the hole!). And if you want BLAZING speed - then you should give high end SSD's in a RAID0 a try - OMG fast!

On linux I found that zfs seemed far more efficient then running RAID, but I ended up heading off to uber fast NVMe's and havent looked back.
*QSI = Quick System Info from menu (Copy for Forum)
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!

Post Reply

Return to “MX Help”