-
[Support] GridcoinWalletGUI
Could be related to this: https://www.reddit.com/r/gridcoin/comments/1u0qsqp/emergency_5510_hotfix_release/
-
[Support] GridcoinWalletGUI
I was finally able to open the file. It crashes at line 117 which is the call to gridcoinresearch. The logs in /dockerstartup/vnc_startup.log do not give any useful information.
-
[Support] GridcoinWalletGUI
I am having the exact same issue. Nothing changed other than being on Unraid 7.3.1. I tried to look at /dockerstartup/vnc_startup.sh inside the container, but the container crashes too quickly for me to get to the script. Having a public repository would really help in this case.
-
[Support] GridcoinWalletGUI
Do you have a public repo somewhere? I can probably take care of of update
-
Random full system crash with no apparent cause
So here's a final update. All my issues were caused by a failing PSU. The server crashed in the same way as before, but that time it did not boot back up. The fans would "twitch" when powering on (had to toggle the PSU switch before) but nothing else. I was able to use a spare PSU to confirm that was the issue before buying a new power supply. It has now been almost 20 days since the last crash, with no sign of issues. Thank you all for your help resolving this!
-
Random full system crash with no apparent cause
Someone on the LTT forums suggested removing one of the RAM stick and see what happens. The first RAM made it crash 3 times in 6 hours. With the second, only 1 crash since the 26th. I'll continue testing that for a few more days and do a few more swaps to confirm.
-
Random full system crash with no apparent cause
Could this issue cause/contribute to the crashes I am seeing?
-
Random full system crash with no apparent cause
Yeah it happened after I generated the file Here's a new one birdskeep-diagnostics-20241023-0911.zip
-
Random full system crash with no apparent cause
This might have something to do with it... Oct 23 09:04:16 BirdsKeep kernel: ata4: SATA link down (SStatus 0 SControl 300) Oct 23 09:04:17 BirdsKeep kernel: ata4: SATA link down (SStatus 0 SControl 300) Oct 23 09:04:17 BirdsKeep kernel: ata4: limiting SATA link speed to <unknown> Oct 23 09:04:20 BirdsKeep kernel: ata4: SATA link down (SStatus 0 SControl 3F0) Oct 23 09:04:20 BirdsKeep kernel: ata4.00: disable device Oct 23 09:04:20 BirdsKeep kernel: usb 1-2.3: USB disconnect, device number 78 Oct 23 09:04:20 BirdsKeep kernel: usb 1-2.3: new low-speed USB device number 79 using xhci_hcd Oct 23 09:04:21 BirdsKeep kernel: hid-generic 0003:09AE:2012.0137: hiddev96,hidraw1: USB HID v1.10 Device [Tripp Lite Tripp Lite UPS ] on usb-0000:00:14.0-2.3/input0 Oct 23 09:04:21 BirdsKeep kernel: ata4: SATA link down (SStatus 0 SControl 300) Oct 23 09:04:21 BirdsKeep kernel: ata4.00: detaching (SCSI 4:0:0:0) Oct 23 09:04:21 BirdsKeep kernel: sd 4:0:0:0: [sde] Synchronizing SCSI cache Oct 23 09:04:21 BirdsKeep kernel: sd 4:0:0:0: [sde] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK Oct 23 09:04:22 BirdsKeep kernel: ata4: limiting SATA link speed to 1.5 Gbps Oct 23 09:04:27 BirdsKeep kernel: ata4: link is slow to respond, please be patient (ready=0) Oct 23 09:04:28 BirdsKeep kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Oct 23 09:04:28 BirdsKeep kernel: ata4.00: ATA-10: WDC WD80EFPX-68C4ZN0, 81.00A81, max UDMA/133 Oct 23 09:04:28 BirdsKeep kernel: ata4.00: 15628053168 sectors, multi 16: LBA48 NCQ (depth 32), AA Oct 23 09:04:28 BirdsKeep kernel: ata4.00: Features: NCQ-prio Oct 23 09:04:28 BirdsKeep kernel: ata4.00: configured for UDMA/133 Oct 23 09:04:28 BirdsKeep kernel: scsi 4:0:0:0: Direct-Access ATA WDC WD80EFPX-68C 0A81 PQ: 0 ANSI: 5 Oct 23 09:04:28 BirdsKeep kernel: sd 4:0:0:0: Attached scsi generic sg4 type 0 Oct 23 09:04:28 BirdsKeep kernel: sd 4:0:0:0: [sdk] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB) Oct 23 09:04:28 BirdsKeep kernel: sd 4:0:0:0: [sdk] 4096-byte physical blocks Oct 23 09:04:28 BirdsKeep kernel: sd 4:0:0:0: [sdk] Write Protect is off Oct 23 09:04:28 BirdsKeep kernel: sd 4:0:0:0: [sdk] Mode Sense: 00 3a 00 00 Oct 23 09:04:28 BirdsKeep kernel: sd 4:0:0:0: [sdk] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 23 09:04:28 BirdsKeep kernel: sd 4:0:0:0: [sdk] Preferred minimum I/O size 4096 bytes Oct 23 09:04:28 BirdsKeep kernel: sdk: sdk1 Oct 23 09:04:28 BirdsKeep kernel: sd 4:0:0:0: [sdk] Attached SCSI disk Oct 23 09:04:29 BirdsKeep unassigned.devices: Disk with ID 'WDC_WD80EFPX-68C4ZN0_WD-RD04BPDE (dev1)' is not set to auto mount.
-
Random full system crash with no apparent cause
-
Random full system crash with no apparent cause
Crashed again this morning, this time it took down Disk 1. Is there information somewhere that can tell me why the disk was disabled? It's the second time this has happened to that disk since I replaced it. I tried running an extended self-test, but it stops before completing without errors birdskeep-diagnostics-20241023-0900.zip
-
Random full system crash with no apparent cause
Ill take a look, the only usb devices I have is the USB drive and a UPS Weird, I thought it did that automatically. I reduced the size from 100mb to 5mb
-
Random full system crash with no apparent cause
You can't make this up... I was writing an update to let the world know that the issue seems to be fixed after replacing the CPU (Intel 13th gen RMA), but it crashed again after almost 8 days of uptime. I've attached my diagnostics.zip file. The only thing I notice in the logs is that one SSD is having trouble to trim and that there is around 5 minutes of missing log before the restart (server takes at most 1 minute to boot) birdskeep-diagnostics-20241021-0831.zip birdskeep-syslog-10.10.10.40-20241021-1236.zip
-
Random full system crash with no apparent cause
I received a replacement drive, and the server crashed when rebuilding the array and will not post anymore. I unplugged the new drive and the server is able to post again. I am starting to believe all this is caused by the 600W psu, including the random crashes. The new drive has a higer power load (WD40EFRX vs WD80EFPX) Hopefully the crash during the rebuild wont cause more problems.
-
Random full system crash with no apparent cause
Here's everything for today. The crash recovered around 11:45 (line 94) For reference, here's the syslog configuration: syslog-10.10.10.40.log
TheBird956
Members
-
Joined
-
Last visited