horrorhound

Members
  • Posts

    11
  • Joined

  • Last visited

Recent Profile Visitors

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

horrorhound's Achievements

Newbie

Newbie (1/14)

1

Reputation

  1. Turns out to be plex docker crashing the server each night during it's maintenance run. I've tried both binhex and linuxserver docker versions of plex and they both crash the server... Still trying to figure out why.
  2. Did you ever find a solution for this? My binhex/plex is crashing server each night.
  3. Problem seems to be with one of the docker containers. (wonder why safe mode doesn't disable docker containers). Server up for past 2 days, I'll start going through each docker now. It maybe due to the "New Permissions" which I ran recently and maybe broke or caused problems with one of the containers.
  4. Mover is set to execute weekly, so we'll see if Unraid crashes tonight.
  5. I have the syslog mirrored to the flash drive already, but it doesn't really show anything.. Just shows HD's being spindown and then when I have to hard-restart then unraid starts writing to the syslog again. Crash again last night on 6.8.1 so the problem isn't with 6.8.2. "Mar 1 16:04:02 Tower kernel: mdcmd (69): spindown 6 Mar 1 16:05:06 Tower kernel: mdcmd (70): spindown 10 Mar 1 16:05:29 Tower kernel: mdcmd (71): spindown 2 Mar 1 16:05:34 Tower kernel: mdcmd (72): spindown 7 Mar 1 16:05:36 Tower kernel: mdcmd (73): spindown 9 Mar 1 16:05:36 Tower kernel: mdcmd (74): spindown 11 Mar 1 16:05:58 Tower kernel: mdcmd (75): spindown 1 Mar 1 16:06:00 Tower kernel: mdcmd (76): spindown 3 Mar 1 16:06:02 Tower kernel: mdcmd (77): spindown 4 Mar 1 16:06:05 Tower kernel: mdcmd (78): spindown 0 Mar 1 16:06:06 Tower kernel: mdcmd (79): spindown 5 Mar 1 16:06:08 Tower kernel: mdcmd (80): spindown 8 Mar 1 17:39:40 Tower kernel: mdcmd (81): spindown 8 Mar 1 17:39:44 Tower kernel: mdcmd (82): spindown 10 Mar 1 17:42:01 Tower kernel: mdcmd (83): spindown 9 Mar 1 17:42:18 Tower kernel: mdcmd (84): spindown 2 Mar 1 17:42:22 Tower kernel: mdcmd (85): spindown 6 Mar 1 17:42:24 Tower kernel: mdcmd (86): spindown 1 Mar 1 17:44:39 Tower kernel: mdcmd (87): spindown 5 Mar 1 18:27:39 Tower kernel: mdcmd (88): spindown 7 Mar 1 18:49:01 Tower kernel: mdcmd (89): spindown 10 Mar 1 18:51:04 Tower kernel: mdcmd (90): spindown 2 Mar 1 18:51:22 Tower kernel: mdcmd (91): spindown 6 Mar 1 18:52:43 Tower kernel: mdcmd (92): spindown 1 Mar 1 18:53:11 Tower kernel: mdcmd (93): spindown 3 Mar 1 18:53:17 Tower kernel: mdcmd (94): spindown 5 Mar 1 19:00:20 Tower kernel: mdcmd (95): spindown 4 Mar 1 19:02:46 Tower kernel: mdcmd (96): spindown 0 Mar 1 19:02:47 Tower kernel: mdcmd (97): spindown 8 Mar 1 21:48:47 Tower kernel: mdcmd (98): spindown 2 Mar 2 00:25:36 Tower kernel: mdcmd (99): spindown 1 Mar 2 02:41:19 Tower kernel: mdcmd (100): spindown 2 Mar 2 02:42:05 Tower kernel: mdcmd (101): spindown 7 Mar 2 02:45:10 Tower kernel: mdcmd (102): spindown 10 Mar 2 02:56:12 Tower kernel: mdcmd (103): spindown 1 Mar 2 13:38:42 Tower kernel: Linux version 4.19.94-Unraid (root@Develop) (gcc version 9.2.0 (GCC)) #1 SMP Thu Jan 9 08:20:36 PST 2020 Mar 2 13:38:42 Tower kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot Mar 2 13:38:42 Tower kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Mar 2 13:38:42 Tower kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Mar 2 13:38:42 Tower kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Mar 2 13:38:42 Tower kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Mar 2 13:38:42 Tower kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format."
  6. Downgraded yesterday to 6.8.1, system still crashed last night. Today I started system back up with Safe Mode No GUI.
  7. Unraid Verserion: 6.8.2 Recent Changes: Upgraded a 1TB HD to 4TB HD WDC_WD40EFRX-68N32N0_WD-WCC7K3LF2DJD - 4 TB (sdi) Upgraded to 6.8.2 After these changes I'm experiencing nightly crashes. Troubleshooting: Ran memtest from Unraid bootup option for 3 days with 15 successful passes. While a parity check is running over night unraid does NOT crash. This leads me to believe maybe MOVER is crashing the server but not sure how to troubleshoot that. Today I plan on trying to disable MOVER. tower-diagnostics-20200229-0940.zip
  8. Upgraded to the recently released firmware of MB and server has been stable for 24+ hours now.
  9. Switched to a new power supply AND Switched out RAM also, still crashing. syslog
  10. I've ran memtest twice and ram checks out fine... DateTime is set use NTP and pointed to pool.ntp.org; everything seems fine here. I just changed out Power-Supply so we'll see if it crashes tonight.
  11. New server which Unraid was migrated older machine which ran great for years.... New Build where Unraid Crashing: Model: Custom M/B: Micro-Star International Co., Ltd. MEG X399 CREATION (MS-7B92) Version 1.0 - s/n: IB16121592 BIOS: American Megatrends Inc. Version 1.20. Dated: 11/14/2018 CPU: AMD Ryzen Threadripper 2950X 16-Core @ 3500 MHz HVM: Enabled IOMMU: Enabled Cache: 1536 KiB, 8192 KiB, 32768 KiB Memory: 16 GiB DDR4 (max. installable capacity 512 GiB) Network: bond0: fault-tolerance (active-backup), mtu 1500 eth0: interface down eth1: 1000 Mbps, full duplex, mtu 1500 Kernel: Linux 4.19.41-Unraid x86_64 OpenSSL: 1.1.1b I started outputting the syslog to the Flash drive so I could get sometype of logging because after about 24hours Unraid is totally non-responding from the console or WebGUI. Troubleshooting so far: 1) Had mother-board RMA'd 2) Drop ram down from 32gb to 16gb but still crashed. 3) Turned off all VM's. I could really use some help; I'm not sure where togo from here. syslog-crash2019.05.29.zip