Hi all,

I'm hoping someone has seen this before because I'm running out of ideas.

Hardware

• AOOSTAR R7

• AMD Ryzen 7 5825U

• Dual Intel I226-V NICs

• Intel AX200 Wi-Fi

• SK Hynix P41 / PC801 1TB NVMe

• BIOS originally AR5000-M12 v0.22 (12/15/2023)

• Updated to the latest BIOS from AOOSTAR support

Symptoms

Unraid will boot normally, become available on the network, and then hard lock/reboot within a few minutes.

When it freezes:

• Network connectivity is lost

• Local console becomes unresponsive

• Keyboard Caps Lock / Num Lock no longer toggle

• Eventually the system reboots

What I've Tried

Hardware Testing

• Memtest completed successfully with no errors

• CPU temperatures around 38°C

• NVMe temperatures around 36°C

• System can sit in BIOS setup overnight without freezing

Unraid Testing

Tested with:

• Original Unraid installation

• Fresh USB stick

• Unraid 7.3.2

• Fresh Unraid 7.3.4 install

• Safe Mode

• Array stopped

• Docker disabled

• VM Manager disabled

All eventually reboot.

Kernel Parameters Tested

No improvement from:

processor.max_cstate=1

processor.max_cstate=1 nvme_core.default_ps_max_latency_us=0

iommu=off

amd_iommu=off

iommu=pt

Also tested blacklisting various drivers without success.

BIOS

• Updated to latest AOOSTAR BIOS

• SVM disabled for testing

• No obvious IOMMU setting available in BIOS

Interesting Findings

Ubuntu Live USB appears stable.

I booted Ubuntu from USB and left it running for several hours without issue while Unraid consistently reboots.

Ubuntu hardware:

Intel I226-V using igc driver

Intel AX200 using iwlwifi

AMD Barcelo iGPU using amdgpu

SK Hynix P41 NVMe using nvme

 

Unraid Logs

One of the few interesting messages I've seen is:

pcie_mp2_amd 0000:05:00.7: Failed to discover, sensors not enabled is 0

I also found some corrupted config files after the crashes:

/boot/config/share.cfg

/boot/config/plugins/dynamix/dynamix.cfg

Both were 0-byte files, but a completely fresh Unraid USB exhibits the same crash/reboot behavior, so I believe the corruption is a result of the crashes, not the cause.

Question

Has anyone successfully run an AOOSTAR R7 5825U with Unraid?

Has anyone seen known issues with:

• AMD Barcelo / Ryzen 5825U

• Intel I226-V

• AMD Sensor Fusion Hub (pcie_mp2_amd / amd_sfh)

• Recent Unraid kernels on this platform

At this point I've ruled out:

• RAM

• Temperatures

• Existing Unraid configuration

• Docker

• VMs

• Array activity

• Old BIOS

and I'm trying to identify what Unraid is doing differently from Ubuntu that causes the machine to reboot.

Any ideas would be greatly appreciated.

Thanks!

Edited 2 hours ago2 hr by dak1124
wrong version

23 minutes ago, dak1124 said:

Fresh Unraid 7.6.4 install

What did you really mean? That version doesn't exist.

25 minutes ago, dak1124 said:

Ryzen

Attach Diagnostics ZIP to your NEXT post in this thread.

Sorry. 7.3.4 my typo.

Diagnostics from 7.3.2 attached.

tower-diagnostics-20261027-1805.zip

Hi,

here runs the actual 7.3.4 on the same Aoostar WTR Pro 5825U since about two months (since7.3.2) without any problems at all.

(latest official bios AR5000-MI2_250206A, v0.33)

8 hours ago, dak1124 said:

pcie_mp2_amd 0000:05:00.7: Failed to discover, sensors not enabled is 0

this seems to point to the main cause.

are you shure the bios update was running okay? clear cmos

PREPARE TO FORMAT A DISK INTO FAT32, THEN COPY FIVE FILES TO THE DISK, INSERT A COMPUTER STARTER AND PRESS F7

1. Copy all files to FAT32 USB Stick

2. Boot from USB

3. F3 Optimized defaults to factory reset Bios configurations

(the process runs very quickly, so I was recording it by mobile phone to see the log.)

Edited 11 minutes ago11 min by NoRaid99

It seems to be one of these nasty errors, not beeing clearly shown. the "AMD sensor" error could be anything.

First what I was thinking about is: bios (on the other hand, why is ubuntu running? runs on other kernel?)

If you need some system infos to compare, feel free to ask for.