i have the same issue with sata hdd connected through esata/usb adapter/splitter, changed esata cable, change splitter but it is the same, usb3.0 works fine... and i have this issue from the begining of LEDE, also on openwrt builds....
what can cause this?
Ok, after 2 days 3 enclosures 3 esata cables different LEDE/Openwrt images and my esata port on my computer i have come up with this:
1) Linux uses libata to check connection with the esata drive, this will negotiate a speed and continuously check the connection.
2) Connecting the esata drive directly to my Arch machine yielded the same error, interestingly enough it only had this error once, when first plugged in.
3) I wanted to see if checking hot-swappable in BIOS would help clear the warnings (Dang you American Megatrends) alas there was no bios option. However my sata drive was being seen by bios as a internal drive (makes sense)
4) I continued to boot up my PC and alas journald -rk showed no error (as it initialized the libata and negotiated the speed all at boot along with the other ssd's and hdd's). Continued to use the drive with no problem and the error would not show up again until i purposefully unplugged and replugged the esata from the port (all of this on an Arch kernel 4.8) then the error would show up when unplugged and show up again when i replugged but only once per action!!!! I'm assuming the bios is not set so the esata port is hot-swappable or libata is not used to removable sata drives.
5) did the same thing on the router and poof the error disappeared from the first 20 seconds on the boot and the drive seems to have initialized correctly. But after the 30 second mark more of the errors showed up culminatting on a negotiation speed of 1.5 Gbps and so far no other error message.
[ 31.696706] ata1: exception Emask 0x10 SAct 0x0 SErr 0x100000 action 0x6 frozen
[ 31.704300] ata1: edma_err_cause=00000020 pp_flags=00000003, SError=00100000
[ 31.711420] ata1: hard resetting link
[ 32.222592] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[ 32.262907] ata1.00: configured for UDMA/133
[ 32.267236] ata1: EH complete
[ 34.973424] ata1: exception Emask 0x10 SAct 0x0 SErr 0x100000 action 0x6 frozen
[ 34.980910] ata1: edma_err_cause=00000020 pp_flags=00000000, SError=00100000
[ 34.988095] ata1: hard resetting link
[ 35.492564] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[ 35.532954] ata1.00: configured for UDMA/133
[ 35.537271] ata1: EH complete
[ 42.653220] ata1: exception Emask 0x10 SAct 0x0 SErr 0x100000 action 0x6 frozen
[ 42.660679] ata1: edma_err_cause=00000020 pp_flags=00000000, SError=00100000
[ 42.667866] ata1: hard resetting link
[ 43.172593] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[ 43.212949] ata1.00: configured for UDMA/133
[ 43.217266] ata1: EH complete
[ 62.315050] ata1: limiting SATA link speed to 1.5 Gbps
[ 62.320352] ata1: exception Emask 0x10 SAct 0x0 SErr 0x100000 action 0x6 frozen
[ 62.327795] ata1: edma_err_cause=00000020 pp_flags=00000000, SError=00100000
[ 62.334951] ata1: hard resetting link
[ 62.842508] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl F310)
[ 62.882788] ata1.00: configured for UDMA/133
[ 62.887112] ata1: EH complete
Seems like maybe there was a regression on libata? Arch was using libata 3.0. Right now I can't tell for sure But I know the hdd or the enclosures are not the problem (again I have used 3 diffrent enclosures and 3 different esata cables on the wrt and on my esata port with 3 different hdd all passing smartctl test and dd zeroing all the drives)
update: apparently lede has libata 3.0 too... Just got an Anker esata+usb3 "enclosure" and the error is gone. I am simply lost for words, how do 2 enclosures fail almost at the same time?
Big update: Seems the error is normal for eSata drives when plugging and unplugging the connections (since this enclosure made the same error but only once when i unplugged it and once when I plugged it back in seems the "errors" are just warning about the connection but since this is a new enclosure and another drive seems like it's ok as long as they only happen when connecting or disconnecting [my other enclosure seemed to have a bad controller since it would continually search get "disconnected"])
(Last edited by lifehacksback on 2 Dec 2016, 06:55)