Ceco

So no crashes since yesterday so far. It seems that the issue pay have been docker RAM usage. Only ten minutes after restarting my server the Manyfold container was already eating 10 out of my 32G of RAM so i disabled it to see if it would make a difference and so far so good. I also started putting RAM limits on my containers, especially Plex and Immich as some people have reported RAM problems with those. I've restarted Manyfold with a 16G ram limit to see wether it fills that up and if my server remains operational still. Version 7.3.1 had been stable for me so far but since 7.3.2 is available i'll also upgrade to that.

Will do !

Hey ! I'm not even sure how to go about diagnosing this one. Since the last few days, my unraid server has started becoming completely unresponsive every 5 hours or so. The WebUI is unreachable, containers stop working, ssh doesn't work, and even trying to log in directly to the server via the console returns a timeout error. The only way i have to get the server back up is forcing a shutdown and reboot which is obviously not ideal. What's weird is i haven't changed anything in particular, i haven't updated recently (running Unraid 7.3.1 since its release without issue) and apart from updating some containers i haven't changed anything in the configuration in the last few days. Attaching my diagnostics below !unraid-diagnostics-20240609-1951.zip

They do ! Unfortunately I already updated the firmware when i received the card and checking their website there hasn't been an update, so it doesn't look like this will be my solution.

That's a bummer, I specifically went for a SilverStone card hoping it would be more reliable than generic alternatives as it had positive feedback. Anyway, i'll find a cheap replacement card and see what happens. Thanks for the help.

Pardon the noob question but how can i check that ? I might not be looking in the right place but i can't find anything in the documenation for the parity or diagnostics tool explaining how to read logs or get more information about the parity errors. Not even sure what log i should be reading... I went for a SATA Card with the Asmedia chip cause many users reported it running well in Unraid. Looking back, the start of the errors do coincide with the card's installation so is this kind of errors commonplace with such cards or could i possibly have a faulty one ?

Interesting, didn't think that would be the problem. Is this something that can be safely ignored or is there something i can/should do about it ?

Thanks, took me a minute but I ran another parity check after rebooting and got 5 errors again. Diagnostics are attached. unraid-diagnostics-20240609-1951.zip

Here are the new diagnostics after the second parity check, which returned 0 errors this time. unraid-diagnostics-20240602-1342.zip

Started a new parity check, will send the diagnostics in about a day when it's finished

Hi, Since about 3/4 months every time my monthly Parity-Check runs it returns exactly 5 errors. I have parity corrections enabled so I don't think they should be the same errors (though i have no idea how to check that) but it still seems like an odd coincidence. I never had a problem with parity check before which always returned 0 errors for over a year priori to that. Not sure how to diagnose the potential problem or if i should even be worried about it. System diagnostics are below. unraid-diagnostics-20240601-0941.zip

Indeed i just found out about this and was just testing it and sure enough, covering the 3.3V pin means the drive powers on and works as expected. Not sure how comfortable I am leaving two drives with tape on their power connectors running unattended 24/7 so I might return them but at least i know what went wrong, thanks !

I just received two refurbed 12To HGST 0F29596 drives meant to replace two smaller/failing drives in my server. I replaced one of the drives this morning but booting up Unraid afterwards the drive was not showing in the GUI. I noticed that the drive didn't seem to be powered at all. I tried plugging it with a different SATA and power connector but nothing changed. Went into the BIOS and no drive appeared connected on the corresponding SATA Port, so it doesn't seem to be an Unraid specific issue. However connecting the drive on a windows machine with an external USB bay resulted in it seemingly working without issue. That is also the case for the second drive, works perfect on windows via USB but isn't detected and doesn't power on in my Unraid machine. I tried researching the issue and tweaking a few settings in the BIOS but to no avail. Any ideas what the issue could be ? Motherboard is an MSI MAG B560M BAZOOKA, tried connecting the drive directly on the MB or on my PCI SATA expansion card. Also enabled SATA Hot Plug on all ports.

Well thanks for the input ! The disk is still under warranty so i'll replace it and try to get a refund/replacement, seems like the safest way to go.

I didn't reboot so the parity info should be there. penguin-02-diagnostics-20240124-1416.zip

Where can i find those ?

So yesterday I noticed a SMART warning on my second parity drive "Seek Error Rate". Looking at the SMART attributes the value was at 43 and under "FAILED" it said something like "DISK FAILING". I was a bit surprised as that drive is less than a year old but still, i ordered a replacement right away with the intention of returning the drive. This morning though the warning disappeared from the array screen and the SMART status is "Healthy". However the SMART attributes show the Seek Error Rate as Offline. Running a short and extended SMART test on the drive result both in a test that ends in a few seconds only with an "Unknown Failure". SMART reports below. So since I don't quite get everything about how SMART attributes work, I wanted to make sure : that drive is gonna die right ? I should replace it ASAP rather than keep using it ? Thanks ! Edit : Didn't think to mention it but in case it's relevant, the SMART error first appeared during a parity check that completed last night. The check apparently found 4108 errors wich is the first time in 2 years that any errors was found. I assumed that was because I just replaced my flash drive after the first one failed but maybe that is a sign of disk failure as well ? TOSHIBA_HDWG21C_82U0A003FPBG-20240124-1034.txt