Scott A

Constructor, Thank you for the above information. Again, I didn't format the original disk. I still have it. I did put in a new disk and tried to rebuild which produced nothing...funny that the rebuild ran but nothing came of it. I couldn't access the missing data and the new drive still said unformatted. Therefore I formatted the new disk. As you said, parity stayed in sync so that would have blown away what was there I guess. That leaves me likely with the only recourse is to see whether the original "bad disk" has the data still on it and I can access it on another pc as you also mentioned. All that said, when one of the disks fails in the array then as I understand it, the array uses the remaining disks and the parity disk to recreate the failed disk contents. Correct? If two disks fail then, of course, that wouldn't be possible. In my case I only had one disk fail so i still don't know how or why parity got out of sync initially before this format. Again, I appreciate the help and guidance.

I'm halfway comfortable. My next step is that I ordered a usb to SATA connector and will plug in old drive and use RSTool to see if I see anything on the old disk. If not then it's toast. If so, I'll see next steps. Only other thing would be if the parity disk still has something which seems doubtful and not sure how I would see that. It's almost like the parity for the failed disk got erased as well... I'll also look at upgrading but that looks to be a bigger task for me.

Also, here is the latest clean syslog with the new disk Latest Clean Boot.txt

I kept the original disk and rebuilt to a new one. Here are the smartdisk runs for each drive smartsdg.txt smartsdf.txt smartsdb.txt smartsde.txt smartsdd.txt smartsdcparity.txt

Thanks. No plug-ins. I do and ran smartdisk at the command line. I went ahead and removed bad disk and replaced it with a new one. Did a rebuild (of course after formatting) and the disk shows but any information that was there isn't anymore so it looks like the parity disk lost its information during the original issue. I can run smartdisk and post each one but not sure that matters now but let me know. Again, all disks are functioning and accessible. It's just that the Disk 4 information is no longer there.

OK. I don't have a backup so that is unfortunate. That said, I can pull the disk and put in another and see what happens. I did run SmartDisk on all drives and all passed.

I still don't understand though why even if one disk is unformatted/unmounted why I can't access its contents on the array as it should be there from the parity disk. The disk is absent when looking from another PC through windows explorer. Furthermore, it is trying to rebuild the disk even though it lists it as unformatted. I let it complete one time which took hours and then nothing was there once complete. I don't want to format though yet as am concerned I lose all the data. Again, I appreciate the guidance!

Here is the new syslog after replacing SATA Cables. Think I replaced the correct ones. Syslog after replacing Sata Cables.txt

Ok. I'll do that next. All disks are showing up though now but I only see 4 of the 5 in Windows Explorer so it seems like the array isn't working as well. Thoughts on that?

JorgeB, Thank you for the suggestion. I will need to locate the cable and figure out exactly what to purchase/replace. Can you let me know how you arrived at that conclusion so tht I can learn? Also, when you say disk5, do you mean the disk listed in the webGUI disk 5 slot?

Thank you. Here is the syslog. I also ran the smartctl command on each disk and they all passed. I did have one error on one of the disks even though it passed but it's not my orange/problem drive. I have included the error portion below but think it is something with the configuration vs. the disk but again I'm no expert. Thanks again! It said AT error Count: 1 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: 58461 hours (2435 days + 21 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 51 01 c7 00 00 00 Error: ICRC, ABRT at LBA = 0x000000c7 = 199 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ca 00 08 c0 00 00 e0 00 00:01:04.641 WRITE DMA c8 00 08 08 8a 00 e0 00 00:01:04.641 READ DMA c8 00 08 10 8a 00 e0 00 00:01:04.641 READ DMA c8 00 08 00 8a 00 e0 00 00:01:04.637 READ DMA c8 00 08 d0 00 01 e0 00 00:01:04.627 READ DMA SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 9660 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. unRAID Scott A.txt

Folks, I was one of the unlucky Texans impacted by the recent storms...cycling electricity (mostly off for 4 days) and then frozen busted pipes with flooding. That said, my unraid server stayed dry. I am running unRAID Server Pro v5.0.2 . I received a red ball on of my drives but when I ran smartdisk it looked okay. I ultimately just removed it from array and then reinserted it at which point a full rebuild occurred and was successful. I could access everything. The next day, I received a red ball on a different disk. Note that I had intermittent slowness in my webGUI. I ran smartdisk everything looked fine so I did the same thing. At some point in the rebuild of that disk, things went wrong. Where I sit now is that I have a started array with the "failed" disk in orange(?) status but the problem is that it says Data-ReBuild in process (with a cancel button) as well as an unformatted disk present. Nothing is moving on the Data ReBuild front from what I can see. Ohhh, I forgot to mention that I think my actual problem is one of the NIC ports is bad. I discovered a bunch of dropped packets so I just unplugged from that ethernet port on the server and everything is operating fine outside of the aforementioned issue. I think the network issue was what was creating my problem (or perhaps lack of disk problem) in the beginning. So, what should I do now? Again when I look on my other computers the failed disk is missing so it seems like something is messed up with the array. I am hoping it's a config issue and the data is still there in parity somewhere vs. just missing. Huge thank you in advance! Sincerely, Scott Albright