Im having a problem copying data from Disks. Im trying to copy data from one disk to another so I can replace my 3TB's with 6TB drives. 300Gb should take about 2 hours over my network but sometimes it shows 7 hours. Only a reboot of unRAID cures the problem for a day or so. I have tried this with several of my disks and have had to reboot 10 times now transferring about 6TB of data across disks. I have checked my network cable from my Macbook Pro to my Netgear GS108Tv2 switch and it seems fine. Im running cache Dirs and wonder if somehow I'm running low on memory or its not being released although I have set it to only scan 4 folders deep.

Copying data is not required before replacing a disk. Try starting in SAFE-mode.

I know but I need to copy my data from say disk 5 to all my other disks so I can remove the disk and do a new config. Im reducing from 9 disks to 4 disks. Im adding 6TB drives one at a time. I will try my copying in safe mode when I remove the next drive. Thanks.

I know but I need to copy my data from say disk 5 to all my other disks so I can remove the disk and do a new config. Im reducing from 9 disks to 4 disks. Im adding 6TB drives one at a time. I will try my copying in safe mode when I remove the next drive. Thanks.

If you have a parity disk (which would have to be a 6TB one) then it would be much easier to simply rebuild the 3TB disk that is to be removed onto the 6TB replacement.  You can keep the 3TB one safe while this is happening in case anything goes wrong, but as long as no issue is encountered then the need for the copying disappears.  Once the rebuild is successful then the 3TB can be reused.

Im selling all of my 3TB drives. I have 8 of them and so much free space since converting to MKV's from ISO's that I want to consolidate my server down to a total of 4 x 6TB drives.

I know but I need to copy my data from say disk 5 to all my other disks so I can remove the disk and do a new config. Im reducing from 9 disks to 4 disks. Im adding 6TB drives one at a time. I will try my copying in safe mode when I remove the next drive. Thanks.

If you have a parity disk (which would have to be a 6TB one) then it would be much easier to simply rebuild the 3TB disk that is to be removed onto the 6TB replacement.  You can keep the 3TB one safe while this is happening in case anything goes wrong, but as long as no issue is encountered then the need for the copying disappears.  Once the rebuild is successful then the 3TB can be reused.

This is how I would do it also. Rebuild the fullest 3TB disk onto the 6TB disk. This effectively gives you a copy of that 3TB disks but should be quicker than a file copy. Then you can copy files from other disks onto the 6TB disk. When you are done and sure you have everything from the disks you are removing, then you can wipe and sell them. In the meantime they are good backups if something goes wrong.

Yes sounds like a good idea. Thanks

Aside from the recommendations about copying my files does anyone have any idea why I need to reboot my server every day in order to keep the network copy speeds at reasonable speed. I can start in safe mode but could the file copy speeds have anything to do with all my lower memory been used up or not. A reboot of the unRAID server always cures it and when my memory reaches 98% used after say 6 hours is when I seem to have issues and Im wondering if unRAID is not releasing the memory to plugins that are requesting it.

Does the problem occur in SAFE-mode?

Yes, I booted into safe mode this morning and it was fine, after copying about 300GB of files and then trying another 23GB it displayed 2 hours and would have taken that. A reboot of the server and the 23GB file copy time from my Mac to the server took and displayed 15 minutes. So maybe its an issue between my mac to switch, to router to server network issue or would all the drives being spun up make the copy faster as opposed to just the Parity and disk1?

Connect the Mac directly to the server. If the server uses DHCP, turn Internet Sharing on so the Mac will provide an IP address to the server.