Mailinglist Archive: opensuse (946 mails)

< Previous Next >
Re: [opensuse] WD Green AV HD: rsync read errors mapping
On 2017-09-07 08:19, Felix Miata wrote:
Carlos E. R. composed on 2017-09-07 02:00 (UTC+0200):

Felix Miata wrote:

Badblocks 1.42.11 on the WD Green AV HD has reached 100.00% completion with
(4/0/0 errors) in 129:44:20, 4 bad sectors in sequence.

Smartctl -x before process:

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
9 Power_On_Hours -O--CK 071 071 000 - 21875
192 Power-Off_Retract_Count -O--CK 200 200 000 - 414
193 Load_Cycle_Count -O--CK 200 200 000 - 1448

196 Reallocated_Event_Count -O--CK 200 200 000 - 0
197 Current_Pending_Sector -O--CK 200 200 000 - 6
198 Offline_Uncorrectable ----CK 100 253 000 - 0

Smartctl after process:

Ah, let's see.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE

197 Current_Pending_Sector -O--CK 200 200 000 - 1
198 Offline_Uncorrectable ----CK 100 253 000 - 0

Any comments?

One Pending out of six!

The number was 6, but the listed bad were 4:

984662252 984662253 984662254 984662255

I think the other two got cleared at the start of the test.


Each I assume to be a badblocks block of 1024 bytes. Internally that could be
as
few as one 4k sector, and no more than two.

Much better.

Well, what about the long test? Do that.
What long test? I just tied up a workspace 5.4 days to do badblocks using the
-n
(non-destructive read-write mode) switch, and in sloth mode (without a -b 4096
switch)!!!


smartctl --test=long /dev/sdb

it runs on the disk firmware, you can continue working almost normally. It will
print an estimate of when it will finish, perhaps in 4 hours.

You see the result with

smartctl -a /dev/sda

for instance. You have to look at this block:

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours)
LBA_of_first_error
# 1 Short offline Completed without error 00% 5650 -
# 2 Short offline Completed without error 00% 5641 -
# 3 Short offline Completed without error 00% 5617 -
# 4 Short offline Completed without error 00% 5602 -
# 5 Short offline Completed without error 00% 5585 -
# 6 Short offline Completed without error 00% 5571 -
# 7 Extended offline Completed without error 00% 5559 -

In my case, the short tests are run automatically by a daemon.
If there is an error, the test will abort and print the LBA in the last column.


badblocks -o bb-wd20eurs -s -n /dev/sdb1

The thing to do now is overwrite the bad sector with anything. Assuming
the badblocks program printed the LBA, it is possible to find where that
sector is. Finding the file is far from trivial, though, so you may have
to overwrite the entire partition.

1.863TiB (whole disk) partition. :-( Probably take less time to dd whole disk
and then restore from backup, probably most of another day at least, assuming
I
didn't destroy the device half an hour ago when I tripped and the external
case
it was in went flying onto the floor (fdisk does still find it). Meanwhile I'm
trying to get things in order, including trying to figure out why with my
freshly upgraded 24/7 box, from 42.1 to 42.3, KDE3 no longer reports USB stick
plugins (yet does with OM), anticipating an attack from the strongest Atlantic
hurricane on record. :-(

I don't know about that kde3 problem.

Yes, I heard about that hurricane. That's climate change in action, there is
more energy in the system. I wish good luck to all.


We can investigate whether knowing the LBA we can find what file is affected.
What filesystem is it?


--
Cheers / Saludos,

Carlos E. R.
(from 42.2 x86_64 "Malachite" at Telcontar)

< Previous Next >
Follow Ups