sutherlandm

Hello, I was messing around trying to get a stubborn GPU passed through to a VM, which resulted in full lockups of the web UI and terminal sessions. I had to press the physical reset button on two separate occasions to recover, shortly after the third boot and calling it for the day I received a Machine Check Events Detected in Fix Common Problems. I am not entirely sure what I am looking at, would someone more knowledgeable than I mind checking out the attached diagnostics? Thank you! picard-diagnostics-20230326-1710.zip

Ah alright, thank you! I have moved a few of the drives around so I'm not using any of the 4 Marvell ports. Out of curiosity, why is it best not to use them?

Hi All, I was warned through Fix Common Problems about a Call Trace error this morning, just wondering if someone could help me out to track down what is wrong. From the syslog it looks like the Call Trace came right after the following lines about CPU 5: May 11 21:41:06 Picard kernel: WARNING: CPU: 5 PID: 0 at net/sched/sch_generic.c:320 dev_watchdog+0x157/0x1b8 May 11 21:41:06 Picard kernel: CPU: 5 PID: 0 Comm: swapper/5 Not tainted 4.14.35-unRAID #1 May 11 21:41:06 Picard kernel: Call Trace: After that it goes on about "ata14" and "hard resetting link": May 13 13:45:00 Picard kernel: ata14.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 May 13 13:45:00 Picard kernel: ata14: hard resetting link May 13 13:45:00 Picard kernel: ata14.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 May 13 13:45:00 Picard kernel: ata14: hard resetting link I did notice some odd behavior with downloading docker updates and some of the communication between them lately, not sure if it's related. Any help would be greatly appreciated. Thank you! picard-diagnostics-20180513-1450.zip