Martinxds

Members
  • Posts

    18
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Martinxds's Achievements

Newbie

Newbie (1/14)

0

Reputation

1

Community Answers

  1. Blast from the past is this thread. I can report it has been working fine since! I hade a 3400G with an Asrock B550 Steel Legend. I replaced with a 10400 with a MSI B560M-A PRO (Supported GPU Encoding for Plex woo) New information as well. About two months ago I used the old 3400G and the Asrock B550 Steel Legend to do a budget build for a family member and Windows would crash when a CPU intensive game (Stellaris) was run. Every other game that didn't tax the CPU it was fine. This tells me the motherboard was faulty from the get go as they are meant to be compatible with an updated BIOS. Replaced the board with a B450 of some sort and it stopped crashing Windows. Reminds me I should try warranting that board now I know it was the problem - across two systems and OS's. Not that I have a spare CPU to put in it any more. May not help you in your current troubleshooting as it turned out to be hardware fault so I'd encourage you to open your own thread!
  2. So out of sheer desperation I replaced the CPU and Motherboard. And I am looking stable at over 24 hours uptime running all containers and using Plex extensively. Now this travesty is done, I'll try to enjoy Unraid now!
  3. I Deleted the Docker Image file in case it was corrupt but no luck. So I have swapped everything except the CPU, Mobo and RAM (and drives). It crashed just before, I just started the Array with docker stopped and started deleting plugins and it crashed. I can confirm it also crashes as soon as I try to play anything in Plex. Anything else I can test before I look ate replacing the Mobo and CPU? Worth doing a New Config?
  4. Memtest found nothing. Reseated Ram in different slots anyway. Swapped USB and it still crashed. Ran it today in safe mode without docker running and got a random crash sadly.
  5. I found a could cause it to crash and reproduce the error last night by watching a something on Plex. I then swapped power supply but it still crashed on the Plex usage. Watching it directly via SMB and it worked fine. I have since swapped power supply with the same issue. I have then turned Docker off and let it do a parity check last night with it crashing by the time I woke up. Trying again. I'll turn safe mode on once this is done/fails and see how we go. I did set-up Syslog mirroring a bit ago and here is is attachedsyslog (3) My biggest problem I think is I can't get it to write the Diagnostic file when it crashes. the console responds but it can't write anything to the file system or seem to access the USB drive.
  6. So I formatted and swapped it over to a USB 2 port. It was stable for a good day and a half, sadly just had a crash now. Diagnostics attached. I can't see anything in there indicating what the issue was. hydra-diagnostics-20210928-1051.zip I was able to logon the console and create the diagnostics and issue a reboot command though. Might need to look at replacing other older equipment like PSU? Can't justify a CPU platform swap though.
  7. Unfortunately crashed again without the ability to create a diagnostic file also means the CP command doesn't work with an error: cp: cannot create regular file '/boot/syslog.txt' : Input/output error Is this potentially a USB issue? It is a brand new USB but I'm going to backup the config and format and restore it. I did set it up to write syslog to Flash. But doesn't seem to have anything usefully that I can see: syslog
  8. Thanks from now on when it can't get the diagnostic file I'll grab the syslog . So good(?) news. It hasn't hard crashed since yesterday morning. But today it had disappeared the shares. Attached is the Diagnostic file. The logs has the line in it: Sep 26 07:40:15 Hydra kernel: shfs[2510]: segfault at 0 ip 00000000004043b8 sp 0000148eb975b780 error 4 in shfs[402000+b000] Might indicate cache drive issue? I had to reboot for shares to come back online. hydra-diagnostics-20210926-0748.zip
  9. And sadly another crash and another time I can't create a diagnostic file:
  10. 2nd Sata Card purchased. Will try a parity rebuild now. Fingers crossed!
  11. Thanks for the assistance. At this point it's cheaper and less effort to just buy another Sata card rather than swapping out the motherboard so I will go down that route. I'll check back in a week or two and let you know how I went
  12. Reading a few other threads it looks like this can be caused by heavy usage on the onboard sata controller. Since I have a 6 port sata card and a 6 sata ports on the motherboard and plan to just use 10 Sata device in total I've moved a couple over to the card to minimize the usage on the onboard controller. Lets try another party build!
  13. Yep certainly has the latest Bios on it. I'm at a loss here. Don't suppose you know of any other settings that would help me get this board stable?
  14. Ack! It's a brand new board and I thought I did a Bios update. Let me check. Thanks!