Hello,
I starting using linux maybe 2 weeks ago. I learned how to create raid by following arch wiki. Array mounts and functions well. On system reboot, array is gone. I look at mdadm.conf, array UUID is listed. Tried to add array to /etc/fstab results in boot failure. Had to nano /etc/fstab and remove the array (took many hours to learn to do this xD) I have been searching for days and haven’t been able to find a solution. Can anyone help me with this?
Did you use garuda?
Yes, I am using Garuda Hyperland
Call me picky, but it should be Hyprland and Garuda uses micro not nano 
Why do you want to use Hyprland as a beginner?
It’s for experienced users and still in beta.
As I don’t use a RAID system myself, I’m afraid I can’t help you, also bear in mind that we are not a general technical forum, but are mainly concerned with the Garuda Linux OS.
I understand. I did not know this micro. Nano did work but micro maybe better?
I sampled each one and I like the Hyperland UI the most. But maybe that’s why it’s not working? I will try a different one.
Thank you for your reply ^.^
It’s easier for Linux beginners.
Hyprland, without the e
No, it’s just the desktop enviroment.
And, please, always follow the template and post the garuda-inxi, it helps the helpers a lot and reduces the forum by many unnecessary questions.
BTW, welcome
I will use this.
Okay, I will correct this xD
Okay, I will read how to do this. Thank you!
Type garuda-inxi command into your terminal, paste the log here and format the text with the </> function.
?
This?
https://wiki.archlinux.org/title/RAID
Garuda use Btrfs
Btrfs offers native “RAID” for #Multi-device file systems. Notable features which set Btrfs RAID apart from mdadm are self-healing redundant arrays and online balancing. See the Btrfs wiki page for more information. The Btrfs sysadmin page also has a section with some more technical background.
Warning: Parity RAID (RAID 5/6) code has multiple serious data-loss bugs in it. See the Btrfs Wiki’s RAID5/6 page and a bug report on linux-btrfs mailing list for more detailed information. In June 2020, somebody posted a comprehensive list of current issues and a helpful recovery guide.
System:
Kernel: 6.10.10-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=ecc7fea0-2d72-400d-bd03-6ac885fa0cae rw rootflags=subvol=@
quiet rd.luks.uuid=489b775c-e5ec-4559-a377-258fcd0834a7
rd.luks.uuid=a222b2b5-cf7a-49a2-8e30-7c4e64219e7c
resume=/dev/mapper/luks-a222b2b5-cf7a-49a2-8e30-7c4e64219e7c loglevel=3
ibt=off
Desktop: KDE Plasma v: 6.1.5 tk: Qt v: N/A info: frameworks v: 6.6.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: ROG STRIX B650E-F GAMING WIFI v: Rev 1.xx
serial: <superuser required> part-nu: SKU uuid: <superuser required>
UEFI: American Megatrends v: 3024 date: 08/02/2024
CPU:
Info: model: AMD Ryzen 9 7950X3D bits: 64 type: MT MCP MCM arch: Zen 4
gen: 5 level: v4 note: check built: 2022+ process: TSMC n5 (5nm)
family: 0x19 (25) model-id: 0x61 (97) stepping: 2 microcode: 0xA601206
Topology: cpus: 1x cores: 16 tpc: 2 threads: 32 dies: 2 smt: enabled
cache: L1: 1024 KiB desc: d-16x32 KiB; i-16x32 KiB L2: 16 MiB
desc: 16x1024 KiB L3: 128 MiB desc: 1x32 MiB, 1x96 MiB
Speed (MHz): avg: 841 high: 3913 min/max: 545/5759 scaling:
driver: amd-pstate-epp governor: powersave cores: 1: 545 2: 3594 3: 545
4: 545 5: 545 6: 545 7: 545 8: 545 9: 545 10: 3913 11: 545 12: 545 13: 545
14: 545 15: 3600 16: 545 17: 545 18: 545 19: 545 20: 545 21: 545 22: 545
23: 545 24: 545 25: 545 26: 545 27: 545 28: 545 29: 545 30: 545 31: 545
32: 545 bogomips: 268801
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Navi 31 [Radeon RX 7900 XT/7900 XTX/7900M] vendor: XFX
driver: amdgpu v: kernel arch: RDNA-3 code: Navi-3x process: TSMC n5 (5nm)
built: 2022+ pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-1
empty: DP-2, DP-3, HDMI-A-1, Writeback-1 bus-ID: 03:00.0
chip-ID: 1002:744c class-ID: 0300
Device-2: AMD Raphael vendor: ASUSTeK driver: amdgpu v: kernel
arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie:
gen: 4 speed: 16 GT/s lanes: 16 ports: active: HDMI-A-2
empty: DP-4,Writeback-2 bus-ID: 0f:00.0 chip-ID: 1002:164e class-ID: 0300
temp: 34.0 C
Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.2
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu,amdgpu d-rect: 4480x1440 display-ID: 0
Monitor-1: DP-1 pos: right res: 2560x1440 size: N/A modes: N/A
Monitor-2: HDMI-A-2 pos: primary,left res: 1920x1080 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: radeonsi device: 2 drv: swrast gbm: drv: kms_swrast
surfaceless: drv: radeonsi wayland: drv: radeonsi x11: drv: radeonsi
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.2.2-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon Graphics (radeonsi
raphael_mendocino LLVM 18.1.8 DRM 3.57 6.10.10-zen1-1-zen)
device-ID: 1002:164e memory: 500 MiB unified: no display-ID: :1.0
API: Vulkan v: 1.3.295 layers: 9 device: 0 type: integrated-gpu name: AMD
Radeon Graphics (RADV RAPHAEL_MENDOCINO) driver: mesa radv
v: 24.2.2-arch1.1 device-ID: 1002:164e surfaces: xcb,xlib,wayland
device: 1 type: discrete-gpu name: AMD Radeon RX 7900 XT (RADV NAVI31)
driver: mesa radv v: 24.2.2-arch1.1 device-ID: 1002:744c
surfaces: xcb,xlib,wayland device: 2 type: cpu name: llvmpipe (LLVM
18.1.8 256 bits) driver: mesa llvmpipe v: 24.2.2-arch1.1 (LLVM 18.1.8)
device-ID: 10005:0000 surfaces: xcb,xlib,wayland
Audio:
Device-1: AMD Navi 31 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:ab30
class-ID: 0403
Device-2: AMD Rembrandt Radeon High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0f:00.1 chip-ID: 1002:1640 class-ID: 0403
Device-3: SteelSeries ApS Arctis Nova Pro
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 480 Mb/s
lanes: 1 mode: 2.0 bus-ID: 1-12:12 chip-ID: 1038:12cb class-ID: 0300
Device-4: ASUSTek USB Audio driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-6:3
chip-ID: 0b05:1a52 class-ID: 0300
API: ALSA v: k6.10.10-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.2.3 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 Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel pcie:
gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: 0a:00.0 chip-ID: 8086:15f3
class-ID: 0200
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
vendor: Foxconn driver: mt7921e v: kernel pcie: gen: 2 speed: 5 GT/s
lanes: 1 bus-ID: 0b:00.0 chip-ID: 14c3:0616 class-ID: 0280
IF: wlp11s0 state: down mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Foxconn / Hon Hai Wireless_Device driver: btusb v: 0.8 type: USB
rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-11:10
chip-ID: 0489:e0e2 class-ID: e001 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.3
lmp-v: 12 status: discoverable: no pairing: no class-ID: 6c0104
RAID:
Supported mdraid levels: raid10
Device-1: md127 maj-min: 9:127 type: mdraid level: raid-10 status: active
size: 7.28 TiB
Info: report: 4/4 UUUU blocks: 7813772288 chunk-size: 512K
super-blocks: 1.2
Components: Online:
0: sda1 maj-min: 8:1 size: 3.64 TiB
1: sdb1 maj-min: 8:17 size: 3.64 TiB
2: sdc1 maj-min: 8:33 size: 3.64 TiB
3: sdd1 maj-min: 8:49 size: 3.64 TiB
Drives:
Local Storage: total: raw: 19.33 TiB usable: 12.05 TiB
used: 21.73 GiB (0.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:5 vendor: Crucial model: CT2000P3PSSD8
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: P9CR40D temp: 23.9 C
scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:4 vendor: Crucial model: CT2000P3PSSD8
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: P9CR40D temp: 22.9 C
scheme: GPT
ID-3: /dev/nvme2n1 maj-min: 259:0 vendor: Seagate model: FireCuda 520 SSD
ZP1000GM30002 size: 931.51 GiB block-size: physical: 512 B logical: 512 B
speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter> fw-rev: STNSC014
temp: 23.9 C scheme: GPT
ID-4: /dev/sda maj-min: 8:0 vendor: Seagate model: ST4000VN008-2DR166
size: 3.64 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5980 serial: <filter> fw-rev: SC60 scheme: GPT
ID-5: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST4000VN008-2DR166
size: 3.64 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5980 serial: <filter> fw-rev: SC60 scheme: GPT
ID-6: /dev/sdc maj-min: 8:32 vendor: Seagate model: ST4000VN008-2DR166
size: 3.64 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5980 serial: <filter> fw-rev: SC60 scheme: GPT
ID-7: /dev/sdd maj-min: 8:48 vendor: Seagate model: ST4000VN008-2DR166
size: 3.64 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5980 serial: <filter> fw-rev: SC60 scheme: GPT
ID-8: /dev/sde maj-min: 8:64 model: USB 3.2.2 FD size: 232.89 GiB
block-size: physical: 512 B logical: 512 B type: USB rev: 3.2 spd: 5 Gb/s
lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: N/A fw-rev: PMAP scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 863.08 GiB size: 863.08 GiB (100.00%)
used: 21.73 GiB (2.5%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-489b775c-e5ec-4559-a377-258fcd0834a7
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 728 KiB (0.2%) fs: vfat dev: /dev/nvme2n1p1 maj-min: 259:1
ID-3: /home raw-size: 863.08 GiB size: 863.08 GiB (100.00%)
used: 21.73 GiB (2.5%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-489b775c-e5ec-4559-a377-258fcd0834a7
ID-4: /var/log raw-size: 863.08 GiB size: 863.08 GiB (100.00%)
used: 21.73 GiB (2.5%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-489b775c-e5ec-4559-a377-258fcd0834a7
ID-5: /var/tmp raw-size: 863.08 GiB size: 863.08 GiB (100.00%)
used: 21.73 GiB (2.5%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-489b775c-e5ec-4559-a377-258fcd0834a7
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: partition size: 68.13 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/dm-1 maj-min: 254:1
mapped: luks-a222b2b5-cf7a-49a2-8e30-7c4e64219e7c
ID-2: swap-2 type: zram size: 61.94 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 32 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 40.2 C mobo: 24.0 C
Fan Speeds (rpm): fan-2: 0 fan-3: 0 fan-4: 0 fan-5: 0
GPU: device: amdgpu temp: 27.0 C mem: 46.0 C fan: 0 watts: 13.00
device: amdgpu temp: 34.0 C
Info:
Memory: total: 64 GiB available: 61.94 GiB used: 4.42 GiB (7.1%)
Processes: 560 Power: uptime: 2m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 24.76 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1846 libs: 570 tools: octopi,paru Compilers:
clang: 18.1.8 gcc: 14.2.1 Shell: garuda-inxi default: fish v: 3.7.1
running-in: konsole inxi: 3.3.35
Garuda (2.6.26-1):
System install date: 2024-09-17
Last full system update: 2024-09-17
Is partially upgraded: No
Relevant software: snapper NetworkManager dracut
Windows dual boot: No/Undetected
Failed units: mdmonitor.service
Thank you for showing me this!
Yes, I used this one. I will look at this BTRFS raid and see if it works. Thank you so much!
Oh? What is this?
Some possible reasons for that failed service.
Start with a:
systemctl status mdmonitor
mdmonitor.service - MD array monitor
Loaded: loaded (/usr/lib/systemd/system/mdmonitor.service; static)
Active: failed (Result: exit-code) since Wed 2024-09-18 08:24:05 CDT; 2min 51s ago
Duration: 3ms
Invocation: 5e5191d448924d46ba5fe8db7126b76d
Docs: man:mdadm(8)
Process: 8314 ExecStartPre=/usr/lib/mdadm/mdadm_env.sh (code=exited, status=203/EXEC)
Process: 8318 ExecStart=/sbin/mdadm --monitor $MDADM_MONITOR_ARGS (code=exited, status=1/FAILURE)
Main PID: 8318 (code=exited, status=1/FAILURE)
Mem peak: 1.7M
CPU: 6ms
Sep 18 08:24:05 inaba-systemproductname systemd[1]: Starting MD array monitor...
Sep 18 08:24:05 inaba-systemproductname (m_env.sh)[8314]: mdmonitor.service: Unable to locate executable '/us>
Sep 18 08:24:05 inaba-systemproductname systemd[1]: Started MD array monitor.
Sep 18 08:24:05 inaba-systemproductname mdadm[8318]: mdadm: No mail address or alert command - not monitoring.
Sep 18 08:24:05 inaba-systemproductname systemd[1]: mdmonitor.service: Main process exited, code=exited, stat>
Sep 18 08:24:05 inaba-systemproductname systemd[1]: mdmonitor.service: Failed with result 'exit-code'.
Returns this. Thank you for your reply.
I have no experience at all in mdadm and RAID in general, but, at a quick look at those internet articles, I’m afraid that this failed service is just a red herring.
Probably this is just a monitoring service (so with no infoluence on the RAID operations) failing because no mail address has been configured.
If I understand correctly, this mail should have been defined with a script which for some reasons is not included in the package ( /usr/lib/systemd/scripts/mdadm_env.sh), but can anyway be defined in /etc/mdadm.conf or in a drop-in file, with smething like
MDADM_MAIL="root@localhost"
But, again, in my opinion this has nothing to deal with your issue.
Thank you for looking. The data is fine as long as I recreate the array correctly so I will back up and try the btrfs raid that @SGS posted and see if that works.
Using btrfs is working. Array persists between reboots now. Thanks!
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.