crazyfrenchman

Yes all docker started all looks good Thanks done via PP Really a huge thanks !!!! 3> Jerome

Dear @JorgeB, Rebuild and filesystem checks are done. I have no error detected in my logs, array is started with all the disk OK and I have all my shares again. I will start my dockers soon. How can I thank you ? Really a very big thanks to you 3> Best regards Jerome unraid-diagnostics-20241125-1853 - after rebuild and filesystem check.zip

I am running it right now after I have done a Sync to try to restore disk 6 I have a lot of lines like Nov 25 18:27:43 Unraid emhttpd: error: malloc_share_locations, 7200: Operation not supported (95): getxattr: /mnt/user/documents Nov 25 18:27:44 Unraid emhttpd: error: malloc_share_locations, 7200: Operation not supported (95): getxattr: /mnt/user/backupnew only on these 2 directories, the good points is that sub directory documentsI have all the data on my PC HDD and backupnew are backup of Minecraft, etc .. When the file system check is finished I let you know

I move a power cable from ssd to a hdd, then use the left over power cable from hdd to put it in the ssd I have attached the diag after starting the server and the array. It seems to me that so far only disk 6 is in error which is fine I can rebuild it from my parity drive then when it is done rebuild parity 2 also Can you confirm I don't want to mess it up Really big thanks to help me all along @JorgeB 3> 3> unraid-diagnostics-20241124-1656 - after switch power cable.zip

Do you think I can try to split my Y power cables between SDD and HDD that will help ?

If you mean by splitter Y cable for power I have some as I have 10 disks in my PC and not direct output cable from my power supply. My power supply is 550 Watt Bronze. What do you want me to do now ?, do you think my array is dead ?

Hello again, I have switched the cables 2 by 2 from the disk side but din't change them on the controler side. I have attached the diag after I started the array At the time I stopped the array and waiting for instructions. ATA10 is my parity disk and ATA7 is my 2nd parity disk but not mounted in the arrat (so my old 2nd parity disk before problem appears including touching it) I would like to thanks you very much @JorgeB for all the time and effort you put in order to help me and save my array. Jerome unraid-diagnostics-20241124-1326.zip

OK I do that right now I will switch cable 2 by 2 as I do not know which is disk 5, 6 etc ...

OK I receive my new SATA controler with Chipset ASM1064 and put it on my x1 free port. I have also changed all SATA cables to each of the disks (so 4 disks and 4 SATA cables) I have attached diagnostic before and after array is started. I still have FPDMA errors on disk 5 and disk 6 has I/O errors. What are your advices please and do have I lost my array 😞 I am waiting for your replies and hopefully solutions. unraid-diagnostics-20241124-1204 - after array started.zip unraid-diagnostics-20241124-1202 - before array start.zip

OK it seems I have the same problem as @SieyS, I will order a JMB585 (instead of the Marvell chipset I receive today) from CDiscount also. Thanks for this thread. Thanks to you all specialy @JorgeB for all his precious advices. So the time being my server remain off line 😞

OK then I will do that. At the moment the server is powered off so I leave it as it is until I have the new controler. Before I power it back on I will change the parity disk to the controler on the mother board and leave the second SSD (cache pro has 2 SDD) not connected for the time being. I will report back to you when I will power it up again. Thanks for the advices 🙂

I really hope so. I was think on changing my parity disk to one of the mother board controler and have Cache Pro with only 1 SSD and not two for the time being. Is it a good idea ? My hope is my parity disk will have no error reading and when I receive the new contoller put disk 5 and 6 on them (the new controler)

Do you think I lost my array and all the movie etc... or can I still save it ?

Does that mean it won't work 😞

I look for it in French and in English from the model number (SA3004) and it seems to be an ASM1061 from ASMEDIA (http://www.evisionde.com/prodetail.aspx?ProID=92)

OK I ordered 2 cards with 4 SATA (https://www.cdiscount.com/informatique/composants-informatiques/hum-pcie-a-sata-adaptateur-pcie-vers-sata-carte-a/f-1071311-sjl1712567206792.html) instead of 8. I hope it will be OK I am waiting for them during this time I shut down the server

After reboot of the server the 2 disks (5 and 6 ) are back on their slot. I didn't start the array I am waiting for instructions. After few minutes I got a lot of Nov 15 14:09:11 Unraid kernel: ata51: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 15 14:09:11 Unraid kernel: ata51.00: configured for UDMA/133 Nov 15 14:12:11 Unraid kernel: ata51: limiting SATA link speed to 3.0 Gbps Nov 15 14:12:11 Unraid kernel: ata51: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Nov 15 14:12:12 Unraid kernel: ata51.00: configured for UDMA/133 Nov 15 14:15:12 Unraid kernel: ata51: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Nov 15 14:15:12 Unraid kernel: ata51.00: configured for UDMA/133 Nov 15 14:17:11 Unraid kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 15 14:17:11 Unraid kernel: ata9.00: configured for UDMA/133 Nov 15 14:18:12 Unraid kernel: ata51: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Nov 15 14:18:12 Unraid kernel: ata51.00: configured for UDMA/133 Nov 15 14:19:12 Unraid kernel: ata51: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Nov 15 14:19:12 Unraid kernel: ata51.00: configured for UDMA/133 Nov 15 14:21:10 Unraid kernel: ata9.00: exception Emask 0x10 SAct 0x1000 SErr 0x4010000 action 0xe frozen Nov 15 14:21:10 Unraid kernel: ata9.00: irq_stat 0x80400040, connection status changed Nov 15 14:21:10 Unraid kernel: ata9: SError: { PHYRdyChg DevExch } Nov 15 14:21:10 Unraid kernel: ata9.00: failed command: READ FPDMA QUEUED Nov 15 14:21:10 Unraid kernel: ata9.00: cmd 60/20:60:08:00:00/00:00:00:00:00/40 tag 12 ncq dma 16384 in Nov 15 14:21:10 Unraid kernel: res 50/01:01:01:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error) Nov 15 14:21:10 Unraid kernel: ata9.00: status: { DRDY } Nov 15 14:21:10 Unraid kernel: ata9.00: error: { AMNF } Nov 15 14:21:10 Unraid kernel: ata9: hard resetting link Nov 15 14:21:11 Unraid kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 15 14:21:11 Unraid kernel: ata9.00: configured for UDMA/133 Nov 15 14:21:11 Unraid kernel: sd 9:0:0:0: [sdh] tag#12 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=9s Nov 15 14:21:11 Unraid kernel: sd 9:0:0:0: [sdh] tag#12 Sense Key : 0x3 [current] Nov 15 14:21:11 Unraid kernel: sd 9:0:0:0: [sdh] tag#12 ASC=0x13 ASCQ=0x0 Nov 15 14:21:11 Unraid kernel: sd 9:0:0:0: [sdh] tag#12 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 08 00 00 00 20 00 00 Nov 15 14:21:11 Unraid kernel: I/O error, dev sdh, sector 8 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 2 Nov 15 14:21:11 Unraid kernel: ata9: EH complete Nov 15 14:24:11 Unraid kernel: ata51: limiting SATA link speed to 1.5 Gbps Nov 15 14:24:12 Unraid kernel: ata51: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Nov 15 14:24:12 Unraid kernel: ata51.00: configured for UDMA/133 Nov 15 14:27:11 Unraid kernel: ata51: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Nov 15 14:27:11 Unraid kernel: ata51.00: configured for UDMA/133 Nov 15 14:29:11 Unraid kernel: ata9.00: exception Emask 0x10 SAct 0x40000 SErr 0x4010000 action 0xe frozen Nov 15 14:29:11 Unraid kernel: ata9.00: irq_stat 0x80400040, connection status changed Nov 15 14:29:11 Unraid kernel: ata9: SError: { PHYRdyChg DevExch } Nov 15 14:29:11 Unraid kernel: ata9.00: failed command: READ FPDMA QUEUED Nov 15 14:29:11 Unraid kernel: ata9.00: cmd 60/20:90:08:00:00/00:00:00:00:00/40 tag 18 ncq dma 16384 in Nov 15 14:29:11 Unraid kernel: res 50/01:01:01:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error) Nov 15 14:29:11 Unraid kernel: ata9.00: status: { DRDY } Nov 15 14:29:11 Unraid kernel: ata9.00: error: { AMNF } Nov 15 14:29:11 Unraid kernel: ata9: hard resetting link Nov 15 14:29:11 Unraid kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 15 14:29:12 Unraid kernel: ata9.00: configured for UDMA/133 Nov 15 14:29:12 Unraid kernel: sd 9:0:0:0: [sdh] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=9s Nov 15 14:29:12 Unraid kernel: sd 9:0:0:0: [sdh] tag#18 Sense Key : 0x3 [current] Nov 15 14:29:12 Unraid kernel: sd 9:0:0:0: [sdh] tag#18 ASC=0x13 ASCQ=0x0 Nov 15 14:29:12 Unraid kernel: sd 9:0:0:0: [sdh] tag#18 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 08 00 00 00 20 00 00 Nov 15 14:29:12 Unraid kernel: I/O error, dev sdh, sector 8 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 2 Nov 15 14:29:12 Unraid kernel: ata9: EH complete Nov 15 14:30:11 Unraid kernel: ata9.00: exception Emask 0x10 SAct 0x8000 SErr 0x4010000 action 0xe frozen Nov 15 14:30:11 Unraid kernel: ata9.00: irq_stat 0x80400040, connection status changed Nov 15 14:30:11 Unraid kernel: ata9: SError: { PHYRdyChg DevExch } Nov 15 14:30:11 Unraid kernel: ata9.00: failed command: READ FPDMA QUEUED Nov 15 14:30:11 Unraid kernel: ata9.00: cmd 60/f8:78:48:01:00/00:00:00:00:00/40 tag 15 ncq dma 126976 in Nov 15 14:30:11 Unraid kernel: res 50/01:01:01:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error) Nov 15 14:30:11 Unraid kernel: ata9.00: status: { DRDY } Nov 15 14:30:11 Unraid kernel: ata9.00: error: { AMNF } Nov 15 14:30:11 Unraid kernel: ata9: hard resetting link Nov 15 14:30:11 Unraid kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 15 14:30:11 Unraid kernel: ata9.00: configured for UDMA/133 Nov 15 14:30:11 Unraid kernel: sd 9:0:0:0: [sdh] tag#15 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=9s Nov 15 14:30:11 Unraid kernel: sd 9:0:0:0: [sdh] tag#15 Sense Key : 0x3 [current] Nov 15 14:30:11 Unraid kernel: sd 9:0:0:0: [sdh] tag#15 ASC=0x13 ASCQ=0x0 Nov 15 14:30:11 Unraid kernel: sd 9:0:0:0: [sdh] tag#15 CDB: opcode=0x88 88 00 00 00 00 00 00 00 01 48 00 00 00 f8 00 00 Nov 15 14:30:11 Unraid kernel: I/O error, dev sdh, sector 328 op 0x0:(READ) flags 0x80700 phys_seg 10 prio class 2 Nov 15 14:30:11 Unraid kernel: ata9: EH complete Nov 15 14:30:23 Unraid kernel: ata9: limiting SATA link speed to 3.0 Gbps Nov 15 14:30:23 Unraid kernel: ata9.00: exception Emask 0x10 SAct 0x8000000 SErr 0x4010000 action 0xe frozen Nov 15 14:30:23 Unraid kernel: ata9.00: irq_stat 0x80400040, connection status changed Nov 15 14:30:23 Unraid kernel: ata9: SError: { PHYRdyChg DevExch } Nov 15 14:30:23 Unraid kernel: ata9.00: failed command: READ FPDMA QUEUED Nov 15 14:30:23 Unraid kernel: ata9.00: cmd 60/00:d8:40:26:81/02:00:a3:03:00/40 tag 27 ncq dma 262144 in Nov 15 14:30:23 Unraid kernel: res 50/01:01:01:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error) Nov 15 14:30:23 Unraid kernel: ata9.00: status: { DRDY } Nov 15 14:30:23 Unraid kernel: ata9.00: error: { AMNF } Nov 15 14:30:23 Unraid kernel: ata9: hard resetting link Nov 15 14:30:23 Unraid kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 320) Nov 15 14:30:23 Unraid kernel: ata9.00: configured for UDMA/133 Nov 15 14:30:23 Unraid kernel: sd 9:0:0:0: [sdh] tag#27 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=11s Nov 15 14:30:23 Unraid kernel: sd 9:0:0:0: [sdh] tag#27 Sense Key : 0x3 [current] Nov 15 14:30:23 Unraid kernel: sd 9:0:0:0: [sdh] tag#27 ASC=0x13 ASCQ=0x0 Nov 15 14:30:23 Unraid kernel: sd 9:0:0:0: [sdh] tag#27 CDB: opcode=0x88 88 00 00 00 00 03 a3 81 26 40 00 00 02 00 00 00 Nov 15 14:30:23 Unraid kernel: I/O error, dev sdh, sector 15628052032 op 0x0:(READ) flags 0x80700 phys_seg 64 prio class 2 Nov 15 14:30:23 Unraid kernel: ata9: EH complete

Each have 8 ports 2 on the top and 6 on the side with 2 on top of each other so 2x3

I just lost disk 5 and 6 .... missing ... here the log 😞 Nov 15 13:54:11 Unraid kernel: ata51: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Nov 15 13:54:12 Unraid kernel: ata51.00: configured for UDMA/33 Nov 15 13:56:11 Unraid kernel: ata51: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Nov 15 13:56:11 Unraid kernel: ata51.00: configured for UDMA/33 Nov 15 13:59:31 Unraid kernel: ata9.00: exception Emask 0x0 SAct 0x20 SErr 0x0 action 0x6 frozen Nov 15 13:59:31 Unraid kernel: ata9.00: failed command: READ FPDMA QUEUED Nov 15 13:59:31 Unraid kernel: ata9.00: cmd 60/f8:28:48:02:00/01:00:00:00:00/40 tag 5 ncq dma 258048 in Nov 15 13:59:31 Unraid kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Nov 15 13:59:31 Unraid kernel: ata9.00: status: { DRDY } Nov 15 13:59:31 Unraid kernel: ata9: hard resetting link Nov 15 13:59:37 Unraid kernel: ata9: link is slow to respond, please be patient (ready=0) Nov 15 13:59:38 Unraid kernel: ata51: link is slow to respond, please be patient (ready=0) Nov 15 13:59:41 Unraid kernel: ata9: COMRESET failed (errno=-16) Nov 15 13:59:41 Unraid kernel: ata9: hard resetting link Nov 15 13:59:43 Unraid kernel: ata51: COMRESET failed (errno=-16) Nov 15 13:59:46 Unraid kernel: ata9: found unknown device (class 0) Nov 15 13:59:46 Unraid kernel: ata9: SATA link down (SStatus 0 SControl 310) Nov 15 13:59:47 Unraid kernel: ata9: hard resetting link Nov 15 13:59:47 Unraid kernel: ata9: SATA link down (SStatus 0 SControl 310) Nov 15 13:59:48 Unraid kernel: ata51: link is slow to respond, please be patient (ready=0) Nov 15 13:59:52 Unraid kernel: ata9: hard resetting link Nov 15 13:59:53 Unraid kernel: ata9: SATA link down (SStatus 0 SControl 310) Nov 15 13:59:53 Unraid kernel: ata9.00: disable device Nov 15 13:59:53 Unraid kernel: ata51: COMRESET failed (errno=-16) Nov 15 13:59:53 Unraid kernel: ata23: SATA link down (SStatus 0 SControl 300) Nov 15 13:59:53 Unraid kernel: ata9: SATA link down (SStatus 0 SControl 300) Nov 15 13:59:53 Unraid kernel: sd 9:0:0:0: [sdh] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=52s Nov 15 13:59:53 Unraid kernel: sd 9:0:0:0: [sdh] tag#5 Sense Key : 0x2 [current] Nov 15 13:59:53 Unraid kernel: sd 9:0:0:0: [sdh] tag#5 ASC=0x4 ASCQ=0x21 Nov 15 13:59:53 Unraid kernel: sd 9:0:0:0: [sdh] tag#5 CDB: opcode=0x88 88 00 00 00 00 00 00 00 02 48 00 00 01 f8 00 00 Nov 15 13:59:53 Unraid kernel: I/O error, dev sdh, sector 584 op 0x0:(READ) flags 0x80700 phys_seg 63 prio class 2 Nov 15 13:59:53 Unraid kernel: ata9: EH complete Nov 15 13:59:53 Unraid kernel: ata9.00: detaching (SCSI 9:0:0:0) Nov 15 13:59:53 Unraid kernel: device offline error, dev sdh, sector 584 op 0x0:(READ) flags 0x0 phys_seg 8 prio class 2 Nov 15 13:59:53 Unraid kernel: Buffer I/O error on dev sdh1, logical block 520, async page read Nov 15 13:59:53 Unraid kernel: Buffer I/O error on dev sdh1, logical block 521, async page read Nov 15 13:59:53 Unraid kernel: Buffer I/O error on dev sdh1, logical block 522, async page read Nov 15 13:59:53 Unraid kernel: Buffer I/O error on dev sdh1, logical block 523, async page read Nov 15 13:59:53 Unraid kernel: Buffer I/O error on dev sdh1, logical block 524, async page read Nov 15 13:59:53 Unraid kernel: Buffer I/O error on dev sdh1, logical block 525, async page read Nov 15 13:59:53 Unraid kernel: Buffer I/O error on dev sdh1, logical block 526, async page read Nov 15 13:59:53 Unraid kernel: Buffer I/O error on dev sdh1, logical block 527, async page read Nov 15 13:59:53 Unraid kernel: sd 9:0:0:0: [sdh] Synchronizing SCSI cache Nov 15 13:59:53 Unraid kernel: sd 9:0:0:0: [sdh] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK Nov 15 13:59:57 Unraid kernel: ata24: SATA link down (SStatus 0 SControl 300) Nov 15 13:59:59 Unraid kernel: ata51: link is slow to respond, please be patient (ready=0) Nov 15 14:00:01 Unraid kernel: ata25: SATA link down (SStatus 0 SControl 300) Nov 15 14:00:04 Unraid kernel: ata51: found unknown device (class 0) Nov 15 14:00:04 Unraid kernel: ata51: SATA link down (SStatus 0 SControl 310) Nov 15 14:00:04 Unraid kernel: ata26: SATA link down (SStatus 0 SControl 300) Nov 15 14:00:10 Unraid kernel: ata51: SATA link down (SStatus 0 SControl 310) Nov 15 14:00:15 Unraid kernel: ata51: SATA link down (SStatus 0 SControl 310) Nov 15 14:00:15 Unraid kernel: ata51.00: disable device Nov 15 14:00:15 Unraid kernel: ata51.00: detaching (SCSI 51:0:0:0) Nov 15 14:00:15 Unraid emhttpd: error: get_device_size, 1592: No such device or address (6): open: /dev/sdj Nov 15 14:00:15 Unraid kernel: md: unRAID driver removed Nov 15 14:00:15 Unraid emhttpd: shcmd (4839): /sbin/modprobe md-mod super=/boot/config/super.dat Nov 15 14:00:15 Unraid kernel: md: unRAID driver 2.9.27 installed Nov 15 14:00:15 Unraid kernel: sd 51:0:0:0: [sdj] Synchronizing SCSI cache Nov 15 14:00:15 Unraid kernel: sd 51:0:0:0: [sdj] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK Nov 15 14:00:17 Unraid emhttpd: Device inventory: Nov 15 14:00:17 Unraid emhttpd: Samsung_SSD_850_PRO_256GB_S251NSAG533690L (sdg) 512 500118192 Nov 15 14:00:17 Unraid emhttpd: ST4000VN008-2DR166_ZGY9SRLN (sdd) 512 7814037168 Nov 15 14:00:17 Unraid emhttpd: ST3000DM001-1ER166_Z500RWXR (sde) 512 5860533168 Nov 15 14:00:17 Unraid emhttpd: WDC_WD60EZAZ-00SF3B0_WD-WX12DA1ATSJ1 (sdb) 512 11721045168 Nov 15 14:00:17 Unraid emhttpd: CT250MX500SSD1_2145E5E1DDCA (sdf) 512 488397168 Nov 15 14:00:17 Unraid emhttpd: ST4000VN008-2DR166_ZGY9SRS8 (sdc) 512 7814037168 Nov 15 14:00:17 Unraid emhttpd: CT250P2SSD8_2142E5DAFFEC (nvme0n1) 512 488397168 Nov 15 14:00:17 Unraid emhttpd: WDC_WDS500G2B0C-00PXH0_21375P471310 (nvme1n1) 512 976773168 Nov 15 14:00:17 Unraid emhttpd: ST8000VN004-3CP101_WP00D7F3 (sdi) 512 15628053168 Nov 15 14:00:17 Unraid emhttpd: Kingston_DT_Rubber_3.0_5CD998BECF66FDA02223059A-0:0 (sda) 512 60435442 Nov 15 14:00:17 Unraid kernel: mdcmd (1): import 0 sdi 64 7814026532 0 ST8000VN004-3CP101_WP00D7F3 Nov 15 14:00:17 Unraid kernel: md: import disk0: (sdi) ST8000VN004-3CP101_WP00D7F3 size: 7814026532 Nov 15 14:00:17 Unraid kernel: mdcmd (2): import 1 sdc 64 3907018532 0 ST4000VN008-2DR166_ZGY9SRS8 Nov 15 14:00:17 Unraid kernel: md: import disk1: (sdc) ST4000VN008-2DR166_ZGY9SRS8 size: 3907018532 Nov 15 14:00:17 Unraid kernel: mdcmd (3): import 2 sdd 64 3907018532 0 ST4000VN008-2DR166_ZGY9SRLN Nov 15 14:00:17 Unraid kernel: md: import disk2: (sdd) ST4000VN008-2DR166_ZGY9SRLN size: 3907018532 Nov 15 14:00:17 Unraid kernel: mdcmd (4): import 3 sde 64 2930266532 0 ST3000DM001-1ER166_Z500RWXR Nov 15 14:00:17 Unraid kernel: md: import disk3: (sde) ST3000DM001-1ER166_Z500RWXR size: 2930266532 Nov 15 14:00:17 Unraid kernel: mdcmd (5): import 4 sdb 64 5860522532 0 WDC_WD60EZAZ-00SF3B0_WD-WX12DA1ATSJ1 Nov 15 14:00:17 Unraid kernel: md: import disk4: (sdb) WDC_WD60EZAZ-00SF3B0_WD-WX12DA1ATSJ1 size: 5860522532 Nov 15 14:00:17 Unraid kernel: mdcmd (6): import 5 Nov 15 14:00:17 Unraid kernel: md: import_slot: 5 missing Nov 15 14:00:17 Unraid kernel: mdcmd (7): import 6 Nov 15 14:00:17 Unraid kernel: md: import_slot: 6 missing Nov 15 14:00:17 Unraid kernel: mdcmd (8): import 7 Nov 15 14:00:17 Unraid kernel: mdcmd (9): import 8 Nov 15 14:00:17 Unraid kernel: mdcmd (10): import 9 Nov 15 14:00:17 Unraid kernel: mdcmd (11): import 10 Nov 15 14:00:17 Unraid kernel: mdcmd (12): import 11 Nov 15 14:00:17 Unraid kernel: mdcmd (13): import 12 Nov 15 14:00:17 Unraid kernel: mdcmd (14): import 13 Nov 15 14:00:17 Unraid kernel: mdcmd (15): import 14 Nov 15 14:00:17 Unraid kernel: mdcmd (16): import 15 Nov 15 14:00:17 Unraid kernel: mdcmd (17): import 16 Nov 15 14:00:17 Unraid kernel: mdcmd (18): import 17 Nov 15 14:00:17 Unraid kernel: mdcmd (19): import 18 Nov 15 14:00:17 Unraid kernel: mdcmd (20): import 19 Nov 15 14:00:17 Unraid kernel: mdcmd (21): import 20 Nov 15 14:00:17 Unraid kernel: mdcmd (22): import 21 Nov 15 14:00:17 Unraid kernel: mdcmd (23): import 22 Nov 15 14:00:17 Unraid kernel: mdcmd (24): import 23 Nov 15 14:00:17 Unraid kernel: mdcmd (25): import 24 Nov 15 14:00:17 Unraid kernel: mdcmd (26): import 25 Nov 15 14:00:17 Unraid kernel: mdcmd (27): import 26 Nov 15 14:00:17 Unraid kernel: mdcmd (28): import 27 Nov 15 14:00:17 Unraid kernel: mdcmd (29): import 28 Nov 15 14:00:17 Unraid kernel: mdcmd (30): import 29 Nov 15 14:00:17 Unraid kernel: md: import_slot: 29 empty Nov 15 14:00:17 Unraid emhttpd: import 30 cache device: (nvme0n1) CT250P2SSD8_2142E5DAFFEC Nov 15 14:00:17 Unraid emhttpd: import 31 cache device: (sdg) Samsung_SSD_850_PRO_256GB_S251NSAG533690L Nov 15 14:00:17 Unraid emhttpd: import 32 cache device: (sdf) CT250MX500SSD1_2145E5E1DDCA Nov 15 14:00:17 Unraid emhttpd: import 33 cache device: (nvme1n1) WDC_WDS500G2B0C-00PXH0_21375P471310 Nov 15 14:00:17 Unraid emhttpd: import flash device: sda Nov 15 14:00:17 Unraid root: Submitting SysDrivers Build Nov 15 14:00:17 Unraid SysDrivers: SysDrivers Build Starting Nov 15 14:00:17 Unraid emhttpd: read SMART /dev/sdg Nov 15 14:00:17 Unraid emhttpd: read SMART /dev/sdd Nov 15 14:00:17 Unraid emhttpd: read SMART /dev/sde Nov 15 14:00:17 Unraid emhttpd: read SMART /dev/sdb Nov 15 14:00:17 Unraid emhttpd: read SMART /dev/sdf Nov 15 14:00:17 Unraid emhttpd: read SMART /dev/sdc Nov 15 14:00:17 Unraid emhttpd: read SMART /dev/nvme0n1 Nov 15 14:00:17 Unraid emhttpd: read SMART /dev/nvme1n1 Nov 15 14:00:17 Unraid emhttpd: read SMART /dev/sdi Nov 15 14:00:17 Unraid emhttpd: read SMART /dev/sda Nov 15 14:00:35 Unraid SysDrivers: SysDrivers Build Complete

No I have 1 cable for each drive no splitter. I have my mother board controler filled with SATA cables to SSD and some HD I have 2 SATA controlers with SATA cable running each to one drive

Hi Kilra, I have indeed changed the SATA cables for disks parity, 5 and 6 I doubled checked the wiring for electricity power and data. The power supply is new as of 1 year and it is a 550 Watt bronze

Hello to all, I have multiple problems with my unraid disks they gives me error of type READ FPDMA QUEUED and hard resetting link (I have attached my diag). My version of Unraid 6.12.13 History of the problem : 1. A while a go I had 2 8tb disks Toshiba (disk 5 and 6) which went off line. I took them out and replace them with 2 Seagate (disk 5 and 6). Rebuild the array and all went fine for 2 months I will say 2. Then 2 months after disk 5 started to fail (off line) very often and I had to rebuild it every 2 weeks I will say 3. I bought a new SATA controler (but same brand) because I thougt it was the controler the culprid as it is very unlikely that disk 5 toshiba and disk 5 seagate failed (diffrent brand) 3. After the change of the SATA controler my 2nd parity drive failed (5 hours after I will say). When I started to rebuild it disk 5 started to fail et parity 1 too. My thoughts in order to save the server : 1. I need to "save" my parity drive and correct these hard link resetting and READ FPDMA QUEUED on it 2. Disk 5 is not correct and won't mount so I will have to rebuild but in order to do so I need a correct arity drive 😞 As of today : 1. I ordered a new SATA controler (different brand) in order change the 2 I have (other from my motherboard), should arrive beginning of next week. 2. Docker and VM are stopped, array is stopped, server still ON 3. I would really like to save my array and the data in disk 5 and 6 Could you please help me, and to do so, do you need any more informations ? Sorry if my English is not very good as it is not my mother tongue. Thanks in advance for you all unraid-diagnostics-20241115-1249.zip

Hello, I have done like @Trasher, remove the plug-in, reinstall it, remove the ssl key and recreate one and re enable remote access. It is working. Thanks @Trasher I should have this idea before reading your post.

Hi all, I have the same problem. Port open and forwarded. I didn't have the problem before my current version (6.12.6). Before that I was in 6.12.4 (no probleme) then updated 6.12.5 (didn't test unraid.net) then the day after 6.12.6.