Ata bus error linux

Накрывается жесткий диск?

Заметил в messages такие сообщения:

Это жесткий диск или контроллер глючит?

Это кабель «от ветра» колышет. Или переткни или поставь другой

Словил такое один раз:

После этого пришлось перезагружаться reset-ом.

Ты кабель-то проверил, как тебе выше советовали 😕

Кабель перевоткнул. Можно конечно попробовать заменить.

Стоит попробовать. У меня так же было. Эти SATA-кабели слишком ненадёжны.

Кабель поменял. Вроде ошибок пока нет. Спасибо, потестирую.

такое началось опять. Видимо проблема не в кабеле 🙁

Данные S.M.A.R.T. в студию.

Показатели нормальные. Диск довольно старый. Неплохо бы погонять его на другом компьютере. Если проблем не будет, то, как уже сказали выше, это может быть контроллер.

У меня подобная ситуация:

Жесткий: WD1000EADS, 20 сентября купленный и отформатированный в ext3

Контроллер: вспомогательный Promise (вроде) sata378 (2 родных интеловских заняты другими жесткими).

dmesg выхлоп совпадает с твоим. Но был еще симптом: cat /dev/sdc вызывал такие ошибки буквально через несколько секунд после запуска — в начале диска проблема.

4 раза запускал fsck.ext3 -c (с проверкой на бэды). Всегда были помечены одни и теже сектора. Сейчас на жестком 15 гигов свободно, перевел в RO, буду смотреть.

smartctl -a /dev/sdc:

С сегодняшнего дня проблемы усилились. На компьютере, где он стоял загрузочным с него больше не загрузиться (почти :)). Подключил к другому компьютеру — без проблем читаю данные. Мистика. Грешу на контроллер.

Источник

Arch Linux

You are not logged in.

#1 2013-08-16 01:31:57

[SOLVED] Is this hard drive failing?

I noticed this in my errors.log this morning. Is my SSD on it’s way out.

Last edited by z1lt0id (2013-08-23 10:35:22)

#2 2013-08-16 02:03:11

Re: [SOLVED] Is this hard drive failing?

I noticed this in my errors.log this morning. Is my SSD on it’s way out.

#3 2013-08-16 02:27:59

Re: [SOLVED] Is this hard drive failing?

IMO, it’s something other than your drive. A few observations:

1) FPDMA is a NCQ function. NCQ requires the SATA controller to be in AHCI mode or RAID mode. If you have an old mobo, it’s possible that there are ‘issues’ with the AHCI implementation. It may even be possible that your controller isn’t in AHCI/RAID mode at all, and the commands were sent due to a bug.

2) A mobo of mine has issues when the controller is in AHCI mode. When I put the controller in RAID mode the problem disappears. RAID mode includes all the features/functions of AHCI, and Intel recommends using RAID mode rather than AHCI (Source), if only because ‘you might want to use it at some point’.

3) On the Ubuntu bug report linked by cpatrick08, post 126 recommended disabling NCQ on SSDs because «SSD drives don’t need to optimze the order of disk operationsm apparently it causes some errors». FWIW, Wikipedia disagrees. Still, it could be a good work-around if the errors are causing performance issues.

But whether the Constitution really be one thing, or another, this much is certain — that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner

Источник

Arch Linux

You are not logged in.

#1 2015-05-10 09:35:13

ATA bus error

Hello,
I have some problems with hard drive on my laptop. Sometimes everything freezes for few seconds (usually during start-up, but sometimes after I login) and I get some errors. After that, everything seems to be working fine.

Part of dmesg with errors:

Output of smartctl -a /dev/sda

Is this software bug or hard drive failure? Thanks in advance.

#2 2015-05-10 16:16:12

Re: ATA bus error

Those seek errors and raw read error rates are astronomical. This is a hard drive failure.

Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way

#3 2015-05-10 20:02:41

Re: ATA bus error

Those seek errors and raw read error rates are astronomical. This is a hard drive failure.

Not necessarily, this is a Seagate hard drive. AFAIK Seek Error Rate and Raw Read Error Rate are 48bit values where the lower 24bit encode the total number of sectors read/saught (which overflows to zero) and the upper 24bit encode the acutal errors.

should display OP’s data in a usuable format.

In fact, I turned my recently purchased laptop in for a hard disk replacement of almost the same type as OP (ST500LM000-SSHD-8GB) twice, but all three drives of this type I had provided SMART values which were more of an oracle rather than data useful for monitoring purposes. Forums are full with people unsure about what to do with this kind of drives. If you google for the End-to-End errors with Seagate drives (here marked as FAILING!), you’ll find people reporting that Seagate’s own tools do not report any errors despite the attribute in question being reported by monitoring tools just as bad. Seagate is the horror. So, I’d say that it is rather uncertain whether the SMART values are connected to the actual drive failing or a faulty cable.

OP, did you see these errors from the beginning or after a certain time, or perhaps after a kernel upgrade? Did you check the drive’s cable? What was the situation before these errors showed up (maybe under Windows?)

#4 2015-05-10 22:35:45

Re: ATA bus error

I’d never heard that; So much for trusting the instrumentation. I’ll watch this thread and see how it plays out.

Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way

#5 2015-05-10 22:39:49

Re: ATA bus error

Okay, point of reference. I too have a Seagate drive, but I don’t see the issue 😕

Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way

#6 2015-05-11 06:06:31

Re: ATA bus error

Here’s mine, it looks like all the drives I had before from the same model line looked like:

You can tell that my Seek Error Rate (although not Raw Reads) is worrying even according to the interpretation I gave (likewise, the Reallocated Event Count), but the service people (Lenovo Service, it’s a TP) refuse to exchange the drive a third time since short and long SMART test routines do not error out. As I said, I do not have verified information and do not know anybody who does know how to read these SMART values correctly. I gave up and am just waiting for the drive to fail.

Last edited by 2ion (2015-05-11 06:07:13)

#7 2015-05-11 10:24:56

Re: ATA bus error

Thanks for your answers.

Not necessarily, this is a Seagate hard drive. AFAIK Seek Error Rate and Raw Read Error Rate are 48bit values where the lower 24bit encode the total number of sectors read/saught (which overflows to zero) and the upper 24bit encode the acutal errors.

should display OP’s data in a usuable format.

In fact, I turned my recently purchased laptop in for a hard disk replacement of almost the same type as OP (ST500LM000-SSHD-8GB) twice, but all three drives of this type I had provided SMART values which were more of an oracle rather than data useful for monitoring purposes. Forums are full with people unsure about what to do with this kind of drives. If you google for the End-to-End errors with Seagate drives (here marked as FAILING!), you’ll find people reporting that Seagate’s own tools do not report any errors despite the attribute in question being reported by monitoring tools just as bad. Seagate is the horror. So, I’d say that it is rather uncertain whether the SMART values are connected to the actual drive failing or a faulty cable.

OP, did you see these errors from the beginning or after a certain time, or perhaps after a kernel upgrade? Did you check the drive’s cable? What was the situation before these errors showed up (maybe under Windows?)

smartctl -v 1,hex48 -v 7,hex48 -a /dev/sda

These errors just appeared, not after upgrade and I didn’t get them in the beginning. The situation before errors — everything worked exactly the same, I see no difference in performance, except that few seconds long freeze that sometimes happen. Can’t tell about Windows, I have it pre-installed but never used it so I can’t compare. I didn’t check the cable, and I’d rather not do that — I don’t want to mess with hardware, if I do something wrong I lose the warranty. If something is wrong then I’d rather have it checked and fixed by someone who knows how to do that (and for free, because I still have the warranty).

Источник

Arch Linux

You are not logged in.

#1 2019-03-24 09:22:05

exception Emask 0x50 ATA bus errors on fresh Arch install (unusable)

I have installed Arch Linux on my main desktop computer yesterday. Until then, I was using debian stable for about two years on it. I had no issues.

The install part went smoothly. I chose XFCE DE with full disk encryption.

After a while however, the machine froze completely. After a few tests I was able to describe the following behavior:

1. Whenever some network activity is triggered, such as downloading a file or even opening Firefox, the kernel starts throwing all kind of errors relating to ATA errors, and the computer starts to slow down. It seems to be constantly resetting the SATA link, eventually it results in a complete freeze or a remount in read-only mode (see kernel messages below)
2. This does not seem to happen when I am writing files unto the disk without network activity.
3. SMART test are OK for this disk (very recent, used debian stable on it for 4-5 months without problems).
4. This does not happen when I boot the disk from a USB-SATA adapter (disk currently connected to USB port and running fine now).
5. Changing SATA cables did not solve the problem.
6. Using the same SATA cables with debian stable on an encrypted SSD does not cause these errors, it only happens in Arch Linux (so apparently no hardware failure on the PC side)
7. Replacing the current kernel with the lts version did not solve the problem

I am completely lost at this point. I have no idea how to solve this problem and where to start from. Again, hardware does not seem to be the problem here: I have no issues using another disk with debian stable, and I have no issues when connecting the Arch disk with a USB-SATA adapter. Any suggestion welcome.

My hardware specs are as follows:

CPU i7-4790
Motherboard Gigabyte Z87M-D3H
GPU Radeon R9 270X
SSD Samsung 860EVO 1TB

The kernel messages that I receive:

[ 69.004732] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 69.006641] ata1.00: supports DRM functions and may not be fully accessible
[ 69.010168] ata1.00: supports DRM functions and may not be fully accessible
[ 69.012999] ata1.00: configured for UDMA/133
[ 69.013053] ata1.00: Enabling discard_zeroes_data
[ 74.394764] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 74.396686] ata1.00: supports DRM functions and may not be fully accessible
[ 74.400156] ata1.00: supports DRM functions and may not be fully accessible
[ 74.403093] ata1.00: configured for UDMA/133
[ 74.403159] ata1.00: Enabling discard_zeroes_data
[ 76.614785] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 76.616652] ata1.00: supports DRM functions and may not be fully accessible
[ 76.619944] ata1.00: supports DRM functions and may not be fully accessible
[ 76.622687] ata1.00: configured for UDMA/133
[ 76.622750] ata1.00: Enabling discard_zeroes_data
[ 80.975983] ata1: limiting SATA link speed to 3.0 Gbps
[ 81.704763] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 81.706738] ata1.00: supports DRM functions and may not be fully accessible
[ 81.710280] ata1.00: supports DRM functions and may not be fully accessible
[ 81.713071] ata1.00: configured for UDMA/133
[ 81.713142] ata1.00: Enabling discard_zeroes_data
[ 83.344778] ata1: SATA link down (SStatus 0 SControl 320)
[ 88.756472] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 88.758370] ata1.00: supports DRM functions and may not be fully accessible
[ 88.761694] ata1.00: supports DRM functions and may not be fully accessible
[ 88.764534] ata1.00: configured for UDMA/133
[ 88.764637] ata1.00: Enabling discard_zeroes_data
[ 89.664779] ata1.00: exception Emask 0x50 SAct 0xff0 SErr 0x4890800 action 0xe frozen
[ 89.664785] ata1.00: irq_stat 0x08400040, interface fatal error, connection status changed
[ 89.664788] ata1: SError: < HostInt PHYRdyChg 10B8B LinkSeq DevExch >
[ 89.664792] ata1.00: failed command: WRITE FPDMA QUEUED
[ 89.664799] ata1.00: cmd 61/40:20:80:ea:45/05:00:10:00:00/40 tag 4 ncq dma 688128 out
res 40/00:28:c0:ef:45/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 89.664802] ata1.00: status: < DRDY >
[ 89.664805] ata1.00: failed command: WRITE FPDMA QUEUED
[ 89.664812] ata1.00: cmd 61/40:28:c0:ef:45/00:00:10:00:00/40 tag 5 ncq dma 32768 out
res 40/00:28:c0:ef:45/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 89.664815] ata1.00: status: < DRDY >
[ 89.664817] ata1.00: failed command: WRITE FPDMA QUEUED
[ 89.664824] ata1.00: cmd 61/40:30:00:f0:45/05:00:10:00:00/40 tag 6 ncq dma 688128 out
res 40/00:28:c0:ef:45/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 89.664826] ata1.00: status: < DRDY >
[ 89.664829] ata1.00: failed command: WRITE FPDMA QUEUED
[ 89.664835] ata1.00: cmd 61/40:38:40:f5:45/05:00:10:00:00/40 tag 7 ncq dma 688128 out
res 40/00:28:c0:ef:45/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 89.664838] ata1.00: status: < DRDY >
[ 89.664840] ata1.00: failed command: WRITE FPDMA QUEUED
[ 89.664847] ata1.00: cmd 61/40:40:80:fa:45/05:00:10:00:00/40 tag 8 ncq dma 688128 out
res 40/00:28:c0:ef:45/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 89.664849] ata1.00: status: < DRDY >
[ 89.664852] ata1.00: failed command: WRITE FPDMA QUEUED
[ 89.664858] ata1.00: cmd 61/40:48:c0:ff:45/00:00:10:00:00/40 tag 9 ncq dma 32768 out
res 40/00:28:c0:ef:45/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 89.664861] ata1.00: status: < DRDY >
[ 89.664863] ata1.00: failed command: WRITE FPDMA QUEUED
[ 89.664870] ata1.00: cmd 61/40:50:00:00:46/05:00:10:00:00/40 tag 10 ncq dma 688128 out
res 40/00:28:c0:ef:45/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 89.664873] ata1.00: status: < DRDY >
[ 89.664875] ata1.00: failed command: WRITE FPDMA QUEUED
[ 89.664881] ata1.00: cmd 61/40:58:40:05:46/05:00:10:00:00/40 tag 11 ncq dma 688128 out
res 40/00:28:c0:ef:45/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 89.664884] ata1.00: status: < DRDY >
[ 89.664888] ata1: hard resetting link
[ 90.404756] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 90.406630] ata1.00: supports DRM functions and may not be fully accessible
[ 90.410001] ata1.00: supports DRM functions and may not be fully accessible
[ 90.412862] ata1.00: configured for UDMA/133
[ 90.412884] ata1: EH complete
[ 90.412960] ata1.00: Enabling discard_zeroes_data
[ 90.744760] ata1.00: exception Emask 0x50 SAct 0x60000001 SErr 0x4890800 action 0xe frozen
[ 90.744766] ata1.00: irq_stat 0x08400040, interface fatal error, connection status changed
[ 90.744769] ata1: SError: < HostInt PHYRdyChg 10B8B LinkSeq DevExch >
[ 90.744773] ata1.00: failed command: WRITE FPDMA QUEUED
[ 90.744780] ata1.00: cmd 61/40:00:00:50:47/05:00:10:00:00/40 tag 0 ncq dma 688128 out
res 40/00:f0:c0:4f:47/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 90.744784] ata1.00: status: < DRDY >
[ 90.744787] ata1.00: failed command: WRITE FPDMA QUEUED
[ 90.744793] ata1.00: cmd 61/40:e8:80:4a:47/05:00:10:00:00/40 tag 29 ncq dma 688128 out
res 40/00:f0:c0:4f:47/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 90.744796] ata1.00: status: < DRDY >
[ 90.744799] ata1.00: failed command: WRITE FPDMA QUEUED
[ 90.744805] ata1.00: cmd 61/40:f0:c0:4f:47/00:00:10:00:00/40 tag 30 ncq dma 32768 out
res 40/00:f0:c0:4f:47/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 90.744808] ata1.00: status: < DRDY >
[ 90.744812] ata1: hard resetting link
[ 91.664775] ata1: SATA link down (SStatus 0 SControl 320)
[ 96.734748] ata1: hard resetting link
[ 97.066816] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 97.068830] ata1.00: supports DRM functions and may not be fully accessible
[ 97.072430] ata1.00: supports DRM functions and may not be fully accessible
[ 97.075377] ata1.00: configured for UDMA/133
[ 97.075401] ata1: EH complete
[ 97.075559] ata1.00: Enabling discard_zeroes_data
[ 97.154789] ata1: limiting SATA link speed to 1.5 Gbps
[ 97.154795] ata1.00: exception Emask 0x50 SAct 0x400ffa04 SErr 0x4890800 action 0xe frozen
[ 97.154802] ata1.00: irq_stat 0x08400040, interface fatal error, connection status changed
[ 97.154808] ata1: SError: < HostInt PHYRdyChg 10B8B LinkSeq DevExch >
[ 97.154815] ata1.00: failed command: WRITE FPDMA QUEUED
[ 97.154828] ata1.00: cmd 61/40:10:80:4a:47/05:00:10:00:00/40 tag 2 ncq dma 688128 out
res 40/00:48:40:55:47/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 97.154834] ata1.00: status: < DRDY >
[ 97.154838] ata1.00: failed command: WRITE FPDMA QUEUED
[ 97.154851] ata1.00: cmd 61/40:48:40:55:47/05:00:10:00:00/40 tag 9 ncq dma 688128 out
res 40/00:48:40:55:47/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 97.154856] ata1.00: status: < DRDY >
[ 97.154860] ata1.00: failed command: WRITE FPDMA QUEUED
[ 97.154872] ata1.00: cmd 61/d0:58:80:5a:47/03:00:10:00:00/40 tag 11 ncq dma 499712 out
res 40/00:48:40:55:47/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 97.154877] ata1.00: status: < DRDY >
[ 97.154881] ata1.00: failed command: WRITE FPDMA QUEUED
[ 97.154893] ata1.00: cmd 61/40:60:00:90:47/05:00:10:00:00/40 tag 12 ncq dma 688128 out
res 40/00:48:40:55:47/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 97.154898] ata1.00: status: < DRDY >
[ 97.154902] ata1.00: failed command: WRITE FPDMA QUEUED
[ 97.154913] ata1.00: cmd 61/40:68:40:95:47/05:00:10:00:00/40 tag 13 ncq dma 688128 out
res 40/00:48:40:55:47/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 97.154918] ata1.00: status: < DRDY >
[ 97.154922] ata1.00: failed command: WRITE FPDMA QUEUED
[ 97.154934] ata1.00: cmd 61/40:70:80:9a:47/05:00:10:00:00/40 tag 14 ncq dma 688128 out
res 40/00:48:40:55:47/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 97.154939] ata1.00: status: < DRDY >
[ 97.154943] ata1.00: failed command: WRITE FPDMA QUEUED
[ 97.154955] ata1.00: cmd 61/40:78:c0:9f:47/00:00:10:00:00/40 tag 15 ncq dma 32768 out
res 40/00:48:40:55:47/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 97.154960] ata1.00: status: < DRDY >
[ 97.154964] ata1.00: failed command: WRITE FPDMA QUEUED
[ 97.154976] ata1.00: cmd 61/40:80:40:a5:47/05:00:10:00:00/40 tag 16 ncq dma 688128 out
res 40/00:48:40:55:47/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 97.154980] ata1.00: status: < DRDY >
[ 97.154985] ata1.00: failed command: WRITE FPDMA QUEUED
[ 97.154996] ata1.00: cmd 61/40:88:80:aa:47/05:00:10:00:00/40 tag 17 ncq dma 688128 out
res 40/00:48:40:55:47/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 97.155001] ata1.00: status: < DRDY >
[ 97.155005] ata1.00: failed command: WRITE FPDMA QUEUED
[ 97.155017] ata1.00: cmd 61/40:90:00:50:47/05:00:10:00:00/40 tag 18 ncq dma 688128 out
res 40/00:48:40:55:47/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 97.155022] ata1.00: status: < DRDY >
[ 97.155026] ata1.00: failed command: WRITE FPDMA QUEUED
[ 97.155038] ata1.00: cmd 61/40:98:c0:4f:47/00:00:10:00:00/40 tag 19 ncq dma 32768 out
res 40/00:48:40:55:47/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 97.155043] ata1.00: status: < DRDY >
[ 97.155047] ata1.00: failed command: WRITE FPDMA QUEUED
[ 97.155059] ata1.00: cmd 61/40:f0:00:a0:47/05:00:10:00:00/40 tag 30 ncq dma 688128 out
res 40/00:48:40:55:47/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
[ 97.155064] ata1.00: status: < DRDY >
[ 97.155070] ata1: hard resetting link
[ 97.884756] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 97.886638] ata1.00: supports DRM functions and may not be fully accessible
[ 97.890135] ata1.00: supports DRM functions and may not be fully accessible
[ 97.892980] ata1.00: configured for UDMA/133
[ 97.893026] ata1: EH complete
[ 97.893086] ata1.00: Enabling discard_zeroes_data
[ 105.474760] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 105.476697] ata1.00: supports DRM functions and may not be fully accessible
[ 105.480206] ata1.00: supports DRM functions and may not be fully accessible
[ 105.483163] ata1.00: configured for UDMA/133
[ 105.483220] ata1.00: Enabling discard_zeroes_data
[ 106.884761] ata1: SATA link down (SStatus 0 SControl 310)

Источник