Hi
after extensive testing of my newly arrived setup I pinned down the problem described earlier (https://forum.pine64.org/showthread.php?tid=8359 and https://github.com/ayufan-rock64/linux-build/issues/299) to the official PCI-e to Dual SATA-II Interface Card. As I'm pretty sure that the card is the culprit in this case, I'm re-posting the problem here.
My setup:
RockPro64 4GB
2x4TB Seagate IronWolf 3.5" HDD
PCI-e to Dual SATA-II Interface Card
NAS case with fan and Pine64 power supply (5A)
With two HDDs connected, the system does not boot or crashes frequently (power cycle required to reboot). Before the crash, I can hear the HDDs repeatedly "trying to spin up". I tried with different OS images, including ayufans openmediavault builds (version 0.9.14, armhf and arm64) and "vanilla" armbian buster server (kernel 4.4). Both HDDs are working (tested using an USB-to-SATA adapter) and both SATA cables are tested and OK. Powering the HDDs with a separate PSU didn't help, so the power supply is not the problem.
Connecting only one hard drive to either of the two SATA connectors works without problems. I also tried hot-plugging the second hard drive, which results in the following dmesg output (repetitive, for ata1 or ata2):
Searching for this error, most people seem to suggest a broken cable. I remember reading somewhere on this forum that the signal quality of the PCIe card is not the best, which would explain why two cards could potentially "interfere" on the hardware-level. Did anyone experience similar issues and knows how to fix them?
Otherwise it seems that the pine64 was a total misbuy and I have to find another SATA card now...
after extensive testing of my newly arrived setup I pinned down the problem described earlier (https://forum.pine64.org/showthread.php?tid=8359 and https://github.com/ayufan-rock64/linux-build/issues/299) to the official PCI-e to Dual SATA-II Interface Card. As I'm pretty sure that the card is the culprit in this case, I'm re-posting the problem here.
My setup:
RockPro64 4GB
2x4TB Seagate IronWolf 3.5" HDD
PCI-e to Dual SATA-II Interface Card
NAS case with fan and Pine64 power supply (5A)
With two HDDs connected, the system does not boot or crashes frequently (power cycle required to reboot). Before the crash, I can hear the HDDs repeatedly "trying to spin up". I tried with different OS images, including ayufans openmediavault builds (version 0.9.14, armhf and arm64) and "vanilla" armbian buster server (kernel 4.4). Both HDDs are working (tested using an USB-to-SATA adapter) and both SATA cables are tested and OK. Powering the HDDs with a separate PSU didn't help, so the power supply is not the problem.
Connecting only one hard drive to either of the two SATA connectors works without problems. I also tried hot-plugging the second hard drive, which results in the following dmesg output (repetitive, for ata1 or ata2):
Code:
[ 322.470646] ata2: exception Emask 0x10 SAct 0x0 SErr 0x4050000 action 0xe frozen
[ 322.470669] ata2: irq_stat 0x00400040, connection status changed
[ 322.470687] ata2: SError: { PHYRdyChg CommWake DevExch }Searching for this error, most people seem to suggest a broken cable. I remember reading somewhere on this forum that the signal quality of the PCIe card is not the best, which would explain why two cards could potentially "interfere" on the hardware-level. Did anyone experience similar issues and knows how to fix them?
Otherwise it seems that the pine64 was a total misbuy and I have to find another SATA card now...