jeffrey.el

Hmm might buy those for in the future, thanks for the tip!

I think i'll have to do that then... Because I don't see an crash and it also happened during the memtest.. And also the system powers on directly afterwards which is how I set it up in the BIOS after a power loss event..

Alright.. I just did a memtest and during that test it also rebooted... Does anybody maybe know of a way to test a power supply?

Eh yes I do, but it's not connected..

Hello! I hope anybody might be able to help me with this... Since today my server just randomly powers off and then turns on again. I haven't changed anything or done anything to my server for the past days so I have literally no idea where to start looking. I have a syslog server connected but in those logs I see no error or anything either.. After the first time it happened it just came back online and showed an message of an unclean shutdown, so I started the array which in turn triggered a parity check and let it run. It has been running for a few hours after that and then all of a sudden I hear the *click* sound again and it proceeds to start again. No issues as far as I can see... The onboard IPMI doesn't show anything strange either, no high temperatures or anything. Does anyone maybe have an idea where to look or what might be wrong/causing this?

What my issue was that I was using an motherboard from Asus which has some form of overclocking applied by default. So I changed in the bios a settings to something like "Intel Approved settings"? or something? It disabled all the minor tweaks Asus did by default and that stopped it from crashing for me. If you want I can check the BIOS of that motherboard? I don't know which one you're currently using?

This looks like the exact issue I'm having, especially since I haven't had these issues before enabling drive spin down. Right now I set the drives to never spin down, and thus far I haven't had any issues, so I'm going to apply this fix! Thanks a lot for this information! Marking the post as solved

Also another note, this started happening after I enabled Unraid to spin down disks... Before that I had them on 24/7. I read somewhere on the forum that I/O errors can be spin down related?

I'm in a different situation now, I was trying to replace the failed 8tb to prevent any further issues, but after I tried to stop the array Unraid got stuck with the following error message spamming the log: Nov 10 22:44:39 Obscurity kernel: md: disk0 read error, sector=488460120 Nov 10 22:44:39 Obscurity kernel: md: disk0 read error, sector=488460120 Nov 10 22:44:39 Obscurity kernel: md: disk0 read error, sector=488460120 Is there anything I can do to safely stop it so that I can spin it up one more time? The other disk also only has 4 bad sectors so not all information should be lost... right?...

Nevermind, I missed something.. I see there are read/write errors on 4 specific sectors: Nov 8 21:00:30 Obscurity kernel: md: disk13 read error, sector=9293734176 Nov 8 21:00:30 Obscurity kernel: md: disk13 read error, sector=9293734184 Nov 8 21:00:30 Obscurity kernel: md: disk13 read error, sector=9293734192 Nov 8 21:00:30 Obscurity kernel: md: disk13 read error, sector=9293734200 Nov 8 21:00:56 Obscurity kernel: md: disk13 write error, sector=9293734176 Nov 8 21:00:56 Obscurity kernel: md: disk13 write error, sector=9293734184 Nov 8 21:00:56 Obscurity kernel: md: disk13 write error, sector=9293734192 Nov 8 21:00:56 Obscurity kernel: md: disk13 write error, sector=9293734200 Is it possible to fix these by using the preclear plugin to zero the drive?

Hello! I have an odd issue which I can't really seem to find the cause of... about a week ago my Unraid server finished a parity check and during that check 2 8TB disks got disabled due to an I/O error (Only thing I could find in the logs). 1 8TB disk was the parity disk and the other was a data disk. I noticed this because some folders on my share where empty all of a sudden. I was able to get the data disk to be enabled again and started another parity check/rebuild to get the parity disk back up again as well. This succeeded without any issues. However, a day or 2 later, the 8TB data disk got disabled again, since the parity disk was still running without showing any signs of failure I decided to remove the drive from the array and adding it again, forcing Unraid to wipe the drive and do a rebuild again. This also succeeded without any problems. I thought the issue would be resolved by now, but... today... the 8TB was disabled again... and I have no idea what is causing this.. I have attached the diagnostics of my server and am hoping someone could maybe help me shed some light on the cause of this... My first thought was to rebuild the array again, but since it has happened twice now I want to know for sure.. The SMART tests all came back green showing no signs of disk failures and the cable also seem to work fine since I'm using SAS backplanes and the other 3 drives which are connected over the same cable run without issues. Is there anybody who might know what I'm missing or maybe doing wrong? Or could it be that the disk is indeed dying? obscurity-diagnostics-20211110-2006.zip

Alright, after some testing I found out the problem.. Apparently there we're still some overclocking settings applied to the CPU... Which remained active after resetting the BIOS. I updated the BIOS and things seem to be running stable for now! Thanks for the help!

Well the thing is... it seems to have something to do with more power which is needed? Because the last two times was when I started streaming a movie on Plex which had to transcode... And before that it happened during the installation of some virtual machines.. It also happened just randomly after running fine for like 5 days.. that's when I read something about docker containers that should be rebooted on a daily basis, so I wrote a script for that, so they would restart every day. Is there some way/proper tools to test this? Or are there any maybe known issues with the hardware I'm using?...

Alright, I setup a external syslog server on a different PC in the network.. It froze again and all that was in the syslog was this: Feb 5 02:57:32 Obscurity rsyslogd: [origin software="rsyslogd" swVersion="8.1908.0" x-pid="16104" x-info="https://www.rsyslog.com"] start Feb 5 02:58:30 Obscurity kernel: mdcmd (69): nocheck Cancel Feb 5 02:58:30 Obscurity kernel: md: recovery thread: exit status: -4 Feb 5 02:58:37 Obscurity kernel: eth0: renamed from vethb4ba995 Feb 5 02:59:01 Obscurity sSMTP[19696]: Creating SSL connection to host Feb 5 02:59:01 Obscurity sSMTP[19696]: SSL connection using ECDHE-RSA-AES256-GCM-SHA384 Feb 5 02:59:06 Obscurity sSMTP[19696]: Sent mail for [email protected] (221 2.0.0 Service closing transmission channel) uid=0 username=root outbytes=744 Feb 5 03:00:16 Obscurity crond[2934]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Does this help any?.... I can't find anything in it... I did cancel the parity check because that one was running because of the previous crash. (I know I shouldn't do this, but because I'm still trying to figure out what is wrong...)

Hello all! I'm new on the forums so I apologize in advance if I forget anything.. I have an issue with my current Unraid server, for some reason it randomly completely freezes/becomes unresponsive. I have a monitor hooked up to the server because I'm still actively setting it up and the backlit stays on, but no keyboard input is accepted and the web interface is offline, as well as all VM's and docker containers are offline. I have been unable to find a real source of this problem... but right now it's starting to worry me because it's happening more often.. Last night it happened after starting the party check.. some time before it was when I was watching a movie on Plex... before that it happened a few times while I myself wasn't doing anything special in particular on the server. I have attached the diagnostics output to this post, and just this morning I received a notification regarding a hardware issue? (I never had this notification before so that one is new!) I already replace the HBA because I was running a Supermicro AOC-SASLP-MV8 but that one is using a Marvell controller so I thought that, that might have been causing issues, so I replaced that with a Dell H200 flashed to IT mode but like I already said, it froze I think about an hour or maybe 2 after starting the parity check the disk usage LED's just stopped blinking and the server was unresponsive again... So that didn't help unfortunately... The specs of my server are as followed: - Motherboard: Asus ROG Rampage V Extreme - RAM: Corsair Vengeance LPX 4x 16 GB 2133 Mhz - GPU: MSI Geforce GTX 960 - CPU: Intel Xeon E5-2690 V4 - HBA: Dell Perc H200 - SAS Expander: HPE 468406-B21 - PCI Ethernet card: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller - Power Supply: Corsair V1200 - Unraid USB: SanDisk Cruzer Fit I really hope someone can point me in the right direction because I have no idea how or what might be going on... I have searched the forums for similar symptoms and I looked in to all those possible fixes or solutions, but until now nothing has worked for me... obscurity-diagnostics-20210204-1040.zip