2
1
Заметил в messages такие сообщения:
Apr 5 21:30:49 schultz kernel: ata1.00: exception Emask 0x10 SAct 0x1 SErr 0x4010000 action 0xe frozen
Apr 5 21:30:49 schultz kernel: ata1.00: irq_stat 0x00400040, connection status changed
Apr 5 21:30:49 schultz kernel: ata1: SError: { PHYRdyChg DevExch }
Apr 5 21:30:49 schultz kernel: ata1.00: failed command: READ FPDMA QUEUED
Apr 5 21:30:49 schultz kernel: ata1.00: cmd 60/20:00:07:ee:e2/00:00:02:00:00/40 tag 0 ncq 16384 in
Apr 5 21:30:49 schultz kernel: res 40/00:04:07:ee:e2/00:00:02:00:00/40 Emask 0x10 (ATA bus error)
Apr 5 21:30:49 schultz kernel: ata1.00: status: { DRDY }
Apr 5 21:30:49 schultz kernel: ata1: hard resetting link
Apr 5 21:30:55 schultz kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Apr 5 21:30:55 schultz kernel: ata1.00: configured for UDMA/133
Apr 5 21:30:55 schultz kernel: ata1: EH complete
Apr 5 21:30:56 schultz kernel: ata1.00: exception Emask 0x10 SAct 0x1 SErr 0x4010000 action 0xe frozen
Apr 5 21:30:56 schultz kernel: ata1.00: irq_stat 0x00400040, connection status changed
Apr 5 21:30:56 schultz kernel: ata1: SError: { PHYRdyChg DevExch }
Apr 5 21:30:56 schultz kernel: ata1.00: failed command: READ FPDMA QUEUED
Apr 5 21:30:56 schultz kernel: ata1.00: cmd 60/08:00:d7:f4:e1/00:00:02:00:00/40 tag 0 ncq 4096 in
Apr 5 21:30:56 schultz kernel: res 40/00:04:d7:f4:e1/00:00:02:00:00/40 Emask 0x10 (ATA bus error)
Apr 5 21:30:56 schultz kernel: ata1.00: status: { DRDY }
Apr 5 21:30:56 schultz kernel: ata1: hard resetting link
Apr 5 21:31:02 schultz kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Apr 5 21:31:02 schultz kernel: ata1.00: configured for UDMA/133
Apr 5 21:31:02 schultz kernel: ata1: EH complete
Это жесткий диск или контроллер глючит?
Asked
4 years, 6 months ago
Viewed
13k times
[ 108.138078] ata1.00: exception Emask 0x10 SAct 0x40000 SErr 0x400100 action 0x6 frozen
[ 108.138085] ata1.00: irq_stat 0x08000000, interface fatal error
[ 108.138090] ata1: SError: { UnrecovData Handshk }
[ 108.138095] ata1.00: failed command: WRITE FPDMA QUEUED
[ 108.138106] ata1.00: cmd 61/c8:90:00:10:c6/03:00:5f:00:00/40 tag 18 ncq dma 495616 out
res 40/00:94:00:10:c6/00:00:5f:00:00/40 Emask 0x10 (ATA bus error)
[ 108.138111] ata1.00: status: { DRDY }
[ 108.138116] ata1: hard resetting link
[ 108.453212] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 108.465868] ata1.00: configured for UDMA/133
[ 108.465881] ata1: EH complete
[ 118.396927] ata1.00: exception Emask 0x10 SAct 0x8000 SErr 0x400100 action 0x6 frozen
[ 118.396936] ata1.00: irq_stat 0x08000000, interface fatal error
[ 118.396942] ata1: SError: { UnrecovData Handshk }
[ 118.396949] ata1.00: failed command: WRITE FPDMA QUEUED
[ 118.396964] ata1.00: cmd 61/50:78:d8:44:a8/03:00:70:00:00/40 tag 15 ncq dma 434176 out
res 40/00:7c:d8:44:a8/00:00:70:00:00/40 Emask 0x10 (ATA bus error)
[ 118.396970] ata1.00: status: { DRDY }
[ 118.396978] ata1: hard resetting link
[ 118.712315] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 118.725463] ata1.00: configured for UDMA/133
[ 118.725485] ata1: EH complete
[ 133.731533] ata1.00: exception Emask 0x10 SAct 0x7c00 SErr 0x400100 action 0x6 frozen
[ 133.731537] ata1.00: irq_stat 0x08000000, interface fatal error
[ 133.731540] ata1: SError: { UnrecovData Handshk }
[ 133.731543] ata1.00: failed command: WRITE FPDMA QUEUED
[ 133.731549] ata1.00: cmd 61/f0:50:c8:17:91/00:00:70:00:00/40 tag 10 ncq dma 122880 out
res 40/00:74:70:a4:85/00:00:70:00:00/40 Emask 0x10 (ATA bus error)
[ 133.731552] ata1.00: status: { DRDY }
[ 133.731554] ata1.00: failed command: WRITE FPDMA QUEUED
[ 133.731559] ata1.00: cmd 61/a8:58:d8:64:91/02:00:70:00:00/40 tag 11 ncq dma 348160 out
res 40/00:74:70:a4:85/00:00:70:00:00/40 Emask 0x10 (ATA bus error)
[ 133.731562] ata1.00: status: { DRDY }
[ 133.731564] ata1.00: failed command: WRITE FPDMA QUEUED
[ 133.731569] ata1.00: cmd 61/08:60:78:13:84/00:00:70:00:00/40 tag 12 ncq dma 4096 out
res 40/00:74:70:a4:85/00:00:70:00:00/40 Emask 0x10 (ATA bus error)
[ 133.731572] ata1.00: status: { DRDY }
[ 133.731574] ata1.00: failed command: WRITE FPDMA QUEUED
[ 133.731579] ata1.00: cmd 61/08:68:b8:13:84/00:00:70:00:00/40 tag 13 ncq dma 4096 out
res 40/00:74:70:a4:85/00:00:70:00:00/40 Emask 0x10 (ATA bus error)
[ 133.731581] ata1.00: status: { DRDY }
[ 133.731583] ata1.00: failed command: WRITE FPDMA QUEUED
[ 133.731588] ata1.00: cmd 61/10:70:70:a4:85/00:00:70:00:00/40 tag 14 ncq dma 8192 out
res 40/00:74:70:a4:85/00:00:70:00:00/40 Emask 0x10 (ATA bus error)
[ 133.731591] ata1.00: status: { DRDY }
[ 133.731594] ata1: hard resetting link
[ 134.047939] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 134.061108] ata1.00: configured for UDMA/133
[ 134.061136] ata1: EH complete
asked Jul 28, 2018 at 9:07
1
You have NCQ disk errors, See here
Edit your /etc/default/grub file and change the following:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash libata.force=noncq"
Save the changes and update GRUB, and reboot:
sudo update-grub
reboot
And see if the problem is solved. If not, undo these changes, and suspect a bad SATA port, SATA cable, or a possible bad hard drive.
answered Jul 28, 2018 at 14:24
heynnemaheynnema
66.1k13 gold badges115 silver badges170 bronze badges
Содержание
- Накрывается жесткий диск?
- Arch Linux
- #1 2015-05-10 09:35:13
- ATA bus error
- #2 2015-05-10 16:16:12
- Re: ATA bus error
- #3 2015-05-10 20:02:41
- Re: ATA bus error
- #4 2015-05-10 22:35:45
- Re: ATA bus error
- #5 2015-05-10 22:39:49
- Re: ATA bus error
- #6 2015-05-11 06:06:31
- Re: ATA bus error
- #7 2015-05-11 10:24:56
- Re: ATA bus error
- SSD мёртв? Советы по выбору SSD.
Накрывается жесткий диск?
Заметил в 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 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 jsoy9pQbYVNu5nfU (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).
Источник
SSD мёртв? Советы по выбору SSD.
Дело было вечером. потух экран и всё повисло. После перезапуска попадаю в консоль. Пишет, что корень в read-only. Корень на SSD, которому уже 4.5 года. Видимо пришло его время.
SATA 2 — это проверял входы.
Судя по всему — дело плохо.
SSD, последний раз, выбрал лет 5 назад, не слежу за ними. Какой поcоветует лор? Гугл предлагает брать Samsung 860 PRO (текущий — Intel 520). Разьем только SATA.
PRO имеет смысл брать только если ты рассчитываешь пользоваться уже покойным SATA более пяти лет. Гарантийный ресурс с EVO у них одинаковый.
9 Power_On_Hours_and_Msec 0x0032 000 000 000 Old_age Always — 918778h+27m+32.720s
В смарте ничего особо криминального, переназначений блоков даже нет. Но возможно контроллер сдох.
Судя по всему, smart работает так, что не работает
Вы про мою материнку или про сам разъем? Я вижу что M2/PCI довольно популярны, но первого у меня нет, а второй стоит как самолёт.
Кабель менять не пробовал сначала?
Главное SSD не выкидывай — я серъёзно.
Отдай сосёду, у котрого венда, у него заработает.
Про сам протокол. Я, конечно, преувеличиваю, но что потребительский, что серверный сегменты действительно потихоньку уходят от SATA.
Из двух потребительских самсунгов выбирать можно тупо по гарантийному сроку.
Хм. Помогло. Хз на сколько его хватит. Может через пол часа опять заглючит.
Винда его вообще не видит.
Многих SSD в hwdb нет, потому такие весёлые вещи бывают.
Если интерпретировать «дословно»
32*149228 = 4 775 296
И 7.2 TB — это ничто для диска на 100 GB.
Объём диска какой?
Значения смарта с новым кабелем теже самые?
60ГБ. Диску, как оказалось, 5 лет уже.
С другим кабелем уже 2 часа аптайм. Хз что это было.
Сейчас запустил self-test=long на 48 мин. Жду.
Samsung EVO/PRO. /thread
Бережёшь ресурс. Диск, наверняка, только под корень, даже /var, небось, вынес, не так?
Если записано 7.2 TB — то это 120 записей на ячейку. Очень мало.
и как обычно лор соетут херню
А ну-ка, посоветуй не херню.
Ага. Куча симлинков и tmpfs. Когда покупал — пугали, что через пару лет сдохнет.
Хотя хомяк не выносил.
Поменял кабель — пока жив.
В любом случае купил 860 evo. Не помешает.
новый ssd -> hdd -> старый ssd
У discard в fstab.
А что делает discard?
Для того, что бы вернуться к «начальному» состоянию диска, надо
Write performance is known to degrade over time even on SSDs with native TRIM support.
(Все твои файлы будут безвозвратно уничтожены, надеюсь, понимаешь.)
Этот тест я делал уже после форматирования. Сейчас ещё и это попробую.
В теории, тоже самое.
Не из под линя, не из под винды не даёт стереть.
Почитай описание опции, что ли. Спойлер: нет, не то же самое.
и оставить диск в покое минут на 20 (с питанием), дабы он ячейки почистил.
В чём разница? С точки зрения ядра вроде бы одно и то же.
В том, что fstrim обрабатывает TRIM’ами всё свободное место, которое есть, а опция discard делает «reclaim space freed by the filesystem». Чтобы гарантированно покрыть TRIM’ами всё доступное свободное место, нужно сначала насоздавать файлов, а потом их удалить. Проще и быстрее один раз fstrim вручную запустить.
А, ну это понятно. Я думал, ты про какую-то разницу внутри. Тоже запускаю fstrim раз в несколько месяцев для профилактики, а опцию монтирования не использую.
для начала попробуй провод sata поменять. в smart вроде криминала кроме кривой наработки не видно.
Уже нашел. Правда у меня он за пару минут справился.
Так что, discard не нужен? У меня он уже 5 лет включен.
Дело не в этом. Дело в том, что хотя при включенном discard в асимптотике ты имеешь все свободные ячейки trim’нутыми, там слишком много «если». Раз чистятся только освобождённые блоки, для очистки блок нужно освободить.
Прошивка то актуальная хоть?
P.S. А хотя она как была 400i так и осталась.
Именно она. Они быстро забили на поддержку.
меня уже эти ssd задолбали — то пропадают, выну полежат — после чего появляются снова, поначалу покупал радуясь визуальному приросту производительности — больше не буду, уж лучше hdd — некоторым по 15 лет и ничего работают, правда говорят сейчас научились делать так что бы они ломались в течении года. так что еду пока на старых запасах
Сидите в криокамере дальше.
Только аккуратнее с опцией discard на прошках. Может ФС посыпаться. Проходил.
Я в итоге evo взял.
У них вроде такой проблемы с discard нет.
В принципе сейчас они все ппочти одинаковы Бодьшое количество записей — запросов быстро убъёт любой SSD Postgresql сожрал за полтора года. Теперь работаю только в связке с HDD
Очень толсто, бро.
Бодьшое количество записей — запросов быстро убъёт любой SSD Postgresql сожрал за полтора года.
Источник
| View previous topic :: View next topic | |||||||||||
| Author | Message | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| pandaxiongmao Guru  
Joined: 29 Sep 2003 |
|
||||||||||
| Back to top |
|
||||||||||
 |
|||||||||||
| didymos Advocate  
Joined: 10 Oct 2005 |
|
||||||||||
| Back to top |
|
||||||||||
|
|||||||||||
| pandaxiongmao Guru
Joined: 29 Sep 2003 |
|
||||||||||
| Back to top |
|
||||||||||
|
|||||||||||
| pandaxiongmao Guru
Joined: 29 Sep 2003 |
|
||||||||||
| Back to top |
|
||||||||||
|
|||||||||||
|
|
You cannot post new topics in this forum |
Модератор: weec
Правила форума
Убедительная просьба юзать теги [cоde] при оформлении листингов.
Сообщения не оформленные должным образом имеют все шансы быть незамеченными.
-
kpp
- лейтенант
- Сообщения: 613
- Зарегистрирован: 2009-08-05 16:10:46
- Откуда: Украина Днепропетровск-Киев
- Контактная информация:
Ошибки SATA: exception Emask
Линукс дебиан.
Контроллер St-lab A-370 (Marvell 88SX7042) вставлен в PCIe16x.
С разной периодичностью по одному порту(на этом порту висит WD10EADS порт вышеописанного контроллера) проскакивает одна и таже ошибка:
Код: Выделить всё
ata8: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen
ata8: edma_err_cause=00000020 pp_flags=00000002, SError=00180000
ata8: SError: { 10B8B Dispar }
ata8: hard resetting link
ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata8.00: configured for UDMA/133
ata8: EH complete
sd 7:0:0:0: [sde] 1953525168 512-byte hardware sectors (1000205 MB)
sd 7:0:0:0: [sde] Write Protect is off
sd 7:0:0:0: [sde] Mode Sense: 00 3a 00 00
sd 7:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
На просторах инета вычитал что возможно проблема с несовместимостью ядра с NCQ.
Ищу как отключить поддержку ядром NCQ.(Если кто подскажет — буду благодарен 
)
Чем черевато, как лечить?
Нет, ребята, я не гордый. Не загадывая вдаль, так скажу: зачем мне орден? Я согласен на медаль.
-
Хостинг HostFood.ru
Услуги хостинговой компании Host-Food.ru
Хостинг HostFood.ru
Тарифы на хостинг в России, от 12 рублей: https://www.host-food.ru/tariffs/hosting/
Тарифы на виртуальные сервера (VPS/VDS/KVM) в РФ, от 189 руб.: https://www.host-food.ru/tariffs/virtualny-server-vps/
Выделенные сервера, Россия, Москва, от 2000 рублей (HP Proliant G5, Intel Xeon E5430 (2.66GHz, Quad-Core, 12Mb), 8Gb RAM, 2x300Gb SAS HDD, P400i, 512Mb, BBU):
https://www.host-food.ru/tariffs/vydelennyi-server-ds/
Недорогие домены в популярных зонах: https://www.host-food.ru/domains/
-
kpp
- лейтенант
- Сообщения: 613
- Зарегистрирован: 2009-08-05 16:10:46
- Откуда: Украина Днепропетровск-Киев
- Контактная информация:
Re: Ошибки SATA: exception Emask
Непрочитанное сообщение
kpp » 2010-03-26 13:45:41
В дополнение к первому посту, этот же Debian Lenny (Linux 2.6.26-2-amd64) не всегда грузится с первого раза,
часто не может увидеть разделы на системном диске
см. фото1:ftp://hi.dp.ua/pub/Debian/Debian_Probl1.jpg,
фото2:ftp://hi.dp.ua/pub/Debian/Debian_Probl2.jpg
Так же смущают строки (см фото1):
Код: Выделить всё
ata5 : softreset failed (device not redy)
ata6 : softreset failed (device not redy)
ata7 : softreset failed (device not redy)
ata8 : softreset failed (device not redy)
Подозрение на контроллер St-Lab A-370(Marvell 88SX7042) PCIe4X,
вставленный в слот 16X.
При копировании на этот винт (ata8 sde) в лог плотно сыпятся ошибки:
Код: Выделить всё
ata8.00: cmd 61/00:08:cf:fd:46/04:00:00:00:00/40 tag 1 ncq 524288 out
res 40/00:4c:cf:1d:47/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
ata8.00: status: { DRDY }
ata8.00: cmd 61/f8:10:cf:01:47/03:00:00:00:00/40 tag 2 ncq 520192 out
res 40/00:4c:cf:1d:47/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
ata8.00: status: { DRDY }
ata8.00: cmd 61/00:18:cf:05:47/04:00:00:00:00/40 tag 3 ncq 524288 out
res 40/00:4c:cf:1d:47/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
ata8.00: status: { DRDY }
ata8.00: cmd 61/00:20:cf:09:47/04:00:00:00:00/40 tag 4 ncq 524288 out
res 40/00:4c:cf:1d:47/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
ata8.00: status: { DRDY }
ata8.00: cmd 61/00:28:cf:0d:47/04:00:00:00:00/40 tag 5 ncq 524288 out
res 40/00:4c:cf:1d:47/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
ata8.00: status: { DRDY }
ata8.00: cmd 61/00:30:cf:11:47/04:00:00:00:00/40 tag 6 ncq 524288 out
res 40/00:4c:cf:1d:47/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
ata8.00: status: { DRDY }Нет, ребята, я не гордый. Не загадывая вдаль, так скажу: зачем мне орден? Я согласен на медаль.
-
Gerk
- сержант
- Сообщения: 194
- Зарегистрирован: 2009-09-23 23:01:37
- Откуда: Симферополь, UA
Re: Ошибки SATA: exception Emask
Непрочитанное сообщение
Gerk » 2010-03-26 19:27:53
параметр /sys/block/<HDD>/device/queue_depth в 1цу пробовали изменять?
-
kpp
- лейтенант
- Сообщения: 613
- Зарегистрирован: 2009-08-05 16:10:46
- Откуда: Украина Днепропетровск-Киев
- Контактная информация:
Re: Ошибки SATA: exception Emask
Непрочитанное сообщение
kpp » 2010-04-13 12:58:53
Сдал Контроллер St-lab A-370 (Marvell 88SX7042) по гарантии.
Обещают поменять. А там посмотрим.
Нет, ребята, я не гордый. Не загадывая вдаль, так скажу: зачем мне орден? Я согласен на медаль.
smartctl version 5.38 [x86_64-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Model Family: SAMSUNG SpinPoint P80 SD series
Device Model: SAMSUNG HD160JJ
Serial Number: S08HJ10YB33273
Firmware Version: ZM100-33
User Capacity: 160,041,885,696 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: ATA/ATAPI-7 T13 1532D revision 4a
Local Time is: Mon Aug 17 11:43:51 2009 CEST
SMART support is: Available — device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x84) Offline data collection activity
was suspended by an interrupting command from host.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (3654) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 60) minutes.
SCT capabilities: (0x003f) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 100 100 051 Pre-fail Always — 1
3 Spin_Up_Time 0x0007 100 100 025 Pre-fail Always — 6208
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always — 520
5 Reallocated_Sector_Ct 0x0033 253 253 010 Pre-fail Always — 0
7 Seek_Error_Rate 0x000f 253 253 051 Pre-fail Always — 0
8 Seek_Time_Performance 0x0025 253 253 015 Pre-fail Offline — 0
9 Power_On_Hours 0x0032 100 100 000 Old_age Always — 30817
10 Spin_Retry_Count 0x0033 253 253 051 Pre-fail Always — 0
11 Calibration_Retry_Count 0x0012 253 002 000 Old_age Always — 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always — 388
190 Airflow_Temperature_Cel 0x0022 100 058 000 Old_age Always — 46
194 Temperature_Celsius 0x0022 100 058 000 Old_age Always — 46
195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always — 67415327
196 Reallocated_Event_Count 0x0032 253 253 000 Old_age Always — 0
197 Current_Pending_Sector 0x0012 253 253 000 Old_age Always — 0
198 Offline_Uncorrectable 0x0030 253 253 000 Old_age Offline — 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always — 1723
200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always — 0
201 Soft_Read_Error_Rate 0x000a 100 100 000 Old_age Always — 0
202 TA_Increase_Count 0x0032 253 253 000 Old_age Always — 0
SMART Error Log Version: 1
ATA Error Count: 1707 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It «wraps» after 49.710 days.
Error 1707 occurred at disk power-on lifetime: 30794 hours (1283 days + 2 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
— — — — — — —
84 51 80 cd 74 1d e5 Error: ICRC, ABRT 128 sectors at LBA = 0x051d74cd = 85816525
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————- ———————
c8 00 80 cd 74 1d e5 00 4d+18:27:26.625 READ DMA
c8 00 38 95 74 1d e5 00 4d+18:27:26.625 READ DMA
c8 00 00 cd 70 1d e5 00 4d+18:27:26.625 READ DMA
c8 00 48 4d 76 1d e5 00 4d+18:27:26.625 READ DMA
c8 00 58 f5 75 1d e5 00 4d+18:27:26.563 READ DMA
Error 1706 occurred at disk power-on lifetime: 30794 hours (1283 days + 2 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
— — — — — — —
84 51 58 f5 75 1d e5 Error: ICRC, ABRT 88 sectors at LBA = 0x051d75f5 = 85816821
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————- ———————
c8 00 58 f5 75 1d e5 00 4d+18:27:25.625 READ DMA
c8 00 48 05 ea 1d e5 00 4d+18:27:25.625 READ DMA
c8 00 10 ed e9 1d e5 00 4d+18:27:25.625 READ DMA
c8 00 08 dd ea 1d e5 00 4d+18:27:25.625 READ DMA
c8 00 08 cd ea 1d e5 00 4d+18:27:25.625 READ DMA
Error 1705 occurred at disk power-on lifetime: 30794 hours (1283 days + 2 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
— — — — — — —
84 51 70 de be 3b e7 Error: ICRC, ABRT 112 sectors at LBA = 0x073bbede = 121355998
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————- ———————
c8 00 70 de be 3b e7 00 4d+18:23:10.625 READ DMA
c8 00 90 4e be 3b e7 00 4d+18:23:10.625 READ DMA
c8 00 40 e6 72 3b e7 00 4d+18:23:10.625 READ DMA
c8 00 08 de 72 3b e7 00 4d+18:23:10.625 READ DMA
c8 00 10 06 e1 3a e7 00 4d+18:23:10.313 READ DMA
Error 1704 occurred at disk power-on lifetime: 30794 hours (1283 days + 2 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
— — — — — — —
84 51 80 4d d5 f7 e5 Error: ICRC, ABRT 128 sectors at LBA = 0x05f7d54d = 100128077
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————- ———————
c8 00 80 4d d5 f7 e5 00 4d+18:12:22.250 READ DMA
c8 00 80 4d d4 f7 e5 00 4d+18:12:22.188 READ DMA
ca 00 28 5e c3 4d e6 00 4d+18:12:21.063 WRITE DMA
ca 00 f8 e6 fb 3d e7 00 4d+18:12:20.438 WRITE DMA
ca 00 08 de fb 3d e7 00 4d+18:12:20.438 WRITE DMA
Error 1703 occurred at disk power-on lifetime: 30794 hours (1283 days + 2 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
— — — — — — —
84 51 18 46 80 3b e7 Error: ICRC, ABRT 24 sectors at LBA = 0x073b8046 = 121339974
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————- ———————
c8 00 18 46 80 3b e7 00 4d+18:11:59.250 READ DMA
c8 00 30 ae 6a 3b e7 00 4d+18:11:59.188 READ DMA
c8 00 08 7e 6a 3b e7 00 4d+18:11:59.188 READ DMA
c8 00 38 ee 69 3b e7 00 4d+18:11:59.188 READ DMA
c8 00 10 de 69 3b e7 00 4d+18:11:59.125 READ DMA
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 30805 —
# 2 Short offline Completed without error 00% 30804 —
# 3 Extended offline Completed without error 00% 26054 —
# 4 Extended offline Interrupted (host reset) 60% 26052 —
SMART Selective Self-Test Log Data Structure Revision Number (0) should be 1
SMART Selective self-test log data structure revision number 0
Warning: ATA Specification requires selective self-test log data structure revision number = 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
# smartctl -a /dev/sdb
smartctl version 5.38 [x86_64-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Model Family: SAMSUNG SpinPoint P80 SD series
Device Model: SAMSUNG HD160JJ
Serial Number: S08HJ10YB33277
Firmware Version: ZM100-33
User Capacity: 160,041,885,696 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: ATA/ATAPI-7 T13 1532D revision 4a
Local Time is: Mon Aug 17 11:44:29 2009 CEST
SMART support is: Available — device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x84) Offline data collection activity
was suspended by an interrupting command from host.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (3561) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 59) minutes.
SCT capabilities: (0x003f) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 100 100 051 Pre-fail Always — 0
3 Spin_Up_Time 0x0007 100 100 025 Pre-fail Always — 6144
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always — 524
5 Reallocated_Sector_Ct 0x0033 253 253 010 Pre-fail Always — 0
7 Seek_Error_Rate 0x000f 253 253 051 Pre-fail Always — 0
8 Seek_Time_Performance 0x0025 253 253 015 Pre-fail Offline — 0
9 Power_On_Hours 0x0032 100 100 000 Old_age Always — 30817
10 Spin_Retry_Count 0x0033 253 253 051 Pre-fail Always — 0
11 Calibration_Retry_Count 0x0012 253 002 000 Old_age Always — 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always — 386
190 Airflow_Temperature_Cel 0x0022 094 055 000 Old_age Always — 48
194 Temperature_Celsius 0x0022 094 055 000 Old_age Always — 48
195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always — 58540580
196 Reallocated_Event_Count 0x0032 253 253 000 Old_age Always — 0
197 Current_Pending_Sector 0x0012 253 253 000 Old_age Always — 0
198 Offline_Uncorrectable 0x0030 253 253 000 Old_age Offline — 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always — 1
200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always — 0
201 Soft_Read_Error_Rate 0x000a 100 100 000 Old_age Always — 0
202 TA_Increase_Count 0x0032 100 100 000 Old_age Always — 262
SMART Error Log Version: 1
ATA Error Count: 357 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It «wraps» after 49.710 days.
Error 357 occurred at disk power-on lifetime: 27619 hours (1150 days + 19 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
— — — — — — —
84 51 08 35 c3 57 e4 Error: ICRC, ABRT at LBA = 0x0457c335 = 72860469
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————- ———————
ca 00 08 35 c3 57 e4 00 04:55:42.000 WRITE DMA
ec 00 00 00 00 00 a0 00 04:55:41.938 IDENTIFY DEVICE
ef 03 42 00 00 00 a0 00 04:55:41.938 SET FEATURES [Set transfer mode]
ec 00 00 00 00 00 a0 00 04:55:41.938 IDENTIFY DEVICE
00 00 01 01 00 00 a0 00 04:55:41.563 NOP [Abort queued commands]
Error 356 occurred at disk power-on lifetime: 27619 hours (1150 days + 19 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
— — — — — — —
84 51 28 de e8 e3 e6 Error: ICRC, ABRT at LBA = 0x06e3e8de = 115599582
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————- ———————
ca 00 28 de e8 e3 e6 00 04:55:41.500 WRITE DMA
ec 00 00 00 00 00 a0 00 04:55:41.500 IDENTIFY DEVICE
ef 03 42 00 00 00 a0 00 04:55:41.500 SET FEATURES [Set transfer mode]
ec 00 00 00 00 00 a0 00 04:55:41.500 IDENTIFY DEVICE
00 00 01 01 00 00 a0 00 04:55:41.125 NOP [Abort queued commands]
Error 355 occurred at disk power-on lifetime: 27619 hours (1150 days + 19 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
— — — — — — —
84 51 28 de e8 e3 e6 Error: ICRC, ABRT at LBA = 0x06e3e8de = 115599582
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————- ———————
ca 00 28 de e8 e3 e6 00 04:55:41.063 WRITE DMA
ec 00 00 00 00 00 a0 00 04:55:41.063 IDENTIFY DEVICE
ef 03 42 00 00 00 a0 00 04:55:41.063 SET FEATURES [Set transfer mode]
ec 00 00 00 00 00 a0 00 04:55:41.063 IDENTIFY DEVICE
00 00 01 01 00 00 a0 00 04:55:40.688 NOP [Abort queued commands]
Error 354 occurred at disk power-on lifetime: 27619 hours (1150 days + 19 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
— — — — — — —
84 51 28 de e8 e3 e6 Error: ICRC, ABRT at LBA = 0x06e3e8de = 115599582
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————- ———————
ca 00 28 de e8 e3 e6 00 04:55:40.625 WRITE DMA
ec 00 00 00 00 00 a0 00 04:55:40.625 IDENTIFY DEVICE
ef 03 42 00 00 00 a0 00 04:55:40.625 SET FEATURES [Set transfer mode]
ec 00 00 00 00 00 a0 00 04:55:40.563 IDENTIFY DEVICE
00 00 01 01 00 00 a0 00 04:55:40.250 NOP [Abort queued commands]
Error 353 occurred at disk power-on lifetime: 27619 hours (1150 days + 19 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
— — — — — — —
84 51 28 de e8 e3 e6 Error: ICRC, ABRT at LBA = 0x06e3e8de = 115599582
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————- ———————
ca 00 28 de e8 e3 e6 00 04:55:34.813 WRITE DMA
ec 00 00 00 00 00 a0 00 04:55:34.750 IDENTIFY DEVICE
ef 03 42 00 00 00 a0 00 04:55:34.750 SET FEATURES [Set transfer mode]
ec 00 00 00 00 00 a0 00 04:55:34.750 IDENTIFY DEVICE
00 00 01 01 00 00 a0 00 04:55:34.375 NOP [Abort queued commands]
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 30806 —
# 2 Short offline Completed without error 00% 30805 —
# 3 Extended offline Completed without error 00% 26051 —
# 4 Extended offline Interrupted (host reset) 60% 26049 —
SMART Selective Self-Test Log Data Structure Revision Number (0) should be 1
SMART Selective self-test log data structure revision number 0
Warning: ATA Specification requires selective self-test log data structure revision number = 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
|
# (отредактировано 8 лет, 5 месяцев назад) |
|
|
Темы: 166 Сообщения: 836 Участник с: 04 августа 2009 |
вообщем увидел следующее:
просканировал /dev/sda через smartctl и вот что он мне выдал: неподскажите в чём может быть проблема? не приходит ли конец жёсткому диску? |
|
cucullus |
# |
|
Темы: 258 Сообщения: 3460 Участник с: 06 июня 2007 |
при проблемах с сатой первым делом проверяется кабель
такие дела. |
|
killer1804 |
# |
|
Темы: 54 Сообщения: 515 Участник с: 13 марта 2007 |
попробуйте добавить опцию irqpoll в строку ядра в загрузчике |
|
SmiGes |
# |
|
Темы: 166 Сообщения: 836 Участник с: 04 августа 2009 |
Спасибо. Поменял кабель, проблема ушла. |
-
- #1
Hi,
I’m new to the openmediavault forum and
I just setup a new NAS and wanted to create a RAID 5 with 4*14TB harddisks.
Everything went fine, but now while initializing the RAID 5, There are some errors:
ata4.00: exception EMask 0x10 SAct 0x0 SErr 0x8000000 action 0x6 frozen
ata4.00: irq_stat 0x08000000, interface fatal error
ata4.00: SError: [ LinkSeq ]
ata4.00: failed command: READ_DMA EXT
ata4.00: cmd … tag 10 dma 688128 in
res … Emask 0x10 (ATA bus error)
ata4.00: status [ DRDY ]
I already updated the grub file, but still get sometimes that error.
The initializiation broke two times before, currently its running (20% finished) but the error occurred 8 times.
I changed the SATA 3 connectors to SATA2, but with no effect.
Does anyone know this erro or where it comes from?
-
- #2
So I deactivated two harddisks and created just a stripe RAID (RAID 0). And I still got the same issue.
It was not possible to create the filesystem.
After that I used some new SATA3 cables. And now it worked for the two HDDs as RAID0.
I just ordered new SATA3 cabel for the remaining two HDDs and will try it.
So it seems that the issue is realted to the SATA cabels. Don’t save money on that
-
- #3
I just setup a new NAS and wanted to create a RAID 5 with 4*14TB harddisks.
You should really think about if a RAID5 array created with 14 TB disks is still an appropriate way nowadays. If you had to replace a disk in the future the resilvering process takes forever and entails the risk that a second disk fails. Which then means a complete loss of the array.
So I deactivated two harddisks and created just a stripe RAID (RAID 0).
You are aware, that RAID0 has no data redundancy? If one disk fails you lost the array. A RAID 0 is normally not useful in a NAS, especially with a GB Lan connection.
How do you want to organize your data backup system?
-
- #4
The RAID0 I created is just vor testing, if the error still occurs and if the HDDs are working and I had only two new SATA3 cables.
And yes, RAID5 with 4*14TB will take a loooong time to be restored if I have to change a harddisk, But this is just an archive data, so I can wait a few days if the cases really happens, that one disc is failing (hopefully only one ;)). For the data of the daily use, I have a backup concept, which I can access atonce.
Thanks for your feedback !
-
- #5
But this is just an archive data, so I can wait a few days if the cases really happens, that one disc is failing (hopefully only one ;))
If this NAS is only for archived data you really should have a look at SnapRaid / mergerfs. Especially snapraid is perfect for data which is not changing permanently and has the ability to check for silent data corruption which RAID did not. Today I would no longer use a solution that did not guarantee data integrity.
One of many available SnapRaid tutorials: DIY NAS with OMV, SnapRAID, MergerFS, and Disk Encryption
-
- #6
If this NAS is only for archived data you really should have a look at SnapRaid / mergerfs. Especially snapraid is perfect for data which is not changing permanently and has the ability to check for silent data corruption which RAID did not. Today I would no longer use a solution that did not guarantee data integrity.
I like this and will try this out. Unless I don’t have data on my NAS, I can try out some things. Thanks a lot.
Btw. now with all new SATA3 cabels, all discs are running without errors. If anybody would have told me to change the SATA cables I would not believe him.
problem found
With MCP7A Controller Nvidia chipset (ATOM / ION Platform), mini-ITX
AMI BIOS -> N1012WZT.rom — release12 October 2009
Creates many problems connecting hard disk SSD OCZ Agility 3
Consequent block of the entire operating system and reboot and errors created the filesystem (ext3-ext4).
Total instability detected using the motherboard:
Zotac IONITX FE — (MCP7A Controller Nvidia chipset)
SSD 60GB OCZ Agility 3 — (Sata Cable Short — Bios Settings AHCI)
Using Hard Disk to Another Motherboard:
ASUS P5E — (Controller Intel ICH9 Chipset)
ASROCK PV530 — (Chipset — VIA VX900)
I have not found any error in communication and / or instability of the operating system.
Can I assume that it is a form of Kernel Bugs, which manages the Controller MCP7A Nvidia chipset.
Please you to make changes readily resolutive this drawback …
Best Regards
Complete Log ==>> http://pastebin.com/YGD3wCmm
[ 326.023319] ata1: exception Emask 0x10 SAct 0x0 SErr 0x1990000 action 0xe frozen
[ 326.023329] ata1: irq_stat 0x00400000, PHY RDY changed
[ 326.023338] ata1: SError: { PHYRdyChg 10B8B Dispar LinkSeq TrStaTrns }
[ 326.023350] ata1: hard resetting link
[ 326.744046] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 326.765644] ata1.00: configured for UDMA/100
[ 326.766071] ata1: EH complete
[ 334.383910] ata1.00: exception Emask 0x10 SAct 0x7fffffff SErr 0x1990000 action 0xe frozen
[ 334.383925] ata1.00: irq_stat 0x08400000, interface fatal error, PHY RDY changed
[ 334.383939] ata1: SError: { PHYRdyChg 10B8B Dispar LinkSeq TrStaTrns }
[ 334.383952] ata1.00: failed command: WRITE FPDMA QUEUED
[ 334.383975] ata1.00: cmd 61/c0:00:20:4c:56/01:00:03:00:00/40 tag 0 ncq 229376 out
[ 334.383979] res 40/00:b8:00:7d:56/00:00:03:00:00/40 Emask 0x10 (ATA bus error)
[ 334.383991] ata1.00: status: { DRDY }
[ 334.384001] ata1.00: failed command: WRITE FPDMA QUEUED
[ 334.384052] ata1.00: cmd 61/08:08:f0:4d:56/00:00:03:00:00/40 tag 1 ncq 4096 out
[ 334.384057] res 40/00:b8:00:7d:56/00:00:03:00:00/40 Emask 0x10 (ATA bus error)
[ 334.384068] ata1.00: status: { DRDY }
[ 334.384077] ata1.00: failed command: WRITE FPDMA QUEUED
[ 334.384096] ata1.00: cmd 61/00:10:00:4e:56/04:00:03:00:00/40 tag 2 ncq 524288 out
[ 334.384100] res 40/00:b8:00:7d:56/00:00:03:00:00/40 Emask 0x10 (ATA bus error)
—
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: knap 1716 F…. pulseaudio
Card0.Amixer.info:
Card hw:0 ‘NVidia’/’HDA NVidia at 0xfab78000 irq 23’
Mixer name : ‘Nvidia MCP79/7A HDMI’
Components : ‘HDA:10ec0662,19daa108,00100101 HDA:10de0007,10de0101,00100100’
Controls : 42
Simple ctrls : 21
DistroRelease: LinuxMint 13
HibernationDevice: RESUME=UUID=ab3786a8-24af-4eb8-bc41-761f035267e2
InstallationMedia: Linux Mint 13 «Maya» — Release i386 (20120520)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 045e:00f9 Microsoft Corp. Wireless Desktop Receiver 3.1
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: tbs6981fe
Package: linux (not installed)
ProcEnviron:
TERM=xterm
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=533b4514-fa82-4470-bbcf-6f2b7e58f2da ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
RelatedPackageVersions:
linux-restricted-modules-3.2.0-24-generic N/A
linux-backports-modules-3.2.0-24-generic N/A
linux-firmware 1.79
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: maya
Uname: Linux 3.2.0-24-generic i686
UnreportableReason: Questo non è un pacchetto ufficiale di LinuxMint. Rimuovere tutti i pacchetti di terze parti, quindi riprovare.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 10/12/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: To be filled by O.E.M.
dmi.board.vendor: To be filled by O.E.M.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd10/12/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
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:
[ 10.019887] ata1.00: cmd 60/00:10:10:da:59/01:00:0f:00:00/40 tag 2 ncq 131072 in
res 41/84:00:f2:da:59/00:01:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 10.019968] ata1.00: status: { DRDY ERR }
[ 10.019992] ata1.00: error: { ICRC ABRT }
[ 10.020017] ata1: hard resetting link
[ 10.339913] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 10.443163] ata1.00: configured for UDMA/133
[ 10.443191] ata1: EH complete
[ 10.516832] ata1.00: exception Emask 0x0 SAct 0x7000 SErr 0x0 action 0x6
[ 10.516877] ata1.00: irq_stat 0x40000008
[ 10.516902] ata1.00: failed command: READ FPDMA QUEUED
[ 10.516935] ata1.00: cmd 60/e8:60:e8:16:3b/00:00:0f:00:00/40 tag 12 ncq 118784 in
res 41/84:e8:8c:17:3b/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 10.517017] ata1.00: status: { DRDY ERR }
[ 10.517041] ata1.00: error: { ICRC ABRT }
[ 10.517067] ata1: hard resetting link
[ 10.836973] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 10.964972] ata1.00: configured for UDMA/133
[ 10.965002] ata1: EH complete
[ 10.984003] ata1: limiting SATA link speed to 3.0 Gbps
[ 10.984015] ata1.00: exception Emask 0x0 SAct 0x60020000 SErr 0x0 action 0x6
[ 10.984106] ata1.00: irq_stat 0x40000008
[ 10.984157] ata1.00: failed command: READ FPDMA QUEUED
[ 10.984225] ata1.00: cmd 60/20:e8:40:6e:b0/00:00:13:00:00/40 tag 29 ncq 16384 in
res 41/84:20:46:6e:b0/00:00:13:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 10.984397] ata1.00: status: { DRDY ERR }
[ 10.984445] ata1.00: error: { ICRC ABRT }
[ 10.984497] ata1: hard resetting link
[ 11.304016] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 11.409308] ata1.00: configured for UDMA/133
[ 11.409343] ata1: EH complete
[ 11.441025] vboxpci: IOMMU not found (not registered)
[ 11.543239] bbswitch: version 0.8
[ 11.543246] bbswitch: Found integrated VGA device 0000:00:02.0: _SB_.PCI0.GFX0
[ 11.543252] bbswitch: Found discrete VGA device 0000:03:00.0: _SB_.PCI0.RP05.PEGP
[ 11.543262] ACPI Warning: _SB_.PCI0.RP05.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20141107/nsarguments-95)
[ 11.543355] bbswitch: detected an Optimus _DSM function
[ 11.543372] pci 0000:03:00.0: enabling device (0006 -> 0007)
[ 11.543434] bbswitch: Succesfully loaded. Discrete card 0000:03:00.0 is on
[ 11.545169] bbswitch: disabling discrete graphics
[ 11.545181] ACPI Warning: _SB_.PCI0.RP05.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20141107/nsarguments-95)
[ 13.327790] r8169 0000:01:00.0 enp1s0: link up
[ 20.651344] ata1.00: exception Emask 0x0 SAct 0x2000000 SErr 0x0 action 0x6
[ 20.651349] ata1.00: irq_stat 0x40000008
[ 20.651353] ata1.00: failed command: READ FPDMA QUEUED
[ 20.651359] ata1.00: cmd 60/08:c8:98:86:ae/00:00:10:00:00/40 tag 25 ncq 4096 in
res 41/84:08:98:86:ae/00:00:10:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 20.651361] ata1.00: status: { DRDY ERR }
[ 20.651363] ata1.00: error: { ICRC ABRT }
[ 20.651367] ata1: hard resetting link
[ 20.971293] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 21.080441] ata1.00: configured for UDMA/133
[ 21.080467] ata1: EH complete
[ 21.121498] ata1.00: exception Emask 0x0 SAct 0x20000000 SErr 0x0 action 0x6
[ 21.121503] ata1.00: irq_stat 0x40000008
[ 21.121507] ata1.00: failed command: READ FPDMA QUEUED
[ 21.121513] ata1.00: cmd 60/00:e8:00:f4:69/01:00:0f:00:00/40 tag 29 ncq 131072 in
res 41/84:00:ee:f4:69/00:01:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 21.121515] ata1.00: status: { DRDY ERR }
[ 21.121517] ata1.00: error: { ICRC ABRT }
[ 21.121521] ata1: hard resetting link
[ 21.441483] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 21.546775] ata1.00: configured for UDMA/133
[ 21.546795] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 21.546798] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 21.546801] sd 0:0:0:0: [sda] ASC=0x47 ASCQ=0x0
[ 21.546802] sd 0:0:0:0: [sda] CDB:
[ 21.546804] cdb[0]=0x28: 28 00 0f 69 f4 00 00 01 00 00
[ 21.546812] blk_update_request: I/O error, dev sda, sector 258601984
[ 21.546829] ata1: EH complete
[ 21.606131] ata1.00: exception Emask 0x0 SAct 0x200 SErr 0x0 action 0x6
[ 21.606139] ata1.00: irq_stat 0x40000008
[ 21.606145] ata1.00: failed command: READ FPDMA QUEUED
[ 21.606155] ata1.00: cmd 60/88:48:00:d8:36/00:00:0f:00:00/40 tag 9 ncq 69632 in
res 41/84:88:04:d8:36/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 21.606160] ata1.00: status: { DRDY ERR }
[ 21.606163] ata1.00: error: { ICRC ABRT }
[ 21.606170] ata1: hard resetting link
[ 21.924963] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 22.035385] ata1.00: configured for UDMA/133
[ 22.035408] ata1: EH complete
[ 22.111984] ata1: limiting SATA link speed to 1.5 Gbps
[ 22.111991] ata1.00: exception Emask 0x0 SAct 0x1000000 SErr 0x0 action 0x6
[ 22.111994] ata1.00: irq_stat 0x40000008
[ 22.111997] ata1.00: failed command: READ FPDMA QUEUED
[ 22.112003] ata1.00: cmd 60/90:c0:48:39:32/00:00:0f:00:00/40 tag 24 ncq 73728 in
res 41/84:90:8a:39:32/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 22.112005] ata1.00: status: { DRDY ERR }
[ 22.112007] ata1.00: error: { ICRC ABRT }
[ 22.112011] ata1: hard resetting link
[ 22.431783] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 22.535011] ata1.00: configured for UDMA/133
[ 22.535038] ata1: EH complete
[ 22.618877] ata1.00: exception Emask 0x0 SAct 0x1e SErr 0x0 action 0x6
[ 22.618886] ata1.00: irq_stat 0x40000008
[ 22.618891] ata1.00: failed command: READ FPDMA QUEUED
[ 22.618901] ata1.00: cmd 60/00:08:08:2c:32/01:00:0f:00:00/40 tag 1 ncq 131072 in
res 41/84:00:70:2c:32/00:01:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 22.618906] ata1.00: status: { DRDY ERR }
[ 22.618909] ata1.00: error: { ICRC ABRT }
[ 22.618920] ata1: hard resetting link
[ 22.938608] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 23.023643] ata1.00: configured for UDMA/133
[ 23.023682] ata1: EH complete
[ 53.428943] ata1.00: exception Emask 0x1 SAct 0x7fffffff SErr 0x0 action 0x6 frozen
[ 53.428953] ata1.00: irq_stat 0x40000008
[ 53.428960] ata1.00: failed command: READ FPDMA QUEUED
[ 53.428971] ata1.00: cmd 60/00:00:00:e8:31/01:00:10:00:00/40 tag 0 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x5 (timeout)
[ 53.428976] ata1.00: status: { DRDY }
[ 53.428981] ata1.00: failed command: READ FPDMA QUEUED
[ 53.428990] ata1.00: cmd 60/08:08:20:fe:e9/00:00:0f:00:00/40 tag 1 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.428994] ata1.00: status: { DRDY }
[ 53.428998] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429006] ata1.00: cmd 60/08:10:28:fe:e9/00:00:0f:00:00/40 tag 2 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429010] ata1.00: status: { DRDY }
[ 53.429014] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429022] ata1.00: cmd 60/08:18:30:fe:e9/00:00:0f:00:00/40 tag 3 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429026] ata1.00: status: { DRDY }
[ 53.429029] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429037] ata1.00: cmd 60/08:20:38:fe:e9/00:00:0f:00:00/40 tag 4 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429042] ata1.00: status: { DRDY }
[ 53.429045] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429053] ata1.00: cmd 60/08:28:40:fe:e9/00:00:0f:00:00/40 tag 5 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429057] ata1.00: status: { DRDY }
[ 53.429061] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429069] ata1.00: cmd 60/08:30:48:fe:e9/00:00:0f:00:00/40 tag 6 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429073] ata1.00: status: { DRDY }
[ 53.429076] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429084] ata1.00: cmd 60/08:38:50:fe:e9/00:00:0f:00:00/40 tag 7 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429089] ata1.00: status: { DRDY }
[ 53.429092] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429100] ata1.00: cmd 60/08:40:58:fe:e9/00:00:0f:00:00/40 tag 8 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429104] ata1.00: status: { DRDY }
[ 53.429108] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429116] ata1.00: cmd 60/08:48:60:fe:e9/00:00:0f:00:00/40 tag 9 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429120] ata1.00: status: { DRDY }
[ 53.429124] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429132] ata1.00: cmd 60/08:50:68:fe:e9/00:00:0f:00:00/40 tag 10 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429136] ata1.00: status: { DRDY }
[ 53.429139] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429148] ata1.00: cmd 60/08:58:70:fe:e9/00:00:0f:00:00/40 tag 11 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429152] ata1.00: status: { DRDY }
[ 53.429155] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429163] ata1.00: cmd 60/08:60:78:fe:e9/00:00:0f:00:00/40 tag 12 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429168] ata1.00: status: { DRDY }
[ 53.429171] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429179] ata1.00: cmd 60/08:68:80:fe:e9/00:00:0f:00:00/40 tag 13 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429183] ata1.00: status: { DRDY }
[ 53.429187] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429195] ata1.00: cmd 60/08:70:18:e8:a9/00:00:16:00:00/40 tag 14 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429199] ata1.00: status: { DRDY }
[ 53.429203] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429211] ata1.00: cmd 60/08:78:90:fe:e9/00:00:0f:00:00/40 tag 15 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429215] ata1.00: status: { DRDY }
[ 53.429218] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429226] ata1.00: cmd 60/08:80:98:fe:e9/00:00:0f:00:00/40 tag 16 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429230] ata1.00: status: { DRDY }
[ 53.429234] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429242] ata1.00: cmd 60/08:88:a0:fe:e9/00:00:0f:00:00/40 tag 17 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429246] ata1.00: status: { DRDY }
[ 53.429250] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429258] ata1.00: cmd 60/08:90:a8:fe:e9/00:00:0f:00:00/40 tag 18 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429262] ata1.00: status: { DRDY }
[ 53.429265] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429273] ata1.00: cmd 60/08:98:b0:fe:e9/00:00:0f:00:00/40 tag 19 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429277] ata1.00: status: { DRDY }
[ 53.429281] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429289] ata1.00: cmd 60/08:a0:b8:fe:e9/00:00:0f:00:00/40 tag 20 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429293] ata1.00: status: { DRDY }
[ 53.429297] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429305] ata1.00: cmd 60/08:a8:c0:fe:e9/00:00:0f:00:00/40 tag 21 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429309] ata1.00: status: { DRDY }
[ 53.429312] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429320] ata1.00: cmd 60/08:b0:c8:fe:e9/00:00:0f:00:00/40 tag 22 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429325] ata1.00: status: { DRDY }
[ 53.429328] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429336] ata1.00: cmd 60/08:b8:d0:fe:e9/00:00:0f:00:00/40 tag 23 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429340] ata1.00: status: { DRDY }
[ 53.429344] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429352] ata1.00: cmd 60/08:c0:d8:fe:e9/00:00:0f:00:00/40 tag 24 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429356] ata1.00: status: { DRDY }
[ 53.429360] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429367] ata1.00: cmd 60/08:c8:e0:fe:e9/00:00:0f:00:00/40 tag 25 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429372] ata1.00: status: { DRDY }
[ 53.429375] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429383] ata1.00: cmd 60/08:d0:e8:fe:e9/00:00:0f:00:00/40 tag 26 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429387] ata1.00: status: { DRDY }
[ 53.429391] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429399] ata1.00: cmd 60/08:d8:f0:fe:e9/00:00:0f:00:00/40 tag 27 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429403] ata1.00: status: { DRDY }
[ 53.429407] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429414] ata1.00: cmd 60/08:e0:f8:fe:e9/00:00:0f:00:00/40 tag 28 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429419] ata1.00: status: { DRDY }
[ 53.429422] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429430] ata1.00: cmd 60/08:e8:00:ff:e9/00:00:0f:00:00/40 tag 29 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429435] ata1.00: status: { DRDY }
[ 53.429438] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429446] ata1.00: cmd 60/08:f0:88:fe:e9/00:00:0f:00:00/40 tag 30 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429450] ata1.00: status: { DRDY }
[ 53.429458] ata1: hard resetting link
[ 53.749173] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 53.836070] ata1.00: configured for UDMA/133
[ 53.836079] ata1.00: device reported invalid CHS sector 0
[ 53.836116] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 53.836119] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 53.836121] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[ 53.836123] sd 0:0:0:0: [sda] CDB:
[ 53.836125] cdb[0]=0x28: 28 00 0f e9 fe 20 00 00 08 00
[ 53.836133] blk_update_request: I/O error, dev sda, sector 266993184
[ 53.836148] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 53.836151] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 53.836153] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[ 53.836154] sd 0:0:0:0: [sda] CDB:
[ 53.836155] cdb[0]=0x28: 28 00 0f e9 fe 28 00 00 08 00
[ 53.836162] blk_update_request: I/O error, dev sda, sector 266993192
[ 53.836167] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 53.836169] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 53.836171] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[ 53.836173] sd 0:0:0:0: [sda] CDB:
[ 53.836174] cdb[0]=0x28: 28 00 0f e9 fe 30 00 00 08 00
[ 53.836180] blk_update_request: I/O error, dev sda, sector 266993200
[ 53.836185] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 53.836187] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 53.836189] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[ 53.836190] sd 0:0:0:0: [sda] CDB:
[ 53.836191] cdb[0]=0x28: 28 00 0f e9 fe 38 00 00 08 00
[ 53.836198] blk_update_request: I/O error, dev sda, sector 266993208
[ 53.836202] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 53.836204] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 53.836206] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[ 53.836208] sd 0:0:0:0: [sda] CDB:
[ 53.836209] cdb[0]=0x28: 28 00 0f e9 fe 40 00 00 08 00
[ 53.836215] blk_update_request: I/O error, dev sda, sector 266993216
[ 53.836220] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 53.836222] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 53.836224] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[ 53.836225] sd 0:0:0:0: [sda] CDB:
[ 53.836226] cdb[0]=0x28: 28 00 0f e9 fe 48 00 00 08 00
[ 53.836232] blk_update_request: I/O error, dev sda, sector 266993224
[ 53.836237] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 53.836239] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 53.836241] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[ 53.836242] sd 0:0:0:0: [sda] CDB:
[ 53.836243] cdb[0]=0x28: 28 00 0f e9 fe 50 00 00 08 00
[ 53.836249] blk_update_request: I/O error, dev sda, sector 266993232
[ 53.836253] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 53.836255] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 53.836257] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[ 53.836259] sd 0:0:0:0: [sda] CDB:
[ 53.836260] cdb[0]=0x28: 28 00 0f e9 fe 58 00 00 08 00
[ 53.836266] blk_update_request: I/O error, dev sda, sector 266993240
[ 53.836270] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 53.836272] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 53.836274] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[ 53.836276] sd 0:0:0:0: [sda] CDB:
[ 53.836277] cdb[0]=0x28: 28 00 0f e9 fe 60 00 00 08 00
[ 53.836283] blk_update_request: I/O error, dev sda, sector 266993248
[ 53.836287] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 53.836289] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 53.836291] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[ 53.836293] sd 0:0:0:0: [sda] CDB:
[ 53.836294] cdb[0]=0x28: 28 00 0f e9 fe 68 00 00 08 00
[ 53.836300] blk_update_request: I/O error, dev sda, sector 266993256
[ 53.836354] ata1: EH complete
[ 53.922776] ata1.00: exception Emask 0x0 SAct 0x20 SErr 0x0 action 0x6
[ 53.922827] ata1.00: irq_stat 0x40000008
[ 53.922855] ata1.00: failed command: READ FPDMA QUEUED
[ 53.922891] ata1.00: cmd 60/00:28:38:3f:04/01:00:10:00:00/40 tag 5 ncq 131072 in
res 41/84:00:5a:3f:04/00:01:10:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 53.922981] ata1.00: status: { DRDY ERR }
[ 53.923007] ata1.00: error: { ICRC ABRT }
[ 53.923037] ata1: hard resetting link
[ 54.242882] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 54.357940] ata1.00: configured for UDMA/133
[ 54.357967] ata1: EH complete
[ 54.413337] ata1.00: limiting speed to UDMA/100:PIO4
[ 54.413343] ata1.00: exception Emask 0x0 SAct 0x100 SErr 0x0 action 0x6
[ 54.413387] ata1.00: irq_stat 0x40000008
[ 54.413412] ata1.00: failed command: READ FPDMA QUEUED
[ 54.413445] ata1.00: cmd 60/20:40:c0:04:b1/00:00:16:00:00/40 tag 8 ncq 16384 in
res 41/84:20:d4:04:b1/00:00:16:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 54.413527] ata1.00: status: { DRDY ERR }
[ 54.413551] ata1.00: error: { ICRC ABRT }
[ 54.413578] ata1: hard resetting link
[ 54.733264] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 54.835393] ata1.00: configured for UDMA/100
[ 54.835419] ata1: EH complete
[ 54.883575] ata1.00: exception Emask 0x0 SAct 0x8 SErr 0x0 action 0x6
[ 54.883618] ata1.00: irq_stat 0x40000008
[ 54.883643] ata1.00: failed command: READ FPDMA QUEUED
[ 54.883675] ata1.00: cmd 60/08:18:e0:04:b1/00:00:16:00:00/40 tag 3 ncq 4096 in
res 41/84:08:e4:04:b1/00:00:16:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 54.883756] ata1.00: status: { DRDY ERR }
[ 54.883779] ata1.00: error: { ICRC ABRT }
[ 54.883805] ata1: hard resetting link
[ 55.203636] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 55.301754] ata1.00: configured for UDMA/100
[ 55.301780] ata1: EH complete
[ 55.357428] ata1.00: exception Emask 0x0 SAct 0x40000 SErr 0x0 action 0x6
[ 55.357474] ata1.00: irq_stat 0x40000008
[ 55.357500] ata1.00: failed command: READ FPDMA QUEUED
[ 55.357532] ata1.00: cmd 60/f0:90:e0:34:a5/00:00:0e:00:00/40 tag 18 ncq 122880 in
res 41/84:f0:ea:34:a5/00:00:0e:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 55.357613] ata1.00: status: { DRDY ERR }
[ 55.357636] ata1.00: error: { ICRC ABRT }
[ 55.357661] ata1: hard resetting link
[ 55.677344] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 55.779200] ata1.00: configured for UDMA/100
[ 55.779228] ata1: EH complete
[ 55.954538] ata1.00: exception Emask 0x0 SAct 0xc0000 SErr 0x0 action 0x6
[ 55.954585] ata1.00: irq_stat 0x40000008
[ 55.954610] ata1.00: failed command: READ FPDMA QUEUED
[ 55.954643] ata1.00: cmd 60/00:90:00:eb:a4/01:00:0e:00:00/40 tag 18 ncq 131072 in
res 41/84:00:10:eb:a4/00:01:0e:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 55.954725] ata1.00: status: { DRDY ERR }
[ 55.954748] ata1.00: error: { ICRC ABRT }
[ 55.954774] ata1: hard resetting link
[ 56.274496] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 56.367864] ata1.00: configured for UDMA/100
[ 56.367921] ata1: EH complete
[ 56.448401] ata1.00: limiting speed to UDMA/33:PIO4
[ 56.448412] ata1.00: exception Emask 0x0 SAct 0x4 SErr 0x0 action 0x6
[ 56.448483] ata1.00: irq_stat 0x40000008
[ 56.448524] ata1.00: failed command: READ FPDMA QUEUED
[ 56.448578] ata1.00: cmd 60/00:10:58:ec:a4/01:00:0e:00:00/40 tag 2 ncq 131072 in
res 41/84:00:fe:ec:a4/00:01:0e:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 56.448715] ata1.00: status: { DRDY ERR }
[ 56.448753] ata1.00: error: { ICRC ABRT }
[ 56.448798] ata1: hard resetting link
[ 56.768215] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 56.856253] ata1.00: configured for UDMA/33
[ 56.856297] ata1: EH complete
[ 56.898690] ata1.00: exception Emask 0x0 SAct 0x60 SErr 0x0 action 0x6
[ 56.898770] ata1.00: irq_stat 0x40000008
[ 56.898816] ata1.00: failed command: READ FPDMA QUEUED
[ 56.898876] ata1.00: cmd 60/00:30:c8:ee:a4/01:00:0e:00:00/40 tag 6 ncq 131072 in
res 41/84:00:e8:ee:a4/00:01:0e:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 56.899029] ata1.00: status: { DRDY ERR }
[ 56.899072] ata1.00: error: { ICRC ABRT }
[ 56.899121] ata1: hard resetting link
[ 57.218560] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 57.311513] ata1.00: configured for UDMA/33
[ 57.311542] ata1: EH complete
[ 57.355664] ata1.00: exception Emask 0x0 SAct 0x500 SErr 0x0 action 0x6
[ 57.355754] ata1.00: irq_stat 0x40000008
[ 57.355806] ata1.00: failed command: READ FPDMA QUEUED
[ 57.355873] ata1.00: cmd 60/58:50:00:ec:a4/00:00:0e:00:00/40 tag 10 ncq 45056 in
res 41/84:58:1a:ec:a4/00:00:0e:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 57.356044] ata1.00: status: { DRDY ERR }
[ 57.356091] ata1.00: error: { ICRC ABRT }
[ 57.356145] ata1: hard resetting link
[ 57.675608] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 57.766781] ata1.00: configured for UDMA/33
[ 57.766816] ata1: EH complete
[ 57.806077] ata1.00: exception Emask 0x0 SAct 0x3000 SErr 0x0 action 0x6
[ 57.806134] ata1.00: irq_stat 0x40000008
[ 57.806164] ata1.00: failed command: READ FPDMA QUEUED
[ 57.806203] ata1.00: cmd 60/00:68:70:24:a5/01:00:0e:00:00/40 tag 13 ncq 131072 in
res 41/84:00:f2:24:a5/00:01:0e:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 57.806302] ata1.00: status: { DRDY ERR }
[ 57.806330] ata1.00: error: { ICRC ABRT }
[ 57.806362] ata1: hard resetting link
[ 58.125961] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 58.211103] ata1.00: configured for UDMA/33
[ 58.211156] ata1: EH complete
[ 58.249769] ata1.00: exception Emask 0x0 SAct 0x18000 SErr 0x0 action 0x6
[ 58.249854] ata1.00: irq_stat 0x40000008
[ 58.249901] ata1.00: failed command: READ FPDMA QUEUED
[ 58.249962] ata1.00: cmd 60/00:80:20:27:a5/01:00:0e:00:00/40 tag 16 ncq 131072 in
res 41/84:00:a2:27:a5/00:01:0e:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 58.255626] ata1.00: status: { DRDY ERR }
[ 58.258790] ata1.00: error: { ICRC ABRT }
[ 58.261924] ata1: hard resetting link
[ 58.579657] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 58.666164] ata1.00: configured for UDMA/33
[ 58.666199] ata1: EH complete
[ 58.716707] ata1.00: exception Emask 0x0 SAct 0x4000000 SErr 0x0 action 0x6
[ 58.718539] ata1.00: irq_stat 0x40000008
[ 58.720328] ata1.00: failed command: READ FPDMA QUEUED
[ 58.722121] ata1.00: cmd 60/00:d0:68:92:5c/01:00:0f:00:00/40 tag 26 ncq 131072 in
res 41/84:00:76:92:5c/00:01:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 58.725736] ata1.00: status: { DRDY ERR }
[ 58.727553] ata1.00: error: { ICRC ABRT }
[ 58.728965] ata1: hard resetting link
[ 59.046670] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 59.132488] ata1.00: configured for UDMA/33
[ 59.132515] ata1: EH complete
[ 59.180459] ata1.00: exception Emask 0x0 SAct 0x20000000 SErr 0x0 action 0x6
[ 59.181979] ata1.00: irq_stat 0x40000008
[ 59.182990] ata1.00: failed command: READ FPDMA QUEUED
[ 59.183943] ata1.00: cmd 60/f8:e8:68:93:5c/00:00:0f:00:00/40 tag 29 ncq 126976 in
res 41/84:f8:6a:93:5c/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 59.185831] ata1.00: status: { DRDY ERR }
[ 59.186778] ata1.00: error: { ICRC ABRT }
[ 59.187715] ata1: hard resetting link
[ 59.507035] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 59.610051] ata1.00: configured for UDMA/33
[ 59.610080] ata1: EH complete
[ 59.661766] ata1.00: exception Emask 0x0 SAct 0x80 SErr 0x0 action 0x6
[ 59.663154] ata1.00: irq_stat 0x40000008
[ 59.664089] ata1.00: failed command: READ FPDMA QUEUED
[ 59.665027] ata1.00: cmd 60/98:38:60:94:5c/00:00:0f:00:00/40 tag 7 ncq 77824 in
res 41/84:98:64:94:5c/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 59.666916] ata1.00: status: { DRDY ERR }
[ 59.669774] ata1.00: error: { ICRC ABRT }
[ 59.672954] ata1: hard resetting link
[ 59.990695] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 60.087554] ata1.00: configured for UDMA/33
[ 60.087600] ata1: EH complete
[ 60.217903] ata1.00: exception Emask 0x0 SAct 0x80 SErr 0x0 action 0x6
[ 60.219413] ata1.00: irq_stat 0x40000008
[ 60.220456] ata1.00: failed command: READ FPDMA QUEUED
[ 60.221440] ata1.00: cmd 60/20:38:00:1b:3e/00:00:0f:00:00/40 tag 7 ncq 16384 in
res 41/84:20:18:1b:3e/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 60.223332] ata1.00: status: { DRDY ERR }
[ 60.224269] ata1.00: error: { ICRC ABRT }
[ 60.225206] ata1: hard resetting link
[ 60.544531] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 60.653686] ata1.00: configured for UDMA/33
[ 60.653713] ata1: EH complete
[ 60.701540] ata1.00: exception Emask 0x0 SAct 0x400 SErr 0x0 action 0x6
[ 60.703016] ata1.00: irq_stat 0x40000008
[ 60.704106] ata1.00: failed command: READ FPDMA QUEUED
[ 60.705056] ata1.00: cmd 60/88:50:78:1b:3e/00:00:0f:00:00/40 tag 10 ncq 69632 in
res 41/84:88:78:1b:3e/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 60.706949] ata1.00: status: { DRDY ERR }
[ 60.707884] ata1.00: error: { ICRC ABRT }
[ 60.708824] ata1: hard resetting link
[ 61.028237] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 61.142293] ata1.00: configured for UDMA/33
[ 61.142319] ata1: EH complete
[ 61.195399] ata1.00: exception Emask 0x0 SAct 0x8000 SErr 0x0 action 0x6
[ 61.197750] ata1.00: irq_stat 0x40000008
[ 61.200089] ata1.00: failed command: READ FPDMA QUEUED
[ 61.201690] ata1.00: cmd 60/20:78:10:39:38/00:00:0f:00:00/40 tag 15 ncq 16384 in
res 41/84:20:14:39:38/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 61.204897] ata1.00: status: { DRDY ERR }
[ 61.206484] ata1.00: error: { ICRC ABRT }
[ 61.208071] ata1: hard resetting link
[ 61.525313] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 61.630818] ata1.00: configured for UDMA/33
[ 61.630845] ata1: EH complete
[ 61.675724] ata1.00: exception Emask 0x0 SAct 0x40000 SErr 0x0 action 0x6
[ 61.677345] ata1.00: irq_stat 0x40000008
[ 61.678943] ata1.00: failed command: READ FPDMA QUEUED
[ 61.680539] ata1.00: cmd 60/50:90:30:39:38/00:00:0f:00:00/40 tag 18 ncq 40960 in
res 41/84:50:70:39:38/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 61.683756] ata1.00: status: { DRDY ERR }
[ 61.685369] ata1.00: error: { ICRC ABRT }
[ 61.686586] ata1: hard resetting link
[ 62.005676] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 62.108289] ata1.00: configured for UDMA/33
[ 62.108316] ata1: EH complete
[ 62.162783] ata1.00: exception Emask 0x0 SAct 0x400000 SErr 0x0 action 0x6
[ 62.164411] ata1.00: irq_stat 0x40000008
[ 62.166015] ata1.00: failed command: READ FPDMA QUEUED
[ 62.167617] ata1.00: cmd 60/20:b0:d8:c3:3d/00:00:0f:00:00/40 tag 22 ncq 16384 in
res 41/84:20:d8:c3:3d/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 62.170837] ata1.00: status: { DRDY ERR }
[ 62.172433] ata1.00: error: { ICRC ABRT }
[ 62.173698] ata1: hard resetting link
[ 62.492749] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 62.607944] ata1.00: configured for UDMA/33
[ 62.607974] ata1: EH completeOutput of smartctl -a /dev/sda
smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.19.3-3-ARCH] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate Laptop SSHD
Device Model: ST1000LM014-SSHD-8GB
Serial Number: W3829AM6
LU WWN Device Id: 5 000c50 07be01372
Firmware Version: LVD3
User Capacity: 1,000,204,886,016 bytes [1,00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is: Sun May 10 11:12:02 2015 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
See vendor-specific Attribute list for marginal Attributes.
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 150) seconds.
Offline data collection
capabilities: (0x73) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 198) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x1081) SCT Status supported.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 117 099 006 Pre-fail Always - 158141600
3 Spin_Up_Time 0x0003 097 097 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 429
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 073 060 030 Pre-fail Always - 4319585187
9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 1864
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 437
184 End-to-End_Error 0x0032 089 089 099 Old_age Always FAILING_NOW 11
187 Reported_Uncorrect 0x0032 098 098 000 Old_age Always - 2
188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 069 052 045 Old_age Always - 31 (Min/Max 25/31)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 50
193 Load_Cycle_Count 0x0032 097 097 000 Old_age Always - 6179
194 Temperature_Celsius 0x0022 031 048 000 Old_age Always - 31 (0 19 0 0 0)
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
254 Free_Fall_Sensor 0x0032 100 100 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 13 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 13 occurred at disk power-on lifetime: 1779 hours (74 days + 3 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 10 ff ff ff 4f 00 09:58:41.053 READ FPDMA QUEUED
60 00 b0 ff ff ff 4f 00 09:58:41.053 READ FPDMA QUEUED
60 00 30 ff ff ff 4f 00 09:58:41.053 READ FPDMA QUEUED
ea 00 00 00 00 00 a0 00 09:58:40.403 FLUSH CACHE EXT
61 00 08 ff ff ff 4f 00 09:58:40.403 WRITE FPDMA QUEUED
Error 12 occurred at disk power-on lifetime: 1722 hours (71 days + 18 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 00 ff ff ff 4f 00 00:01:28.048 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:01:28.048 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 00:01:28.047 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:01:28.047 READ FPDMA QUEUED
60 00 30 50 3a c5 4e 00 00:01:28.045 READ FPDMA QUEUED
Error 11 occurred at disk power-on lifetime: 1537 hours (64 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 00 ff ff ff 4f 00 00:00:35.199 READ FPDMA QUEUED
60 00 20 ff ff ff 4f 00 00:00:35.198 READ FPDMA QUEUED
60 00 08 10 10 2b 4f 00 00:00:35.188 READ FPDMA QUEUED
60 00 e0 20 e0 78 4f 00 00:00:35.187 READ FPDMA QUEUED
60 00 90 68 e1 78 4f 00 00:00:35.185 READ FPDMA QUEUED
Error 10 occurred at disk power-on lifetime: 1525 hours (63 days + 13 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 a0 ff ff ff 4f 00 00:00:15.374 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 00:00:15.373 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 00:00:15.373 READ FPDMA QUEUED
60 00 80 ff ff ff 4f 00 00:00:15.370 READ FPDMA QUEUED
60 00 68 ff ff ff 4f 00 00:00:15.370 READ FPDMA QUEUED
Error 9 occurred at disk power-on lifetime: 1525 hours (63 days + 13 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 08 e0 9e 31 4f 00 00:00:15.146 READ FPDMA QUEUED
60 00 a8 ff ff ff 4f 00 00:00:15.073 READ FPDMA QUEUED
60 00 18 ff ff ff 4f 00 00:00:15.072 READ FPDMA QUEUED
60 00 98 ff ff ff 4f 00 00:00:15.072 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:00:15.068 READ FPDMA QUEUED
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.Is this software bug or hard drive failure? Thanks in advance.