SATA issues

[dponzone]

You can also try reducing the SATA link speed using "libata.force=1.5G" or "libata.force=3G" in the kernel arguments. That seems to have fixed some intermittent problems with my ASMedia SATA card.

I concur.

I was not able to achieve this with stretch-openmediavault-rockpro64-0.9.14-1159-arm64.img or other Debian-OMV distro, because the kernel arg (libata.force=1.5G) I added in /boot/efi/extlinux/extlinux.conf does not seem to work.
But with rockpro64-debian-mrfixit-190531.img, I was able to add it to /boot/extlinux/extlinux.conf, and it works: no more errors.
I tried 3G but errors are back.

My SATA card is not the exact official one.
It reports as:
01:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01)

I think we can consider it's crappy.

I must add that I also had to buy a new PSU (12V 7.5A), as the 12V 5A (bought from a German Pine64 reseller on Amazon, Humberg Computertechnik) was not able to spin up my 2 HGST 8TB drives.
It's the possible the 5A PSU they sent me was not the one Pine64 sells, it seems very light to me.

David

[dponzone]

Like others, I switched to a Marvell-based SATA card, and the issues are gone even at 3Gbps or 6Gbps.
I guess some ASM-based cards are crappy (jumpers related ?).

[Nikolay_Po]

Like others, I switched to a Marvell-based SATA card, and the issues are gone even at 3Gbps or 6Gbps.
I guess some ASM-based cards are crappy (jumpers related ?).

If the card is with big ugly standard jumpers at SATA differential signal path then yes. On practice it depends. Mine ASMedia-based Pine64 supplied card is working flawlessly with two different drives, one HGST, another Seagate. Sure there are existing another drives that will fail to operate stable with certain card. Just a matter of drive's SATA interface signal compensation capabilities. Some drives can compensate the distortions of bad SATA path, some can not.

[abdel]

Guys, the hardware is working fine.
The issue is on rockchip blob firmware that use undeclared memory.
You have to use a newest version of uboot without this blob firmware:
check patstew's post: https://forum.pine64.org/showthread.php?tid=8372&page=2

If you don't want to do this you will have to wait.
I know that MrFixit is working on this.
On manjaro there i a BUG: https://gitlab.manjaro.org/manjaro-arm/p...4/issues/1
For ayufan's debian, I couldn't contact him, so I dont know if he is aware of that.

In my case I couldn't use my PCIe card until I updated uboot.

[hemertje]

having the same problem with same original Pine64 NAS hardware:

https://forum.openmediavault.org/index.p.../?pageNo=1

https://forum.pine64.org/showthread.php?...2#pid60402

[lrb]

You can also try reducing the SATA link speed using "libata.force=1.5G" or "libata.force=3G" in the kernel arguments. That seems to have fixed some intermittent problems with my ASMedia SATA card.

I added "libata.force=1.5G" to the "append" line in extlinux.conf and have had no more problems, so I second this as a solution!

I didn't try "libata.force=3G". I probably should, but considering that the point of slowdown in my case is definitely the network connection, I don't really care anyway.

Current setup is NAS RockPro64, with "standard" SATA card from the pine store and Western Digital 8 TB spinners. I have ZFS set up on it, and it's "resilvering" as we speak. It was erroring on that before, and was even giving a problem (as in other posts) writing a lot of data to a single drive.

So as far as I'm concerned, this is "the" solution.

I add this comment for the use of others as a "this worked for me", not to take away from patstew, without whom I'd NEVER had figured out this option, and to whom I'm very VERY thankful for enabling me to have a functional setup!