LordMael

I know this topic is a bit over 2 years old but it helped me greatly. Just moved my unraid from one server to a completely different hardware / HDD / Cache / VMPool setup with all new drives. This is what I did (per the directions supplied by the posters in this forum) copy all data from old server to new server using rsync shutdown vm's / dockers copy vm's over copy appdata over shutdown old server move usb from old to new and boot up create new array configuration without parity enabled right away re-installed all dockers / plugins re-created docker networks double check dockers in the right docker networks (edit as needed) fire up docker and make sure everything works stop array add parity disk start array and start parity sync. I would say it took a few days to copy the data and then a final rsync to catch anything new. the rest of the process was just done this evening in < 3 hours. The people in these forums, for the most part, are extremely helpful and I could not have gotten this far without your help. (even though I mostly only lurk) :)

So this is my first unraid build thanks to retiring hardware at one of my offices. The case and a full complement of 4TB WD Black drives along with a supermicro X9SCM-F with 32GB of ram is what came with the case. I had spare E5 2650v2's and extra DDR3 ram lying around so I purchased a used X0DR3-F motherboard online along with the super quiet power supplies. The non 4TB hdd's came from my existing 8 bay synology that i was using previously. OS at time of building: 6.11.1 CPU: 2x Intel E5-2650v2 Motherboard: Supermicro X9DR3-F RAM: 256GB DDR3 Case: Supermicro CSE-846 Drive Cage(s): 24 Power Supply: 2x 900 SQ SATA Expansion Card(s): ARC-1882IX-24 Cables: no idea Fans: All stock supermicro cse-846 case fans Parity Drive: 1x 10TB Seagate Ironwolf and 1x 10TB Seagate EXOS Enterprise Data Drives: 1x 4TB Seagate Constellation, 13x 4TB WD Black, 7x 6TB Seagate Ironwolf, 1x 8TB Seagate Ironwolf Cache Drive: 2x Samsung 860 EVO 1TB SSD Total Drive Capacity: 106 TB Primary Use: Media Storage and NextCloud Likes: 24 bays of storage capacity Dislikes: the weight... ugh, it's not fun to move while i still don't have a rack for it Add Ons Used: My Servers, Nvidia Driver, rclone, Unassigned devices (and plus), user scripts, plex, nextcloud, swag Future Plans: More VM's for testing things and probably newer CPU / Mobo combo eventually Boot (peak): 413W Idle (avg): 333W Active (avg): 365W Light use (avg): 345 https://imgur.com/0opKlwv https://imgur.com/mvWh5Bh I would like to get the power consumption down but I'm happy with it currently. The hardware used was mostly hand me downs with only really purchasing the used motherboard, cpu heat-sinks, and the replacement super quiet psu's. All in, i think I've only invested around $250. I would not say you can build this for $250 to anyone. The case used alone is more than that on the open market. But, for equipment saved from going to the recycler and going to my house, I'm happy with the cost. [hr]

You can have parity disks assigned and the parity task stopped. This was a brand new array and I'm new to unraid so I thought by disabling the parity sync the copy would go faster, it doesn't. the only way it was moving faster was to shutdown the array, remove the drives that were assigned to the parity slots and then fire the array back up again. i went from 50MB/s to 116MB/s writes. Currently the array is building the parity on the 1x 10TB parity drive now that the data is all moved.

I had 2 drives assigned to be parity but no parity task had yet been started. after shutting down the array, de-selecting the two parity drives and removing them from the parity assignment, copy was 2x as fast. I have since finished copying over the 18TB of data from my old synology to my new unraid host and moved over the newer drives that were in the synology into the unraid host. Went from 88TB to 108 TB with a 10TB parity drive. I have a few drives i need to replace (the server came with used drives in it from work) so I will be ordering new drives to replace the ones that are showing errors. I hope this answers your question d[^_^]b

So that was part of the issue. Because I also had 2 parity disks selected but not enabled that was the other part of the problem I have unassigned the 2 parity disks (that weren't being used yet) and copy jobs are working much better. Once everything is copied over, I'll turn parity back on and let that sync. Thank you for pointing me in the right direction.

I have recently built a new unraid server with 24 drives. I am copying a bunch of data off my older synology to the unraid host and currently have parity turned off (due to the TB of data being copied). Also, I will be moving the larger drives off of the synology into the unraid host to slowly start expanding (88TB isn't enough compared to some of the servers here ) I can't for the life of me figure out why every drive is being read while writing to one drive. I have no dockers, no cache at the moment and no vm's. I have attached the diag zip in hopes that someone smarter than me in unraid can help me figure out what the issue is. I have looked online and through the forums to find something similar but have not. Thank you all in advance for any assistance. tower-diagnostics-20221014-2004.zip