October 29, 200916 yr Disk3\Movies Disk4\Movies Disk5\Movies I created the Movies folder in each drive manually… restarted the array and then I get the single user share. Brilliant. (I’m running the latest beta) So I set the share to use the “fill-up” method. Now let’s pretend that I want to take that share off of disk4. What’s the proper procedure? I’m thinking: Stop array Use MC to move the data off of disk4 onto the other drives (if space allows) or just MOVE the Movies folder to another disk, say disk2, Start array… That should be it?
October 29, 200916 yr No - you don't need to stop the array. MC, move data were you want, go in unRAID properties and tell unRAID that Movies is now only in disk3 and disk5. Then you can delete the (empty) Movies folder from disk4.
October 30, 200916 yr You may also have to reboot, because the User Share system is setup fresh on each boot, and may not have 'forgotten' that drive until the next boot (I could be wrong). I would move the files away, delete the Movies folder, check and correct the Share Inclusion/Exclusion settings, then shut down and reboot.
October 30, 200916 yr Just to add a little more. If you stop the array, then the parity will not be updated during the move and it will be bad once you re-start the array. The move will go much quicker but you will not have any parity protection during the whole move process. You would also have to do a parity check after you start the array to get the protection back. So, it's not really an invalid option but rather just has consequences - you will get a faster move but lose the protection until the parity check is completed. Peter
October 30, 200916 yr If you stop the array your disks are un-mounted... you don't have access to your files, so movement or browsing via MC or otherwise is impossible. Moves must be made with the array started.
October 30, 200916 yr Oops, that's correct the disks are complete unmounted. They'd have to be mounted first to do any file work outside of the array. Peter
October 30, 200916 yr Oops, that's correct the disks are complete unmounted. They'd have to be mounted first to do any file work outside of the array. Peter Also correct. Writing to any drive with the array stopped is guaranteed to break parity. Even worse, since the array was not "watching" what you did, it may have no idea parity is bad. You won't know until you check it and find errors or try to reconstruct data when a drive fails and find you cannot.
Archived
This topic is now archived and is closed to further replies.