Max3dmoon

Ok so I did that and ended up crashing a few minutes ago....the log is gibberish to me but I'm surprised to see tons of errors hours before the crash (Sept 27 AM but I crashed in PM) Any idea what could be the culprit ? syslog-192.168.1.175.log

Interesting, thanks ! There has been a new development, a few hours after posting my last message I came back to find my unraid server completely unresponsive. Had to do a hard reboot. Grabbed the diagnostic after the hard reboot, do you see anything that could explain what is going on ? The server is currently doing a parity check and in // I also started a extended SMART test (still ongoing) on the unmounted drive that failed the pre-clear. Once the parity and the extended SMART is complete, I'll probably reboot and do another memtest. [ I had an unraid build for years with not a single issue (with containers, VM etc.) and this new build is giving me so much headaches ! 🥴 ] tower-diagnostics-20220923-2029.zip

Here it is, thanks JorgeB. Really appreciate you putting the time 🙏 tower-diagnostics-20220923-1901.zip

Sorry I should have mentioned it, I did an extensive memtest and it came back with zero errors

Hi, Was pre-clearing a new HDD and got that: What are my options please ? Or should I just send back the HDD ?

Update: I've been able to move almost everything from the failing disk, it's still in progress - should be done in a bunch of hours- but so far everything has been working with no hiccups and all the most critical data is safe already so it's possible I achieve 100% data retrieval ! I'm also moving all the data from the other ST3000DM001 (still healthy but for how long ?) and will be replacing both with some brand new WD RED. Again thanks everyone for your help ! PS: for the temperature, yes it's now in a 19" rackcase with some 120mm fan directly blowing at them.

Great ! Thanks a lot !

Hey, Still in the newbie phase where you do use the search engine before asking for help but you don't always understand the answers... so better safe than sorry ! I'm moving data from various shared folders to ONE shared folder and this shared folder is only on ONE HDD (excluding all other HDD and no parity/no cache on the server) Can I take this HDD remove it physically from my machine and plug it into another unRAID machine (no parity as well). Will it work flawlessly ? Thanks !

Thanks a lot for your help. Truly an awesome community...people weren't lying ! Going to buy some HDDs, salvage everything I can and restart from scratch.

uh oh.....must have missed the memo about that....."funny" thing is I have another one in my array ok so go run to the nearest store and go buy some WD RED I guess ? Should I try to re-launch the array and see what I can salvage (if any) from the one that went offline ? Note: I had a lot of data backed on ACD unlimited with ARQ but not everything so I still lost some stuffs (stupid me for not being organised enough)

Thanks for answering so quickly ! Did what you asked, launched a "SMART extended self-test" on the dive but after few minutes I got an error message saying I should check the report. (Attached) ST3000DM001-1E6166_Z1F2E2K5-20170515-1434.txt

Hey, New to unRAID, had a lot of fun in the last 48 hours. Was keep telling me, this is a game changer and then....boom Let's rewind: I took a bunch of HDD that I've been using for a while (with no priors issues), put them together, very patiently transferred all the data in the Array (cache disabled and no parity) Earlier today, I was happy, everything was consolidated and green/smart everywhere. Time to create the parity disk and call it a day ! And then few hours after (in the middle of the parity process) one of my disk "exploded" with millions of reads errors (according to the main tabs). I can't access anything thru the shares folders (not even the content on the other HDDs, everything show-up empty). Don't know what to do....the parity check is still going....should I stop the array ? Start mourning my data ? Thanks for your help and advice (make it easily understandable please, I'm new to all this) Config: M/B: ASUSTeK COMPUTER INC. - Z87-A CPU: Intel® Core™ i5-4440 CPU @ 3.10GHz HVM: Enabled IOMMU: Enabled Cache: 256 kB, 1024 kB, 6144 kB Memory: 24 GB (max. installable capacity 32 GB) Network: bond0: fault-tolerance (active-backup), mtu 1500 eth0: 1000 Mb/s, full duplex, mtu 1500 Kernel: Linux 4.9.19-unRAID x86_64 nas-diagnostics-20170515-1341.zip