FreakyBigFoot Posted March 24 Share Posted March 24 (edited) I've been having this issue for while now. I've downgraded, upgraded, disabled dockers, disabled VMs, disabled cstates, swapped out RAM, deleted and re-created docker.img. I'm using a pc from minisforum, the MS-01. I'm not sure if it's just giving out or what. I've setup a logging server and I have 0 logs. Nothing indicating what's going on. I did finally get something on my screen. I've also attached my diagnostic logs. I could really use some help. I'll just wake up and it's unresponsive. I have to hold the power button to get it to turn off. tower-diagnostics-20240324-1153.zip Edited March 24 by FreakyBigFoot Quote Link to comment
JorgeB Posted March 24 Share Posted March 24 The previous syslog only covers half an hour or so, does it cover a crash? Quote Link to comment
FreakyBigFoot Posted March 24 Author Share Posted March 24 No, that's the thing. I'm not getting any logs. I'll wake up and it's 'on' but nothing is responsive. I have to hold the power button.. Quote Link to comment
JorgeB Posted March 25 Share Posted March 25 9 hours ago, FreakyBigFoot said: No, that's the thing. I'm not getting any logs. Don't follow, there is a previous log, post a screenshot of the syslog server settings. Quote Link to comment
FreakyBigFoot Posted March 25 Author Share Posted March 25 (edited) I’m also using Datadog to gather logs. I have zero logs around the time it crashes. It crashed about an hour ago and same thing. Absolutely nothing. My fans kick on high and unraid just crashes. Edited March 25 by FreakyBigFoot Quote Link to comment
JorgeB Posted March 26 Share Posted March 26 13 hours ago, FreakyBigFoot said: I have zero logs around the time it crashes. There won't be anything on the Alex share since the remote server is blank, you need to use the server IP, but there should be in the flash drive, logs folder. Quote Link to comment
FreakyBigFoot Posted March 30 Author Share Posted March 30 I got this today. Still no logs.. I’m starting to think my CPU is bad. Quote Link to comment
FreakyBigFoot Posted March 30 Author Share Posted March 30 Here is all I have: Mar 30 00:00:05 Tower emhttpd: read SMART /dev/sde Mar 30 00:00:21 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 00:10:33 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 00:15:07 Tower emhttpd: spinning down /dev/sde Mar 30 00:20:45 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 00:30:57 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 00:41:09 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 00:51:21 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 01:01:33 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 01:11:45 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 01:21:57 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 01:32:09 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 01:42:21 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 01:52:32 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 02:00:03 Tower emhttpd: read SMART /dev/sdd Mar 30 02:00:11 Tower emhttpd: read SMART /dev/sdc Mar 30 02:01:51 Tower root: /etc/libvirt: 71.2 MiB (74670080 bytes) trimmed on /dev/loop3 Mar 30 02:01:51 Tower root: /var/lib/docker: 1.7 GiB (1846673408 bytes) trimmed on /dev/loop2 Mar 30 02:01:51 Tower root: /mnt/cache: 28 GiB (30114258944 bytes) trimmed on /dev/nvme0n1p1 Mar 30 02:02:31 Tower emhttpd: read SMART /dev/sdh Mar 30 02:02:44 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 02:02:51 Tower emhttpd: read SMART /dev/sde Mar 30 02:12:55 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 02:22:51 Tower emhttpd: spinning down /dev/sdc Mar 30 02:23:06 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 02:33:18 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 02:43:30 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 02:53:42 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 03:03:54 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 03:14:06 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 03:24:19 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 03:34:31 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 03:44:43 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 03:54:55 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 04:05:07 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 04:10:09 Tower emhttpd: spinning down /dev/sde Mar 30 04:10:10 Tower emhttpd: spinning down /dev/sdg Mar 30 04:15:20 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 04:25:32 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 04:32:25 Tower emhttpd: spinning down /dev/sdd Mar 30 04:35:44 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 04:40:01 Tower root: Fix Common Problems Version 2024.03.09 Mar 30 04:40:02 Tower root: Fix Common Problems: Warning: Plugin fix.common.problems.plg is not up to date Mar 30 04:40:02 Tower root: Fix Common Problems: Warning: Plugin user.scripts.plg is not up to date Mar 30 04:40:02 Tower root: Fix Common Problems: Warning: Docker Application transmission has an update available for it Mar 30 04:40:09 Tower root: Fix Common Problems: Warning: Syslog mirrored to flash Mar 30 04:40:09 Tower root: Fix Common Problems: Warning: Wrong DNS entry for host ** Ignored Mar 30 04:40:20 Tower emhttpd: read SMART /dev/sdc Mar 30 04:40:21 Tower emhttpd: read SMART /dev/sdg Mar 30 04:40:21 Tower emhttpd: read SMART /dev/sde Mar 30 04:40:21 Tower emhttpd: read SMART /dev/sdf Mar 30 04:40:31 Tower emhttpd: read SMART /dev/sdd Mar 30 04:45:56 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 04:56:09 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 04:56:44 Tower emhttpd: spinning down /dev/sde Mar 30 04:56:45 Tower emhttpd: spinning down /dev/sdg Mar 30 04:56:45 Tower emhttpd: spinning down /dev/sdf Mar 30 04:56:55 Tower emhttpd: spinning down /dev/sdd Mar 30 04:56:55 Tower emhttpd: spinning down /dev/sdc Mar 30 05:06:21 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 05:16:13 Tower emhttpd: spinning down /dev/sdi Mar 30 05:16:34 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 05:24:50 Tower emhttpd: spinning down /dev/sdh Mar 30 05:26:47 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 05:37:01 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 05:47:13 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 05:57:26 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 06:07:39 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 06:17:52 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 06:28:05 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 06:38:17 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 06:48:30 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 06:58:44 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 07:08:58 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 07:19:10 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 07:29:24 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 07:39:37 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 07:49:50 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 08:00:04 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 08:10:18 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 08:20:30 Tower apcupsd[3370]: Communications with UPS lost. Mar 30 08:30:43 Tower apcupsd[3370]: Communications with UPS lost. I uplugged the UPS on purpose because I have been trying to see if it runs better with certain things unplugged. It was crashing before & after I unplugged it so I know it's not the issue. Nothing indicating an issue here it seems. It just straight crashes Quote Link to comment
JorgeB Posted March 31 Share Posted March 31 Those do look to me more like a hardware issue. Quote Link to comment
JonathanM Posted March 31 Share Posted March 31 On 3/30/2024 at 1:43 PM, FreakyBigFoot said: I’m starting to think my CPU is bad. Garbled video like that could also be RAM. Quote Link to comment
FreakyBigFoot Posted April 1 Author Share Posted April 1 I’ve tested it with memtest86. Let it run for hours. Also purchased more RAM and did the same. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.