threiner

Thanks for your help i have attached the diag

sure ere the diag is: tower-diagnostics-20240203-1747.zip

ok then i did nothing i should not do i think how can i fix this right issues ?

i just seen i use this filemanager

Thanks. So using the move function to move data from one drive to another can cause these problems? How do I fix this?

Can nobody tell me where to start searching for the problem?

no idea what this culd be ?

tower-diagnostics-20240131-2046.zip

My backup system started to behave very strangely; I get PCIe errors, and now two drives that are nearly new are disabled for errors. I have attached the log. I would really appreciate it if someone could point me in the right direction to fix this. Thanks!

Hi i have some issues I guess it's rightly related; I get access from Windows and the problem is that I can't overwrite some files. I have checked, and the owner is nobody, and there are 777 rights on the files. So I have no idea what is happening there. Also, I get some times that the files I copy to the share have 0 bytes, so I am very confused about what is happening there. thanks for the support

hab noch eine Frage da noch eine Platte disabeld ist, muss ich die wiederherstellen oder gibt es einen anderen weg auf der platte ist nix drauf die ist leer

Ich hab den Kontroller getauscht ohne Erfolg, alle SATA Verteiler auch ohne Erfolg, hab das Netzteil gegen ein 1000W Gold + ausgetauscht und probleme sind weg... leider aber durch das gnaze theater jetzt : Nov 12 14:56:01 Tower root: Fix Common Problems: Error: disk3 (ST8000DM004-2CX188_WCT375PV) has file system errors () kann ich das irgendwie korrigieren ohne die Platte zu formatieren?

I changed the power supply, and the errors disappeared.

i swap cabels and ports, the drive is also precleared without any issue... i am starting to think it could be an issue with the powersuply as the errors are quite random

tower-diagnostics-20231030-1616.zip

now i get this... Oct 30 16:14:37 Tower kernel: ata1: EH complete Oct 30 16:14:37 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x20000000 SErr 0x4890000 action 0xe frozen Oct 30 16:14:37 Tower kernel: ata1.00: irq_stat 0x0c400040, interface fatal error, connection status changed Oct 30 16:14:37 Tower kernel: ata1: SError: { PHYRdyChg 10B8B LinkSeq DevExch } Oct 30 16:14:37 Tower kernel: ata1.00: failed command: READ FPDMA QUEUED Oct 30 16:14:37 Tower kernel: ata1.00: cmd 60/40:e8:d8:1b:01/05:00:00:00:00/40 tag 29 ncq dma 688128 in Oct 30 16:14:37 Tower kernel: res 40/00:e8:d8:1b:01/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 16:14:37 Tower kernel: ata1.00: status: { DRDY } Oct 30 16:14:37 Tower kernel: ata1: hard resetting link Oct 30 16:14:43 Tower kernel: ata1: link is slow to respond, please be patient (ready=0) Oct 30 16:14:46 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Oct 30 16:14:46 Tower kernel: ata1.00: configured for UDMA/133 Oct 30 16:14:46 Tower kernel: ata1: EH complete Oct 30 16:14:46 Tower kernel: ata1: limiting SATA link speed to 1.5 Gbps Oct 30 16:14:46 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x600 SErr 0x4890000 action 0xe frozen Oct 30 16:14:46 Tower kernel: ata1.00: irq_stat 0x0c400040, interface fatal error, connection status changed Oct 30 16:14:46 Tower kernel: ata1: SError: { PHYRdyChg 10B8B LinkSeq DevExch } Oct 30 16:14:46 Tower kernel: ata1.00: failed command: READ FPDMA QUEUED Oct 30 16:14:46 Tower kernel: ata1.00: cmd 60/40:48:98:8b:01/05:00:00:00:00/40 tag 9 ncq dma 688128 in Oct 30 16:14:46 Tower kernel: res 40/00:48:98:8b:01/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 16:14:46 Tower kernel: ata1.00: status: { DRDY } Oct 30 16:14:46 Tower kernel: ata1.00: failed command: READ FPDMA QUEUED Oct 30 16:14:46 Tower kernel: ata1.00: cmd 60/80:50:d8:90:01/00:00:00:00:00/40 tag 10 ncq dma 65536 in Oct 30 16:14:46 Tower kernel: res 40/00:48:98:8b:01/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 16:14:46 Tower kernel: ata1.00: status: { DRDY } Oct 30 16:14:46 Tower kernel: ata1: hard resetting link

thank you can i find this also out allone? where do i need to look ?

sure tower-diagnostics-20231030-1423.zip

how do i find out what drive it is ?

jetzt habe ich den Kontroller zu einem SATA Cotroller getauscht und eine der Platten ausgetauscht die Unraid disabeld hatte und bekomme dieses Fehler... Wie kann ich den herausfinden um welche Platte es sich handelt ? Oct 30 11:49:34 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:49:34 Tower kernel: ata9.00: cmd 60/40:10:d8:de:03/05:00:00:00:00/40 tag 2 ncq dma 688128 in Oct 30 11:49:34 Tower kernel: res 40/00:58:d8:0f:05/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:49:34 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:49:34 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:49:34 Tower kernel: ata9.00: cmd 60/80:18:18:e4:03/00:00:00:00:00/40 tag 3 ncq dma 65536 in Oct 30 11:49:34 Tower kernel: res 40/00:58:d8:0f:05/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:49:34 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:49:34 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:49:34 Tower kernel: ata9.00: cmd 60/40:48:58:87:04/05:00:00:00:00/40 tag 9 ncq dma 688128 in Oct 30 11:49:34 Tower kernel: res 40/00:58:d8:0f:05/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:49:34 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:49:34 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:49:34 Tower kernel: ata9.00: cmd 60/40:f0:18:cf:03/05:00:00:00:00/40 tag 30 ncq dma 688128 in Oct 30 11:49:34 Tower kernel: res 40/00:58:d8:0f:05/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:49:34 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:49:34 Tower kernel: ata9: hard resetting link Oct 30 11:49:34 Tower kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 320) Oct 30 11:49:35 Tower kernel: ata9.00: configured for UDMA/133 Oct 30 11:49:35 Tower kernel: ata9: EH complete Oct 30 11:50:15 Tower kernel: ata9.00: exception Emask 0x10 SAct 0xc00400 SErr 0x4010000 action 0xe frozen Oct 30 11:50:15 Tower kernel: ata9.00: irq_stat 0x80400040, connection status changed Oct 30 11:50:15 Tower kernel: ata9: SError: { PHYRdyChg DevExch } Oct 30 11:50:15 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:50:15 Tower kernel: ata9.00: cmd 60/40:50:58:fa:05/05:00:00:00:00/40 tag 10 ncq dma 688128 in Oct 30 11:50:15 Tower kernel: res 40/00:60:d8:5b:06/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:50:15 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:50:15 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:50:15 Tower kernel: ata9.00: cmd 60/40:b0:d8:a4:05/05:00:00:00:00/40 tag 22 ncq dma 688128 in Oct 30 11:50:15 Tower kernel: res 40/00:60:d8:5b:06/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:50:15 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:50:15 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:50:15 Tower kernel: ata9.00: cmd 60/40:b8:18:aa:05/05:00:00:00:00/40 tag 23 ncq dma 688128 in Oct 30 11:50:15 Tower kernel: res 40/00:60:d8:5b:06/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:50:15 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:50:15 Tower kernel: ata9: hard resetting link Oct 30 11:50:16 Tower kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 320) Oct 30 11:50:16 Tower kernel: ata9.00: configured for UDMA/133 Oct 30 11:50:16 Tower kernel: ata9: EH complete Oct 30 11:50:47 Tower kernel: ata9: limiting SATA link speed to 1.5 Gbps Oct 30 11:50:47 Tower kernel: ata9.00: exception Emask 0x10 SAct 0x380280 SErr 0x4010000 action 0xe frozen Oct 30 11:50:47 Tower kernel: ata9.00: irq_stat 0x80400040, connection status changed Oct 30 11:50:47 Tower kernel: ata9: SError: { PHYRdyChg DevExch } Oct 30 11:50:47 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:50:47 Tower kernel: ata9.00: cmd 60/40:38:d8:86:06/05:00:00:00:00/40 tag 7 ncq dma 688128 in Oct 30 11:50:47 Tower kernel: res 40/00:00:d8:3c:07/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:50:47 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:50:47 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:50:47 Tower kernel: ata9.00: cmd 60/40:48:18:d7:06/05:00:00:00:00/40 tag 9 ncq dma 688128 in Oct 30 11:50:47 Tower kernel: res 40/00:00:d8:3c:07/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:50:47 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:50:47 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:50:47 Tower kernel: ata9.00: cmd 60/40:98:58:12:07/05:00:00:00:00/40 tag 19 ncq dma 688128 in Oct 30 11:50:47 Tower kernel: res 40/00:00:d8:3c:07/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:50:47 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:50:47 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:50:47 Tower kernel: ata9.00: cmd 60/40:a0:98:17:07/05:00:00:00:00/40 tag 20 ncq dma 688128 in Oct 30 11:50:47 Tower kernel: res 40/00:00:d8:3c:07/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:50:47 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:50:47 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:50:47 Tower kernel: ata9.00: cmd 60/80:a8:d8:1c:07/00:00:00:00:00/40 tag 21 ncq dma 65536 in Oct 30 11:50:47 Tower kernel: res 40/00:00:d8:3c:07/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:50:47 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:50:47 Tower kernel: ata9: hard resetting link Oct 30 11:50:48 Tower kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 310) Oct 30 11:50:48 Tower kernel: ata9.00: configured for UDMA/133 Oct 30 11:50:48 Tower kernel: ata9: EH complete Oct 30 11:51:20 Tower kernel: ata9.00: exception Emask 0x10 SAct 0xe400000 SErr 0x4010000 action 0xe frozen Oct 30 11:51:20 Tower kernel: ata9.00: irq_stat 0x80400040, connection status changed Oct 30 11:51:20 Tower kernel: ata9: SError: { PHYRdyChg DevExch } Oct 30 11:51:20 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:51:20 Tower kernel: ata9.00: cmd 60/40:b0:58:05:08/05:00:00:00:00/40 tag 22 ncq dma 688128 in Oct 30 11:51:20 Tower kernel: res 40/00:80:d8:63:08/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:51:20 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:51:20 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:51:20 Tower kernel: ata9.00: cmd 60/40:c8:58:7c:07/05:00:00:00:00/40 tag 25 ncq dma 688128 in Oct 30 11:51:20 Tower kernel: res 40/00:80:d8:63:08/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:51:20 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:51:20 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:51:20 Tower kernel: ata9.00: cmd 60/40:d0:98:81:07/05:00:00:00:00/40 tag 26 ncq dma 688128 in Oct 30 11:51:20 Tower kernel: res 40/00:80:d8:63:08/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:51:20 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:51:20 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:51:20 Tower kernel: ata9.00: cmd 60/80:d8:d8:86:07/00:00:00:00:00/40 tag 27 ncq dma 65536 in Oct 30 11:51:20 Tower kernel: res 40/00:80:d8:63:08/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:51:20 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:51:20 Tower kernel: ata9: hard resetting link Oct 30 11:51:21 Tower kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 310) Oct 30 11:51:21 Tower kernel: ata9.00: configured for UDMA/133 Oct 30 11:51:21 Tower kernel: ata9: EH complete

i get this error after replacing a drive Oct 30 11:49:34 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:49:34 Tower kernel: ata9.00: cmd 60/40:10:d8:de:03/05:00:00:00:00/40 tag 2 ncq dma 688128 in Oct 30 11:49:34 Tower kernel: res 40/00:58:d8:0f:05/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:49:34 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:49:34 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:49:34 Tower kernel: ata9.00: cmd 60/80:18:18:e4:03/00:00:00:00:00/40 tag 3 ncq dma 65536 in Oct 30 11:49:34 Tower kernel: res 40/00:58:d8:0f:05/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:49:34 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:49:34 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:49:34 Tower kernel: ata9.00: cmd 60/40:48:58:87:04/05:00:00:00:00/40 tag 9 ncq dma 688128 in Oct 30 11:49:34 Tower kernel: res 40/00:58:d8:0f:05/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:49:34 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:49:34 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:49:34 Tower kernel: ata9.00: cmd 60/40:f0:18:cf:03/05:00:00:00:00/40 tag 30 ncq dma 688128 in Oct 30 11:49:34 Tower kernel: res 40/00:58:d8:0f:05/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:49:34 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:49:34 Tower kernel: ata9: hard resetting link Oct 30 11:49:34 Tower kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 320) Oct 30 11:49:35 Tower kernel: ata9.00: configured for UDMA/133 Oct 30 11:49:35 Tower kernel: ata9: EH complete Oct 30 11:50:15 Tower kernel: ata9.00: exception Emask 0x10 SAct 0xc00400 SErr 0x4010000 action 0xe frozen Oct 30 11:50:15 Tower kernel: ata9.00: irq_stat 0x80400040, connection status changed Oct 30 11:50:15 Tower kernel: ata9: SError: { PHYRdyChg DevExch } Oct 30 11:50:15 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:50:15 Tower kernel: ata9.00: cmd 60/40:50:58:fa:05/05:00:00:00:00/40 tag 10 ncq dma 688128 in Oct 30 11:50:15 Tower kernel: res 40/00:60:d8:5b:06/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:50:15 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:50:15 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:50:15 Tower kernel: ata9.00: cmd 60/40:b0:d8:a4:05/05:00:00:00:00/40 tag 22 ncq dma 688128 in Oct 30 11:50:15 Tower kernel: res 40/00:60:d8:5b:06/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:50:15 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:50:15 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:50:15 Tower kernel: ata9.00: cmd 60/40:b8:18:aa:05/05:00:00:00:00/40 tag 23 ncq dma 688128 in Oct 30 11:50:15 Tower kernel: res 40/00:60:d8:5b:06/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:50:15 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:50:15 Tower kernel: ata9: hard resetting link Oct 30 11:50:16 Tower kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 320) Oct 30 11:50:16 Tower kernel: ata9.00: configured for UDMA/133 Oct 30 11:50:16 Tower kernel: ata9: EH complete Oct 30 11:50:47 Tower kernel: ata9: limiting SATA link speed to 1.5 Gbps Oct 30 11:50:47 Tower kernel: ata9.00: exception Emask 0x10 SAct 0x380280 SErr 0x4010000 action 0xe frozen Oct 30 11:50:47 Tower kernel: ata9.00: irq_stat 0x80400040, connection status changed Oct 30 11:50:47 Tower kernel: ata9: SError: { PHYRdyChg DevExch } Oct 30 11:50:47 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:50:47 Tower kernel: ata9.00: cmd 60/40:38:d8:86:06/05:00:00:00:00/40 tag 7 ncq dma 688128 in Oct 30 11:50:47 Tower kernel: res 40/00:00:d8:3c:07/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:50:47 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:50:47 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:50:47 Tower kernel: ata9.00: cmd 60/40:48:18:d7:06/05:00:00:00:00/40 tag 9 ncq dma 688128 in Oct 30 11:50:47 Tower kernel: res 40/00:00:d8:3c:07/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:50:47 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:50:47 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:50:47 Tower kernel: ata9.00: cmd 60/40:98:58:12:07/05:00:00:00:00/40 tag 19 ncq dma 688128 in Oct 30 11:50:47 Tower kernel: res 40/00:00:d8:3c:07/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:50:47 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:50:47 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:50:47 Tower kernel: ata9.00: cmd 60/40:a0:98:17:07/05:00:00:00:00/40 tag 20 ncq dma 688128 in Oct 30 11:50:47 Tower kernel: res 40/00:00:d8:3c:07/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:50:47 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:50:47 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:50:47 Tower kernel: ata9.00: cmd 60/80:a8:d8:1c:07/00:00:00:00:00/40 tag 21 ncq dma 65536 in Oct 30 11:50:47 Tower kernel: res 40/00:00:d8:3c:07/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:50:47 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:50:47 Tower kernel: ata9: hard resetting link Oct 30 11:50:48 Tower kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 310) Oct 30 11:50:48 Tower kernel: ata9.00: configured for UDMA/133 Oct 30 11:50:48 Tower kernel: ata9: EH complete Oct 30 11:51:20 Tower kernel: ata9.00: exception Emask 0x10 SAct 0xe400000 SErr 0x4010000 action 0xe frozen Oct 30 11:51:20 Tower kernel: ata9.00: irq_stat 0x80400040, connection status changed Oct 30 11:51:20 Tower kernel: ata9: SError: { PHYRdyChg DevExch } Oct 30 11:51:20 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:51:20 Tower kernel: ata9.00: cmd 60/40:b0:58:05:08/05:00:00:00:00/40 tag 22 ncq dma 688128 in Oct 30 11:51:20 Tower kernel: res 40/00:80:d8:63:08/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:51:20 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:51:20 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:51:20 Tower kernel: ata9.00: cmd 60/40:c8:58:7c:07/05:00:00:00:00/40 tag 25 ncq dma 688128 in Oct 30 11:51:20 Tower kernel: res 40/00:80:d8:63:08/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:51:20 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:51:20 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:51:20 Tower kernel: ata9.00: cmd 60/40:d0:98:81:07/05:00:00:00:00/40 tag 26 ncq dma 688128 in Oct 30 11:51:20 Tower kernel: res 40/00:80:d8:63:08/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:51:20 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:51:20 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Oct 30 11:51:20 Tower kernel: ata9.00: cmd 60/80:d8:d8:86:07/00:00:00:00:00/40 tag 27 ncq dma 65536 in Oct 30 11:51:20 Tower kernel: res 40/00:80:d8:63:08/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 30 11:51:20 Tower kernel: ata9.00: status: { DRDY } Oct 30 11:51:20 Tower kernel: ata9: hard resetting link Oct 30 11:51:21 Tower kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 310) Oct 30 11:51:21 Tower kernel: ata9.00: configured for UDMA/133 Oct 30 11:51:21 Tower kernel: ata9: EH complete

ich hab jetzt mal den Cotroller ausgetauscht und das netzteil auch im moment läuft es problemlos. Der HBA ist ein DELL und ist aktiv gekühlt der bleibt immer unter 40 grad constant es hat ja auch über zwei Jahre problemlos funktioniert. Ich habe ein 650 W netzteil gehabt jetzt ein 850er ich kann mir nur vorstellen das durch die 4 zusätzlichen platten eventuell das Netzteil an seine grenzen gestossen ist. Ich werde da smal in meinen zweiten System mit den SAS platten mal testen wie die controller da funktionieren.

niemand eine idee?

gerade fängt es wieder an... ich wollte die beiden deaktivierten Platten einzeln wieder herstellen und dann passiert das: Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293280 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293288 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293296 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293304 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293312 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293320 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293328 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293336 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293344 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293352 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293360 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293368 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293376 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293384 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293392 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293400 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293408 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293416 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293424 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293432 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293440 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293448 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293456 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293464 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293472 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293480 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293488 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293496 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293504 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293512 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293520 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293528 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293536 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293544 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293552 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293560 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293568 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293576 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293584 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293592 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293600 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293608 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293616 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293624 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293632 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293640 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293648 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293656 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293664 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293672 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293680 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293688 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293696 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293704 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293712 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293720 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293728 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293736 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293744 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293752 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293760 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293768 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293776 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293784 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293792 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293800 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293808 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293816 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293824 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293832 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293840 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293848 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293856 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293864 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293872 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293880 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293888 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293896 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293904 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293912 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293920 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293928 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293936 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293944 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293952 Sep 27 03:16:20 Tower kernel: md: disk3 read error, sector=3293960 Sep 27 03:16:20 Tower kernel: sd 8:0:1:0: Power-on or device reset occurred Sep 27 03:16:21 Tower kernel: sd 8:0:1:0: Power-on or device reset occurred tower-diagnostics-20230927-0324.zip

I found the Solution, there was for some reason more then one key on the USB Stick. I guess this is a bug, no idea how this can happen. as the Trail key is normal to have, i thought it get deleted after i purchased a license. ok a new thing to know