I have recently migrated all of my drives/dockers/VMs from Unraid 6.9.X (I don't remember what the last number was) to 6.10.3

Now, the array will not auto-start.

I have enabled auto-start in the disk settings but it won't auto-start.

 

Please help and please let me know if I can provide any info that can help.

 

Regards,

Ash

You should provide your system’s diagnostics zip file so we can see what is going on.

Here is the requested diagnostics archive.

aperturescience-diagnostics-20220623-2236.zip

I noticed this in the syslog in the diagnostics:

 Jun 23 20:42:39 Tower emhttpd: Autostart disabled (device configuration change)

 

That suggests some recent change stopped autostart from running, but no idea what that change might be.

Parity is invalid, autostart will start to work once it's synced.

Was it unexpected that parity is being rebuilt?

Unrelated, but your appdata, domains, system shares are all set cache-yes, which means move them to the array. And appdata and domains already has files on the array.

 

If these shares are on the array, your docker/VM performance will be impacted by slower parity, and array disks can't spindown since these files are always open.

 

Nothing can move open files, so you will have to disable Docker and VM Manager in Settings, set all of those shares to cache-prefer, and run mover to get them moved to cache.

 

Wait until parity finishes rebuilding.

Looks like I'm going to be waiting for awhile for the parity rebuild.

I'll let you know the results, once that's done.

On 6/24/2022 at 1:21 AM, JorgeB said:

Parity is invalid, autostart will start to work once it's synced.

This was the issue.

It is now resolved.

 

Thank you for your help.