Sono

Look good so far. I did as JorgeB said. Mover is currently running. Thanks everyone.

Here you go. Sorry, could have thought of this beforehand. As some shares have similar names, here are the configs of my examples: Movies: # Share exists on disk1, disk2, disk3 # Generated settings: shareComment="" shareInclude="" shareExclude="" shareUseCache="yes" shareCachePool="cache" shareCachePool2="" shareCOW="auto" shareAllocator="highwater" shareSplitLevel="1" shareFloor="50000000" shareExport="e" shareCaseSensitive="auto" shareSecurity="secure" shareReadList="..." shareWriteList="..." shareVolsizelimit="" shareExportNFS="-" shareExportNFSFsid="0" shareSecurityNFS="private" shareHostListNFS="" For the backup share it says # This share has default settings. # Share exists on cache, disk1, disk2, disk3 I also saw in shareDisks.txt that I have a double entry for the backup. But in the GUI I have only ‘backup’ (lower case), which also matches the name in /mnt/user. Not sure where the capital letter Backup comes from. B----p shareUseCache="yes" # Share does not exist b----p shareUseCache="no" # Share exists on cache, disk1, disk2, disk3 unraidtower-diagnostics-20250618-1718.zip

I have this issue recently as well. Strangely enough the automatic mover did work fine for me for my ‘Movies’ share, but does not work for my ‘backup’ share. Primary storage for both is ‘Cache’ and secondary storage is ‘Array’. Mover action is Cache to Array. Nothing fancy there. I don’t have any plugins regarding the mover installed. Using the automatic mover does nothing. Clicking the ‘Move Now’ in the GUI does invoke the mover in the log, but the files don’t move. When calling mover manually via CLI it starts and finishes immediately. root@unRAIDTower:~# /usr/local/sbin/mover start mover: started mover: finished The only error I have is from the Fix Common Problems plugin: Jun 18 11:00:00 unRAIDTower root: Fix Common Problems: Error: Default docker appdata location is not a cache-only share Though this should be ‘ok’ for now, as I currently don’t run any containers or VMs on the unRAID machine. I did try to put a new folder in the Movies share and it was created in Cache, as expected and then when calling the mover via CLI the folder was moved to array. So this works fine. The only difference it seems between these two shares are the security settings. The Movies share is set to ’Secure’ and backup is set to ‘Private’. Though this should not influence the mover. Now I’m quite confused.. this happens to me with the current 7.1.3 Any ideas?

Hello, I'm in the process of moving my system to new hardware and for that I switched parity and one data disk to a bigger size and then used mover to empty the smallest drive in the array, as the new system has one less space for a drive. I followed the process described in the release notes and this worked fine from what I can tell. Now earlier today mover finished, and on the web terminal the drive looks empty: root@unRAIDTower:~# ls -lart /mnt/disk4 total 0 drwxrwxrwx 2 nobody users 6 Apr 23 13:05 ./ drwxr-xr-x 9 root root 180 Apr 23 13:24 ../ However, looking at the GUI disk4 is still showing to use 2.03 GB. Can someone explain this please? Thanks a lot!

You are right, obviously. I've set this system up so long ago and then also over some time did not use it at all, that I forgot partially how the user shares are actually being stored on the disks. Thanks for clearing that up.

Last question (I think). When I reset the array configuration to make a new config, after moving to the new hardware, will this also reset shares? I've read the documentation, it does not mention that, so I would assume shares are untouched, though is there something to keep an eye on? E.g. if a share is not using all disks, but only certain ones?

Thanks. The system is currently still at 6.9.2, guess it would make sense then to update it first. I was so far putting this off till after the hardware move, but besides the new system being faster there is no reason against it I guess.

Yes you are right, I forgot to mention that. The new parity drive will be 10TB, I have an 8TB drive as well and an older 4TB. I will most likely add another 8 or 10TB drive, though even if I do only add the 8TB and keep the two 4TB currently in the system that would give me a total of 16TB with ample room to grow. By 'make a new config' you are referring to the 'reset array configuration', right? Is there a special way to move data of one disk or do I need to move it manually from one disk to another?

Hello, I am currently running an old unRAID 6.9.2 setup with a Basic licence (funny enough that licence will turn 10 years in 2 weeks). I also want to stay with unRAID, but exchange the disks as they are quite filled up (moving from 5 data drives + Cache to 4 + Cache and also using bigger drives), so I am not entirely sure what is my best method here. I'm only using user shares and xfs as filesystem on the disks. My current motherboard is using 6 SATA connectors (5xHDD,1xSSD). The new one has 5 SATA connectors + an NVMe slot. One idea was to setup a new unRAID box with the new drives (using the free trial) and then copy over data from the old box to the new one. Also using this to sort my data as I guess there are a bunch of duplicates in there. Then after finishing this turn off the old system, move the USB stick to the new one and be done? Or will this be problematic to exchange USB sticks as the current system uses the old 6.9 version while a new one would be version 7? The other idea was to place the old drives and my USB stick into the new machine and exchange one disk after the other for bigger ones, starting with parity, or will this not be a good idea? This would be a little janky first as I can only fit 4 drives into the new case, so one drive would need to be placed kind of outside, not ideal... In this case I would also need guidance on how I can move all data of one disk to others, so I will safely be able to size down to 4 disks total. I would leave out the SSD and only transfer the HDDs, as I will use an NVMe for cache in the future. Though I guess I would need to rebuild the array/parity every time after changing a disk. What is the recommended approach here? Thank you very much. Here is a screenshot of the current devices.