eveslage

OK, found the Answer myself. create a new USB unraid device, insert and transfer the license to the USB device. Thanks

Hello, I had to replace my server. I had NVMe boot enabled with TPM licensing. I could only salvage the NVMe boot drive and the data disks. Every thing looks fine in the new server, but I have issues to get the license running. The new server only has TPM1.2 (which is not supported). So how can I still boot form my NVMe (with all the setting) and license from a USB stick again? Thanks for your support

OK, with another power supply, parity checking worked. Thanks for the help

disk 7 and 4 are connected to the same power supply after the reconfiguration. But not to the same controller. I will try another power supply. this is really strange and hard to debug.

I changed both power supplies for disk 7 and 8. it happened again. only a little later. are still the same disks affected? any other theories? unraid-diagnostics-20260706-2131.zip

as soon as a parity check starts, I see these error in the log: Jul 6 13:37:07 unraid kernel: md: recovery thread: check P Q ... Jul 6 13:37:45 unraid kernel: ata2.00: exception Emask 0x50 SAct 0x7ff00001 SErr 0x4890800 action 0xe frozen Jul 6 13:37:45 unraid kernel: ata2.00: irq_stat 0x04400040, connection status changed Jul 6 13:37:45 unraid kernel: ata2: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch } Jul 6 13:37:45 unraid kernel: ata2.00: failed command: READ FPDMA QUEUED Jul 6 13:37:45 unraid kernel: ata2.00: cmd 60/40:00:40:b5:9b/01:00:00:00:00/40 tag 0 ncq dma 163840 in Jul 6 13:37:45 unraid kernel: res 40/00:01:04:06:00/00:00:00:00:00/00 Emask 0x50 (ATA bus error) Jul 6 13:37:45 unraid kernel: ata2.00: status: { DRDY } Jul 6 13:37:45 unraid kernel: ata2.00: failed command: READ FPDMA QUEUED Jul 6 13:37:45 unraid kernel: ata2.00: cmd 60/00:a0:80:96:9b/04:00:00:00:00/40 tag 20 ncq dma 524288 in Jul 6 13:37:45 unraid kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x50 (ATA bus error) .... Jul 6 13:37:45 unraid kernel: ata2: hard resetting link Jul 6 13:37:45 unraid kernel: ata3.00: exception Emask 0x50 SAct 0x400007ff SErr 0x4890800 action 0xe frozen Jul 6 13:37:45 unraid kernel: ata3.00: irq_stat 0x04400040, connection status changed Jul 6 13:37:45 unraid kernel: ata3: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch } Jul 6 13:37:45 unraid kernel: ata3.00: failed command: READ FPDMA QUEUED Jul 6 13:37:45 unraid kernel: ata3.00: cmd 60/00:00:80:9a:9b/04:00:00:00:00/40 tag 0 ncq dma 524288 in Jul 6 13:37:45 unraid kernel: res 40/00:01:30:02:00/00:00:00:00:00/00 Emask 0x50 (ATA bus error) Jul 6 13:37:45 unraid kernel: ata3.00: status: { DRDY } Jul 6 13:37:45 unraid kernel: ata3.00: failed command: READ FPDMA QUEUED I tried this also in maintenance mode, same result. after immediately cancelling the parity check, I see this: Jul 6 13:37:51 unraid kernel: mdcmd (37): nocheck cancel Jul 6 13:37:51 unraid kernel: ata3: link is slow to respond, please be patient (ready=0) Jul 6 13:37:51 unraid kernel: ata2: link is slow to respond, please be patient (ready=0) Jul 6 13:37:55 unraid kernel: ata2: hard resetting link Jul 6 13:37:55 unraid kernel: ata3: hard resetting link Jul 6 13:38:00 unraid kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 6 13:38:00 unraid kernel: ata2.00: configured for UDMA/133 Jul 6 13:38:00 unraid kernel: ata2: EH complete Jul 6 13:38:01 unraid kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 6 13:38:01 unraid kernel: ata3.00: configured for UDMA/133 Jul 6 13:38:01 unraid kernel: ata3: EH complete Jul 6 13:38:02 unraid kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 6 13:38:02 unraid kernel: ata6.00: configured for UDMA/133 Jul 6 13:38:03 unraid sSMTP[15179]: Creating SSL connection to host Jul 6 13:38:03 unraid sSMTP[15179]: SSL connection using TLS_AES_256_GCM_SHA384 Jul 6 13:38:05 unraid kernel: md: recovery thread: exit status: -4 any idea, what could be wrong? unraid-diagnostics-20260706-1338.zip

Tonight my monthly parity check started and it ran very slow with a lot of error messages in the log. Jul 1 06:59:56 unraid kernel: ata8.00: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0x6 frozen Jul 1 06:59:56 unraid kernel: ata8.00: irq_stat 0x08000000, interface fatal error Jul 1 06:59:56 unraid kernel: ata8.00: failed command: READ DMA EXT Jul 1 06:59:56 unraid kernel: ata8.00: cmd 25/00:c0:48:f5:09/00:03:41:00:00/e0 tag 3 dma 491520 in Jul 1 06:59:56 unraid kernel: res 50/01:01:01:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error) Jul 1 06:59:56 unraid kernel: ata8.00: status: { DRDY } Jul 1 06:59:56 unraid kernel: ata8.00: error: { AMNF } Jul 1 06:59:56 unraid kernel: ata8: hard resetting link Jul 1 06:59:57 unraid kernel: ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 310) Jul 1 06:59:57 unraid kernel: ata8.00: configured for UDMA/33 Jul 1 06:59:57 unraid kernel: ata8: EH complete Jul 1 06:59:58 unraid kernel: ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0x6 frozen Jul 1 06:59:58 unraid kernel: ata5.00: irq_stat 0x08000000, interface fatal error Jul 1 06:59:58 unraid kernel: ata5.00: failed command: READ DMA EXT Jul 1 06:59:58 unraid kernel: ata5.00: cmd 25/00:c0:48:f5:09/00:03:41:00:00/e0 tag 22 dma 491520 in Jul 1 06:59:58 unraid kernel: res 50/01:01:01:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error) Jul 1 06:59:58 unraid kernel: ata5.00: status: { DRDY } Jul 1 06:59:58 unraid kernel: ata5.00: error: { AMNF } and a lot more. any idea, what's going on? unraid-diagnostics-20260701-0901.zip

Hey, my log is full with these error messages: Jun 3 07:00:53 unraid kernel: ata1.00: cmd 60/00:e0:f8:70:22/04:00:26:00:00/40 tag 28 ncq dma 524288 in Jun 3 07:00:53 unraid kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x50 (ATA bus error) Jun 3 07:00:53 unraid kernel: ata1.00: status: { DRDY } Jun 3 07:00:53 unraid kernel: ata1.00: failed command: READ FPDMA QUEUED Jun 3 07:00:53 unraid kernel: ata1.00: cmd 60/00:e8:f8:74:22/04:00:26:00:00/40 tag 29 ncq dma 524288 in Jun 3 07:00:53 unraid kernel: res 40/00:ff:ff:00:00/00:00:00:00:00/40 Emask 0x50 (ATA bus error) Jun 3 07:00:53 unraid kernel: ata1.00: status: { DRDY } Jun 3 07:00:53 unraid kernel: ata1.00: failed command: READ FPDMA QUEUED Jun 3 07:00:53 unraid kernel: ata1.00: cmd 60/00:f0:f8:78:22/04:00:26:00:00/40 tag 30 ncq dma 524288 in Jun 3 07:00:53 unraid kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x50 (ATA bus error) Jun 3 07:00:53 unraid kernel: ata1.00: status: { DRDY } Jun 3 07:00:53 unraid kernel: ata1: hard resetting link Jun 3 07:00:56 unraid kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jun 3 07:00:56 unraid kernel: ata1.00: configured for UDMA/33 Jun 3 07:00:56 unraid kernel: ata1: EH complete I am not even sure which drive/controller is affected. Any ideas what could be the reason? unraid-diagnostics-20260603-0709.zip

Hi, I have issues with my 12TB Seagate IronWolf drives. I have two SAS2308 controllers in my system and had suddenly "lost" two of my 12 TB drives on the one controller. I reconnected them to the other controller and at first everything was fine, the total loss again. Reconnecting one of the drives to an on-board SATA port, where its now working and rebuilding the Array. Any common issues with the SAS2308 controller and these drives? I am a little afraid. I am running 2 drives redundancy, but every rebuild takes >24h. unraid-diagnostics-20260601-1412.zip