BrianAz

Thanks again for taking a look. I rebuilt on top and then went through the entire process to add 2x12TB parity disks one at a time and then moved my old 2x10TB parity disks down to data disks. No errors.

Attached. Thanks tower-diagnostics-20240716-0903.zip

Today, I have 130 read errors on a different drive (19). This time it looks like Unraid has pulled the drive and it's now being emulated. Attached new Diagnostics.. please help. New drives should hopefully get here soon.tower-diagnostics-20240715-1936.zip

Thank you for taking the time to evaluate. I will pay attention to the attributes you highlighted.

No issues during the extended SMART test for Disk 17. SMART self-test history: Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 64998 - # 2 Short offline Completed without error 00% 64984 - The Smart Error Log item still shows "No Errors Logged". Still just the 128 read errors. Current diagnostics attached. Thanks again. tower-diagnostics-20240713-1617.zip

This morning I encountered 128 read errors with one of my drives (Disk 17, a 6TB WD Red). Nothing else seems to be amiss. I've been running without any issue for years in an enterprise chassis. I run a monthly parity check and it's been 6+ months since I've physically touched any of the hardware. There was nothing unusual about this morning (no one bumped the case, no power hiccups, etc). Would someone please take a look at my attached diagnostics and let me know if anything stands out? Disk 17 - SMART short-test completed without error, running long test now. (Side note, I have 2x 12TB drives on the way. The plan was to upgrade parity and move the 2x 10TB I have as parity now, to data drives. Hopefully I can still do that.) Thanks in advance tower-diagnostics-20240711-1511.zip

Same. Any ideas? I'm not sure why it happens, but it does not seem to impact my Plex server (that I've noticed)

I am interested in running two dual-parity protected arrays in a single chassis w/ Unraid on bare metal. I have a smaller array for testing and data that would be a minor headache to replace (6 data drives + 2 parity). I also have my "Production" Unraid array that houses my primary data that would be a huge issue if I lost (18 data drives and growing + 2 parity & full/daily offsite backup). My chassis is 36 bays and I currently run Unraid on top of ESXi, passing through the USB keys along with HBAs and NVMe cache drives to get as close to bare metal as I can. Edit: After ZFS lands, surely multiple Unraid parity arrays will be next…?

I'm having this issue as well... I have two Ubuntu 16.04 servers and they both will throw an error after a while on my most used folders. I have the mover enabled (FYI), but haven't tied any of this to it yet. This had not been a problem until recently. I guess I'll try to use 1.0 and see if it fixes it. Very frustrating.

Thanks for the app. I am trying to get my NUT stats to display. Am I missing them? iOS 13 ControlR v4.10.0 NUT Plug-in 02-03-19 unRaid 6.7.2 Do I need the ControlR plugin for NUT stats to work? Thanks

Wanted to chime in and say thanks! I had this happen to me tonight on version 6.3.5. Would be really nice to get an explanation on what might cause this from LT.

unRAID won't clear a new parity drive. There is no need for it to be clear since it will be completely overwritten by the parity sync. So if you want to test your new parity drive you may want to preclear it anyway. I meant I would be preclearing the OLD parity drive to be used as a new data drive in the array (like you discuss below). Thanks for this, I'll be sure to keep a link to it for the future.

FYI, since v6.2 clear is done with the array online, but disk is not tested like when using preclear. Thanks for that info too. I'll take advantage of that when I upgrade my parity drives again (and look to use them as data drives in the array). As a follow up to what you noted above, I proceeded with starting the array and unRAID picked up the preclear signature and prompted for only a quick format. Everything as you indicated. thx

That's normal, unRAID only checks for the preclear signature after starting the array. Many thanks Johnnie! Been quite a while since I expanded my array. Wanted to make sure I wasn't giving the go-ahead for 9+ hours of downtime.

Hello - I'm attempting to preclear a 4TB drive to expand my array but after each successful preclear, the array appears to want to Clear it again before adding it. I've attached diagnostics, preclear reports and a screenshot of the "Start will bring the array on-line and start Clearing new data disks" message I'm concerned about. Please let me know what else might be helpful to troubleshoot. I'm hoping to avoid multiple hours of downtime by pre clearing and the language I'm seeing seems to tell me thats what unRAID intends to do once I click start. Am I misunderstanding the meaning or is something not right? Thanks for your help, Brian tower-diagnostics-20170215-1213.zip TOWER-preclear.disk-20170215-1211.zip