EagleEyes96

I've got the flash drive changed and it still crashes just as often it seems every time it crashes the last line is this on the logs Apr 19 08:23:38 unraid kernel: ata10.01: status: { DRDY } Apr 19 08:23:38 unraid kernel: ata10.15: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Apr 19 08:23:39 unraid kernel: ata10.00: SATA link down (SStatus 0 SControl 330) Apr 19 08:23:39 unraid kernel: ata10.01: hard resetting link Apr 19 08:23:39 unraid kernel: ata10.01: SATA link up 6.0 Gbps (SStatus 133 SControl 330) Apr 19 08:23:40 unraid kernel: ata10.02: SATA link up 6.0 Gbps (SStatus 133 SControl 330) Apr 19 08:23:40 unraid kernel: ata10.03: SATA link up 6.0 Gbps (SStatus 133 SControl 330) Apr 19 08:23:41 unraid kernel: ata10.04: SATA link up 6.0 Gbps (SStatus 133 SControl 330) Apr 19 08:23:41 unraid kernel: ata10.01: configured for UDMA/133 Apr 19 08:23:41 unraid kernel: ata10.02: configured for UDMA/133 Apr 19 08:23:41 unraid kernel: ata10.03: configured for UDMA/133 Apr 19 08:23:41 unraid kernel: ata10.04: configured for UDMA/133 Apr 19 08:23:41 unraid kernel: ata10: EH complete

This was the last codes i got before it crashed this last time if it helps Apr 18 12:00:17 unraid Parity Check Tuning: Send notification: mover running: (type=normal link=/Settings/Scheduler) Apr 18 12:00:19 unraid kernel: ata9.00: failed to read SCR 1 (Emask=0x40) Apr 18 12:00:19 unraid kernel: ata9.01: failed to read SCR 1 (Emask=0x40) Apr 18 12:00:19 unraid kernel: ata9.02: failed to read SCR 1 (Emask=0x40) Apr 18 12:00:19 unraid kernel: ata9.03: failed to read SCR 1 (Emask=0x40) Apr 18 12:00:19 unraid kernel: ata9.04: failed to read SCR 1 (Emask=0x40) Apr 18 12:00:19 unraid kernel: ata9.02: exception Emask 0x100 SAct 0x80000 SErr 0x0 action 0x6 frozen Apr 18 12:00:19 unraid kernel: ata9.02: failed command: READ FPDMA QUEUED Apr 18 12:00:19 unraid kernel: ata9.02: cmd 60/40:98:f8:fd:4f/05:00:7b:00:00/40 tag 19 ncq dma 688128 in Apr 18 12:00:19 unraid kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 18 12:00:19 unraid kernel: ata9.02: status: { DRDY } Apr 18 12:00:19 unraid kernel: ata9.15: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Apr 18 12:00:20 unraid kernel: ata9.00: SATA link down (SStatus 0 SControl 330) Apr 18 12:00:20 unraid kernel: ata9.01: SATA link down (SStatus 0 SControl 330) Apr 18 12:00:20 unraid kernel: ata9.02: hard resetting link Apr 18 12:00:20 unraid kernel: ata9.02: SATA link up 6.0 Gbps (SStatus 133 SControl 330) Apr 18 12:00:21 unraid kernel: ata9.03: SATA link up 6.0 Gbps (SStatus 133 SControl 330) Apr 18 12:00:21 unraid kernel: ata9.04: SATA link down (SStatus 0 SControl 330) Apr 18 12:00:21 unraid kernel: ata9.02: configured for UDMA/133 Apr 18 12:00:21 unraid kernel: ata9.03: configured for UDMA/133 Apr 18 12:00:21 unraid kernel: ata9: EH complete Apr 18 12:00:22 unraid kernel: mdcmd (46): nocheck PAUSE Apr 18 12:00:22 unraid kernel: Apr 18 12:00:22 unraid kernel: md: recovery thread: exit status: -4 Apr 18 12:00:32 unraid Parity Check Tuning: Send notification: Paused: Automatic Correcting Parity-Check (5.3% completed) (type=normal link=/Settings/Scheduler) Apr 18 12:06:25 unraid Parity Check Tuning: Send notification: mover no longer running: (type=normal link=/Settings/Scheduler) Apr 18 12:06:31 unraid kernel: mdcmd (47): check resume Apr 18 12:06:31 unraid kernel: Apr 18 12:06:31 unraid kernel: md: recovery thread: check P ... Apr 18 12:06:36 unraid Parity Check Tuning: Send notification: Resumed: Automatic Correcting Parity-Check (5.3% completed) (type=normal link=/Settings/Scheduler) Apr 18 12:51:00 unraid kernel: ata10.00: failed to read SCR 1 (Emask=0x40) Apr 18 12:51:00 unraid kernel: ata10.01: failed to read SCR 1 (Emask=0x40) Apr 18 12:51:00 unraid kernel: ata10.02: failed to read SCR 1 (Emask=0x40) Apr 18 12:51:00 unraid kernel: ata10.03: failed to read SCR 1 (Emask=0x40) Apr 18 12:51:00 unraid kernel: ata10.04: failed to read SCR 1 (Emask=0x40) Apr 18 12:51:00 unraid kernel: ata10.01: exception Emask 0x100 SAct 0xf8000 SErr 0x0 action 0x6 frozen Apr 18 12:51:00 unraid kernel: ata10.01: failed command: READ FPDMA QUEUED Apr 18 12:51:00 unraid kernel: ata10.01: cmd 60/40:78:78:e8:9b/05:00:82:00:00/40 tag 15 ncq dma 688128 in Apr 18 12:51:00 unraid kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 18 12:51:00 unraid kernel: ata10.01: status: { DRDY } Apr 18 12:51:00 unraid kernel: ata10.01: failed command: READ FPDMA QUEUED Apr 18 12:51:00 unraid kernel: ata10.01: cmd 60/40:80:b8:ed:9b/05:00:82:00:00/40 tag 16 ncq dma 688128 in Apr 18 12:51:00 unraid kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 18 12:51:00 unraid kernel: ata10.01: status: { DRDY } Apr 18 12:51:00 unraid kernel: ata10.01: failed command: READ FPDMA QUEUED Apr 18 12:51:00 unraid kernel: ata10.01: cmd 60/40:88:f8:f2:9b/05:00:82:00:00/40 tag 17 ncq dma 688128 in Apr 18 12:51:00 unraid kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 18 12:51:00 unraid kernel: ata10.01: status: { DRDY } Apr 18 12:51:00 unraid kernel: ata10.01: failed command: READ FPDMA QUEUED Apr 18 12:51:00 unraid kernel: ata10.01: cmd 60/40:90:38:f8:9b/05:00:82:00:00/40 tag 18 ncq dma 688128 in Apr 18 12:51:00 unraid kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 18 12:51:00 unraid kernel: ata10.01: status: { DRDY } Apr 18 12:51:00 unraid kernel: ata10.01: failed command: READ FPDMA QUEUED Apr 18 12:51:00 unraid kernel: ata10.01: cmd 60/c0:98:78:fd:9b/04:00:82:00:00/40 tag 19 ncq dma 622592 in Apr 18 12:51:00 unraid kernel: res 40/00:ff:81:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Apr 18 12:51:00 unraid kernel: ata10.01: status: { DRDY } Apr 18 12:51:00 unraid kernel: ata10.15: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Apr 18 12:51:00 unraid kernel: ata10.00: SATA link down (SStatus 0 SControl 330) Apr 18 12:51:00 unraid kernel: ata10.01: hard resetting link Apr 18 12:51:01 unraid kernel: ata10.01: SATA link up 6.0 Gbps (SStatus 133 SControl 330) Apr 18 12:51:01 unraid kernel: ata10.02: SATA link up 6.0 Gbps (SStatus 133 SControl 330) Apr 18 12:51:02 unraid kernel: ata10.03: SATA link up 6.0 Gbps (SStatus 133 SControl 330) Apr 18 12:51:02 unraid kernel: ata10.04: SATA link up 6.0 Gbps (SStatus 133 SControl 330) Apr 18 12:51:02 unraid kernel: ata10.01: configured for UDMA/133 Apr 18 12:51:02 unraid kernel: ata10.02: configured for UDMA/133 Apr 18 12:51:02 unraid kernel: ata10.03: configured for UDMA/133 Apr 18 12:51:03 unraid kernel: ata10.04: configured for UDMA/133 Apr 18 12:51:03 unraid kernel: ata10: EH complete syslog-192.168.1.172 (1).log

Somehow i got appdata to take to cache and its moving to it now super weird ill keep you updated

no problem i think the issue is in my cache i moved appdata off the cache and it worked for a While i moved it back and am getting this instead and then it changes from Appdata Array to Cache over to Cache to Array and doesn't want to let me change it back syslog-192.168.1.172.log

I’ll get a new flash drive and go ahead and do that then thanks! I’ll let you know how it goes

I will also not after it "Fixed" the usb it doesn't pop up with scan and repair anymore ill try it out and see what it does for anyone reading in the future!

Ran chkdsk on usb is this a sign i need to replace my usb? It had corrections to make and when I plug it into windows it always says scan and repair before it wants me to open it

Awesome thanks! i guess ill play around with it for a bit and see what i can find is there anything that normally stands out in this case after ram? im about to replace my cache drive to see what that does appreciate all the help as well!

UPDATE: It also crashes after having docker and Vms disabled or set to off

Also can a failing cache drive cause crashes like this? My scrutiny app is saying my cache failed it’s checks but it was like 13 ECC errors I think it said

Ruled this out I put in completely separate sticks from a well working pc and it crashed after about 3 hours its random between 3 hours to 1 day ish

so should i test one stick at a time for a couple days until it starts crashing? they all boot fine with 1 stick

The Ryzen 3900xt did the exact same thing but I did turn the system on with each ram stick individually to test it and ran the plugin to test my ram on unsaid and everything passed as well on it ran a couple passes on it no errors came back. Do you think I should test them all again? Or do you think it could be a issue that doesn’t show up immediately in the ram?

Here is a new one I just now grabbed unraid-diagnostics-20250411-0535.zip

So I have 2 sets of specs because it happens on my old machine I assumed it was hardware and I decided to update and rebuild the server anyways for fun so I was suprised when it still did it. machine 1 ryzen 3900xt 128gb ram asus tuf motherboard 1070 gpu 8gb bunch of hard drives and a 750 watt power supply. machine 2 intel 14900k 128gb ram gigabyte z790 bunch of hard drives 1200 watt psu as for docker containers there is a ton plex the arrs tautulli pterodactyl uptime kuma scrutiny all kinds of reverse proxy stuff overseer petio bunch more stuff too are you looking for something specific

Here you go! unraid-diagnostics-20250410-2050.zip

Finally got one right after it crashed! I noticed it said cache is full for a little before that but its supposed to be running mover to take it down to like 10% before building up to 60% then moving again or something like that. Other than that I'm not sure thanks for any pointers! syslog-192.168.1.172.log

Thanks I’ll get it set up and report back

Like the title says my system is randomly shutting down a couple times a day all new hardware except hard drives and ram is in it. im running a ram test now but didn't know if anything jumped out in the logs to someone smarter than me! Thanks for any help!!! unraid-syslog-20250408-2045.zip unraid-diagnostics-20250408-1538.zip