intermittent ata errors and one failed boot: do I need to be worried?
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.
intermittent ata errors and one failed boot: do I need to be worried?
My Samsung laptop occasionally reports ata errors at boot time. Typically it looks like this:
Code:
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:40:60:bd:c5/00:00:00:00:00/e1 tag 0 dma 32768 in
res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
ata1.00: status: { DRDY }
ata1: link is slow to respond, please be patient (ready=0)
ata1: device not ready (errno=-16), forcing hardreset
ata1: soft resetting link
ata1.00: configured for UDMA/133
ata1: EH complete
The number shown here as 32768 varies but values tend to recur. Afterwards everything is fine.
Yesterday however, it gave a string of errors, and failed to mount the drive at all (which of course meant that most of the commands invoked by the startup scripts failed because the programs could not be found). Also no logs could be written. I tried to transcribe what I saw on the screen by hand but wasn't fast enough.
I have booted it twice since then with no startup errors at all. I ran a short smartctl test yesterday and a long one today. No errors were reported in the log, and the expected lifetime of the drive is given as over 1090 hours. I only have it on for an hour or so now and then as it's not my main machine, so that's a long time calendarwise.
No. You can decide if you want to wait (as long as it works/expected lifetime??) or do a backup and replace it. But you can check if the disk is plugged in properly. If it was an old laptop you probably need to clean it up.
The laptop was second hand but I bought it from Computer Exchange, not directly from the previous owner, so I presume it's been refurbished. I bought it only because I wanted to learn how to use one, and I still can't take it seriously as a computer. It feels like a toy. I use it mainly as a backup device for my desktop. However as it runs AntiX and I don't have Debian on the new desktop, I have transferred the family database (running under Gramps) to it as well. That was backed up yesterday!
I'm going to let the matter rest for a while, but if I do get another failure, I hope I can get down more of the output. I suspect the actual fail messages will be a lot more informative.
A couple of years ago now, way out of guarantee. I just found the original invoice: March 2016. It's always been a well-behaved little machine apart from these occasional ata tantrums. I even once made a Linux From Scratch on it, though I could never get the screen to work properly after waking from sleep (funnily enough this does work in AntiX).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.