Hi,

i think this is the first time an encrypted disk of mine had errors and got deaktivated.

Afterwards i tried different cables and controllers but always got errors like this:

 

Sep 12 19:01:23 Tower kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 12 19:01:23 Tower kernel: ata5.00: cmd 60/20:c8:60:4f:04/00:00:00:00:00/40 tag 25 ncq dma 16384 in
Sep 12 19:01:23 Tower kernel:         res 40/00:c8:60:4f:04/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Sep 12 19:01:23 Tower kernel: ata5.00: status: { DRDY }
Sep 12 19:01:23 Tower kernel: ata5: hard resetting link
Sep 12 19:01:29 Tower kernel: ata5: link is slow to respond, please be patient (ready=0)
Sep 12 19:01:33 Tower kernel: ata5: found unknown device (class 0)
Sep 12 19:01:34 Tower kernel: ata5: found unknown device (class 0)
Sep 12 19:01:34 Tower kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 12 19:01:37 Tower kernel: ata5.00: supports DRM functions and may not be fully accessible
Sep 12 19:01:37 Tower kernel: ata5.00: supports DRM functions and may not be fully accessible
Sep 12 19:01:37 Tower kernel: ata5.00: configured for UDMA/33
Sep 12 19:01:37 Tower kernel: ata5: EH complete
Sep 12 19:01:37 Tower kernel: ata5.00: exception Emask 0x10 SAct 0x8000000 SErr 0x90200 action 0xe frozen
Sep 12 19:01:37 Tower kernel: ata5.00: irq_stat 0x00400000, PHY RDY changed
Sep 12 19:01:37 Tower kernel: ata5: SError: { Persist PHYRdyChg 10B8B }
Sep 12 19:01:37 Tower kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 12 19:01:37 Tower kernel: ata5.00: cmd 60/20:d8:c0:70:04/00:00:00:00:00/40 tag 27 ncq dma 16384 in
Sep 12 19:01:37 Tower kernel:         res 40/00:d8:c0:70:04/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Sep 12 19:01:37 Tower kernel: ata5.00: status: { DRDY }
Sep 12 19:01:37 Tower kernel: ata5: hard resetting link
Sep 12 19:01:43 Tower kernel: ata5: link is slow to respond, please be patient (ready=0)
Sep 12 19:01:47 Tower kernel: ata5: found unknown device (class 0)
Sep 12 19:01:47 Tower kernel: ata5: found unknown device (class 0)
Sep 12 19:01:47 Tower kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 12 19:01:51 Tower kernel: ata5.00: supports DRM functions and may not be fully accessible
Sep 12 19:01:51 Tower kernel: ata5.00: supports DRM functions and may not be fully accessible
Sep 12 19:01:51 Tower kernel: ata5.00: configured for UDMA/33
Sep 12 19:01:51 Tower kernel: ata5: EH complete
Sep 12 19:01:51 Tower kernel: ata5.00: exception Emask 0x10 SAct 0x2000 SErr 0x90200 action 0xe frozen
Sep 12 19:01:51 Tower kernel: ata5.00: irq_stat 0x00400000, PHY RDY changed
Sep 12 19:01:51 Tower kernel: ata5: SError: { Persist PHYRdyChg 10B8B }
Sep 12 19:01:51 Tower kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 12 19:01:51 Tower kernel: ata5.00: cmd 60/20:68:e0:d1:04/00:00:00:00:00/40 tag 13 ncq dma 16384 in
Sep 12 19:01:51 Tower kernel:         res 40/00:68:e0:d1:04/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Sep 12 19:01:51 Tower kernel: ata5.00: status: { DRDY }
Sep 12 19:01:51 Tower kernel: ata5: hard resetting link
Sep 12 19:01:57 Tower kernel: ata5: link is slow to respond, please be patient (ready=0)
Sep 12 19:02:01 Tower kernel: ata5: found unknown device (class 0)
Sep 12 19:02:01 Tower kernel: ata5: found unknown device (class 0)
Sep 12 19:02:01 Tower kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 12 19:02:04 Tower kernel: ata5.00: supports DRM functions and may not be fully accessible
Sep 12 19:02:04 Tower kernel: ata5.00: supports DRM functions and may not be fully accessible
Sep 12 19:02:04 Tower kernel: ata5.00: configured for UDMA/33
Sep 12 19:02:04 Tower kernel: ata5: EH complete
Sep 12 19:02:05 Tower kernel: ata5.00: exception Emask 0x10 SAct 0x1 SErr 0x90200 action 0xe frozen
Sep 12 19:02:05 Tower kernel: ata5.00: irq_stat 0x00400000, PHY RDY changed
Sep 12 19:02:05 Tower kernel: ata5: SError: { Persist PHYRdyChg 10B8B }
Sep 12 19:02:05 Tower kernel: ata5.00: failed command: READ FPDMA QUEUED

 

After some reboots i noticed the message "Unmountable: Wrong encryption key" even though the Disk 7 is missing right now. Is this normal and after i assign a working disk and resync it, it gets fixed?

 

I find this kinda confusing.

Edited September 16, 20241 yr by varona
solved

12 hours ago, varona said:

Is this normal and after i assign a working disk and resync it, it gets fixed?

No, it's not normal, please post the diagnostics.

Hello JorgeB,

here is the diagnostics.

tower-diagnostics-20240913-1146.zip

Try rebooting and try again, in case it was a RAM bit flip or something, I do see a data corruption error in one of your other disks.

 

Do you have a backup of the LUKS headers if needed?

I just did a reboot. The message is still there.

No, i didnt think about backup of the headers..

Edit:

I dont remember which share was on Disk7.

I think all my important stuff is on Disk5 and Disk6.

Which Disk has the data corruption?

Edited September 13, 20241 yr by varona
typo

Disk 5, you should run a scrub.

The scrub didnt help, Disk5 ist still corrupt..

Sep 14 14:34:03 Tower kernel: BTRFS info (device dm-0): bdev /dev/mapper/md5p1 errs: wr 0, rd 0, flush 0, corrupt 1, gen 0

 

I dont really care about Disk7. I know that with a new config, unraid will forget about the Disk7 and i can add it later.

Now I worry about the corruption of Disk5...

Do you have other ideas?

13 minutes ago, varona said:

Disk5 ist still corrupt..

That is expected unless you reset the stats, but was there corruption found during the scrub? If yes check the syslog for the corrupt file.

 

 

There was no corruption found during the scrub process.

In that case reset the stats and keep monitoring:

 

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=700582

 

Thanks a lot. I created the script for hourly checks and i am gonna read the rest of the faq 😀

For the future, could you please tell how to backup the luks header ?

I don't use encryption, but this should work: