mergahtrern

It is awesome so far, @SShadow. Thinking of what else to do with it besides Plex and Minecraft, haha! Am even considering a second Unraid server build for off site backup/storage so I can re-use these WD Reds from my now-retired Drobo 5N and some other hardware I have. That or throw them in the current server as a pool and backup internally.

To put a bow on this, I ended up copying everything over in batches. I noticed transfer speeds suffered after X number of items were being copied at once. Everything is now in my array and parity sync has completed.

It's probably best for me to exercise some patience and just let it roll. Speeds bumped back up to 36-45 MBps. Another TB to go before unRAID should start writing content to the second disk in the array. Will be interesting to see what happens then.

I'm back down to 20 - 25 MBps this afternoon. Should I copy stuff over in smaller batches to avoid this? sol-diagnostics-20250204-1609.zip

Cool. Cruising at 95-101 MBps now. Will check it out in the AM. Thanks for the quick replies, @trurl.

That would require I stop the array which would consequently stop/cancel the current transfer, correct?

So I ran preclear on all three disks and it completed successfully. Also swapped out two of the three SATA cables that each threw 1 CRC error with a pair that were being used in another system. This past weekend, I began a 20 TB transfer from my NAS via SMB which started out strong, but speeds have slowly decreased to 9 MBps. At this rate, the transfer won't complete for another two weeks or more. 🙃 Progress is at 24% so I wouldn't be opposed to cancelling the transfer, figuring out why this is happening, then kick it off again as doing all that would probably let me get this migration of data complete in less than 2 weeks. Another diagnostics is attached for review. I am noticing in the Main tab that the disk currently being written to (Disk 1) has equal read and write rates with the parity disk showing the same rate of writes and Disk 2 showing equal rates of read. Parity sync has been paused since the array came online this weekend until a couple minutes ago after I just cancelled it. This doesn't appear to have had an impact on the read/write stats I shared above. My plan was to wait until everything was moved over to the array, then run a parity sync. FWIW, all other transfers I ran into the array before this one ran anywhere between 50MBps - 90MBps+, but the largest one was just 4 TB and the others were far smaller. sol-diagnostics-20250203-1839.zip

For the timeouts, I had an issue with my current NAS which was resolved by rebooting it. The transfer I had going in unRAID was stuck because of this, but automatically continued once the NAS booted back up and became available on the network again. Only 4 TB of 24 TB copied so far so I don't mind copying data again. Once the SMART test is done (50% now), I'll first reseat the SATA cable on both ends, then remove the drives from the array and preclear them. Can they all be precleared at once? I do have some extra SATA cables lying around so swapping out to another won't be a problem if issues persist.

Diagnostics attached. SMART test has progressed to 40% so I'm just going to leave it be. sol-diagnostics-20250127-1631.zip

Hello, everyone! I've just built myself an unRAID server and am still learning a lot. Have begun transferring my data into the array, but stopped when I came across this error. So far, all my content has been written to Disk 1 due to the allocation method (high-water) and split level configuration (auto split top 3) I'm using. Yesterday, I noticed the dashboard is showing a SMART error for Disk 2 in the array. I've run a SMART short self-test that passed and am now running an extended self-test which has been hanging at 30% for a good portion of the day. SMART log included below. Apologies if the formatting is off a bit. In the Attributes tab of Disk 2, I also have a UDMA CRC error count with a value and worst that equals 100 and Raw Value of 1. Should I be concerned about any of this? ATA Error Count: 1 CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 1 occurred at disk power-on lifetime: 30 hours (1 days + 6 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 43 00 00 00 00 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 40 50 d0 4b da 40 08 20:32:46.579 READ FPDMA QUEUED 60 40 60 90 51 da 40 08 20:32:46.573 READ FPDMA QUEUED 60 80 58 10 51 da 40 08 20:32:46.564 READ FPDMA QUEUED 60 40 48 90 46 da 40 08 20:32:46.564 READ FPDMA QUEUED 60 40 40 50 41 da 40 08 20:32:46.564 READ FPDMA QUEUED