Mailinglist Archive: opensuse (795 mails)

< Previous Next >
Re: [opensuse] another WD Green AV-GP HD failure [solved]


On 06/11/2017 06:51, Felix Miata wrote:
Felix Miata composed on 2017-11-05 18:12 (UTC-0500):

Wols Lists composed on 2017-11-05 12:02 (UTC):

Felix Miata wrote:
...
Had you read the link in the post you replied to you should have noticed the
disk would have been far from new when that recording was made, possibly at
around 14426 hours or 20 months disk on time. The SD DVDR that the disk is in
offers no evidence that it employs Smart technology.

Ah. I see. But even so ...

Earlier in this thread I showed Smartctl reported 131 pending sectors and
reallocated sector count of 0. It's the second of the very same model in
identical service here, the two being manufactured less than 90 days apart. I
consider the old HD junk at this point, and likely most if not all of that model
from that period.

imho you're throwing away a teenager of a drive ... I'll explain why.

Firstly, do you understand what a "pending relocation" is? Yup, that's
at 131, but I'd be far more concerned about that figure if it was the
"reallocated sectors" figure.

Without knowing better, it looks like a quantity of sectors that failed to be
written to.

I had a look at the WD Green spec sheet. It comes with a 2-year
warranty, so yes, assuming the drive is used 8 hours a day it's probably
well outside its wall-clock warranty, but it's only been powered up just
over it.

The drive also is rated at 300K spin-up cycles. If your typical program
is 30mins, that means you've used about 40K. Just over one tenth, which
is why I describe the drive as a teenager. (And you've probably used
rather less.

Apparently you missed the OP:
https://lists.opensuse.org/opensuse/2017-11/msg00010.html

No need to guess. There is ostensibly only one program, the proprietaryware that
uses the disk in its own proprietary manner, with few and generally brief
exceptions, constantly recording when powered up. As I have it powered up more
often than not, its usage differs little from a surveillance system, biggest
difference editing out of commercials. Power cycling is infrequent, while backup
and restore are as a practical matter not feasible even though it includes a
DVD-RW device. Write back from DVD to HD using the device is only possible via
real time (dub) recording. Genuine byte-accurate backup/restore is only possible
by removal from the STB and using other equipment.

Pending relocations say absolutely nothing about the health of the
drive, although they are bad for your data ... all it means is the drive
can no longer read the sector, which could be anything from a stray
cosmic ray, to a tired recording, to a power surge moving the actuator,
to flaking oxide presaging a head crash. Anything.

Lots of sectors on this device hard or impossible to read:
http://fm.no-ip.com/Tmp/Hardware/Disk/Funai/wd3200avvs8180log.txt

The STB is apparently insufficiently sophisticated to utilize Smart features, or
work through repeated read failures gracefully.

Given that this is the second of exact same model, of less than 3 months
difference in age, that developed a multitude of unreadable sectors in 3 years
or less, in exactly equivalent usage, I have to be suspicious of poor design or
execution at manufacture.

Humour me. "dd if=/dev/zero of=/dev/wdgreen". Your pending sectors WILL
go back to zero - trust me. If relocated sectors goes up, then yes that
is cause for concern, but there's every likelihood they will stay at zero.

# date
Sun Nov 5 15:48:14 EST 2017
# dd if=/dev/zero of=/dev/sdb bs=16384
dd: error writing '/dev/sdb': No space left on device
19535702+0 records in
19535701+0 records out
320072933376 bytes (320 GB, 298 GiB) copied, 5324.73 s, 60.1 MB/s
# date
Sun Nov 5 17:45:24 EST 2017
# smartctl -x /dev/sdb | grep -A26 "SMART Attributes Data"
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-K 200 200 051 - 1986
3 Spin_Up_Time POS--K 157 153 021 - 3150
4 Start_Stop_Count -O--CK 099 099 000 - 1535
5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0
7 Seek_Error_Rate -OSR-K 200 200 000 - 0
9 Power_On_Hours -O--CK 072 072 000 - 20916
10 Spin_Retry_Count -O--CK 100 100 000 - 0
11 Calibration_Retry_Count -O--CK 100 100 000 - 0
12 Power_Cycle_Count -O--CK 099 099 000 - 1524
192 Power-Off_Retract_Count -O--CK 200 200 000 - 39
193 Load_Cycle_Count -O--CK 200 200 000 - 1535
194 Temperature_Celsius -O---K 102 084 000 - 41
196 Reallocated_Event_Count -O--CK 200 200 000 - 0
197 Current_Pending_Sector -O--CK 200 198 000 - 0
198 Offline_Uncorrectable ----CK 100 253 000 - 0
199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 1
200 Multi_Zone_Error_Rate ---R-- 100 253 000 - 0
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning

Current Pending was 198 198 000 - 131

So, maybe it's serviceable somewhere, but the DVDR has been upgraded to 500GB.

The drive cannot correct pending sectors by itself, it needs the
computer to attempt to write to them. If the write is successful, it
clears the error. If the write is unsuccessful, it relocates the sector
elsewhere (which is the point at which you start worrying about the
health of the drive).

In its originally shipped proprietary STB installation state, how would one go
about forcing a write to an already occupied area of unknown and unknowable
location?

I found the 3 month older identical model WD3200AVVS pulled from use 3 years ago
and applied essentially the same process to the same state. It appears I have a
fairly matched pair doing shelf duty now:

# smartctl -x /dev/sdc | grep -A26 "SMART Attributes Data"
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-K 200 200 051 - 3342
3 Spin_Up_Time POS--K 156 153 021 - 3191
4 Start_Stop_Count -O--CK 100 100 000 - 873
5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0
7 Seek_Error_Rate -OSR-K 100 253 000 - 0
9 Power_On_Hours -O--CK 063 063 000 - 27078
10 Spin_Retry_Count -O--CK 100 100 000 - 0
11 Calibration_Retry_Count -O--CK 100 100 000 - 0
12 Power_Cycle_Count -O--CK 100 100 000 - 866
192 Power-Off_Retract_Count -O--CK 200 200 000 - 31
193 Load_Cycle_Count -O--CK 200 200 000 - 873
194 Temperature_Celsius -O---K 113 073 000 - 30
196 Reallocated_Event_Count -O--CK 200 200 000 - 0
197 Current_Pending_Sector -O--CK 194 173 000 - 313
198 Offline_Uncorrectable ----CK 100 253 000 - 0
199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 2
200 Multi_Zone_Error_Rate ---R-- 100 253 000 - 0
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning
# date
Sun Nov 5 21:40:11 EST 2017
# dd if=/dev/zero of=/dev/sdb bs=8192
39071404+0 records in
39071404+0 records out
320072933376 bytes (320 GB, 298 GiB) copied, 5406.76 s, 59.2 MB/s
# date
Sun Nov 5 23:21:02 EST 2017
# smartctl -x /dev/sdc | grep -A26 "SMART Attributes Data"
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-K 200 200 051 - 3342
3 Spin_Up_Time POS--K 156 153 021 - 3191
4 Start_Stop_Count -O--CK 100 100 000 - 873
5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0
7 Seek_Error_Rate -OSR-K 100 253 000 - 0
9 Power_On_Hours -O--CK 063 063 000 - 27080
10 Spin_Retry_Count -O--CK 100 100 000 - 0
11 Calibration_Retry_Count -O--CK 100 100 000 - 0
12 Power_Cycle_Count -O--CK 100 100 000 - 866
192 Power-Off_Retract_Count -O--CK 200 200 000 - 31
193 Load_Cycle_Count -O--CK 200 200 000 - 873
194 Temperature_Celsius -O---K 098 073 000 - 45
196 Reallocated_Event_Count -O--CK 200 200 000 - 0
197 Current_Pending_Sector -O--CK 200 173 000 - 0
198 Offline_Uncorrectable ----CK 100 253 000 - 0
199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 2
200 Multi_Zone_Error_Rate ---R-- 100 253 000 - 0
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning

Just a thought, your device doesn't use smart on the disk but smart settings stay across resets and power cycles. Maybe if you enable smart via smartctl the disk might take better care of itself.
Dave P

--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >