SheepContoller

I see, and added the value to the ones unRAID should monitor closely. Well the replacement drive has been precleared 2 runs, guess I'll just keep watching how things go and either replace the one that fails first or maybe if possible get a second HDD and replace them both. Anyway thanks to both of you for sparing a moment to give my problem a look, most appreciated.

Well thanks guys for taking a look - but what makes the "other" a soon-to-fail? "failed" has come up a few times on unRAID checks, like corrected errors and that, "other" has always been the green one. I know "other" has seen more runtime, but is 4.7 years a critical value? (TBH, if it was just me I'd ditch all drives for 2+1 10TB Helium drives, but there's the issue of money) What value other than "uncorrectable" is a critical one to give an extra look, other than the ones being monitored by unRAID anyway ?

Hi there, yesterday, I was greeted with the red X of despair, one of my WD Red 3TB had been disabled. So I went and bought a replacement but since that wasn't precleared and the SMART looked okay-ish to me, I re-activated the drive and the rebuild went flawless ... so is the drive really bad or could it have been something else? Report attached, I run two of these HDDs, marked the reports. I know the drives are collecting age and rust, but is it reasonable to keep them running? Obviously, there is a parity drive and that's pretty new, 1200+ hours. Preclear on the replacement is running right now. Thanks failed - WDC_WD30EFRX-68EUZN0_WD-WMC4N0816310-20180725-0033.txt other - WDC_WD30EFRX-68AX9N0_WD-WMC1T0041512-20180725-0034.txt

System freezes on 6.5.3-rc* and 6.5.3-stable, had to revert to 6.5.2 MB: Asus Pro-Gamer Z97 CPU: Xeon 1231-v3 RAM: 16GB W10 VM (freezes occured on start and during runs) Build: https://de.pcpartpicker.com/user/Thufix/saved/XrCsJx

root@Nexus:~# ls -al /boot/config/ssl/certs/ total 32 drwxrwxrwx 2 root root 8192 Apr 8 16:36 ./ drwxrwxrwx 3 root root 8192 Mar 6 16:57 ../ -rwxrwxrwx 1 root root 2847 Apr 8 16:36 Nexus_unraid_bundle.pem* -rwxrwxrwx 1 root root 2823 Mar 6 16:57 Tower_unraid_bundle.pem* I assume your machine is called SERVO? Mine was Tower, now called Nexus, maybe unBalance is looking for a fixed name?

Awesome, sorry I didn't get to send the logs, but after the update it runs perfectly fine. The folder with 17k+ files? Really can't complain here. It will not open on SSL connection, but that's nothing that's really bothering me, honestly. So here's you 5-star

Wow, same thing here, although it only happens with a large number of files (dozens was okay, 17k-ish wasn't).