BishBashBodge

Thought I'd check in to hopefully finally close of the topic. I've abandoned Ryzen and have bought a new mobo w/ 10th Gen Intel i3. Everything, as you'd expect, is all a little less "exciting" with this set up. I've lost several cores in the process and will likely drop the ambition of running a passthrough VM, but with so much hardware spare as a result of this endeavour, I've now more than enough to build a standalone pc On the plus side now having access to Intel QuickSync hardware transcoding means that, if anything, Plex is even more performant during transcodes. Many thanks for everyone's time and assistance.

Thanks Vr2lo, I hope so - thanks for some reassurance. Shall keep plugging away!

I believe so, BIOS settings as above followed that advice and the replacement of the RAM was also spurred by it - picking a validated set for the Mobo and with lower speeds (XMP or whatever its called is turned off too). I took advice from a colleague that the B450 Tomahawk mobos were well regarded but I've no direct knowledge. Given that its a 2nd Gen (2700) Ryzen I think the need to disable "Global C-States" along with the unraid boot param (for c-state 6) are not applicable. I'd estimated that Ryzen, with its generous core count, was going to be the only way I could achieve a multi-purpose nas/plex/vm box at an affordable price, but given that I've replaced pretty much everything but the CPU I'm beginning to accept that I chose poorly!

Duly noted @jonathanm. I wanted to expand the array anyway so will get a couple on order, appreciate your sense check! Is it common, or even plausible, for a failing drive to cause unraid to crash so drastically though?

Hey @JorgeB does the following look right for BIOS? @Vr2Io, followed your advice last night (actually, I disabled VMs and Docker w/out going into safe-mode for some reason) and I got a little over 16hrs of uptime before shutting it down. Good news. In light of that, I reinstalled the parity disk and when starting the array it pretty much immediately crashed. I can see a smart test on the parity disk is reporting a read error. Could that cause a hard lockup at such a fundamental level? I'm currently of the (possibly naive) assumption that UnRaid is designed to ride out shoddy drives! I've installed the preclear plugin and am currently running a preclear on this drive to see if it resolves the read error. Aware that I probably want to be shot it altogether, but perhaps the read error could be caused by multiple nasty crashes? I'll certainly look to replace it, but would like to know if it's the culprit before doing so. Let me know if this is foolhardy. Furthering my curiosity in this regard, in hindsight, the 3 Mo on Windows server used a different (motley) assortment of drives for the purposes of testing.

Hi All, I came to the forum back in April with this issue and despite some seriously good effort on the community's part was unable to resolve the issue of my unraid setup hard crashing - with nothing in the sys logs to denote an issue. The crash drops everything - graphics, networking even usb power but fans continue to spin and requires to be powered off and back on via the power button. Since the last topic I've replaced the mobo (previously an ASRock B450 that was driving me nuts with hokey BIOS updates) the PSU (I'd gone cheap and figured it was worth a punt) and most recently the RAM (favouring a slightly slower speed and dual channel 2x8GB). I ended up running Windows Server for 3 months with perfect reliability but it was never the solution I wanted to be left with. In the last 48 hours, I've since used a clean USB with a fresh install (6.9.0-rc2) but continue to be plagued by crashes anywhere between 10 minutes to several hours in - I even had a few days of uptime last week that gave me a false sense of security! FWIW, I've also run over 30hrs of memtest with clean results. Any guidance would be enormously appreciated. Current Hardware - MSI B450 Tomahawk MAX - Ryzen 7 2700 - 16GB (2x8GB) Corsair Vengeance LPX 2400Mhz - Seasonic GX550 PSU - Corsair 240GB NVME - Cache drive - 2 x 4TB WD Red BIOS - Latest update - Set to Typical Current Idle - IOMMU Enabled - SVM Enabled Attached are diagnostics. tower-diagnostics-20210204-0051.zip

@Benson good shout, this box has never run anything but Unraid. I'll get Windows on it this weekend and give it a good stretch. Got two 2TB drives lying about now so I've got that covered!.

Hey folks, So.. following on from your earlier queries (for which, once again - thanks!)... 1) Tried a few different usb ports (on different controllers) and one continued to crash whilst the other, though possibly by coincidence, seemed to kill network connectivity?! 2) Tried running parity check with array in maintenance mode - crashed. 3) Upgraded to 6.9-beta1 - crashed on parity check. Am I in "just rebuild the server" territory at this point? Ultimately, the sod's worked since October with zero issues so unless there's subtle hardware failure at play, this thing should run! There's a whole bunch of set up with vms (along with IOMMU GPU passthru magic) and docker for Plex and home automation duties that'd take some time but I'm not seeing many other routes. I'm still of naive hope that I'll either be able to get the data off, or use UD to get the data back on? Wisdom still very welcome. Apologies that this is feeling all a little desperate and defeatist. All of your assistance has been invaluable, I guess I'm just not used to feeling quite as tech-clueless as this!

Hey thanks @Benson hell of a lot of detail there. Appreciate it. The parity rebuild succeeded and I was flying high this morning. Just tried pulling in some new data and the relatively heavy write (think it was about 4GB in out of 40GB) using an rsync operation from a remote server via a docker image. Unfortunately it tanked and crashed during this operation. Following that the parity check once again causes the machine to crash. I've fully, physically removed the two 2TB drives so I think that potential Mobo issue could be able to be ruled out as the cause for crash? Also, could plugging & unplugging a keyboard count for the USB disconnect? I've been swapping my USB hub with kbd & mouse back and forward from my desktop to the server for diagnosis p.s. You guys are awesome. Thanks.

So, I ran some prime95 stress tests and pinned the box for some time without issue. Relieved that this didn't freak it out. Unfortunately testing a large move of music to one of the two 2TB Toshiba drives (I thought they were WD Greens, I was wrong) the box hung again. In honesty the value of that data was sufficiently little that I just binned it after the reboot. With limited options and a full knowledge that the parity drive is effectively useless (as I'm certain there are errors and I'm unable to run a parity check) I've taken what is likely a risky and foolhardy route and shrunk the array - removing the two 2TB drives. Perhaps this could help the power issue as it ran fine for 4 months without them?! This was only an option as those drives had yet to be populated with anything, with the 4TB sitting at about 85% full (I'd intended on spreading this out a little at some point). If it is a power issue, this could help; if it was caused by something I did when adding those drives, likewise. An hour and a half into a parity rebuild and over 20% complete is looking promising and worlds better than previous attempts so I'm moderately hopeful I might get something back out of this - albeit with the chance that some of my data could well still be corrupt. Feel free to tell me I'm an impatient idiot 😦 I'll report back later.

That's interesting, can you think of a decent way I could test the theory? Maybe are there any kind of load test utils that others might have used?

12 hours down of the memtest, 9 passes and no errors. I've left it running, but at only 8 GB it's had a fairly thorough thrashing It stayed up for the entire duration of running the SMART tests (6-7 hours perhaps) whilst the array was offline and then locked up 5 minutes into the parity check I subsequently attempted so with a clean bill of health from the drives I'd be inclined to believe its not hardware(?). If that was the case though, you'd think it'd at least be able to log the triggering event. I'm still so new to Unraid, I've no clue where to go from here!

Great will do, I'll let the SMART test finish then I'll run a memtest for the rest of the day. Cheers.

I vaguely remember seeing some of that when setting up but think I came to the conclusion that given my build was stable, I'd leave it alone. That said, I've now disabled "Global C-State Control" and set "Power Supply Idle Control" in BIOS to "Typical Current Idle". I had a bit of a mare with BIOS originally as the latest update at the time ruined all of the IOMMU groups which stopped me from setting up VMs like I wanted to. Got through that (not that I immediately remember how - fairly sure I deferred to SpaceInvader's expertise) in the end but I get chills every time I go in there now Unfortunately, with that applied it has just locked up a couple of minutes into a parity check. Worth ruling out though and I really should have done that from the beginning given how widely those settings seem to be advocated for a rig like mine. Now running an extended SMART test just 'cos I'm desperate. I'll keep digging through that bug report but I think the link to the comment you highlighted mentioned all the useful bits. Any other thoughts massively appreciated.

Hey folks, So, I've been living the Unraid dream for just over 6 months now, however over the last few weeks I've been battling a server that frequently becomes entirely unresponsive. By this I mean that not only is network down (no ssh or ping) but when running it using the local GUI, even that freezes and stops responding to user input. I've identified that it freezes early on when the parity check kicks in - if Unraid attempts to start one due to the unclean shutdown I have to race to log in and stop it! But I think it happens at other times too - it went again last night and I've disabled the parity check schedule till I can work out how to sort this. When trying to diagnose this I've had it crash despite removing almost all plugins and having disabled the VM manager and Docker also so have run out of things to turn off! I've also been persisting the syslog to the flash drive and there's no entry prior to it freezing that would (obviously) explain whats going on. I also ran the memtest for about 6 hours yesterday with 0 errors having seen that fixed someone else's similar sounding problem. I did have several unclean shutdowns in short succession a while ago which caused some issues (had to rebuild my docker Plex library as it wouldn't load) and I'm fairly certain there will be inconsistencies that the parity check needs to fix - but I assume even if the array was completely borked, Unraid should run regardless. Any advice would be *very* welcome! Otherwise all I've got left is to start from scratch. Our lights are run thru this box using Hass and the wife is starting to lose patience with me having to go through a twenty minute song and dance every time she wants to go to a different room Attached is the diagnostics zip. I've also added a longer syslog that spans multiple crashes if its useful. (Last note: this is running v6.8.2. it was on v6.8.3 and doing the same, I just wondered whether the downgrade would help!) Rough specs if they're useful: Mobo: ASRock B450 PRO4 CPU: AMD Ryzen 7 2700 RAM: 8GB DDR4-2666 GPU: GT 710 1GB PSU: EVGA 550w Parity: 4TB WD Red Array: 4TB WDRed & 2x 2TB WD (Green I think) alfred-diagnostics-20200413-0951.zip syslog