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.
So, yestarday in all consoles linux started writing me error message. Laptop's performance slows down. Then this message disappeared, and now i see it again.
Here is part of it:
Quote:
[66113.147901] ata1.00: exception Emask 0x0 SAct 0x3f SErr 0x0 action 0x0
[66113.147917] ata1.00: irq_stat 0x40000008
[66113.147928] ata1.00: failed command: READ FPDMA QUEUED
[66113.147946] ata1.00: cmd 60/f8:10:82:ef:99/00:00:1c:00:00/40 tag 2 ncq 126976 in
[66113.147949] res 41/40:f8:56:f0:99/00:00:1c:00:00/40 Emask 0x409 (media error) <F>
[66113.147958] ata1.00: status: { DRDY ERR }
[66113.147963] ata1.00: error: { UNC }
[66113.151434] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
[66113.152369] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
[66113.152379] ata1.00: configured for UDMA/133
[66113.152436] ata1: EH complete
[66115.265545] ata1.00: exception Emask 0x0 SAct 0xc SErr 0x0 action 0x0
[66115.265560] ata1.00: irq_stat 0x40000008
[66115.265573] ata1.00: failed command: READ FPDMA QUEUED
[66115.265591] ata1.00: cmd 60/f8:18:82:ef:99/00:00:1c:00:00/40 tag 3 ncq 126976 in
[66115.265594] res 41/40:f8:56:f0:99/00:00:1c:00:00/40 Emask 0x409 (media error) <F>
[66115.265603] ata1.00: status: { DRDY ERR }
[66115.265609] ata1.00: error: { UNC }
[66115.269049] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
[66115.269997] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
[66115.270007] ata1.00: configured for UDMA/133
[66115.270070] ata1: EH complete
[66117.660254] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
[66117.660260] ata1.00: irq_stat 0x40000008
[66117.660265] ata1.00: failed command: READ FPDMA QUEUED
[66117.660272] ata1.00: cmd 60/f8:00:82:ef:99/00:00:1c:00:00/40 tag 0 ncq 126976 in
[66117.660273] res 41/40:f8:56:f0:99/00:00:1c:00:00/40 Emask 0x409 (media error) <F>
[66117.660276] ata1.00: status: { DRDY ERR }
[66117.660279] ata1.00: error: { UNC }
[66117.663762] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
[66117.664611] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
[66117.664616] ata1.00: configured for UDMA/133
[66117.664636] ata1: EH complete
[66120.343258] ata1.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0
[66120.343263] ata1.00: irq_stat 0x40000008
[66120.343268] ata1.00: failed command: READ FPDMA QUEUED
[66120.343276] ata1.00: cmd 60/f8:08:82:ef:99/00:00:1c:00:00/40 tag 1 ncq 126976 in
[66120.343277] res 41/40:f8:56:f0:99/00:00:1c:00:00/40 Emask 0x409 (media error) <F>
[66120.343280] ata1.00: status: { DRDY ERR }
[66120.343283] ata1.00: error: { UNC }
[66120.346759] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
[66120.347580] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
[66120.347583] ata1.00: configured for UDMA/133
[66120.347599] ata1: EH complete
[66122.627071] ata1.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0
[66122.627076] ata1.00: irq_stat 0x40000008
[66122.627081] ata1.00: failed command: READ FPDMA QUEUED
[66122.627088] ata1.00: cmd 60/f8:08:82:ef:99/00:00:1c:00:00/40 tag 1 ncq 126976 in
[66122.627089] res 41/40:f8:56:f0:99/00:00:1c:00:00/40 Emask 0x409 (media error) <F>
[66122.627093] ata1.00: status: { DRDY ERR }
[66122.627095] ata1.00: error: { UNC }
[66122.630572] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
[66122.631369] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
[66122.631372] ata1.00: configured for UDMA/133
[66122.631391] ata1: EH complete
[66124.988577] ata1.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0
[66124.988590] ata1.00: irq_stat 0x40000008
[66124.988600] ata1.00: failed command: READ FPDMA QUEUED
[66124.988618] ata1.00: cmd 60/f8:08:82:ef:99/00:00:1c:00:00/40 tag 1 ncq 126976 in
[66124.988621] res 41/40:f8:56:f0:99/00:00:1c:00:00/40 Emask 0x409 (media error) <F>
[66124.988629] ata1.00: status: { DRDY ERR }
[66124.988635] ata1.00: error: { UNC }
[66124.992108] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
[66124.992998] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
[66124.993006] ata1.00: configured for UDMA/133
[66124.993053] sd 0:0:0:0: [sda] Unhandled sense code
[66124.993058] sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[66124.993068] sd 0:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor]
[66124.993081] Descriptor sense data with sense descriptors (in hex):
[66124.993086] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[66124.993106] 1c 99 f0 56
[66124.993114] sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed
[66124.993127] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 1c 99 ef 82 00 00 f8 00
[66124.993147] end_request: I/O error, dev sda, sector 479850582
[66124.993195] ata1: EH complete
[66160.577466] ata1.00: exception Emask 0x0 SAct 0x7f SErr 0x0 action 0x0
[66160.577482] ata1.00: irq_stat 0x40000008
[66160.577493] ata1.00: failed command: READ FPDMA QUEUED
[66160.577510] ata1.00: cmd 60/80:08:ba:02:9a/00:00:1c:00:00/40 tag 1 ncq 65536 in
[66160.577513] res 41/40:80:fd:02:9a/00:00:1c:00:00/40 Emask 0x409 (media error) <F>
[66160.577521] ata1.00: status: { DRDY ERR }
[66160.577527] ata1.00: error: { UNC }
[66160.582624] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
[66160.583541] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
[66160.583550] ata1.00: configured for UDMA/133
[66160.583622] ata1: EH complete
[66162.883426] ata1.00: exception Emask 0x0 SAct 0x63 SErr 0x0 action 0x0
[66162.883440] ata1.00: irq_stat 0x40000008
[66162.883451] ata1.00: failed command: READ FPDMA QUEUED
[66162.883470] ata1.00: cmd 60/80:28:ba:02:9a/00:00:1c:00:00/40 tag 5 ncq 65536 in
[66162.883473] res 41/40:80:fd:02:9a/00:00:1c:00:00/40 Emask 0x409 (media error) <F>
I would run a check on the disk with the manufacturer's disk integrity tool. I believe the Ultimate Boot CD has utilities from most major hard disk vendors.
Yup! It looks like the drive's on the way out, I'd get a backup of any vital data ASAP.
Disks normally handle bad block problems by re-vectoring bad blocks to a reserved area of the drive - there are usually two alternate cylinders put aside for the job. Your drive is now saying that it can't reallocate. Disks can normally run fine with quite a lot of bad blocks, handling them by re-vectoring them. The host system only sees a perfect disk. Providing the bad block table is stable, not increasing due to continuing bad blocks being found (usually due to a head crash) you're fine. (for a while anyway!)
You're getting read errors (from bad area of disk) which would definitely affect the performance as the system will keep retrying to read the data. I think fsck would just give more of the same errors.
pljvaldez, thanks for link Soadyheid, u're the one who normally explained me what's wrong this HDD, thanks! I made a backup of my vital data immediately, when i saw errors from HDD because 1 year ago previous hard-disk died undetectably and i lost all my information
sorry, it may not be exactly related this post, but i'm having problems with by hdd, too.
I used to use windows 7 but suddenly my screen had frozen while I was using my computer and when I wanted to restart I got a "read error occured" message.
my friends told me that I could try to run linux from a usb to reach the hard disk and save my files, but I got the error messages posted above no matter which ubuntu version i tried (I've tried 8.04,9.04, 10.04, 10.10 and their both desktop i386 and amd64 versions)
from this thread i understood that my hdd is dying or almost dead and I'm unable to run linux, but is there any way to save my files without removing hard drive from computer? (cuz my computer is still under warranty, but I don't want to pay them extra to save those files)
If you can't reach your hard disk from both systems then I assume that your data is lost. Next time I would recommend to backup your data, before an error occurs.
sorry, it may not be exactly related this post, but i'm having problems with by hdd, too.
I used to use windows 7 but suddenly my screen had frozen while I was using my computer and when I wanted to restart I got a "read error occured" message.
my friends told me that I could try to run linux from a usb to reach the hard disk and save my files, but I got the error messages posted above no matter which ubuntu version i tried (I've tried 8.04,9.04, 10.04, 10.10 and their both desktop i386 and amd64 versions)
from this thread i understood that my hdd is dying or almost dead and I'm unable to run linux, but is there any way to save my files without removing hard drive from computer? (cuz my computer is still under warranty, but I don't want to pay them extra to save those files)
thanks for your help!
Your right, this is not related to this thread and is considered rude. Hi-jacking a thread is not considerate to other members or the OP. You should create a new thread.
I suggest that you look at 'How to Ask Questions the Smart Way' so in the future your queries provide information that will aid us in diagnosis of the problem when creating the new thread.
Plus, if you do a Search here on LQ with proper keywords a solution can be found for this problem. This subject has been covered many times.
Thats bad. I had the same issues a few weeks ago, sent the HDD to WD for RMA and they acknowledged the dead drive. If I were you, I would backup ASAP, and dont play with the drive, i.e. dont make it work more that you absolutely need to backup because it will get gradually worst and it might even completey crap on you while you're copying your data.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.