On 4/13/2025 at 10:59 AM, trurl said:

You will have to do a license transfer in that case.

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

2 minutes ago, EagleEyes96 said:

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 1.65 MB · 0 downloads

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

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

Controllers with SATA port multipliers are not recommended, though they don't typically crash a server, but can make it look unresponsive for a few seconds.

On 4/13/2025 at 10:59 AM, trurl said:

You will have to do a license transfer in that case.

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