February 1, 20251 yr I recently had to change my cache drive and I made a bit of a dog's breakfast of it, but recovered successfully and I thought all was well. However, I noticed that new data was remaining on my tempo pool drive and I thought not updating the array when I initiated a move. On closer examination, I saw that the changes are being written to both the target share and to the tempo drive. I have tried various things such as removing the tempo drive and then replacing it but that has not worked. I also tried changing the settings of the two shares associated with the tempo drive to write changes to only the tempo drive and that did not work either. The changes were written directly to the array regardless of what I put in the settings for primary location. I can't see anything wrong with the user share settings and they were working fine before the dog ate his breakfast, so I have to believe that is where the problem lies. I have attached the diagnostics in the hope somebody more clever than I can help. tower-diagnostics-20250201-1144.zip
February 1, 20251 yr Community Expert You should check in the config/shares folder on the flash drive that you only have one .cfg file for the share in question and that the capitalization matches that of the folder on the drives holding that share. If you need to make a change to the .cfg file check that the share settings are still as you want them. i notice also that you have the ‘domains’ share set to be only on the cache but it has files on the array.
February 1, 20251 yr Author Thanks for the speedy response. I appreciate that. I have checked the ;flash drive and the two .cfg files appear to be correct. Here are the contents of the files in question. I deleted the domains share on my array and . . . . the domains file disappeared from my cache. I checked it was there before I deleted from the array, it was, but is not now. As I'm not running any VMs I don't think it's a problem and the array runs and reboots fine. Any other suggestions would be welcome.
February 1, 20251 yr Community Expert 4 minutes ago, Baregills said: I just noticed the media.cfg is capitalized!! It needs to have the same capitalisation as the actual share folder on the drives or you can get unpredictable behaviour.
February 1, 20251 yr Community Expert 4 minutes ago, Baregills said: Yes. I fixed that but I'm still writing to both the pool and the array. Do not see how this is possible as in normal operation a file can only exist in one location at a time. Are you sure you are looking directly at the drives/pools and not the User Share (which spans all drives and pools).
February 1, 20251 yr Author Yes. I am looking from Main at the array and the pool. They both show the file I am using as a test file. Time to reflect and try to think how this could have happened and perhaps a new load of Unraid and see if that clears it. I'll leave it for a day or two before doing anything silly/brave!
February 4, 20251 yr Author Solution Well, today I wrote some changes to the array and they went to the pool drive and not the array. I then initiated a move and the changes were written to the array and deleted from the pool. I changed nothing to facilitate this. I wonder if the change to the capitalization of there media folder was somehow delayed, though I can't see how. I rebooted after making the change and checked after that. Anyway, it is now fixed. Thank you for your help and as always, it is much appreciated.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.