chalkdust

Members
  • Posts

    27
  • Joined

  • Last visited

chalkdust's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Ok right so it crashed again just before OFF of the UPS. Just during normal use. I’m at a total loss. I may put my old board back together in this case to see if it’s maybe the power supply.
  2. Ive moved it off the UPS and ran docker run --rm -it progrium/stress --cpu 16 --io 1 --vm 2 --vm-bytes 128M --timeout 10s which 100% all my cpu cores for 10 seconds. it did not crash. What does this mean? Do i need a higher powered UPS to run this on? Im not 100% this is the cause of my crashing though as i THINK i had it on its own plug and it still crashed yesterday.
  3. it was connected to a CyberPower 425VA with an iMac 27" and secondary monitor attached (only the mac is on battery backup and that lost power too). The server has crashed like this in both my server room (on a different power circuit) and in my office. Ive moved it to its own plug now and will test again.
  4. Quick update: in my effort to troubleshoot my unraid crashing, i've installed a stress tester docker app ( https://hub.docker.com/r/progrium/stress/ ) and when i run it, my CPUS hit near 100% and my motherboard lets out a longgggg beep. It doesn't crash under the test settings ( $ docker run --rm -it progrium/stress --cpu 2 --io 1 --vm 2 --vm-bytes 128M --timeout 10s ) but the temp spikes from ~30deg to 68deg. I actually think i may have heard that same beep before a crash at some point recently. My issue clearly is hardware based. does anyone have any ideas for what to look at first? my cooler? my CPU? EDIT: so it was not actually my motherboard sending out the long, loud beep, it was the UPS i had connected it to! under load, my server took down every device connected to the UPS. something seems up with my power draw? should i swap out for a higher quality power supply or does something seem wrong with the hardware?
  5. No, sorry. It crashed after I booted back to unraid.
  6. I’ve got an LSI sas controller card. I can pull it and see
  7. passed twice. and it crashed again twice in a row within 10 minutes of eachother. im at a loss. any other suggestions?
  8. running from built unraid boot menu option now. i will report back when its done. thanks.
  9. im not sure. Is there a recommended memtest process? i can do it again for sure
  10. so i went ahead and moved the machine to my server room to hook it up on the UPS. it was up for about 3 hours and then became unresponsive and then crashed and rebooted. attached is the latest log. Im at a loss. i guess i can revert back to my old server setup for stability, but i was looking forward to using this new hardware. Brought the machine up for more testing. Ive reset the bios to defaults. Although i cant get unraid to boot unless i enable CSM (Compatibility Support Module) in the BIOS. is that normal? could this be memory stick related? syslog-192.168.1.4 (2).log
  11. It's not currently connected to a UPS. i've got it temporarily set up in my workshop after the build. But i've got one in my server room. wasnt gonna move it until it was stable but i can try if you suggest it. I actually re-used my case (Enthoo Pro) and my 2yo PS, (EVGA GQ 650W 80+G SM ATX PSU). Rest of hardware is new. Running an Intel i9-9900K on a Asus Z390-p mobo with two sticks of Crucial Balistix 8gb DDR4 3200 sticks. with two NVME drives installed and a LSI SAS controller holding 6 spinners. CPU cooled by an Arctic Freezer II 240mm AIO liquid cooler. The mobo and CPU temps are reporting quite low and i'm pretty sure the CPU cooling is OK.
  12. If it matters, I’ve recently upgraded all my hardware and kept the same install of unraid. Before installing unraid I did a mem test via the bios. there were a few lines about samba sending reboot or something in the logs right around the time it went down (9:40 pm) if that helps.
  13. Hi all, For the past few nights, at what seems to be about the same time, my unraid server goes down and reboots. After the first few times, i decided to set up the logserver and capture the errors. can anyone help me interpret the logs? attached are logs and diagnostics tower-diagnostics-20210104-2246.zip syslog-192.168.1.4 (1).log