Hi everyone,

I'm currently facing an issue with my Unraid server: it's stuck at the "Array Starting" stage and won't proceed any further. I've tried waiting for quite a while, but the array never actually starts. Here's a bit more context:

Unraid version: 7.1.4

Symptoms:

• UI shows "Array Starting..."

• Drives spin up and are recognized

• No error messages or alerts

• Just never proceeds to "Started" or mounts shares

• disks are not mounted, but can be mount manually(/mnt/test)

  

What I've Tried:

• Rebooted the system multiple times

• Checked the logs (nothing obvious stands out to me)

• Ensured all drives are connected and detected in the dashboard

• No recent hardware changes

• No plugins that seem obviously related

unraid-diagnostics-20250714-2332.zip

Not seeing an array start logged, do see a strange issue with the flash drive partition. Does it work with 7.0.x?

6 hours ago, JorgeB said:

Not seeing an array start logged, do see a strange issue with the flash drive partition. Does it work with 7.0.x?

It had been working fine until I rebooted Unraid yesterday.

I tend to update Unraid almost every time a new version is released — I upgraded to 7.1.4 about a week ago, and before that, I was on 7.1.3.

You can try redoing the flash drive, backup the current one first and then recreate it using the USB tool and just restore the bare minimum, like the key, super.dat and the pools folder for the assignments, also copy the docker user templates folder (\config\plugins\dockerMan\templates-user), if all works you can then reconfigure the server or try restoring a few config files at a time from the backup to see if you can find the culprit.

I added some commands in config/go that use files from the array, but since the array wasn’t available, the go script didn’t exit with 0, so the system got stuck.

36 minutes ago, wirerope said:

I added some commands in config/go that use files from the array, but since the array wasn’t available, the go script didn’t exit with 0, so the system got stuck.

That would cause problems!

I suspect that whatever you were doing should have been done using the User Scripts plugin with the relevant script set to run at first array start?