Second Hand Disk SMART stats

BennyBoy

BennyBoy

Member
I've just replaced my 500Gb Seagate Pipeline ST3500312CS for a 2nd hand 1TB Seagate Pipeline ST1000VM002. I took a punt from what appears a reputable (100% feedback) vendor on eBay. Checking the HDD SMART data when all plumbed into the HDR-FOX-T2 I can see the following.

Code: 
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   116   099   006    Pre-fail  Always       -       104600776
  3 Spin_Up_Time            0x0003   097   097   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   096   096   020    Old_age   Always       -       4578 <===  OVER HERE
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       8    <=== OVER HERE
  7 Seek_Error_Rate         0x000f   077   060   030    Pre-fail  Always       -       52230830786
  9 Power_On_Hours          0x0032   073   073   000    Old_age   Always       -       24145    <=== OVER HERE
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       992
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   001   001   000    Old_age   Always       -       2338
190 Airflow_Temperature_Cel 0x0022   046   046   045    Old_age   Always       -       54 (Min/Max 41/54)
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       -       985
193 Load_Cycle_Count        0x0032   098   098   000    Old_age   Always       -       4579
194 Temperature_Celsius     0x0022   054   054   000    Old_age   Always       -       54 (0 10 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

This drive has be on for approx 2.75 years! Being a newbie I'm not so sure how "Ok" these SMART stats are.
 
Last edited:
Many Thanks prpr . Got it for £28. Am running Fix Disk on it right now (as the HDD warning came on for and will leave it through the night owing to Line 5 in my post (Reallocated_Sector_Ct).
The Customer Firmware is just BRILLIANT. Has breathed new life into the HDR-FOX-T2.
 
Left Fix Disk running last night. This morning found that you can ping the hummy but it's like no ports were open. Cannot telnet or use Webif. Had to cold boot it (which meant I had to get out of bed). To add, as a precautionary measure I've now set all settings under Power Management to OFF so that there's no cause for the box to power down, and am running Fix Disk again.
 
Last edited:
Okay, so it crashed. No biggie (except the having to get out of bed, but a remote controlled mains socket would sort that).

It strikes me as false economy to be sourcing second hand HDDs for "mission critical" applications, but then again I'm running on six or seven year old drives...
 
Newbie question on the Fix Disk (it's still running; monitoring it through a PuTTy session)...
When the task finishes would I need to "Acknowledge" any warnings in Webif Diagnostics or will Fix Disk have cleared them up?

I agree with you Black Hole ... on the false economy of buying a 2nd HDD. It is a gamble. If I were building a NAS I always get brand new disks. I figured my hummy hardware is getting older too. But this actually made me think of questions to ask on buying 2nd hand drives like this.

(Eg. "Please do you have the SMART data to hand for the Start_Stop_Count, Reallocated_Sector_Ct, Power_On_Hours and the High_Fly_Writes?").

And if they don't have it you can still decide whether to take a punt or not. I tend to archive stuff off the hummy over time so there's usually a backup on NAS or external USB + most of the recent stuff we watch is available on iPlayer, ITV Hub, All 4 etc. (especially with All 4 doing boxsets of series online).
 
Passing post...... Seeing a lot of this during the Fix-Disk run in PuTTy...
Code: 
Too many illegal blocks in inode 25007850.
Clear inode? yes

Inode 25007685 has compression flag set on filesystem without compression support.  Clear? yes

Inode 25007685 has illegal block(s).  Clear? yes

Illegal block #0 (1350801933) in inode 25007685.  CLEARED.
Illegal block #1 (2898426868) in inode 25007685.  CLEARED.
Illegal block #2 (1760658802) in inode 25007685.  CLEARED.
Illegal block #3 (1936842833) in inode 25007685.  CLEARED.
Illegal block #5 (3324756347) in inode 25007685.  CLEARED.
Illegal block #6 (3695537060) in inode 25007685.  CLEARED.
Illegal block #7 (1753171769) in inode 25007685.  CLEARED.
Illegal block #8 (3835715201) in inode 25007685.  CLEARED.
Illegal block #9 (2271133120) in inode 25007685.  CLEARED.
Illegal block #10 (1646757876) in inode 25007685.  CLEARED.
Illegal block #11 (3167553052) in inode 25007685.  CLEARED.
Too many illegal blocks in inode 25007685.

Lost connectivity with the hummy again as Telnet screen has stopped and not able to access Webif.
 
Last edited:
Hey! Sweet turn of events!

Fix-disk finished relatively quickly only after I decided to follow the disk formatting advice from this Wiki Link on 2TB Disk Installation, even though I'm using a 1Tb HDD. Because there were fewer inodes this really sped things up with Fix-Disk. Originally I formatted the HDD using the on-screen message when powering up the hummy. I'm sure this format creates tonnes of inodes. Used "gfdisk" that comes bundled with the CF to create partitions. Also afterwards in SMART output "Reallocated_Sector_Ct" is still set at 8 after running Fix-Disk. Acknowledged this error in Webif.
Took me some time to work out sectors and aligning them with the Linux OS etc.

## My partition config looks like this....
Code: 
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1              64     2097215     1048576  83 Linux
Partition 1 does not end on cylinder boundary         <=== (Linux does not care apparently)
/dev/sda2         2097216  1932553631   965228208  83 Linux
/dev/sda3      1932553632  1953525151    10485760  83 Linux

## And I used these commands to format them.
Code: 
humax# mkfs.ext3 -m 0 -O sparse_super /dev/sda1
humax# mkfs.ext3 -m 0 -O sparse_super -T largefile /dev/sda2
humax# mkfs.ext3 -m 0 -O sparse_super /dev/sda3

## System in action
Code: 
humax# df -h

Filesystem                Size      Used Available Use% Mounted on
/dev/root                21.6M     21.6M         0 100% /
tmpfs                    61.0M     60.0K     61.0M   0% /tmp
tmpfs                    61.0M         0     61.0M   0% /media
/dev/mtdblock1            2.0M    544.0K      1.5M  27% /var/lib/humaxtv
/dev/mtdblock2            2.0M    456.0K      1.6M  22% /var/lib/humaxtv_backup
/dev/sda1              1007.9M     47.5M    960.4M   5% /mnt/hd1
/dev/sda2               920.2G      2.1G    918.1G   0% /mnt/hd2
/dev/sda3                 9.8G    278.8M      9.6G   3% /mnt/hd3

humax# df -ih

Filesystem              Inodes      Used Available Use% Mounted on
/dev/root                 1.8K      1.8K         0 100% /
tmpfs                    15.3K        22     15.2K   0% /tmp
tmpfs                    15.3K         4     15.3K   0% /media
/dev/mtdblock1               0         0         0   0% /var/lib/humaxtv
/dev/mtdblock2               0         0         0   0% /var/lib/humaxtv_backup
/dev/sda1                64.0K        14     64.0K   0% /mnt/hd1
/dev/sda2               920.6K      5.5K    915.1K   1% /mnt/hd2
/dev/sda3               640.0K        14    640.0K   0% /mnt/hd3

Kids are now watching Cbeebies (at last). With the hummy out of action for Fix-Disk maintenance they were persistently asking "Daddy is the TV working".
Chromecast saved my bacon yesterday :)

Thank you ALL for your advice and help.
 
Last edited:
I'm happy. Fix-Disk worked. :) Used WebIf "Diagnostics" to ensure the sectors aligned with the OS.

Code: 
>>> Beginning diagnostic 4kalign

Running: 4kalign

--> This is an Advanced Format (AF) drive.

   Model Number:       ST1000VM002-1CT162                  
   Logical  Sector size:                   512 bytes
   Physical Sector size:                  4096 bytes
   Logical Sector-0 offset:                  0 bytes
   Nominal Media Rotation Rate: 5900

Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x1c41f8d1

Device     Boot      Start        End    Sectors   Size Id Type
/dev/sda1               64    2097215    2097152     1G 83 Linux
/dev/sda2          2097216 1932553631 1930456416 920.5G 83 Linux
/dev/sda3       1932553632 1953525151   20971520    10G 83 Linux

*  OK   * - partiton /dev/sda1 is properly aligned.
*  OK   * - partiton /dev/sda2 is properly aligned.
*  OK   * - partiton /dev/sda3 is properly aligned.

>>> Ending diagnostic 4kalign
 
Last edited:
All this pussy-footing!

The problem is that some newcomers have been offended and stormed off never to darken our doors again by some very minor comments on protocol or whatever (usually from me), which has then made some of the forum elders indignant (real or fake, and almost exclusively those who always have it in for me anyway). I don't have a lot of sympathy.

There was an example recently when somebody came on here brand new, touting information that was dubious and we (with all our experience) were unable to verify, and got in a right huff when we said so.
 
Last edited:
I guess from here, what I would like to do now is just give a summary of what I did and things I've learned from doing this, so if another (newbie or not) comes along they can reference it if they want. Also looking back (he says chuckling to himself) I saw the "Power_On_Hours" from my now old 500Gb disk, and that strangely enough was around the 22,000+ hours mark as well.
Just copying back all the stuff from the old disk via USB and using the Telnet cli now. To preserve file and date timestamps:

Code: 
humax# cp -pR <source> <destination>
If you are copying folders with sub-folders. Omit the "R" if not.
 
Last edited:
For reference, my oldest HDR-FOX with original HDD:
Code: 
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE                                                                             
  1 Raw_Read_Error_Rate     0x000f   105   099   006    Pre-fail  Always       -       9837197                                                                               
  3 Spin_Up_Time            0x0003   097   097   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   094   094   020    Old_age   Always       -       6398                                                                                   
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   087   060   030    Pre-fail  Always       -       667185519                                                                             
  9 Power_On_Hours          0x0032   047   047   000    Old_age   Always       -       47179                                                                                 
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   097   097   020    Old_age   Always       -       3199                                                                                   
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   096   096   000    Old_age   Always       -       4
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   087   087   000    Old_age   Always       -       13                                                                                     
190 Airflow_Temperature_Cel 0x0022   055   042   045    Old_age   Always   In_the_past 45 (Min/Max 42/46 #5121)                                                               
194 Temperature_Celsius     0x0022   045   058   000    Old_age   Always       -       45 (0 13 0 0 0)                                                                       
195 Hardware_ECC_Recovered  0x001a   038   028   000    Old_age   Always       -       9837197                                                                               
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
 
Do you want to "sanitise" the rest of the forum too? It's all valid expression of opinion, and will get buried as time goes on anyway. It's worth tidying up a specific documentation topic that will be a primary reference source, but otherwise it's opening a can of worms.
 
BennyBoy said:
I've just replaced my 500Gb Seagate Pipeline ST3500312CS for a 2nd hand 1TB Seagate Pipeline ST1000VM002. I took a punt from what appears a reputable (100% feedback) vendor on eBay. Checking the HDD SMART data when all plumbed into the HDR-FOX-T2 I can see the following.
Click to expand...
Sorry to be late responding but I have a similar drive (2TB ST2000VM003) with a very similar number of running hours and my statistics look very similar to yours and our drive has been faultless so far.
 
You must log in or register to reply here.
Back
Top