crustcalvin

Update: wdidle3.exe works with this drive, if you set it to /S300 or any other different timer the drive clicks every 8 seconds tho, but if you use /D to disable the timer it seems to work fine, no unusal noises and no speed issues so far.

Hi, I ran a preclear and after it was done I checked the log and saw that after it finished zeroing it logged paused followed by three lines of killing smartctl with pid 1121 - probably stalled ... after that it continued with the post read and finished without any issue Can I ignore this or does this mean there's likely something wrong with the disk? edit: all other disks that I ran a preclear on did not show this behavior

Hey, I got three of those wd drives from wd elements that I had laying around and shucked them to build a new array, their head park timer is 8 seconds which causes a high load cycle count. My question is does anyone know if wdidle3.exe works on those? and if yes should I just increase the timer or disable it fully if possible? I tried hdparm but that did not work, head still parks after 8 sec.

Hey, I created a new usb stick with a fresh install of Unraid 6.12.14 and I got this message on boot after a restart of the server: Loading /bzimage...ok no such file or directory It then booted fine and after I did another restart the message changed to the normal Loading /bzimage...ok Do I need to worry about this or can I ignore it?

Hi, since updating from 6.11.5 to 6.12.10 I get stuff like this: nginx: 2024/07/04 09:46:52 [alert] 1025#1025: *100 open socket #32 left in connection 18 nginx: 2024/07/04 09:46:52 [alert] 1025#1025: *91 open socket #26 left in connection 20 nginx: 2024/07/04 09:46:52 [alert] 1025#1025: aborting in the syslog sometimes, a few in 10 min, sometimes nothing for hours. Is this something to worry about or can I just ignore those? Otherwise the server seems to run fine. Some people seem to also have those messages and experience lockups or nginx crashing.