Hi everyone,

I'm running Unraid on a generic Mini PC (Win element M600) with an AMD Ryzen 7 8845HS.

After updating to version 7.2.3, I can access the WebGUI and dashboard without issues, but the Array refuses to start.

Symptoms:

The Dashboard loads correctly.

Parity and Data disks (Disk 1, Disk 2) show as "Healthy" regarding SMART, but status is "off-line" (green dot) because the array is stopped.

When I press "Start", the page refreshes, but the array stays in the "STOPPED" state.

Tailscale is connected and running fine.

Hardware:

Model: Win element M600

CPU: AMD Ryzen 7 8845HS w/ Radeon 780M Graphics

OS: Unraid 7.2.3 (Basic)

Steps taken:

Rebooted the server.

Checked BIOS settings (nothing changed).

I suspect this might be related to the newer AMD kernel support or a plugin conflict, but I am not sure where to look.

I have attached the Diagnostics ZIP file.

Thanks for the help!

eva-diagnostics-20260210-2007.zip

SSDs in the array cannot be trimmed.

Unraid V7 does not require an array.

Better if those are put in a pool.

It should because you missing cache pool device, if no more in system, try "new config" to remove it.

Feb 10 19:43:02 EVA emhttpd: cache: ERROR:missing devices

diskId="JM_icron_Tech_DD564198839D4-0:0"

this cache disk was never connected, and it didn't change anything, everything worked ok

Thanks for the suggestion regarding the missing cache device.

I followed the instructions:

Performed a New Config (Retaining All).

Unassigned/Removed the missing cache device from the pool slot.

The "Missing Device" error is gone from the Main tab.

However, the Array still refuses to start.

When I click "Start", the page refreshes (showing "Starting..." briefly), but it immediately reverts to "Stopped".

I have attached a fresh Diagnostics ZIP taken after the New Config and the failed start attempt.

Could there be something else blocking the mount? Or maybe a plugin issue?

eva-diagnostics-20260211-0925.zip

Fixed!

The issue was indeed the missing cache device configuration blocking the array start.

I set the Cache slots to 0 in the Main tab (effectively removing the defined pool), and the Array started immediately without issues.

Thanks for the help!

So you don't have any pools now? Do you intend to have any pools? Since you have Docker and VM Manager enabled, your docker/VM related shares - appdata, domains, system - will have been recreated on the array. Ideally, these shares would have all files on cache or other pool with nothing on the array, so Docker/VM will perform better, and so array disks can spin down since these files are always open.

It will take some work to get those moved to cache if you decide to have cache again.