coopermoto

Members
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

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

coopermoto's Achievements

Noob

Noob (1/14)

1

Reputation

1

Community Answers

  1. My server has been 100% stable now for over 2 weeks so I no longer have a problem. It has been back in its normal location for almost 5 days, with only a network and UPS connected. I'll mark this as the solution as I don't know what the actual problem was. Thanks for the help fault finding. I have a better idea of where to look for issues now.
  2. Since my last post I've had my server running on my bench, where I moved it to perform the memory test on Sunday, 4 days ago. It normally lives in an out of the way place on a UPS and with only a network connection. On my bench it is not using the UPS and has a keyboard, mouse, monitor and network plugged in. It is also started in GUI mode. It has now been up for 3 days 10 hours 22 minutes, which it has not been doing for months. Could there be anything involving the UPS that might make it crash & restart without anything useful being logged?
  3. Is there anything else that I (the OP) should check?
  4. The memtest results are in; 12 hours of testing found 0 memory errors. Report attached. MemTest86-Report-20230219-154229.html
  5. I have never run memtest - would you suggest that as my next course of action? If so should I be using https://www.memtest.org/ or https://www.memtest86.com/? (my system boots in UEFI mode)
  6. Should I post the syslog in a new topic?
  7. It's happened again and here is the syslog. The first entry in the now current syslog (Tools > System Log) is at 04:29:20 so it happened just before that I guess. syslog-192.168.1.5.log
  8. Thanks, I've done that and will update once it happens next.
  9. Hi General Support I have an Unraid Pro system that has been running for around 3 years quite happily. Over the last few months I have been experiencing semi regular/regular I guess crashes. The system disappears for 5-10 minutes and when it comes back reports an unclean shutdown, which then triggers a parity check. There have been no hardware changes since I built it 3 years ago and I have a bunch of Docker containers running (27) but no VMs. I'd like it not to do this (crash) so I'd appreciate any help that anyone can give; I've attached diagnostics logs taken right after the most recent crash. Many thanks, Barrie sulaco-diagnostics-20230217-1150.zip
  10. Brilliant. I had exactly the same problem and this has fixed it. Thank you soooo much. I'm amazed there aren't more people moaning about this.