OrangePi 5 Wont Boot When RAID Drives Connected

Troubleshooting
1

Creating a bug report/issue

I have searched the existing open and closed issues

Required Information

  • DietPi version | cat /boot/dietpi/.version
    G_DIETPI_VERSION_CORE=10
    G_DIETPI_VERSION_SUB=0
    G_DIETPI_VERSION_RC=1
    G_GITBRANCH=‘master’
    G_GITOWNER=‘MichaIng’

  • Distro version | echo $G_DISTRO_NAME $G_RASPBIAN
    trixie

  • Kernel version | uname --all
    Linux DietPi 6.1.115-vendor-rk35xx #1 SMP Wed Dec 24 10:54:39 UTC 2025 aarch64 GNU/Linux

  • Architecture | dpkg --print-architecture
    arm64

  • SBC model | echo $G_HW_MODEL_NAME or (EG: RPi3)
    Orange Pi 5 (aarch64)

  • Power supply used | (EG: 5V 1A RAVpower)
    5V 4A ~20W

  • SD card used | (EG: SanDisk ultra)
    none

Additional Information (if applicable)

  • before using RAID it ran fine
  • recently setting up RAID and have a problem it won’t boot after a reboot/poweroff if RAID disks is being attached.
  • using this SATA to NVME (5 ports)
    Sata to NVME
    Sata to NVME800×800 26.8 KB
  • i have couples of SSD/HDD
    1. SSD 128GB SATA (OS) - Port 1
    2. HDD 1TB XFS (RAID0) - Port 2 - separated PSU
    3. HDD 1TB XFS (RAID0) - Port 3 - separated PSU
    4. HDD 1TB EXT4 (NO RAID) - USB A 3.0 Port

Steps to reproduce

  1. Reboot/Poweroff
  2. not BOOTING (connect to Display, seems can’t even reach the first bootlog)

Expected behaviour

  • Booting

Actual behaviour

  • powered off
  • unplug SATA Port 2 and 3 (RAID Disks)
  • turn ON OPi5
  • Replug SATA after booted and remount

Extra details

root@DietPi:~# lsblk
NAME      MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
sda         8:0    0 111.8G  0 disk
└─sda1      8:1    0 111.8G  0 part  /              - PORT 1 SATA to NVME
sdb         8:16   0 931.5G  0 disk
└─sdb1      8:17   0 931.5G  0 part  /var/www/hd1   - USB A 3 Port
                                     /mnt/hd1
sdc         8:32   0 931.5G  0 disk
└─md0       9:0    0   2.7T  0 raid0
  └─md0p1 259:0    0   2.7T  0 part  /var/www/hd2   - PORT 2 SATA to NVME
                                     /mnt/hd2
sdd         8:48   0   1.8T  0 disk
└─md0       9:0    0   2.7T  0 raid0
  └─md0p1 259:0    0   2.7T  0 part  /var/www/hd2   - PORT 3 SATA to NVME
                                     /mnt/hd2
mtdblock0  31:0    0    16M  0 disk

root@DietPi:~# blkid
/dev/sda1: UUID="b5ffad73-5909-4c89-b018-6b27f752e4b4" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="root" PARTUUID="0d4393da-6a40-45b3-8d2a-95821c4320cb"
/dev/sdb1: UUID="66a22db6-65c2-47ac-93d8-da5b9e101fa4" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="primary" PARTUUID="2e533825-70fd-48bd-93eb-be1dd986c533"
/dev/md0p1: UUID="87c2d1d7-a035-4d20-ba26-1b3a02832576" BLOCK_SIZE="4096" TYPE="xfs" PARTLABEL="primary" PARTUUID="0ff5ca6e-ab5f-4b2d-bfb1-dbf0b827abab"
/dev/sdd: UUID="56f3927c-77f7-5be2-8c31-53ffa7fc328b" UUID_SUB="63173827-4bf9-808d-91f7-13fd90a1e8f6" LABEL="DietPi:0" TYPE="linux_raid_member"
/dev/sdc: UUID="56f3927c-77f7-5be2-8c31-53ffa7fc328b" UUID_SUB="a89a3bab-ed58-122d-ec56-f630e771bd72" LABEL="DietPi:0" TYPE="linux_raid_member"

root@DietPi:~# cat /boot/dietpiEnv.txt
rootdev=UUID=b5ffad73-5909-4c89-b018-6b27f752e4b4
rootfstype=ext4
# The init system logs to the console defined last.
consoleargs=console=tty1
extraargs=fsck.repair=yes net.ifnames=0
docker_optimizations=off
overlay_path=rockchip
# Multiple prefixes are supported separated by space
overlay_prefix=orangepi-5 rockchip-rk3588 rk3588 rockchip
overlays=dwc3-host
user_overlays=
2

nvm, i’m just gonna moving to armbian

:poop:

3

Good luck with that.
My guess it cannot handle RAID so early in the boot process. You can try to mark the drives as non-critical in the fstab via nofail optionand applying a timeout.

Or you could create a service to mount the RAID after boot has finished.

:thinking:
Could be also a powering issue, but IDK how well the OPi 5 handles USB power plus power delivery via the HAT. And without logs from the boot process this is only speculation.

If you’re willing you can report back if it’s working on Armbian.

4

yes, it works on Armbian 26.2.1

Well no Power is via OPi, so it’s not Power problem, I believed. that’s why i said can’t tell where the boot it’s stucked bcs can’t get into boot logging

Yes the problem was it wont even reach the boot logs, so adding nofail was a no go or adding “mounting” after booting as well was a no go.

Like it had to be unplugged (DATA SATA Cable) to be able to reach the “booting logs”, and replugged after it booted.

5

So even no output via UART? Or what do you mean with “you can’t get into boot logging”?