The appdate share primary storage is set to "Cashe-system" which is a pool of two mirrored (RAID1) SSD 1.6TB drives, however, every time I reboot the system, the primary storage changes to "Array".

This has been going on for a few months but I can't tell exactly for how long.

 

Your help will be appreciated.

 

unraid-diagnostics-20250514-0430.zip

It's currently set to cache=only, did you already change it after rebooting?

Yes. After a reboot, I change the primary storage on the share to "Cashe-system" then start the docker containers.

If the change is not persisting this implies that there might be an issue with the flash drive.    If might be worth checking the config/shares/appdata.cfg file on the flash drive to work out if/when it is getting changed.

14 minutes ago, itimpi said:

If the change is not persisting this implies that there might be an issue with the flash drive.    If might be worth checking the config/shares/appdata.cfg file on the flash drive to work out if/when it is getting changed.

This is what I see now accessing the flash drive from within UNRAID. It looks fine to me. Is it possible that the changes I did to the share after the reboot are cashed and are not being written to the flash drive? I can shut down the server and check the flash drive on another computer just to make sure.

11 minutes ago, Farid said:

Is it possible that the changes I did to the share after the reboot are cashed and are not being written to the flash drive?

A new .cfg file should be written when you hit Apply on that share.    Are you sure you never hit Done without hitting Apply first?

14 minutes ago, itimpi said:

A new .cfg file should be written when you hit Apply on that share.    Are you sure you never hit Done without hitting Apply first?

I definitely applied the changes then hit the done key. The image above is from the config/shares/appdata.cfg from the flash drive and contains the change to the primary storage which was "Array" after the reboot and the date on the .cfg file also reflects that 14/5/2025.

14 minutes ago, Farid said:

I definitely applied the changes then hit the done key. The image above is from the config/shares/appdata.cfg from the flash drive and contains the change to the primary storage which was "Array" after the reboot and the date on the .cfg file also reflects that 14/5/2025.

The question is now when you reboot does the change persist or does that file revert to something else, and if so what?

So, I shutdown the server, took the flash drive out and viewed the file .cfg file on my laptop. The first image is from the flash drive and the second is from the appdata share after reboot. Notice how the primary stoarage has been changed to "Array" !!!!

After the reboot and before modifying the appdata share, on UNRAID, I noticed that the appdata share does not exist on the flash drive !!!!!.

Perhaps this can give you a clue on what is happening.

14 minutes ago, Farid said:

After the reboot and before modifying the appdata share, on UNRAID, I noticed that the appdata share does not exist on the flash drive !!!!!.

Perhaps this can give you a clue on what is happening.

It explains why your changes do not persist as Unraid then reverts to default settings, but does not explain why the file is not on the flash drive as your earlier screenshot said it WAS there.

3 minutes ago, itimpi said:

It explains why your changes do not persist as Unraid then reverts to default settings, but does not explain why the file is not on the flash drive as your earlier screenshot said it WAS there.

It gets created on the flash drive only when I modify the share on unraid and apply the changes

Just now, Farid said:

It gets created on the flash drive only when I modify the share on unraid and apply the changes

Yes, but you then said it subsequently gets deleted which is strange as share .cfg files are never automatically deleted.

If there's no appdata share on the storage, the cfg will be deleted during array start.

When I shut down the system about half an hour ago, the appdata.cfg was on the flash drive. Once I rebooted, it got deleted from the flash drive and got created again once I changed the share on UNRAID and applied the changes.

I compared the parameters of appdata share on the flash against the system share. They are both on the same pool and both have identical parameters except for the shareCOW= where it is "no" on the system share and "auto" on appdata. Not sure what this parameter is.

May 14 03:50:25 unRAID emhttpd: shcmd (96): rm -f /boot/config/shares/appdata.cfg

 

The cfg file is being deleted on array start, this should only happen if appdata didn't exist, post the output from:

 

ls -l /mnt/user

 

49 minutes ago, JorgeB said:

May 14 03:50:25 unRAID emhttpd: shcmd (96): rm -f /boot/config/shares/appdata.cfg

 

The cfg file is being deleted on array start, this should only happen if appdata didn't exist, post the output from:

 

ls -l /mnt/user

 

I stopped the array then restarted it and it did exactly what you said. It deleted the appdata.cfg

For some reason, it's not finding the current appdata folder, you can try disabling all containers from auto-starting, then the docker service, rename the appdata folder, then re-enable the docker service, Unraid should create a new appdata share, test if it now works, if yes, move the data from the old share to the new one and re-enable the containers.

11 hours ago, JorgeB said:

For some reason, it's not finding the current appdata folder, you can try disabling all containers from auto-starting, then the docker service, rename the appdata folder, then re-enable the docker service, Unraid should create a new appdata share, test if it now works, if yes, move the data from the old share to the new one and re-enable the containers.

Followed your suggestions above and that RESOLVED the problem.

Thank you very much