05-30-2019, 01:20 PM
(This post was last modified: 05-30-2019, 02:00 PM by Nikolay_Po.)
(05-30-2019, 11:48 AM)vecnar Wrote: Thank you for the above information. I have bundled sata and power cables as much as i could. I tried to reproduce it on armbian but couldn't, left off overnight and plugged in the afternoon and no problems, no errors in dmesg output regarding ata.
Can you confirm that there is none difference for armbian how the cables are placed and attached? Does armbian operation reacts for HDD case connecting or disconnecting from a chassis?
Quote:But after changing sd card with omv on it i couldn't get them recognized, i had to reboot twice. I was getting below errors sames as before
Code:[ 7.461809] ata2: SATA link down (SStatus 1 SControl 300)
[ 7.476399] ata2: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
[ 7.483279] ata2: irq_stat 0x00000040, connection status changed
[ 7.489419] ata2: SError: { CommWake DevExch }
[ 7.495414] ata2: hard resetting link
Quick look into SStatus register description, SStatus=1 means "Device presence detected but Phy communication not established". This is an information (a SStatus register read) from the cnotroller. It is hardware status. The link just completely is gone. The signal is present (device detected), but interface information is destroyed too badly to keep SATA communication up.
You need to check somehow at which SATA speed operates armbian and at which OpenMediaVault.
It may be that one is trying to operate at higher speed than another. And higher speed fails.
It is hard to say anything without of seeing full log about SATA initialization.
Quote:I will try to reproduce on armbian to be sure it is software and not hardware.
When hardware fails using one distributive and not using another, it may be still hardware problem. One need to know all details like interface speeds and initialization sequences to judge. Of course it may be software problem. But SATA is rather well established protocol and it uses well established source codes. It is harder imagine there is software bug rather than hardware.
Quote:Regarding grounding points on sbc, you meant connect cable to rj45 metal shield, 1 hdmi and 2 usb shields and wrap wire around the bolts that hold sbc to the case or just pcie bracket screw?
Also what is the easiest way to attach cable to flat metal surfaces on sbc shields?
The best is to solder a wire to the minus of DC socket (at the top side of board) then to squeeze this wire (shorter is better) by the SATA card bottom screw. At the bottom side to solder another wire to the minus and squeeze this wire by a mounting screw to the mounting pin of the chassis. This will tighten the grounds of the components together into one point (DC socket minus) with a good contact.
If you can't or wish not to solder, just ensure that Ethernet socket have good contact and try to place a clamp filters on the wires. Something like ZCAT20D from TDK on SATA interface cables. See clamp filter catalog for a reference.
And... It may turns out to be software problem. So don't be afflicted too much after following my advices if follow.