Hard drive woes - new 2TB Seagate Pipeline, lots of disk errors

[dkto]

Hi to all.

I have had my HDR-T2 for quite a while and have sent it back for disk replacement once already, which they did for disk cost and postage and in short time frame. Very happy with that but it was years ago.
The disk failed again a while later and I did not get round to doing anything about it until recently, when I bought a 2TB Seagate Pipeline and popped it in. No obvious hardware issues on the install.
Everything seemed to work fine - reinstalled custom firmware 3.13 and some packages and it looked good and I scheduled some recordings and initially all worked as expected.
I then started to get generalised freezing issues and apparently unplayable recordings, saw from the forum that this is dometimes disk related, so ran disk checks.
These threw out problems, and I accepted and reset, but they returned. I then went into the maintenance menu and tried short and long and fix-disk, but still had issues.

The fix-disk output includes a lot of messages like:

Running select disk self test
Error at LBA 3602390208

/dev/sda:
re-writing sector 3602390208: succeeded
This is an advanced-format disk.
Also checking blocks 3602390208 - 3602390215 (8 blocks)
Block 3602390208 - OK
Block 3602390209 - FAILED: Input/output error
- Repaired
... repeats for blocks 3602390210,3602390211,3602390212,3602390213,3602390214 ...
Block 3602390215 - FAILED: Input/output error
- Repaired

Running select disk self test
Error at LBA 3602390216

/dev/sda:
re-writing sector 3602390216: succeeded
This is an advanced-format disk.
Also checking blocks 3602390216 - 3602390223 (8 blocks)
Block 3602390216 - OK
Block 3602390217 - FAILED: Input/output error
- Repaired
... repeats again ...

(and lots more similar errors before and after those examples), but it did complete, and they all seemed to say 'Repaired'.

I removed a couple of potentially corrupt files and other things started working better - some recordings decrypted and became watchable (may or may not be due to disk, but it looked like it - I was also playing with autodecrypt settings so cannot be 100% sure it was just from file removal that things started working better). I was able to back up most things to my PC, so whilst nothing is vital, I have not even lost much of my recordings.

Disk problems continued, however and I ran fix-disk again but it seemed to go into an infinite loop in that it kept finding new bad sectors (like in the above messages) and resetting its count-down counter to 1520ish every time, so looked like it was never going to finish. After around 36 hours I gave up, rebooted, and ran the maint menu reformat option, deleting everything.

The 'gfdisk -lu /dev/sda' showed that the reformat had tweaked the partition start points a little - post (maint menu) reformat it is now:

Disk /dev/sda: 2000 GB, 2000396321280 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907024065 sectors
Units = sectors of 1 * 512 = 512 bytes

Device Boot Start End Blocks Id System
/dev/sda1 2048 2099199 1052226 83 Linux
/dev/sda2 2099200 3886057614 1941977362 83 Linux
/dev/sda3 3886059520 3907029134 10482412 83 Linux

I then reinstalled the firmware and got the web interface back, and first thing I see is the 'disk error' message panel, so went to disk diag and see:



and the disk info from that page is:

SMART data read from device /dev/sda

Disk Information

SMART Status PASSED
Model Family Seagate Video 3.5 HDD
Device Model ST2000VM003-1ET164
Serial Number Z520EQHE
LU WWN Device Id 5 000c50 092fa8eb6
Firmware Version SC12
User Capacity 2,000,398,934,016 bytes [2.00 TB]
Sector Sizes 512 bytes logical, 4096 bytes physical
Rotation Rate 5900 rpm
Form Factor 3.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: 3.0 Gb/s)
Local Time is Fri Aug 28 14:11:03 2020 BST
SMART support is Available - device has SMART capability.
SMART support is Enabled

Attributes
ID Name Flags Raw Value Value Worst Threshold Life Left Notes
1 Raw_Read_Error_Rate POSR-- 184566193 084 070 006 -
3 Spin_Up_Time PO---- 0 095 095 000 -
4 Start_Stop_Count -O--CK 30 100 100 020 100% -
5 Reallocated_Sector_Ct PO--CK 16553 087 087 010 86% -
7 Seek_Error_Rate POSR-- 13039219 071 060 030 -
9 Power_On_Hours -O--CK 1327 099 099 000 99% -
10 Spin_Retry_Count PO--C- 0 100 100 097 100% -
12 Power_Cycle_Count -O--CK 31 100 100 020 100% -
184 End-to-End_Error -O--CK 0 100 100 099 -
187 Reported_Uncorrect -O--CK 30164 001 001 000 -
188 Command_Timeout -O--CK 300652298310 100 091 000 -
189 High_Fly_Writes -O-RCK 198 001 001 000 -
190 Airflow_Temperature_Cel -O---K 49 051 (49°C) 046 (54°C) 045 (55°C) -
191 G-Sense_Error_Rate -O--CK 0 100 100 000 -
192 Power-Off_Retract_Count -O--CK 30 100 100 000 100% -
193 Load_Cycle_Count -O--CK 32 100 100 000 100% -
194 Temperature_Celsius -O---K 49 049 054 000 -
197 Current_Pending_Sector -O--C- 9255 044 001 000 -
198 Offline_Uncorrectable ----C- 9255 044 001 000 -
199 UDMA_CRC_Error_Count -OSRCK 0 200 200 000 -

Self-test logs
No. Description Status Remaining When First Error LBA
# 1 Short offline Completed without error 00% 1325 -
# 2 Selective offline Completed: read failure 90% 1325 3521603000
... repeats but with different 'First error LBA' entries (3521602976,3521602968,3521602960 etc.) up to ...
#21 Selective offline Completed: read failure 90% 1325 3521602816


So, is there anything else I can usefully try such as tweaking the e2fs parameters, or does it look like my brand new disk is just faulty ?

Let me know if there is anything else I can run - I will send or post any output as files unless very short.

Thank you for any help you can offer.

Rick

 

[MymsMan]

Three faulty disks would be incredibly unlucky, I am (touch wood) still using the original disk with no more than a couple of faulty sectors.

I wonder if there could be something else wrong in the system affecting the disk such as supply voltages or fan failures,
Do you use the fan package? though the smart data doesn't show any abnormally high temperatures.

 

[dkto]

I used to use fan package before last disk blew up - I was on out-of-box firmware until first disk died, after a number of years, then ran on custom firmware with the factory replacement, for a few more years. I had not yet put 'fan' back on and weather has been a tad warm, but I think that latest disk should not have failed within a couple of weeks of installation.

I was not very disappointed with first disks - they served for years at a time - but a brand new one should be doing better.

I can try to get seller to replace if I know it is faulty, and am just looking to make sure I do know that and have not left any unturned stones in my config options.

Thanks
Rick

 

[dkto]

The unit is quite old and therefore supply voltages may have drifted if controlled with evaporating electrolytics or something, or historically abused by one the other drives in its death throes.
I don't have anything very precise to measure them with unfortunately, especially under load and normal working.

I do have a USB caddy and could probably attach to a linux box for additional testing of the disk, though.

 

[MartinLiddle]

I can try to get seller to replace if I know it is faulty, and am just looking to make sure I do know that and have not left any unturned stones in my config options.

Can you tell us who the seller was please? What is the year of manufacture on the label on the hard drive?

 

[prpr]

reinstalled custom firmware 3.13

Why? The firmware isn't stored on the disk.

I gave up, rebooted, and ran the maint menu reformat option, deleting everything.

That doesn't fix the physical problems with the disk. It just builds a brand new brick wall on marshmallow foundations.

I then reinstalled the firmware

What, again?

first thing I see is the 'disk error' message panel

Well yes, you would, seeing as the disk is still broken. Your brand new wall has cracks in it as soon as it's been built.

5 Reallocated_Sector_Ct PO--CK 16553 087 087 010 86% -
187 Reported_Uncorrect -O--CK 30164 001 001 000 -
188 Command_Timeout -O--CK 300652298310 100 091 000 -
189 High_Fly_Writes -O-RCK 198 001 001 000 -
197 Current_Pending_Sector -O--C- 9255 044 001 000 -
198 Offline_Uncorrectable ----C- 9255 044 001 000 -

All very bad.

So, is there anything else I can usefully try such as tweaking the e2fs parameters, or does it look like my brand new disk is just faulty ?

No, it's broken beyond any help. Send it back.

 

[dkto]

@MymsMan Thanks for feedback.

 

[dkto]

@MartinLiddle Good thought - I will post more details from (paper) disk label when I open box up again after the weekend as I am away until next week.
Sorry did not take a photo before install, which is always a handy thing to have done.

For better or worse it was an Amazon order (I am not permitted to include links but you can look up I should think):

Seagate ST2000VM003 Pipeline HD 2 TB 3.5-Inch Internal Hard Drive (Amazon product ID B008B0RQ1C)
Sold by Artio International Limited (Amazon seller A1R111JYQQ0J9G)

 

[dkto]

@prpr Thank you for your reply.

Seeing as you asked, I reinstalled the custom firmware initially to get it up to date as it was several years old, then after wiping the disk I did it again to get a clean slate and exclude any possible complications from any added packages or messing up of config on my part, to remove those potential sources of 'noise' from the situation.

Corroboration that the disk is probably duff is interesting, but ' a bloke on a forum says it is broken' won't help with the supplier.

I was/am looking for a bit more understanding or, if it happened to not be duff, suggestions as to what newbie idiocy I might have perpetrated in my config which could be undone to make things right.

Repeating short and cryptic messages from the diagnostic without further 'aha - that means this definitive disastrous disk condition is extant', or just pointers to useful docs or explanations, does not really move things forward.

I welcome all attempts to sympathise, share experiences, or educate, but please do not just suggest that steps taken are brain dead or that it was pointless to mention them, or assume that an authoritative opinion has value without evidence - Russel's teapot is definitely out there, but I encourage you to go check.

Thank you for replying, though -
"There is only one thing worse than [your forum post pleading for help] being talked about, and that is [your forum post pleading for help] not being talked about"

 

[MymsMan]

Corroboration that the disk is probably duff is interesting, but ' a bloke on a forum says it is broken' won't help with the supplier.

No but @prpr is making his comments based on the smart data you presented and no supplier can legitimately claim that the offline and reallocated sector counts are normal on a new disk. You don't need any further evidence that the disk is not fit for purpose

 

[Andy Fox]

I bought the 1TB version of this from Amazon (seller was Abel-TV Handels GmbH) a few weeks ago. My HDR T2 didn't recognise it, and neither did the Bios on my PC. Sent it back and got an immediate full refund. The label on the drive didn't look like other Seagate drives I have, so I was a bit suspicious from the start.

In the end I got a 500MB reconditioned one from Ultratec (ST3500312CS 9GW132-191, same as the old one) which arrived very well packaged, for under £20 including delivery. So far no problems with it, but early days yet.

 

[prpr]

Corroboration that the disk is probably duff is interesting, but ' a bloke on a forum says it is broken' won't help with the supplier.

16000+ re-mapped bad sectors and 9000+ unre-mappable bad sectors (because there aren't any spares left to re-map) says to me this disk is completely and utterly broken. Both values should be 0.

Seeing as you asked, I reinstalled the custom firmware initially to get it up to date as it was several years old

I would use the word "updated" or "upgraded" rather than "reinstalled" then. Or at least make it clear you were on an old version. To me, reinstall means re-apply the same version. Put yourself in the position of the reader, with no prior knowledge of your particular circumstances and see if it still makes sense.

 

[Ezra Pound]

@dkto : The SMART data you supplied says the HDD has been running for 1327 hours which at 24 hours a day is 55 days, a lot more than the 'couple of weeks' you have been running it, so it had obviously been used (and abused?), before you got it

 

[MartinLiddle]

For better or worse it was an Amazon order (I am not permitted to include links but you can look up I should think):

Seagate ST2000VM003 Pipeline HD 2 TB 3.5-Inch Internal Hard Drive (Amazon product ID B008B0RQ1C)
Sold by Artio International Limited (Amazon seller A1R111JYQQ0J9G)

I remain very suspicious of these hard drives from sellers on Amazon Marketplace.

 

[dkto]

@prpr Thank you - that is exactly the sort of thing I need highlighted and explained.
@MymsMan Thank you too for highlighting and explaining
@AndyFox Good to know, thank you
@Ezra Pound Perfect ammunition, thank you

Time to start fighting with supplier for a refund (they do give every impression of trying to avoid returns).

I will seek out another supplier for a replacement.

I will post resolution when I get one.

Thanks again to all,
Rick

 

[dkto]

@MartinLiddle - also thank you.

Will still post label when I get at box.

For what it is worth, hummy still cranks away despite disk problems and continues to record stuff, most of which is coming out fine.

 

[dkto]

Well, thank you to all respondents and I seem to have a working disk now.

Caution over Amazon suppliers seems warranted.

The Seagate Pipeline ST2000VM003 which others have found a good replacement 2TB drive is now discontinued, but I persisted.

First Amazon supplier (Artio International Limited (Amazon seller A1R111JYQQ0J9G)) did not trouble themselves overmuch with packaging.
They used standard Amazon small package with disk just bubblewraped round its anti-static bag.
They are offering a return for refund (as they should) even though outside of Amazon send-it-back-even-if-you-just-dont-like-it window.
I will send it back this week once I have retrieved remaining files off it, in case they are still watchable (pot luck - some were OK).

Dodgy disk had the following info on its label:

ST2000VM003
SN: Z520EQHE
PN: 1ET164-512
FW: SC12
WWN: 5000C50092FA8EB6
PSID: T720LWAV8SMU8KRES0TG8XQF749EREUA
Site: TK
DOM:15OCT2016

Netherlands Seagate office address, Product of Thailand

Obviously 4 years old and may have been recycled from somewhere or left on an OEM shelf then resold.

Found another one at similar price (glutton for punishment) (WEB-NF | Preise inkl. MwSt. (Amazon seller A332MX0Z0E0ZL)), similar inadequate packaging.
This disk was DOA, did not even spin up in a docking bay or the hummy. Also signs of sticky label or tape having being removed either side of Seagate ID label, which was not encouraging.
Returned for refund and got refund same afternoon as dropped parcel at pick-up shop for collection by courier. Have photo if anyone wants disk label info.

Had trouble finding this disk in stock anywhere else at a half reasonable price, so thought I would try Amazon one last time before trying a WD or newer Seagate model.
Pricing was £50-60 on Amazon with very quick delivery, £150 elsewhere - and yes, I do realise there is a reason for this !

I found another seller (Abel-TV Handels GmbH (Amazon seller A3RD70G5C10ORJ) - the same seller "Andy Fox" had trouble with his disk from, but I did not notice this in time (would have probably not used them).
Disk arrived in much better packaging - no foam but shrink wrapped into properly designed cardboard support packaging then shipped, with additional packing materials, in a larger Amazon box.
Disk reports perfectly OK, formatted from TV menu and left running for 12 hours before running short disk check and it reports all seems fine (so far so good).

Web interface trashed, obviously, and had trouble reinstalling it (from telnet menu or opkg --force-reinstall) so successfully reinstalled firmware (again) so I know nothing missing and all clean as I hope to run with this for another few years. webif now back up and running. I will also make sure 'fan' package is installed and running and keep a close eye on disk for a while in case I have PSU voltage drift or something else causing trouble under the covers.

Some of the recordings on the dodgy disk worked so I will copy them back onto new disk over network, accepting that some of the files may be slightly corrupted by bad sectors on failing disk.

I will post again if further trouble, but thanks to all for their help.

Rick

 

[MartinLiddle]

I found another seller (Abel-TV Handels GmbH (Amazon seller A3RD70G5C10ORJ) - the same seller "Andy Fox" had trouble with his disk from, but I did not notice this in time (would have probably not used them).

Could you tell us the date of manufacture of this one please?

 

[RogerW17]

My disk is failing and I see that the disk replacements mentioned in the forums are no longer easily available. Does anyone have any experience of using the Seagate SkyHawk 2TB Surveillance Hard Drive ST2000VX008 or can recommend another currently available drive that would work?

 

[Black Hole]

Does anyone have any experience of using the Seagate SkyHawk 2TB Surveillance Hard Drive ST2000VX008

A forum search on "skyhawk" achieves several hits.