Is my HDD ok?

rodp

Member
Hi All,

I've trying to understand the diagnostics for my HDD after reading this post: http://hummy.tv/forum/threads/beeping-box.4671/

This is my info. This was taken whilst nothing was recording and i wasn't playing anything, just watching TV. What does the 'Pre-fail' mean and does that change to 'fail' if the raw value exceeds the threshold value or something?

Perhaps there is a good explanation of each of these attributes but as yet I haven't come across anything yet.

Thanks

Rodp
Some info about my box: HDR Fox T2 1TB 1.02.32 with CF 2.17, Box was purchase 2nd hand from JL June 2013 but first purchase ~Dec 2012.

(apologies for the table layout - tried very hard to create a normal table but forum wont let me)

ID Name Flags Raw Value Value Worst Thresh Type Updated When Failed
1 Raw_Read_Error_Rate POSR-- 1.28E+08 117 99 6 Pre-fail Always -
3 Spin_Up_Time PO---- 0 97 97 0 Pre-fail Always -
4 Start_Stop_Count =-O--CK 1376 99 99 20 Old_age Always -
5 Reallocated_Sector_Ct PO--CK 0 100 100 36 Pre-fail Always -
7 Seek_Error_Rate POSR-- 1.9E+08 82 60 30 Pre-fail Always -
9 Power_On_Hours =-O--CK 3259 97 97 0 Old_age Always -
10 Spin_Retry_Count PO--C- 0 100 100 97 Pre-fail Always -
12 Power_Cycle_Count =-O--CK 1376 99 99 20 Old_age Always -
184 End-to-End_Error =-O--CK 0 100 100 99 Old_age Always -
187 Reported_Uncorrect =-O--CK 0 100 100 0 Old_age Always -
188 Command_Timeout =-O--CK 0 100 100 0 Old_age Always -
189 High_Fly_Writes =-O-RCK 206 1 1 0 Old_age Always -
190 Airflow_Temperature_Cel =-O---K 51 49 40 45 Old_age Always In_the_past
191 G-Sense_Error_Rate =-O--CK 0 100 100 0 Old_age Always -
192 Power-Off_Retract_Count =-O--CK 1375 100 100 0 Old_age Always -
193 Load_Cycle_Count =-O--CK 1376 100 100 0 Old_age Always -
194 Temperature_Celsius =-O---K 51 51 60 0 Old_age Always -
197 Current_Pending_Sector -O--C- 0 100 100 0 Old_age Always -
198 Offline_Uncorrectable ----C- 0 100 100 0 Old_age Offline -
199 UDMA_CRC_Error_Count =-OSRCK 0 200 200 0 Old_age Always -
 

Ezra Pound

Well-Known Member
Not sure which aspect of your HDD you are interested in but :-
5, 197 and 198 raw = zero . . . this is good as far as failures / corrections go
194 worst = 60 deg. C . . . the hottest temperature your disk has reached shows the fan has never failed
9 raw = 3259 . . . total hours drive has been on
4, 12 raw = 1376 . . . on off cycles (so average on hours is 2.36 hours)
BTW
190 is not saying it failed in the past, only that the fan turn on temperature was reached

Not sure about pre-fail. There is some info. on SMART parameters HERE
 

af123

Administrator
Staff member
The pre-fail indicates that if the attribute value were to exceed the threshold then it would be an indication of impending failure.

Other attributes indicate old-age once they pass the threshold.

Only your disk temperature has ever exceeded a threshold and that's normal - the threshold is set too low really as these AV disks are rated for a much higher temperature.
 

HarveyB

Active Member
Just got back from holiday to find webif raising disk problem.
Ran fix-disk in maintenance mode, it found a bad sector and says it fixed it with a lot of Inode fixing etc, and finished successfully. It is hard to tell properly since I stupidly ran it from iPad and I can't scroll the output (Telnet lite app!!!).
Anyway, afterwards webif hard disk diag showed the following (after acknowledging faults):
ImageUploadedByTapatalkHD1405628233.646618.jpg
As you can see the 2nd item in log at bottom shows a problem!

What should I do now?
 

af123

Administrator
Staff member
The most recent test is the top one which is fine. The second was run by fix-disk to find out which sector needed repair, and it looks like it's done the job. Nothing to worry about.
 
OP
R

rodp

Member
Hi All,

2 years on and my Hummy has alerted me to a fault on my HDD. So I read up and ran Maintenance mode and ran option 1: Fix-disk. Please could I ask for your valued advise and reassurance that I don't need to do anything else?

The pics below are after I had ran Fix-disk. but beforehand it was

Reallocated_Sector_Ct = 0
Current_Pending Sector = 8
Offline_uncorrectable = 8

I've also included the telnet log. One thing at the beginning of the process to note... I kept getting error at LBA 216360 but it wouldn't fix it so in the end I said 'N' and it continued the checks.

Referring to the below pics, has the fix only fixed one of the Sectors?

Any advise would be great.

Thanks in advance

Rodp

Disk Diagnostics 2016-10-03 (after having run fix-disk) 1.JPG Disk Diagnostics 2016-10-03 (after having run fix-disk) 2.JPG

Code:
      /---------------------------------------------\
      |  M A I N T E N A N C E   M O D E   M E N U  |
      \---------------------------------------------/

  [ Humax HDR-Fox T2 (humax) 1.03.12/3.00 ]

    1 - Check and repair hard disk (fix-disk).
    2 - Run short hard-disk self test.
    3 - Run long hard-disk self test.
    4 - Check self-test progress.
  epg - Clear persistent EPG data.
dlna - Reset DLNA server database.
    x - Leave maintenance mode (Humax will restart).
diag - Run a diagnostic.
  cli - System command line (advanced users).

Please select option:
Please select option: 1
Any additional options (or press return for none):
Are you sure you wish to run the hard disk checker? [Y/N] y
Running /bin/fix-disk
Custom firmware version 3.00


Checking disk sda

Unmounted /dev/sda1
Unmounted /dev/sda2
Unmounted /dev/sda3

Running short disk self test
Error at LBA 216360
Do you wish to attempt repair of the bad block? [Y/N]: y

/dev/sda:
re-writing sector 216360: succeeded

Running short disk self test
Error at LBA 216360
Do you wish to attempt repair of the bad block? [Y/N]: y

/dev/sda:
re-writing sector 216360: succeeded

Running short disk self test
Error at LBA 216360
Do you wish to attempt repair of the bad block? [Y/N]: Y

/dev/sda:
re-writing sector 216360: succeeded

Running short disk self test
Error at LBA 216360
Do you wish to attempt repair of the bad block? [Y/N]: Y

/dev/sda:
re-writing sector 216360: succeeded

Running short disk self test
Error at LBA 216360
Do you wish to attempt repair of the bad block? [Y/N]: Y

/dev/sda:
re-writing sector 216360: succeeded

Running short disk self test
Error at LBA 216360
Do you wish to attempt repair of the bad block? [Y/N]: N
Skipped repair of LBA 216360
Using superblock 0 on sda1
Using superblock 0 on sda2
Using superblock 0 on sda3
Dev: /dev/sda LBA: 216360
LBA: 216360 is on partition /dev/sda1, start: 2, bad sector offset: 216358
dumpe2fs 1.42.10 (18-May-2014)
Using superblock 0
Block size: 4096
LBA 216360 maps to file system block 27044 on /dev/sda1

Checking to see if this block is in use...
debugfs 1.42.10 (18-May-2014)
Block 27044 is not in use
Dev: /dev/sda LBA: 216360
LBA: 216360 is on partition /dev/sda1, start: 2, bad sector offset: 216358
dumpe2fs 1.42.10 (18-May-2014)
Using superblock 0
Block size: 4096
LBA 216360 maps to file system block 27044 on /dev/sda1

Checking to see if this block is in use...
debugfs 1.42.10 (18-May-2014)
Block 27044 is not in use
Dev: /dev/sda LBA: 216360
LBA: 216360 is on partition /dev/sda1, start: 2, bad sector offset: 216358
dumpe2fs 1.42.10 (18-May-2014)
Using superblock 0
Block size: 4096
LBA 216360 maps to file system block 27044 on /dev/sda1

Checking to see if this block is in use...
debugfs 1.42.10 (18-May-2014)
Block 27044 is not in use
Dev: /dev/sda LBA: 216360
LBA: 216360 is on partition /dev/sda1, start: 2, bad sector offset: 216358
dumpe2fs 1.42.10 (18-May-2014)
Using superblock 0
Block size: 4096
LBA 216360 maps to file system block 27044 on /dev/sda1

Checking to see if this block is in use...
debugfs 1.42.10 (18-May-2014)
Block 27044 is not in use
Dev: /dev/sda LBA: 216360
LBA: 216360 is on partition /dev/sda1, start: 2, bad sector offset: 216358
dumpe2fs 1.42.10 (18-May-2014)
Using superblock 0
Block size: 4096
LBA 216360 maps to file system block 27044 on /dev/sda1

Checking to see if this block is in use...
debugfs 1.42.10 (18-May-2014)
Block 27044 is not in use


Checking partition /dev/sda3...
e2fsck 1.42.10 (18-May-2014)
Pass 1: Checking inodes, blocks, and sizes
?Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
?/lost+found not found.  Create? yes

Pass 4: Checking reference counts
?Pass 5: Checking group summary information
??
/dev/sda3: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda3: 14/655776 files (0.0% non-contiguous), 296327/2622611 blocks

Checking partition /dev/sda1...
e2fsck 1.42.10 (18-May-2014)
Pass 1: Checking inodes, blocks, and sizes
?Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found.  Create? yes

Pass 4: Checking reference counts
?Pass 5: Checking group summary information
??
/dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda1: 15/65808 files (6.7% non-contiguous), 15952/263064 blocks

Creating swap file...
Setting up swapspace version 1, size = 1073737728 bytes
UUID=1c5e91cc-dc88-4e4c-a792-cc0e4b62d0cb

Checking partition /dev/sda2...
e2fsck 1.42.10 (18-May-2014)
Pass 1: Checking inodes, blocks, and sizes
☻Pass 2: Checking directory structure
☻Pass 3: Checking directory connectivity
☻/lost+found not found.  Create? yes

Pass 4: Checking reference counts
☻Pass 5: Checking group summary information
☻Free blocks count wrong for group #3820 (65535, counted=0).
Fix? yes

Free blocks count wrong (20417474, counted=20351939).
Fix? yes

☻☺
/dev/sda2: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda2: 10728/60334080 files (13.8% non-contiguous), 220952393/241304332 blocks
Removing extra swap space.
Are you having problems with a delete loop? [Y/N]: N
Skipped

Finished
 
Last edited:

prpr

Well-Known Member
You're on an old version of firmware. Upgrade to 1.03.12/3.10 and then re-run the fixdisk process. It should fix the above fault properly.
(3.10 works properly on Advanced Format drives, which is what you have, whereas 3.00 doesn't. You can tell because the physical sector size is 4096 instead of 512. 3.00 has only fixed 1 lump of 512, leaving the other 7 lumps of 512 unfixed, which is why you get the repeated LBA error.)
 
Last edited:
OP
R

rodp

Member
Hi prpr, will do.

Can you help me understand the numbers and the meanings of Current_Pending_Sector, Offline_Uncorrectable and Reallocated_Sector_Ct. I'm familiar with bad sectors / bad blocks but on windows etc. I've just let chkdsk sort itself out.

Is there also anyway to understand what file intersects said bad sectors / blocks so that you can check that the file is ok afterwards?

Thanks

Rodp
 

prpr

Well-Known Member
Can you help me understand the numbers and the meanings of Current_Pending_Sector, Offline_Uncorrectable and Reallocated_Sector_Ct.
Use <search engine> of your choice. The first two are things that need fixing and the last one is things that have been fixed. There are a limited number of spares, so if "things that have been fixed" keeps increasing after "things that need fixing" have been fixed, then you will eventually need a new drive.
Is there also anyway to understand what file intersects said bad sectors / blocks so that you can check that the file is ok afterwards?
Fixdisk already told you the block wasn't in use. See your telnet log.
 
OP
R

rodp

Member
Hi Black Hole - sorry - I've now put it in a code section - not sure whether that's made any difference as I took it from the telnet window directly (the ms windows 7 telnet bog-standard app).

Does anyone have any more opinions about the state of my HDD scoring and whether the 8 sectors which are bad is a start of more things to occur 'more' quickly? I've had the unit since 2013 but it was a 2012 unit so making it about 4 years old at present. (I was expecting / hoping the drive to not show signs of ware and tare for a little while longer).

Thanks

Rodp
 

af123

Administrator
Staff member
Does anyone have any more opinions about the state of my HDD scoring and whether the 8 sectors which are bad is a start of more things to occur 'more' quickly?
There's no way of being absolutely sure but it's fine for now. There are lots of spare sectors (of the order of 1000s but it depends on the disk manufacturer and model) so 8 reallocations is nothing to be worried about.
 

MartinLiddle

Super Moderator
Staff member
Does anyone have any more opinions about the state of my HDD scoring and whether the 8 sectors which are bad is a start of more things to occur 'more' quickly?
The time to start worrying about reallocated sectors is when the rate of reallocation averages more than one a day. Some people are running boxes with thousands of reallocated sectors.
 
Top