Re: HDD - Read verification failed - Grupy dyskusyjne w eGospodarka.pl

eGospodarka.pl › Grupy › pl.comp.pecet › HDD - Read verification failed › Re: HDD - Read verification failed

Path: news-archive.icm.edu.pl!news.icm.edu.pl!news.nask.pl!news.nask.org.pl!news.unit
0.net!newsreader4.netcologne.de!news.netcologne.de!peer03.ams1!peer.ams1.xlned.
com!news.xlned.com!feeder.cambriumusenet.nl!feed.tweaknews.nl!posting.tweaknews
.nl!fx05.ams1.POSTED!not-for-mail
Newsgroups: pl.comp.pecet
From: Marcin Debowski <a...@I...zoho.com>
Subject: Re: HDD - Read verification failed
References: <5bf03032$0$485$65785112@news.neostrada.pl>
<pspf8v$gpm$1@node2.news.atman.pl>
<5bf0569d$0$500$65785112@news.neostrada.pl>
<5bf05d49$0$498$65785112@news.neostrada.pl>
<pspncs$odr$1@node2.news.atman.pl>
<5bf062f5$0$522$65785112@news.neostrada.pl>
<5bf06660$0$516$65785112@news.neostrada.pl>
<5bf06bc7$0$479$65785112@news.neostrada.pl>
<N33ID.588843$FD.352655@fx17.ams1>
<5bf15659$0$483$65785112@news.neostrada.pl>
<TdpID.409342$086.67357@fx03.ams1>
<5bf25fa2$0$493$65785112@news.neostrada.pl>
<o2uID.590616$FD.307490@fx17.ams1>
<5bf287bc$0$476$65785112@news.neostrada.pl>
<p_vID.466422$pK.429320@fx20.ams1>
<5bf2a2e6$0$506$65785112@news.neostrada.pl>
User-Agent: slrn/1.0.3 (Linux)
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Lines: 34
Message-ID: <QdyID.422530$PY.214637@fx05.ams1>
X-Complaints-To: a...@t...nl
NNTP-Posting-Date: Mon, 19 Nov 2018 12:43:28 UTC
Organization: Tweaknews
Date: Mon, 19 Nov 2018 12:43:28 GMT
X-Received-Body-CRC: 1671838261
Xref: news-archive.icm.edu.pl pl.comp.pecet:1260544
[ ukryj nagłówki ]
On 2018-11-19, E <n...@p...pl> wrote:
> Error 426 [17] occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
> When the command that caused the error occurred, the device was in an unknown
state.
>
> After command completion occurred, registers were:
> ER -- ST COUNT LBA_48 LH LM LL DV DC
> -- -- -- == -- == == == -- -- -- -- --
> 40 -- 00 00 08 00 51 00 00 e0 00 00 00
>
> Commands leading to the command that caused the error were:
> CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
> -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
> 00 76 25 08 7c 00 00 00 00 00 00 00 00 00:00:00.000 NOP [Reserved
subcommand] [OBS-ACS-2]
> 00 08 00 00 00 07 31 00 8a 25 00 00 00 00:00:00.008 NOP [Abort queued
commands]
> 00 a0 b0 06 97 00 08 00 00 00 00 00 00 00:07:12.033 NOP [Reserved
subcommand] [OBS-ACS-2]
> 00 08 00 00 a0 06 15 12 89 25 00 00 00 00:00:57.345 NOP [Abort queued
commands]

Może inni coś więcej z tego wyciągną, ale ja nie widzę niczego jakoś
silnie niepokojącego. Te błędy to może być np. poluzowany kabel sata lub
coś w podobnym stylu.

Zapuść proszę, najpierw:

smartctl -d sat -t short /dev/sdb
wyniki w sekcji SMART Self-tests log ......

A jeśli nie zwróci błędów to długi:

smartctl -d sat -t long /dev/sdb
To protrwa.
Status możesz sprawdzać smartctl -a -d sat /dev/sdb|grep remaining

--
Marcin