Rappel concernant les règles de confidentialité de Google
Afin de nous conformer à la législation relative à la protection des données, nous vous demandons de bien vouloir prendre quelques instants pour étudier les principaux aspects de nos règles de confidentialité, qui s'appliquent à tous les services Google et décrivent la manière dont nous utilisons les données et les options qui sont à votre disposition. Nous vous prions de le faire aujourd'hui.
Consulter maintenant
Résultats de recherche
hard drive - Are these SATA errors dangerous? - Ask Ubuntu
https://askubuntu.com/questions/133946/are-these-sata-errors-dangerous
I'm getting these errors ramdomly, and I don't know if its normal or not.
[39441.061856]... PLUS
I'm getting these errors ramdomly, and I don't know if its normal or not.
[39441.061856] ata3.00: failed to read SCR 1 (Emask=0x40)
[39441.061866] ata3.01: failed to read SCR 1 (Emask=0x40)
[39441.061892] ata3.15: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen
[39441.061897] ata3.15: irq_stat 0x08000000, interface fatal error
[39441.061904] ata3.15: SError: { UnrecovData 10B8B BadCRC }
[39441.061910] ata3.00: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
[39441.061917] ata3.01: exception Emask 0x100 SAct 0xe SErr 0x0 action 0x6 frozen
[39441.061923] ata3.01: failed command: READ FPDMA QUEUED
[39441.061933] ata3.01: cmd 60/a8:08:b0:48:62/00:00:00:00:00/40 tag 1 ncq 86016 in
[39441.061940] ata3.01: status: { DRDY }
[39441.061944] ata3.01: failed command: READ FPDMA QUEUED
[39441.061953] ata3.01: cmd 60/a8:10:b0:49:62/00:00:00:00:00/40 tag 2 ncq 86016 in
[39441.061959] ata3.01: status: { DRDY }
[39441.061963] ata3.01: failed command: READ FPDMA QUEUED
[39441.061972] ata3.01: cmd 60/58:18:58:4a:62/00:00:00:00:00/40 tag 3 ncq 45056 in
[39441.061978] ata3.01: status: { DRDY }
[39441.061987] ata3.15: hard resetting link
[39441.608302] ata3.15: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[39441.609090] ata3.00: hard resetting link
[39441.929246] ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[39441.929333] ata3.01: hard resetting link
[39442.249184] ata3.01: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[39442.263242] ata3.00: configured for UDMA/133
[39442.277570] ata3.01: configured for UDMA/133
[39442.277725] ata3: EH complete
I'm also pasting smartctl -a for sda, sdb and sdc.
Thanks in advance for your help.
9 answers
Best Answer
While I essentially agree with Geppettvs D'Constanzo's answer, I would suggest that some of the first things you might also try are
• Checking that your SATA cable is securely attached and plugged into the sockets on the motherboard and hard drive.
• Replacing your SATA cable. SATA cables are...
Answer 2 of 9
It looks like you have a bad quality/damaged SATA Power/Data Cable. Which may be causing Bad CRC's. They aren't harmful at all and you can live with them but you are going to lose a lot of data soon.
The SMART report of your hard disk drives looks sane, so I am for power supply issues based on...
Answer 3 of 9
There seems to be a problem between some kernel versions ans some SATA controllers.
I have recently started to suffer a very similar problem (not sure if it is just the same) on a web server running Scientific Linux.
The most accurate and complete information I have found about such problem is...
Answer 4 of 9
This is almost always a bad drive, I have thousands of drives that we use and although these errors never cause the drive to fail they have resulted in file system corruption. I think it really has to do with a problem with the controller board on the drive.
I have tried everything to solve this...
Answer 5 of 9
I know this thread is old but I recently encountered the same problem on a newly bought machine with 6 sata slots. I installed the cdrom and the hardrive on 2 sata slots close to each other and then proceeded to install ubuntu without errors until I reboot then on I saw the ata8: hard resetting...
Answer 6 of 9
Had the same issue - in my case this was due to 4-pin to SATA power adapter not being plugged snugly.
Answer 7 of 9
This error is dangerous and it can damage your HD.
To solve it:
• Replace the SATA cable.
• If the error persists, plug the SATA cable on other motherboard socket (the current socket could be oxidated).
• If the error persists, the problem should be on your power supply unit (PSU).
...
Answer 8 of 9
I had the same problem. I had tried everything but only on the j- micron port on my asus p5k I did not have the errors.
But when I put the drive to an other power supply it worked and the errors were gone. Then I put the drive back to its original power supply but a new power connector and that...
Answer 9 of 9
I know this thread is old, but just ran into the same issue, came here from google.
• getting ata3.01: failed command: READ FPDMA QUEUED on booting the KUBUNTU 16.04 livecd.
• WINDOWS 7 will behave erratically, works ok for a while, but freezes after watching youtube.
Changing the SATA cable...
[SOLVED] ata5: hard resetting link - UBUNTU 9.10 Karmic Cola - 2TB ...
https://ubuntuforums.org/showthread.php?t=1447138Traduire cette page
5 avr. 2010 - Every 30 mins my system has a SMART interrupt error, and has to "Hard reseting links" So every 30 mins, my other hard drives in my linux box restart, making a squelch ... I've read in a lot of places that this issue is at the kernal level, and effects all distrabutions such as Fedora, CentOS, Mint, ubuntu.... etc.HDD & SSD Linux: Hard resetting link - Super User
https://superuser.com/questions/464642/hdd-ssd-linux-hard-resetting-link
my current storage setup consists of two traditional HDD's and two SSD's in my Linux box, each... PLUS
my current storage setup consists of two traditional HDD's and two SSD's in my Linux box, each two on their own RAID 1 array which is encrypted via luks. I have a story of sorts, rather than a concrete question.
For over a year now, I've randomly gotten "hard resetting link" errors in the kernel log from some of my drives. I would RMA the problem drive, and the new drives would cause the problem to stop. A few months later, I would eventually start seeing the same error again at seemingly random times. The drive would be marked as failed in RAID and no longer showed up in fdisk -l. I would reboot the computer and the drive would show up again and I could re-add to the array and it would rebuild. Sooner or later that problem would happen again, usually a few hours later.
About six months ago, I replaced two of the traditional HDD's with SSD's in the hopes that they wouldn't have nearly as high of a failure rate as the traditional drives. However, over the past few days I started having problems with both one of the new SSD's and one of the traditional drives.
I'm starting to see a pattern emerge. I get a new drive, a few months later I start having problems with it. I always assumed it was due to HDD's having a high failure rate, but now it's happening with SSD's so I'm thinking it isn't the drive's fault. What else could be problem? I've had multiple OS's installed since I started having the problem so I want to rule out a software issue. This leaves either the SATA cables, or the motherboard. Could the disk encryption be putting too much stress on the drives? Is there anything I can do to determine more info? Thanks as always.
Below is the dmesg output of the problem from a question I asked a few months ago when I was having the same problem.
[43161.734107] ata3: ATA_REG 0x41 ERR_REG 0x84
[43161.734110] ata3: tag : dhfis dmafis sdbfis sactive
[43161.734113] ata3: tag 0x0: 1 1 0 1
[43161.734123] ata3.00: exception Emask 0x1 SAct 0x1 SErr 0x180000 action 0x6 frozen
[43161.734127] ata3.00: Ata error. fis:0x21
[43161.734130] ata3: SError: { 10B8B Dispar }
[43161.734134] ata3.00: failed command: READ FPDMA QUEUED
[43161.734142] ata3.00: cmd 60/08:00:a8:03:00/00:00:00:00:00/40 tag 0 ncq 4096 in
[43161.734144] res 41/84:04:a8:03:00/84:00:00:00:00/40 Emask 0x10 (ATA bus error)
[43161.734148] ata3.00: status: { DRDY ERR }
[43161.734150] ata3.00: error: { ICRC ABRT }
[43161.734155] ata3: hard resetting link
[43161.734158] ata3: nv: skipping hardreset on occupied port
[43162.220095] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[43162.260202] ata3.00: model number mismatch 'WDC WD2002FAEX-007BA0' != 'C WD2002FAEX-007BA0 '
[43162.260206] ata3.00: revalidation failed (errno=-19)
[43162.260211] ata3.00: limiting speed to UDMA/133:PIO2
[43167.220123] ata3: hard resetting link
[43167.220127] ata3: nv: skipping hardreset on occupied port
[43167.710060] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[43167.750228] ata3.00: model number mismatch 'WDC WD2002FAEX-007BA0' != 'C WD2002FAEX-007BA0 '
[43167.750232] ata3.00: revalidation failed (errno=-19)
[43167.750236] ata3.00: disabled
[43172.710100] ata3: hard resetting link
[43173.620110] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[43173.640455] ata3.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80)
[43178.620116] ata3: hard resetting link
[43179.530113] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[43179.550748] ata3.00: ATA-8: WDC WD2002FAEX-007BA0, 05.01D05, max UDMA/133
[43179.550753] ata3.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32)
[43179.570208] ata3.00: model number mismatch 'WDC WD2002FAEX-007BA0' != 'C WD2002FAEX-007BA0 '
[43179.570213] ata3.00: revalidation failed (errno=-19)
[43179.570220] ata3: limiting SATA link speed to 1.5 Gbps
[43179.570224] ata3.00: limiting speed to UDMA/133:PIO3
[43184.530066] ata3: hard resetting link
[43184.530070] ata3: nv: skipping hardreset on occupied port
[43185.020091] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[43185.060949] ata3.00: configured for UDMA/133
[43185.060969] sd 2:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[43185.060974] sd 2:0:0:0: [sdd] Sense Key : Aborted Command [current] [descriptor]
[43185.060980] Descriptor sense data with sense descriptors (in hex):
[43185.060983] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[43185.060995] 00 00 03 a8
[43185.061000] sd 2:0:0:0: [sdd] Add. Sense: Scsi parity error
[43185.061006] sd 2:0:0:0: [sdd] CDB: Read(10): 28 00 00 00 03 a8 00 00 08 00
[43185.061017] end_request: I/O error, dev sdd, sector 936
[43185.061023] Buffer I/O error on device sdd, logical block 117
[43185.061044] sd 2:0:0:0: rejecting I/O to offline device
[43185.061048] sd 2:0:0:0: killing request
[43185.061062] ata3: EH complete
[43185.061075] sd 2:0:0:0: rejecting I/O to offline device
[43185.061123] sd 2:0:0:0: rejecting I/O to offline device
[43185.061134] sd 2:0:0:0: rejecting I/O to offline device
[43185.061140] sd 2:0:0:0: rejecting I/O to offline device
[43185.061145] sd 2:0:0:0: [sdd] READ CAPACITY(16) failed
[43185.061147] sd 2:0:0:0: [sdd] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[43185.061152] sd 2:0:0:0: [sdd] Sense not available.
[43185.061155] sd 2:0:0:0: rejecting I/O to offline device
[43185.061166] sd 2:0:0:0: rejecting I/O to offline device
[43185.061175] sd 2:0:0:0: rejecting I/O to offline device
[43185.061185] sd 2:0:0:0: rejecting I/O to offline device
[43185.061193] sd 2:0:0:0: rejecting I/O to offline device
[43185.061198] sd 2:0:0:0: [sdd] READ CAPACITY failed
[43185.061202] sd 2:0:0:0: rejecting I/O to offline device
[43185.061209] sd 2:0:0:0: [sdd] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[43185.061215] sd 2:0:0:0: [sdd] Sense not available.
[43185.061226] sd 2:0:0:0: rejecting I/O to offline device
[43185.061235] sd 2:0:0:0: rejecting I/O to offline device
[43185.061245] sd 2:0:0:0: rejecting I/O to offline device
[43185.061254] sd 2:0:0:0: rejecting I/O to offline device
[43185.061263] sd 2:0:0:0: rejecting I/O to offline device
[43185.061274] sd 2:0:0:0: rejecting I/O to offline device
[43185.061280] sd 2:0:0:0: [sdd] Asking for cache data failed
[43185.061283] sd 2:0:0:0: [sdd] Assuming drive cache: write through
[43185.061289] sdd: detected capacity change from 2000398934016 to 0
[43185.061610] ata3.00: detaching (SCSI 2:0:0:0)
[43185.062444] sd 2:0:0:0: [sdd] Stopping disk
[43249.120042] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[43249.120046] ata4.00: failed command: FLUSH CACHE EXT
[43249.120051] ata4.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[43249.120052] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[43249.120054] ata4.00: status: { DRDY }
[43249.120059] ata4: hard resetting link
[43249.120060] ata4: nv: skipping hardreset on occupied port
[43249.610042] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[43249.650323] ata4.00: configured for UDMA/133
[43249.650326] ata4.00: retrying FLUSH 0xea Emask 0x4
[43249.650452] ata4.00: device reported invalid CHS sector 0
[43249.650458] ata4: EH complete
2 answers
Best Answer
You do have a question here. I think (if I understand correctly) what is the process to determine what is causing this failure?
I'm a Network Security Engineer. So understand I'm cringing while typing this. Eliminate this as a crypto problem. Decrypt the drives and see if you still have the...
Answer 2 of 2
It looks like you have a lot of errors on your SATA link. As a result, the host cannot get commands reliably across the link, and when it does sometimes the data returned is corrupted.
You see that in messages that the speed is limited, or that the expected drive identifier was not received. You...
Found many ATA link reset error in logs - Red Hat Customer Portal
https://access.redhat.com/solutions/293693Traduire cette page
21 déc. 2015 - messages:Aug 22 09:55:39 host1 kernel: ata1: hard resetting link messages:Aug 22 09:55:39 host1 kernel: ata2: hard resetting link messages:Aug 22 09:55:40 host1 kernel: ata2: hard resetting link messages:Aug 22 10:31:44 host1 kernel: ata1: hard resetting link messages:Aug 22 10:31:45 host1 kernel: ...SATA hard resetting link - Server Fault
https://serverfault.com/questions/211645/sata-hard-resetting-linkTraduire cette page
11 déc. 2010 - No, the Reallocated_Event_Count should not cause the error in dmesg. The error in dmesg indicates that communication between the drive and the host chipset locked up and the drive needed to be reset. If this only happens once, I wouldn't consider it significant. If it occurs regularly, I would begin to ...ata - {DRDY} - hard resetting link / LiveCD/LiveUSB / Forum Ubuntu ...
https://forum.ubuntu-fr.org › Forum › LiveCD/LiveUSB
9 févr. 2013 - 1 message - 1 auteur
Bonjour smile. Ayant récemment monté un nouveau PC, j'ai voulu installer Ubuntu sur clef USB... Je commence déjà avec un live (Ubuntu 12.04 Desktop 32bits) installé avec YUMI et testé sur un autre PC (il fonctionne). Seulement, sur mon PC j'obtiens une erreur pendant le chargement juste après avoir ...Bug #315912 “ata*: hard resetting link” : Bugs : linux package : Ubuntu
https://bugs.launchpad.net/bugs/315912Traduire cette page
10 janv. 2009 - Binary package hint: linux-image-2.6.27-7-server System is stalling every few seconds for 30 seconds each time. Syslog repeats following messages: [ 4842.388413] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen [ 4842.388457] ata1.00: cmd 35/00:08:3f:52:54/00:00:57:00:00/e0 tag 0 ...libata / SATA Error Messages During Linux Boot Sequence (exception ...
https://www.linuxquestions.org/...hardware.../libata-sata-error-mess...Traduire cette page
14 oct. 2017 - 8 messages - 6 auteurs
Exclamation libata / SATA Error Messages During Linux Boot Sequence (Est-ce que mon disque dur est en train de crever? - LinuxFr.org
linuxfr.org/forums/linux-general/.../est-ce-que-mon-disque-dur-est-en-train-de-crever
12 juin 2013 - 2 messages - 2 auteurs
... toutatis kernel: [749637.447344] ata1.00: SRST failed (errno=-16) Jun 12 09:SATA hard resetting link - CubieBoard Forum
www.cubieforums.com/index.php?topic=366.0Traduire cette page
9 juin 2013 - 2 messages
[ 203.100000] res 40/00:04:00:76:05/00:00:00:00:00/40 Emask 0x10 (ATA bus error) [ 203.130000] ata1.00: status: { DRDY } [ 203.130000] ata1: hard resetting link [ 203.890000] ata1: SATA link down (SStatus 0 SControl 310) [ 207.060000] ata1: hard resetting link [ 207.420000] ata1: SATA link up 1.5 Gbps ...