JorgeB

Disks are failing to initialze and there's this on all 4 SMART reports: device Test Unit Ready [medium or hardware error (serious)] Could be bad devices, or they could be locked/protected, some SAS devices have format or other type of protection enable and can't be used before they are unlocked.

You need to disable secure boot in the BIOS.

Just boot Unraid and look at the main GUI page.

Like already mentioned check filesystem won't help for this case.

Did you enable UEFI boot on the tool? It's disable by default.

Please post diags.

Not that I can think of, you can look for a BIOS update though.

Look for the chipsets listed above JMB585 is fine, JMB5xx can be a lot of things, including JMB575 which is a port multiplier, a big clue in the controller you mentioned is that there's also a Marvell SATA controller, so that JMB5xx can only be a port multiplier.

I usually prefer buiyng used server pulls, they are about the same price or cheaper than a new Chinese LSI and much more likely to be genuine.

It says the same in this thread, so you should avoid that one.

Diags are after rebooting and you didn't capture the beginning of the problem, SMART for the disk looks OK, but clicking noises suggests it might not be, you can replace/swap cables to rule those out and try again.

If errors persist with new cables/port it's likely a bad disk.

You should be able to disable that function in the BIOS, if not replace the board or don't use the onboard SATA controller.

Then try to connect that drive to the same controller were removing the HPA worked.

gdisk should be able to fix that, see here: https://forums.unraid.net/topic/112243-solved-mount-error-unsupported-partition-layout/?do=findComment&comment=1023895 This should be fairly safe but always good to make sure backups are up to date before trying it, or clone the disk with dd first.

Unlikely to be the HBA if the same happens with another one, you can try connecting up to 8 disks directly to the HBA, even if it doesn't allow array start, you can see if the connected disks are detected and if yes it suggests the problem is the backplane.

This usually indicates a corrupt GPT partition, please post output of: fdisk -l /dev/sdX

Run again without -n or nothing will be done, if it asks for -L use it.

Best bet is to post in the existing zfs plugin support thread.

You need to put it back on the onboard SATA.

Still constant ATA errors on disk6: Sep 30 17:59:33 HOMESERVER01 kernel: ata4.00: cmd 60/08:70:78:9a:05/05:00:00:00:00/40 tag 14 ncq dma 659456 in Sep 30 17:59:33 HOMESERVER01 kernel: res 40/00:88:f8:9f:05/00:00:00:00:00/40 Emask 0x50 (ATA bus error) Sep 30 17:59:33 HOMESERVER01 kernel: ata4.00: status: { DRDY } Sep 30 17:59:33 HOMESERVER01 kernel: ata4.00: failed command: READ FPDMA QUEUED Sep 30 17:59:33 HOMESERVER01 kernel: ata4.00: cmd 60/38:78:80:9f:05/00:00:00:00:00/40 tag 15 ncq dma 28672 in Sep 30 17:59:33 HOMESERVER01 kernel: res 40/00:88:f8:9f:05/00:00:00:00:00/40 Emask 0x50 (ATA bus error) Sep 30 17:59:33 HOMESERVER01 kernel: ata4.00: status: { DRDY } Sep 30 17:59:33 HOMESERVER01 kernel: ata4.00: failed command: READ FPDMA QUEUED Sep 30 17:59:33 HOMESERVER01 kernel: ata4.00: cmd 60/40:80:b8:9f:05/00:00:00:00:00/40 tag 16 ncq dma 32768 in Sep 30 17:59:33 HOMESERVER01 kernel: res 40/00:88:f8:9f:05/00:00:00:00:00/40 Emask 0x50 (ATA bus error) Sep 30 17:59:33 HOMESERVER01 kernel: ata4.00: status: { DRDY } Sep 30 17:59:33 HOMESERVER01 kernel: ata4.00: failed command: READ FPDMA QUEUED Sep 30 17:59:33 HOMESERVER01 kernel: ata4.00: cmd 60/40:88:f8:9f:05/05:00:00:00:00/40 tag 17 ncq dma 688128 in Sep 30 17:59:33 HOMESERVER01 kernel: res 40/00:88:f8:9f:05/00:00:00:00:00/40 Emask 0x50 (ATA bus error) Sep 30 17:59:33 HOMESERVER01 kernel: ata4.00: status: { DRDY } Sep 30 17:59:33 HOMESERVER01 kernel: ata4: hard resetting link Sep 30 17:59:38 HOMESERVER01 kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Replace/swap both cables

Check/replace cables on disk6 and try again.

To confirm if the problem is with the board or the disks, it can still be a disk problem, just not surface related, i.e., not bad sectors.

As you prefer, like mentioned those errors are not a disk surface problem, preclear should always be successeful, unless there are other issues.

Please post the diagnostics.