Change: Single SSD (XFS) was removed from Slot 1 of array. New Config with no preservations. Assigned SSD as Cache Pool.

 

Fix Common Problems:

• Default docker appdata location is not a cache-only share
• Share domains set to not use the cache, but files / folders exist on the cache drive
• Share system set to not use the cache, but files / folders exist on the cache drive

 

All shares are set: 'Primary storage: Cache'

 

Primary and Secondary storage options show Array greyed out as expected.

 

Server rebooted.

 

Diagnostics attached.

diagnostics-20250111-2320.zip

Edited January 11, 20251 yr by ivanavich

Your diagnostics show that the saved settings for the Shares are not as you describe.    I suggest you go into each share mentioned and make a dummy change and hit Apply to get the settings resaved.

 

Note that for the ‘system’ and ‘domains shares to get all their files onto the cache you need cache set as primary storage; array set as secondary storage; and mover direction as array->cache.   Then temporarily disable VM and Docker services under Settings and manually run mover from the Main tab.   When all files are on the cache you can (optionally) remove the secondary storage setting.

 

After doing this you might want to post new diagnostics so we can check everything now looks correct.

16 minutes ago, ivanavich said:

New Config with no preservations

For future reference, there is seldom any good reason for preserve none. Preserve all is the best approach, that gives a starting point from which you can make any assignment changes before starting the array.

15 minutes ago, itimpi said:

Your diagnostics show that the saved settings for the Shares are not as you describe.    I suggest you go into each share mentioned and make a dummy change and hit Apply to get the settings resaved.

 

Note that for the ‘system’ and ‘domains shares to get all their files onto the cache you need cache set as primary storage; array set as secondary storage; and mover direction as array->cache.   Then temporarily disable VM and Docker services under Settings and manually run mover from the Main tab.   When all files are on the cache you can (optionally) remove the secondary storage setting.

 

After doing this you might want to post new diagnostics so we can check everything now looks correct.

 

Thanks for your reply itimpi.

 

This has occurred on multiple Unraid NUC servers which have a single SSD using New Config. There is no options to change array/cache when there is a single SSD.

 

5 minutes ago, trurl said:

For future reference, there is seldom any good reason for preserve none. Preserve all is the best approach, that gives a starting point from which you can make any assignment changes before starting the array.

 

Have I missed something in using New Config to move a single SSD from the Array slot 1 to Cache Pool? In the release notes for Unraid 7 - "If you are running an all-SSD/NMVe server, we recommend assigning all devices to one or more ZFS/BTRFS pools, since Trim/Discard is not supported with unRAID array devices". The same can be said with XFS formatted SSDs as the trim scheduler works on all supported file systems.

Edited January 11, 20251 yr by ivanavich

I modified the share cfg files with a reboot and that has resolved the problem.

 

OId:

shareUseCache="no"
shareCachePool=""

 

New:

shareUseCache="only"
shareCachePool="cache"

 

Something amiss in the handling of handling of SSD moves from array to cache pools; specific to Unraid 7 as it is the only version that allows array to start without at least one drive in Slot 1.

Edited January 11, 20251 yr by ivanavich

I guess if you only have one drive and you intend to change its assignment, there is no effective difference between Preserve All and Preserve None. But in the more general case, better to start from Preserve All.