superfans124

finally got around to do memtest, let it ran over night, 10 hours, zero error

thanks. it does support UASP, even tho I don't understand it, but going back to the amazon listing where I purchased it, it states so... I will do memtest, and report back with any finding.

so I got a refurb WD HDD, ran pre-clear, the first full pre-clear, it failed at the very end of post-read, pre-read and zero were fine. I didn't save any logs, since I thought if the disk is bad, I'll just ask the merchant for a replacement. no big deal. but, before I initiate replacement call, it doesn't hurt to run preclear again, just to confirm, right? so I ran preclear the 2nd time, and it passed without a hitch. so now I'm confused, is there any problem with this HDD? is this common? it's connect to my unraid rig via external-powered sata-usb adapter for HDD to run preclear. Thanks.

Hi, so I waited a bit, it just so happens I had new HDDs coming in and was running preclear, I waited for that disk to complete pre-clear first in case I need it to step in to replace disk 2. so per your suggestion, what I found was that disk 2 is fine, or so I think. it's a shucked WD HDD with those 3.3V pin, the tape that I put on to block the pin got loose somehow, once I checked the cables and reapplied new tape, Disk 2 becomes available again upon boot up. Even though I don't know what else to look for before jumping to conclusion but I think Disk 2 is fine...if it is, could you update the link to procedure for "re-enable the drive" you originally posted at or do their reddit discussion also cover the correct procedure? I really don't want to rebuild the entire parity if I could avoid it...thanks so much for everything! unryzend-diagnostics-20240131-0029.zip

awesome, thanks. will do.

thank you. the failed drive is disk 2 unryzend-diagnostics-20240129-1020.zip

I too just got my first failed drive for the first time, if someone could take a look at the smart report (no rebooting of the system over night, woke up in the morning and saw the red X) that would be much appreciated, while I'm still searching for to-do list and learning what to do. thanks. unryzend-smart-20240128-1234.zip

v6.12rc2 did the trick, thank you! so relieved I don't have to scramble for hardware solutions.

hi, sorry, can I trouble you again? so I checked the cables and upgraded bios, rebuild went smoothly for about 70% before I went to sleep, system crashed when I got up in the morning requiring hard reboot, once logged in notified me rebuild failed with tons of errors. this is the first diagnostics I pulled before starting the array, but after reboot... all the disks with errors are connected directly to the onboard sata ports, but I'm bit perplexed why the initial parity rebuild went thru without any trouble, but a new data disk a day later is giving me all this hassel. unryzend-diagnostics-20230329-0916.zip

thank you

unryzend-diagnostics-20230327-0905.zip last week I first upgraded my parity to 18tb disk, that went without a hitch, completed with no errors and warnings. then I tried to upgrade disk 7, from 8tb to a brand new 14tb (already stress tested) and half way thru, all kinds of errors started popping out (reading errors?). and this is my 2nd attempt, it already happened once over the weekend, I tried shutting it down and checked all cables and started over, but apparently this is more complicated than I can handle on my own. thanks.

thanks. I got stuck here as well. adding disk no.12 after more than a year, suddenly lost all senses what I'm supposed to be doing

did that, uninstalled, reinstalled, didn't help.

unryzend-diagnostics-20211210-2133.zip

if I'm not posting in the correct section, please let me know. thanks. ever since updating Unassigned Devices a week ago, one of my previously working portable drive started showing up as "array" in UD, instead of "mount/unmount". my go around is to stop the array and re-start again, or reboot, then UD will correctly allow me to "mount/unmount" it, but then, once I unplugged that drive, do my thing with it, replug it back in, it's back to "array" in UD once more, requiring the go-around again. it's not a critical issue as there are go-arounds, but if someone knows how I can do without restarting my whole array everytime I want to transfer some files, that'd be really neat. Thanks.