hey everyone! been loving unraid over the year and was excited to see the public release of unraid 7. Been having an issue since though that my cache drive never clears now.  Mainly my data folder. I did notice that it skips my data folder but it capitalizes the "D" so not sure if that has something to do with it (all the main folders are labled lower case and in the logs they are capital)

 

Thanks for any help

 

edit: Diagnostics attatched further down

 

tower-syslog-20250124-2307.zip

Edited January 25, 20251 yr by Signet

Remove your old mover tuning plugin. If you really need it reinstall the current version.

I did read about that and after doing that running mover and checking the logs it would start the mover and immediately finish. There are 2 version of mover up on the app store too I noticed

22 minutes ago, Signet said:

I did read about that and after doing that running mover and checking the logs it would start the mover and immediately finish. There are 2 version of mover up on the app store too I noticed

You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

15 minutes ago, itimpi said:

You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

fair enough. attatched

tower-diagnostics-20250125-1027.zip

Looking at the diagnostics I think you may have two share configuration files with the same name but different capitalization:

D--a                              shareUseCache="yes"     # Share does not exist
d--a                              shareUseCache="no"      # Share exists on cache, disk1, disk2, disk3, disk4, disk5, disk6, disk7, disk8, disk9, disk10, disk11, disk12, disk13

 

This can cause an issue as Linux is case sensitive whereas Samba is not so you can get the wrong one picked up.

 

To rectify this you should delete the one that does not have the same capitalization as the top level folders corresponding to the share on your drives from the 'config/shares' folder on the flash drive (Dynamix File Manager is an easy way to do this).   Having done that check the settings for the share are now as you want them.

 

I would suggest for the time being also removing the Mover Tuning plugin as that has been known to cause issues on Unraid 7.

 

Try mover again and with any luck it will now work as expected  

3 minutes ago, itimpi said:

Looking at the diagnostics I think you may have two share configuration files with the same name but different capitalization:

D--a                              shareUseCache="yes"     # Share does not exist
d--a                              shareUseCache="no"      # Share exists on cache, disk1, disk2, disk3, disk4, disk5, disk6, disk7, disk8, disk9, disk10, disk11, disk12, disk13

 

This can cause an issue as Linux is case sensitive whereas Samba is not so you can get the wrong one picked up.

 

To rectify this you should delete the one that does not have the same capitalization as the top level folders corresponding to the share on your drives from the 'config/shares' folder on the flash drive (Dynamix File Manager is an easy way to do this).   Having done that check the settings for the share are now as you want them.

 

I would suggest for the time being also removing the Mover Tuning plugin as that has been known to cause issues on Unraid 7.

 

Try mover again and with any luck it will now work as expected  

What about the data folder too? In the share folder I have a Data.cfg but in unraid it's all in lower case? I was going to test shortly and see what happens haha

44 minutes ago, Signet said:

What about the data folder too? In the share folder I have a Data.cfg but in unraid it's all in lower case? I was going to test shortly and see what happens haha

You do not want to touch the data folder on your drives.   

 

Do you not have both a 'Data.cfg' and a 'data,cfg' file in the shares folder on the flash drive (which is what the diagnostics suggest)?   To avoid potential problems you want only a share configuration file that uses exactly the same capitalisation as the data folder.    In the worst case if you accidentally delete a sharename.cfg type file that corresponds to the name of a top level folder on you drives then Unraid will recreated the configuration file with default settings.

 

If you have two data folders on your data drives with the same name but different capitalisation then this a different issue and you should ask for advice.

22 minutes ago, itimpi said:

You do not want to touch the data folder on your drives.   

 

Do you not have both a 'Data.cfg' and a 'data,cfg' file in the shares folder on the flash drive (which is what the diagnostics suggest)?   To avoid potential problems you want only a share configuration file that uses exactly the same capitalisation as the data folder.    In the worst case if you accidentally delete a sharename.cfg type file that corresponds to the name of a top level folder on you drives then Unraid will recreated the configuration file with default settings.

 

If you have two data folders on your data drives with the same name but different capitalisation then this a different issue and you should ask for advice.

as per the screenshot from my phone above, i sshed into unraid and what you see in the /boot/config/shares folder is present. I dont have a data.cfg but have a Data.cfg file. i created a copy of the Data.cfg, was going to stop the array and change the Data.cfg to data.cfg and see what happens. In one of the original screenshot from the top when i had mover tuner installed it said the same thing: "/mnt/cache/Data doesn't exist" Really confusing

Edited January 25, 20251 yr by Signet
spelling

20 minutes ago, Signet said:

Data.cfg

Delete this one from the flash drive, then re-apply the setting for the data share, and a data.cfg will be created.

48 minutes ago, JorgeB said:

Delete this one from the flash drive, then re-apply the setting for the data share, and a data.cfg will be created.

Ok I'll give that a go. Do you suggest I shutdown the array first before doing this?

Also, when you say flash drive, without having to shutdown the server and plugging the USB into another computer is that /boot folder when you SSH in? Eg. /boot/config/shares

 

Thank you again for all the help

38 minutes ago, Signet said:

Do you suggest I shutdown the array first before doing this?

Should not be necessary.

39 minutes ago, Signet said:

when you say flash drive, without having to shutdown the server and plugging the USB into another computer is that /boot folder when you SSH in? Eg. /boot/config/shares

Yes.    Note that you can also make the flash drive visible over the network (as the 'flash' share) by clicking on it on the Main tab and setting the SMB settings appropriately For security reasons it is not shared over the network by default.

Thank you all for your help! Managed to get it working again. Did what you said: created an smb share to the flash drive, deleted the data.cfg file, went into the share within unraid and applied settings. It did default settings meaning it was only storing it on the array so just changed the primary to cache and secondary to array. working without the tuner too

Not sure why the .CFG changed... Never touched the directory or the share files after the upgrade to v7

Support has been great

❤️

Edited January 25, 20251 yr by Signet
Additional info