Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Oh, I think a bunch of "interface fatal error" complaints from the OS together with ICRC (Interface CRC) errors logged by the drive qualifies. If this were a desktop PC or an external drive, I would strongly suspect the cable. In a netbook, about all that can be said is that the problem is somewhere in (a) the motherboard interface, (b) the connector, or (c) the interface circuitry in the drive. Since another drive was presumably working in the netbook, that suggests that the motherboard interface circuitry is fine. That leaves either poor contact at the connector or an internal problem in the drive itself as the only remaining candidates.
I would first see if the original drive still works without those error messages. If you have another system to which you could connect that new drive, I'd try that to see if the drive is OK. I'm hesitant to recommend any method of cleaning the connector because you can easily do more harm than good.
Oh, I think a bunch of "interface fatal error" complaints from the OS together with ICRC (Interface CRC) errors logged by the drive qualifies. If this were a desktop PC or an external drive, I would strongly suspect the cable. In a netbook, about all that can be said is that the problem is somewhere in (a) the motherboard interface, (b) the connector, or (c) the interface circuitry in the drive. Since another drive was presumably working in the netbook, that suggests that the motherboard interface circuitry is fine. That leaves either poor contact at the connector or an internal problem in the drive itself as the only remaining candidates.
I would first see if the original drive still works without those error messages. If you have another system to which you could connect that new drive, I'd try that to see if the drive is OK. I'm hesitant to recommend any method of cleaning the connector because you can easily do more harm than good.
Next episode of X-files: G-Sense_Error_Rate jumped from 0 to 65552!
I have performed several tests with this drive. I connected it to same netbook but with same results. The old drive works fine. Then the X-files one has been connected to desktop machine (with AMD SB950) and there it works fine on 6.0Gb link w/o any errors form kernel for about a day. Moreover - G-Sense_Error_Rate changed back to 0 there (wth?!).
The guy had exactly same errors as I. I have appended libata.force=3.0 to kernel parameters and system started w/o any errors. But I have to work on such configuration for some time to see if it really helped.
Final conclusion/possible reason: when the system by specification is 6.0Gb capable (AMD A50M chipset) then it not necessarily means that hardware (disk connector, when tere is no SATA cable) is as well. There is possibility that Sony who is the netbook manufacturer put hard drive SATA connector only 3.0Gb capable. Then it initially negotiates 6.0Gb because both the chipset and the drive are capable but then after first data transmission it fails and kernel decides to renegotiate connection with drive with slower one.
There is no connector difference between SATA II (3.0 Gb/s) and SATA III (6.0 Gb/s). A couple of new connector types (one for 1.8 inch devices, one for slimline optical devices) are included in the SATA III standard, but the regular connector is unchanged. Cables for SATA III have better shielding, but the connectors are the same. It's possible that the chipset in the netbook supports 6.0 Gb/s, but other parts of the circuitry do not.
In your original post, I did notice another interface fatal error after the switch to 3.0 Gb/s, but perhaps that was just a hiccup in the negotiation.
FWIW, in the past I had a couple of external drives (eSATA) that also had to renegotiate to a lower speed after errors at the initial speed. I had to add that "libata.force=" to the boot parameters to make those drives connect cleanly.
So far symptoms and test results indicates that the issue is caused by something between the drive and SATA host adapter (in the chipset). As it is netbook there is no standard SATA cable but some custom connector, which looks like this one: http://thumbs.ebaystatic.com/images/...sHK/s-l225.jpg
That's a normal SATA connector that combines the power and data connectors in one physical piece. It's totally standard for laptops, netbooks, and the like where the drive attaches directly to the circuit board with no intervening cable. My 4-year-old laptop has one just like it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.