en/accessories/storage/penta-sata-hat/penta-for-rpi5

[giscus[bot]]

en/accessories/storage/penta-sata-hat/penta-for-rpi5

The Raspberry Pi 5 has a PCIe port that works well with the Radxa Penta SATA HAT.

https://docs.radxa.com/en/accessories/storage/penta-sata-hat/penta-for-rpi5

[Benockel]

Hey at sudo lspci -vvv -s 0000:01:00.1 | grep LnkSta my Pi do not give any feedback.
Can someone tell me what is the problem?!

My Pi 5 writes at lspci this:
0001:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries BCM2712 PCIe Bridge (rev 30)
0001:01:00.0 SATA controller: JMicron Technology Corp. JMB58x AHCI SATA controller
0002:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries BCM2712 PCIe Bridge (rev 30)
0002:01:00.0 Ethernet controller: Raspberry Pi Ltd RP1 PCIe 2.0 South Bridge

[fnhieu69]

0001:01:00.0 SATA controller: JMicron Technology Corp. JMB58x AHCI SATA controller

-> lspci -vvv -s 0001:01:00.0 | grep LnkSta

[MichaelKutscherBS]

Hi. it works, that's fine. However, I wonder if its possible to boot the raspi from one of the ssds or to have the OS on it und just a small bootloader on the sd-card?
I've tried with a complete OS on the first ssd, set the raspis boot-priority, but it did not work.
As sd-cards don't last long, it would be great to reduce it's use.
Is it possible and how can it be done?

[fnhieu69]

No because actuallty the rpi epprom can only boot from :

• NVMe Hat (PCIe)
• SDCard
• USB3 disk

Booting from AHCI devices (SATA HDD and SATA SSD) is too complex and the code should be too large to be kept in the flash memory of the pi.
This is not a limitation of the Hat but a limitation of the Pi.

The best way is in an hybrid way : boot from SD card only to load the kernel and to put the root (/) on the SATA HDD (split boot partition).

[hpathanjaly]

Im getting errors where my sata links reset and attempt to come back up at SATA II then SATA I speeds. This can happen at seemingly random times but maybe under load. I am using my HAT with a Pi 5 connecting 4 enterprise SATA drives and using a 12V 10A power supply though the jack.
Here is what it looks like. I believe this is the crux of other issues I have been having but at the very least, solving this might help me rule it out. Is there a power issue? could my HAT be defective somehow?

[Fri Aug  7 21:09:04 2026] ata1: SATA max UDMA/133 abar m8192@0x1b80010000 port 0x1b80010100 irq 171 lpm-pol 1 ext
[Fri Aug  7 21:09:04 2026] ata2: SATA max UDMA/133 abar m8192@0x1b80010000 port 0x1b80010180 irq 172 lpm-pol 1 ext
[Fri Aug  7 21:09:04 2026] ata3: SATA max UDMA/133 abar m8192@0x1b80010000 port 0x1b80010200 irq 173 lpm-pol 1 ext
[Fri Aug  7 21:09:04 2026] ata4: SATA max UDMA/133 abar m8192@0x1b80010000 port 0x1b80010280 irq 174 lpm-pol 1 ext
[Fri Aug  7 21:09:04 2026] ata5: SATA max UDMA/133 abar m8192@0x1b80010000 port 0x1b80010300 irq 175 lpm-pol 1 ext
[Fri Aug  7 21:09:05 2026] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Fri Aug  7 21:09:05 2026] ata1.00: ATA-8: TOSHIBA MG04ACA600A, FS3B, max UDMA/100
[Fri Aug  7 21:09:05 2026] ata1.00: 1465130646 sectors, multi 2: LBA48 NCQ (depth 32), AA
[Fri Aug  7 21:09:05 2026] ata1.00: Features: HIPM DIPM
[Fri Aug  7 21:09:05 2026] ata1.00: configured for UDMA/100
[Fri Aug  7 21:09:05 2026] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Fri Aug  7 21:09:05 2026] ata2.00: ATA-8: TOSHIBA MG04ACA600A, FS3B, max UDMA/100
[Fri Aug  7 21:09:05 2026] ata2.00: 1465130646 sectors, multi 2: LBA48 NCQ (depth 32), AA
[Fri Aug  7 21:09:05 2026] ata2.00: Features: HIPM DIPM
[Fri Aug  7 21:09:05 2026] ata2.00: configured for UDMA/100
[Fri Aug  7 21:09:06 2026] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Fri Aug  7 21:09:06 2026] ata3.00: ATA-8: TOSHIBA MG04ACA600A, FS3B, max UDMA/100
[Fri Aug  7 21:09:06 2026] ata3.00: 1465130646 sectors, multi 2: LBA48 NCQ (depth 32), AA
[Fri Aug  7 21:09:06 2026] ata3.00: Features: HIPM DIPM
[Fri Aug  7 21:09:06 2026] ata3.00: configured for UDMA/100
[Fri Aug  7 21:09:06 2026] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Fri Aug  7 21:09:07 2026] ata4.00: ATA-8: TOSHIBA MG04ACA600A, FS3B, max UDMA/100
[Fri Aug  7 21:09:07 2026] ata4.00: 1465130646 sectors, multi 2: LBA48 NCQ (depth 32), AA
[Fri Aug  7 21:09:07 2026] ata4.00: Features: HIPM DIPM
[Fri Aug  7 21:09:07 2026] ata4.00: configured for UDMA/100
[Fri Aug  7 21:09:07 2026] ata5: SATA link down (SStatus 0 SControl 300)
[Fri Aug  7 21:28:20 2026] ata3: SATA link down (SStatus 0 SControl 300)
[Fri Aug  7 21:28:29 2026] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Fri Aug  7 21:28:29 2026] ata3.00: configured for UDMA/100
[Fri Aug  7 21:30:42 2026] ata4: SATA link down (SStatus 0 SControl 300)
[Fri Aug  7 21:30:45 2026] ata2: SATA link down (SStatus 0 SControl 300)
[Fri Aug  7 21:30:45 2026] ata3: reset failed (errno=-32), retrying in 7 secs
[Fri Aug  7 21:30:45 2026] ata1: reset failed (errno=-32), retrying in 7 secs
[Fri Aug  7 21:30:50 2026] ata4: link is slow to respond, please be patient (ready=-19)
[Fri Aug  7 21:30:50 2026] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Fri Aug  7 21:30:50 2026] ata2.00: configured for UDMA/100
[Fri Aug  7 21:30:51 2026] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Fri Aug  7 21:30:51 2026] ata4.00: configured for UDMA/100
[Fri Aug  7 21:30:51 2026] ata1: limiting SATA link speed to 3.0 Gbps
[Fri Aug  7 21:30:51 2026] ata3: limiting SATA link speed to 3.0 Gbps
[Fri Aug  7 21:30:52 2026] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[Fri Aug  7 21:30:52 2026] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[Fri Aug  7 21:30:52 2026] ata1.00: configured for UDMA/100
[Fri Aug  7 21:30:52 2026] ata3.00: configured for UDMA/100
[Fri Aug  7 22:16:46 2026] ata1: SATA link down (SStatus 0 SControl 320)
[Fri Aug  7 22:16:49 2026] ata2: SATA link down (SStatus 0 SControl 300)
[Fri Aug  7 22:16:49 2026] ata3: reset failed (errno=-32), retrying in 7 secs
[Fri Aug  7 22:16:49 2026] ata4: reset failed (errno=-32), retrying in 7 secs
[Fri Aug  7 22:16:50 2026] ata2: found unknown device (class 0)
[Fri Aug  7 22:16:50 2026] ata2: SATA link down (SStatus 0 SControl 300)
-----
[Fri Aug  7 23:14:01 2026] ata1: link is slow to respond, please be patient (ready=-19)
[Fri Aug  7 23:14:03 2026] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Fri Aug  7 23:14:03 2026] ata1.00: ATA-8: TOSHIBA MG04ACA600A, FS3B, max UDMA/100
[Fri Aug  7 23:14:03 2026] ata1.00: 1465130646 sectors, multi 2: LBA48 NCQ (depth 32), AA
[Fri Aug  7 23:14:03 2026] ata1.00: Features: HIPM DIPM
[Fri Aug  7 23:14:03 2026] ata1.00: configured for UDMA/100
[Fri Aug  7 23:14:03 2026] ata1.00: detaching (SCSI 0:0:0:0)
[Fri Aug  7 23:28:50 2026] ata4: SATA link down (SStatus 0 SControl 320)
[Fri Aug  7 23:28:53 2026] ata1: reset failed (errno=-32), retrying in 7 secs
[Fri Aug  7 23:28:53 2026] ata3: SATA link down (SStatus 0 SControl 310)
[Fri Aug  7 23:28:53 2026] ata2: SATA link down (SStatus 0 SControl 3F0)
[Fri Aug  7 23:28:53 2026] ata3: found unknown device (class 0)
[Fri Aug  7 23:28:53 2026] ata3: SATA link down (SStatus 0 SControl 310)
[Fri Aug  7 23:28:54 2026] ata2: found unknown device (class 0)
[Fri Aug  7 23:28:54 2026] ata2: SATA link down (SStatus 0 SControl 3F0)
[Fri Aug  7 23:28:54 2026] ata2: limiting SATA link speed to <unknown>
[Fri Aug  7 23:28:54 2026] ata4: found unknown device (class 0)
[Fri Aug  7 23:28:54 2026] ata4: SATA link down (SStatus 0 SControl 320)
[Fri Aug  7 23:28:54 2026] ata4: limiting SATA link speed to 1.5 Gbps
[Fri Aug  7 23:28:59 2026] ata2: found unknown device (class 0)
[Fri Aug  7 23:28:59 2026] ata2: SATA link down (SStatus 0 SControl 3E0)
[Fri Aug  7 23:28:59 2026] ata2.00: disable device
[Fri Aug  7 23:28:59 2026] ata3: found unknown device (class 0)
[Fri Aug  7 23:28:59 2026] ata3: SATA link down (SStatus 0 SControl 310)
[Fri Aug  7 23:28:59 2026] ata3.00: disable device
[Fri Aug  7 23:28:59 2026] ata4: found unknown device (class 0)
[Fri Aug  7 23:28:59 2026] ata4: SATA link down (SStatus 0 SControl 310)
[Fri Aug  7 23:28:59 2026] ata4.00: disable device
[Fri Aug  7 23:29:04 2026] ata1: limiting SATA link speed to 3.0 Gbps
[Fri Aug  7 23:29:09 2026] ata2: found unknown device (class 0)
[Fri Aug  7 23:29:09 2026] ata3: found unknown device (class 0)
[Fri Aug  7 23:29:09 2026] ata2: softreset failed (device not ready)
[Fri Aug  7 23:29:09 2026] ata3: softreset failed (device not ready)
[Fri Aug  7 23:29:10 2026] ata4: link is slow to respond, please be patient (ready=-19)
[Fri Aug  7 23:29:10 2026] ata1: link is slow to respond, please be patient (ready=-19)
[Fri Aug  7 23:29:12 2026] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Fri Aug  7 23:29:12 2026] ata2.00: ATA-8: TOSHIBA MG04ACA600A, FS3B, max UDMA/100
[Fri Aug  7 23:29:12 2026] ata2.00: 1465130646 sectors, multi 2: LBA48 NCQ (depth 32), AA
[Fri Aug  7 23:29:12 2026] ata2.00: Features: HIPM DIPM
[Fri Aug  7 23:29:12 2026] ata2.00: configured for UDMA/100
[Fri Aug  7 23:29:12 2026] ata2.00: detaching (SCSI 1:0:0:0)
[Fri Aug  7 23:29:12 2026] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Fri Aug  7 23:29:12 2026] ata3.00: ATA-8: TOSHIBA MG04ACA600A, FS3B, max UDMA/100
[Fri Aug  7 23:29:12 2026] ata3.00: 1465130646 sectors, multi 2: LBA48 NCQ (depth 32), AA
[Fri Aug  7 23:29:12 2026] ata3.00: Features: HIPM DIPM
[Fri Aug  7 23:29:12 2026] ata3.00: configured for UDMA/100
[Fri Aug  7 23:29:12 2026] ata3.00: detaching (SCSI 2:0:0:0)
[Fri Aug  7 23:29:13 2026] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[Fri Aug  7 23:29:13 2026] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Fri Aug  7 23:29:13 2026] ata1.00: configured for UDMA/100
[Fri Aug  7 23:29:13 2026] ata4.00: ATA-8: TOSHIBA MG04ACA600A, FS3B, max UDMA/100
[Fri Aug  7 23:29:13 2026] ata4.00: 1465130646 sectors, multi 2: LBA48 NCQ (depth 32), AA
[Fri Aug  7 23:29:13 2026] ata4.00: Features: HIPM DIPM
[Fri Aug  7 23:29:13 2026] ata4.00: configured for UDMA/100
[Fri Aug  7 23:29:13 2026] ata4.00: detaching (SCSI 3:0:0:0)
[Fri Aug  7 23:42:26 2026] ata3.00: exception Emask 0x62 SAct 0x700000 SErr 0xc00 action 0x6 frozen
[Fri Aug  7 23:42:26 2026] ata3.00: irq_stat 0x38000000, host bus error
[Fri Aug  7 23:42:26 2026] ata3: SError: { Proto HostInt }
[Fri Aug  7 23:42:26 2026] ata3.00: failed command: READ FPDMA QUEUED
[Fri Aug  7 23:42:26 2026] ata3.00: cmd 60/20:a0:60:08:00/00:00:00:00:00/40 tag 20 ncq dma 131072 in
[Fri Aug  7 23:42:26 2026] ata3.00: status: { DRDY }
[Fri Aug  7 23:42:26 2026] ata3.00: failed command: READ FPDMA QUEUED
[Fri Aug  7 23:42:26 2026] ata3.00: cmd 60/20:a8:a0:d7:53/00:00:57:00:00/40 tag 21 ncq dma 131072 in
[Fri Aug  7 23:42:26 2026] ata3.00: status: { DRDY }
[Fri Aug  7 23:42:26 2026] ata3.00: failed command: READ FPDMA QUEUED
[Fri Aug  7 23:42:26 2026] ata3.00: cmd 60/20:b0:e0:d7:53/00:00:57:00:00/40 tag 22 ncq dma 131072 in
[Fri Aug  7 23:42:26 2026] ata3.00: status: { DRDY }
[Fri Aug  7 23:42:26 2026] ata3: hard resetting link
[Fri Aug  7 23:42:26 2026] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Fri Aug  7 23:42:27 2026] ata3.00: configured for UDMA/100
[Fri Aug  7 23:42:27 2026] ata3: EH complete

[tangzz-radxa]

Thanks for the detailed logs. Our hardware team reviewed this and here are two things to check:

1. Power supply margin: 12V/10A may not be enough for 4 enterprise 3.5" drives at peak (spin-up and seek current). Enterprise drives such as the TOSHIBA MG04ACA600A can draw significantly more current at peak than typical desktop drives. As a quick test, please try connecting only 2 drives and see whether the link resets / speed downgrades stop. If it is stable with fewer drives, the root cause is most likely power related.

2. Known JMB585 compatibility issue on Raspberry Pi 5 with newer kernels: The Penta SATA HAT uses the JMB585 PCIe SATA controller. Since Linux kernel commit ee95f3c, this chip needs additional configuration to work properly on the Pi 5. If drives are not detected or the AHCI driver fails to load after a system update, add the following line to /boot/firmware/config.txt and reboot:

dtoverlay=pcie-32bit-dma-pi5

This is documented here: https://docs.radxa.com/en/accessories/storage/penta-sata-hat/penta-for-rpi5#enable-pcie

Please try both steps and let us know the results. If the issue persists with 2 drives and the dtoverlay applied, we will investigate further.