Is my disc bust?

PH111 · Jul 31, 2013

Thanks Black Hole and prpr - sorry about mistake

new result...

humax# ls /sys/block/sda
dev holders range size stat uevent
device queue removable slaves subsystem

PH111 · Jul 31, 2013

humax# ls /sys/block/sda
dev holders range size stat uevent
device queue removable slaves subsystem
humax# ls sys/block
loop0 loop1 loop2 loop3 loop4 loop5 loop6 loop7 mtdblock0 mtdblock1 mtdblock2 mtdblock3 mtdblock4 mtdblock5 mtdblock6 sda
humax#
humax# ls /sys
block bus class devices firmware fs kernel module
humax#

Running fix disc gives this...

ls: /sys/block/sda/sda*: No such file or directory
Unable to determine which disk has to be checked

PH111 · Jul 31, 2013

So...
This may be a dumb question but
Is my disk dead?

prpr · Jul 31, 2013

To my eye (untrained in such subtleties of Linux), I would say the disk appears to be alive but has no partitions (and therefore no files) on it.
You may just have to try formatting it and see what happens, but I would wait for confirmation from the real experts.
I could of course be completely wrong about what your results suggest...

xyz321 · Jul 31, 2013

Yes, the partition table appears to be missing/corrupt. Partition table repair is not currently supported by fix-disk. I suggest running the following to see the general state of the disk.

Code:

smartctl -t short /dev/sda

Wait for however long it says for the test to complete (usually a few minutes), then

Code:

smartctl -a /dev/sda

Please post the results of this here between [code]...[/code] tags.

If it looks reasonably OK we should be able to write a new partition table and then repair the rest of the disk.

Edit: Also can you run the following and post the results:

Code:

fdisk -lu /dev/sda

PH111 · Jul 31, 2013

Thanks prpr & xyz321 - I shall run that code in the morning as wife just wants to watch telly tonight.
I really appreciate this help

xyz321 · Jul 31, 2013

I have modified my post above to add an additional smartctl test at the beginning.

PH111 · Aug 1, 2013

Hi ran the 1st test - asked me to wait 1min - so waited 2

Then the second test gave the following

Code:

humax# smartctl -t short /dev/sda
smartctl 5.41 2011-06-09 r3365 [7405b0-smp-linux-2.6.18-7.1] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command: "Execute SMART Short self-test routine immediately in off-line mode".
Drive command "Execute SMART Short self-test routine immediately in off-line mode" successful.
Testing has begun.
Please wait 1 minutes for test to complete.
Test will complete after Thu Aug  1 10:36:55 2013

Use smartctl -X to abort test.
humax#
=== START OF INFORMATION SECTION ===
Model Family:     Seagate Pipeline HD 5900.2
Device Model:     ST31000424CS
Serial Number:    5VX1FX8C
LU WWN Device Id: 5 000c50 037dc149d
Firmware Version: SC13
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Thu Aug  1 10:38:38 2013 BST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
See vendor-specific Attribute list for marginal Attributes.

General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      ( 121) The previous self-test completed having
                                        the read element of the test failed.
Total time to complete Offline
data collection:                (  653) seconds.
Offline data collection
capabilities:                    (0x73) SMART execute Offline immediate.
                                        Auto Offline data collection on/off supp                                                                                        ort.
                                        Suspend Offline collection upon new
                                        command.
                                        No Offline surface scan supported.
                                        Self-test supported.
                                        Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   1) minutes.
Extended self-test routine
recommended polling time:        ( 234) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x103b) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_                                                                                        FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   090   090   006    Pre-fail  Always       -                                                                                               159609470
  3 Spin_Up_Time            0x0003   095   095   000    Pre-fail  Always       -                                                                                               0
  4 Start_Stop_Count        0x0032   095   095   020    Old_age   Always       -                                                                                               5404
  5 Reallocated_Sector_Ct   0x0033   070   070   036    Pre-fail  Always       -                                                                                               1236
  7 Seek_Error_Rate         0x000f   083   060   030    Pre-fail  Always       -                                                                                               202620204
  9 Power_On_Hours          0x0032   090   090   000    Old_age   Always       -                                                                                               8889
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -                                                                                               0
 12 Power_Cycle_Count       0x0032   098   098   020    Old_age   Always       -                                                                                               2705
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -                                                                                               0
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -                                                                                               637
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -                                                                                               0
189 High_Fly_Writes         0x003a   099   099   000    Old_age   Always       -                                                                                               1
190 Airflow_Temperature_Cel 0x0022   061   033   045    Old_age   Always   In_th                                                                                        e_past 39 (0 185 39 36)
194 Temperature_Celsius     0x0022   039   067   000    Old_age   Always       -                                                                                               39 (0 19 0 0)
195 Hardware_ECC_Recovered  0x001a   044   035   000    Old_age   Always       -                                                                                               159609470
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -                                                                                               1
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -                                                                                               1
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -                                                                                               0

SMART Error Log Version: 1
ATA Error Count: 641 (device log contains only the most recent five errors)
        CR = Command Register [HEX]
        FR = Features Register [HEX]
        SC = Sector Count Register [HEX]
        SN = Sector Number Register [HEX]
        CL = Cylinder Low Register [HEX]
        CH = Cylinder High Register [HEX]
        DH = Device/Head Register [HEX]
        DC = Device Command Register [HEX]
        ER = Error register [HEX]
        ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 641 occurred at disk power-on lifetime: 8889 hours (370 days + 9 hours)
  When the command that caused the error occurred, the device was active or idle                                                                                        .

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 06 00 00 00  Error: UNC at LBA = 0x00000006 = 6

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 00 00 00 e0 00      00:00:22.119  READ DMA
  ec 00 00 06 00 00 a0 00      00:00:22.094  IDENTIFY DEVICE
  c8 00 08 00 00 00 e0 00      00:00:20.786  READ DMA
  ec 00 00 06 00 00 a0 00      00:00:20.761  IDENTIFY DEVICE
  c8 00 08 00 00 00 e0 00      00:00:19.443  READ DMA

Error 640 occurred at disk power-on lifetime: 8889 hours (370 days + 9 hours)
  When the command that caused the error occurred, the device was active or idle                                                                                        .

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 06 00 00 00  Error: UNC at LBA = 0x00000006 = 6

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 00 00 00 e0 00      00:00:20.786  READ DMA
  ec 00 00 06 00 00 a0 00      00:00:20.761  IDENTIFY DEVICE
  c8 00 08 00 00 00 e0 00      00:00:19.443  READ DMA
  ec 00 00 06 00 00 a0 00      00:00:19.418  IDENTIFY DEVICE
  c8 00 08 00 00 00 e0 00      00:00:18.121  READ DMA

Error 639 occurred at disk power-on lifetime: 8889 hours (370 days + 9 hours)
  When the command that caused the error occurred, the device was active or idle                                                                                        .

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 06 00 00 00  Error: UNC at LBA = 0x00000006 = 6

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 00 00 00 e0 00      00:00:19.443  READ DMA
  ec 00 00 06 00 00 a0 00      00:00:19.418  IDENTIFY DEVICE
  c8 00 08 00 00 00 e0 00      00:00:18.121  READ DMA
  ec 00 00 06 00 00 a0 00      00:00:18.096  IDENTIFY DEVICE
  c8 00 08 00 00 00 e0 00      00:00:16.778  READ DMA

Error 638 occurred at disk power-on lifetime: 8889 hours (370 days + 9 hours)
  When the command that caused the error occurred, the device was active or idle                                                                                        .

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 06 00 00 00  Error: UNC at LBA = 0x00000006 = 6

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 00 00 00 e0 00      00:00:18.121  READ DMA
  ec 00 00 06 00 00 a0 00      00:00:18.096  IDENTIFY DEVICE
  c8 00 08 00 00 00 e0 00      00:00:16.778  READ DMA
  ec 00 00 06 00 00 a0 00      00:00:16.753  IDENTIFY DEVICE
  c8 00 08 00 00 00 e0 00      00:00:15.435  READ DMA

Error 637 occurred at disk power-on lifetime: 8889 hours (370 days + 9 hours)
  When the command that caused the error occurred, the device was active or idle                                                                                        .

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 06 00 00 00  Error: UNC at LBA = 0x00000006 = 6

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 00 00 00 e0 00      00:00:16.778  READ DMA
  ec 00 00 06 00 00 a0 00      00:00:16.753  IDENTIFY DEVICE
  c8 00 08 00 00 00 e0 00      00:00:15.435  READ DMA
  ec 00 00 06 00 00 a0 00      00:00:15.410  IDENTIFY DEVICE
  c8 00 08 00 00 00 e0 00      00:00:14.113  READ DMA

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA                                                                                        _of_first_error
# 1  Short offline       Completed: read failure       90%      8889         6
# 2  Short offline       Completed: read failure       90%      8889         6
# 3  Short offline       Completed: read failure       90%      8889         6
# 4  Short offline       Completed: read failure       90%      8889         6
# 5  Short offline       Completed: read failure       90%      8889         6
# 6  Short offline       Completed: read failure       90%      8889         6
# 7  Short offline       Completed: read failure       90%      8889         6

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

humax#

Now the fdisk command gave the following...

Code:

 humax# fdisk -lu /dev/sda
fdisk: can't open '/dev/sda': Input/output error
humax#
humax#

Hope this makes sense

Thanks

prpr · Aug 1, 2013

Your disk looks to me to be on the verge of death, so I would be ordering another one.
If you want to try recovering your recordings, you could try starting with this:

Code:

humax# dd if=/dev/sda of=dev/null count=1 bs=512 skip=6

and if it returns a read error, try this to force a sector reallocation:

Code:

humax# dd if=/dev/zero of=/dev/sda count=1 bs=512 seek=6

If that works, then repeat the "smartctl -t" test to identify the next failed LBA and loop until you have no more fails (replacing the 6 in the above commands with whatever the failing LBA number is).
You could try the fdisk command again to see what happens then.

af123 · Aug 1, 2013

Rather than use dd, I would recommend hdparm as it writes directly to the disk bypassing buffers etc.

Code:

humax# hdparm --repair-sector 6 --yes-i-know-what-i-am-doing /dev/sda

This often works in more cases than dd. Once that sector is fixed, the partition table may reappear so try
fdisk -lu /dev/sda again.

PH111 · Aug 1, 2013

Thanks

Ran

Code:

hdparm --repair-sector 6 --yes-i-know-what-i-am-doing /dev/sda

Result

Code:

humax# hdparm --repair-sector 6 --yes-i-know-what-i-am-doing /dev/sda
 
/dev/sda:
re-writing sector 6: succeeded

Then ran

Code:

fdisk -lu /dev/sda

Result

Code:

humax# fdisk -lu /dev/sda
fdisk: can't open '/dev/sda': Input/output error
humax#

So do I continue on other sectors now?

xyz321 · Aug 1, 2013

Try running the smart tests again:

Code:

smartctl -t short /dev/sda
(wait a few minutes)
smartctl -l selftest /dev/sda

Edit: I have just noticed that the smartctl output has been truncated by the cut & paste operation - The last column of the table is missing. It would be useful to have the figures for ID numbers 197 & 198.

prpr · Aug 1, 2013

No, the raw values are there - they are just hidden by the need to scroll horizontally - confused me initially as well...
Presumably the 1 sector it was complaining about was sector 6, so I would guess the test may succeed now.

Might be interesting for PH111 to run "hdparm --read-sector 0 /dev/sda" just to see whether it works and what's in it.
What is the procedure to recreate the partition table if the sector is empty? Why can fdisk apparently not read the disk?

Incidentally, reading sector 6 on my disk returns all zeroes.

af123 · Aug 1, 2013

Maybe try gfdisk?

Code:

humax# gfdisk -lu /dev/sda

xyz321 · Aug 1, 2013

prpr said:
No, the raw values are there - they are just hidden by the need to scroll horizontally - confused me initially as well...

Yes, indeed, there is just a large gap!

Presumably the 1 sector it was complaining about was sector 6, so I would guess the test may succeed now.

There's a good chance or it might find another problem sector

Might be interesting for PH111 to run "hdparm --read-sector 0 /dev/sda" just to see whether it works and what's in it.

Yes, it is possible that the kernel may not have updated its internal representation of the partition table, a reboot may help if hdparm gives sensible results.

What is the procedure to recreate the partition table if the sector is empty? Why can fdisk apparently not read the disk?

I wonder if the sector has been reallocated because the disk decided it was faulty. If that is the case then writing new data to it should fix it (for now). The partition table can be recreated by typing the numbers into gfdisk or by copying it from a binary or hex file.

xyz321 · Aug 1, 2013

Apologies for the long post.
Here is the procedure for recreating the partition table.

I suggest first of all writing zeros to sector 0 in a similar way to that used on sector 6 and then reading it back to make sure there are no more I/O errors. Note to others - please don't try this on a working disk you will erase the partition table!

Code:

hdparm --repair-sector 0 --yes-i-know-what-i-am-doing /dev/sda
hdparm --read-sector 0 /dev/sda

Note to others:- these figures are for the original 1TB disk please do not use these numbers on another disk.

This is the partition layout you are aiming for:

Code:

    humax# fdisk -lu
     
    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              2    2104514    1052256+ 83 Linux
    /dev/sda2        2104515  1932539174  965217330  83 Linux
    /dev/sda3      1932539175  1953520064    10490445  83 Linux

There is a bug in the fdisk app in that it will not let you enter a value of 2 for the initial sector size, so use gfdisk instead. The gfdisk app. uses single letter commands.

In the listing that follows, blue text is typed in by the user and the green text is my comments, anything else should be returned by the program.

humax# gfdisk -u /dev/sda
GNU Fdisk 1.3.0a
Copyright (C) 1998 - 2006 Free Software Foundation, Inc.
This program is free software, covered by the GNU General Public License.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.

Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that, of course, the previous
content won't be recoverable.

Using /dev/sda

# Create a new primary partition starting at sector 2 and ending at 2104514
Command (m for help): n
Partition type
e extended
p primary partition (1-4)
p
First sector (default 63s): 2
Last sector or +size or +sizeMB or +sizeKB (default 0s): 2104514

# Create the next partition, just hit return to accept the default for the start sector
Command (m for help): n
Partition type
e extended
p primary partition (1-4)
p
First sector (default 2104515s):
Last sector or +size or +sizeMB or +sizeKB (default 1953520064s): 1932539174

# Create the last partition accepting the defaults for both start and end sectors
Command (m for help): n
Partition type
e extended
p primary partition (1-4)
p
First sector (default 1932539175s):
Last sector or +size or +sizeMB or +sizeKB (default 1953520064s):

# Print the partition table, note that there is a slight mismatch in the size column due to differences in the way that fdsik and gfdisk calculate the sizes. The start and end columns should be identical.
Command (m for help): p

Disk /dev/sda: 1000 GB, 1000202273280 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953520065 sectors
Units = sectors of 1 * 512 = 512 bytes

Device Boot Start End Blocks Id System
/dev/sda1 2 2104514 1052226 83 Linux
/dev/sda2 2104515 1932539174 965209297 83 Linux
/dev/sda3 1932539175 1953520064 10482412 83 Linux

# If you are happy with the figures write the partition table to disk
Command (m for help): w

Information: Don't forget to update /etc/fstab, if necessary.

# quit the application
Command (m for help): q

# You can now run fdisk and check that all the figures match
humax# fdisk -lu /dev/sda

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 2 2104514 1052256+ 83 Linux
/dev/sda2 2104515 1932539174 965217330 83 Linux
/dev/sda3 1932539175 1953520064 10490445 83 Linux

PH111 · Aug 1, 2013

Ran the following tests...

Code:

humax# hdparm --read-sector 0 /dev/sda

/dev/sda:
reading sector 0: succeeded
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0003 fe83 823f 0002 0000 1cc1 0020 0000
8301 fe83 ffff 1cc3 0020 1864 7310 fe00
ffff fe83 ffff 3527 7330 249a 0140 0000
0000 0000 0000 0000 0000 0000 0000 aa55
humax#

Code:

 gfdisk -lu /dev/sda
GNU Fdisk 1.3.0a
Copyright (C) 1998 - 2006 Free Software Foundation, Inc.
This program is free software, covered by the GNU General Public License.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

Disk /dev/sda: 1000 GB, 1000202273280 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953520065 sectors
Units = sectors of 1 * 512 = 512 bytes

   Device Boot      Start         End      Blocks   Id  System
humax#

Code:

smartctl -t short /dev/sda
(wait a few minutes)
smartctl -l selftest /dev/sda

smartctl 5.41 2011-06-09 r3365 [7405b0-smp-linux-2.6.18-7.1] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command: "Execute SMART Short self-test routine immediately in off-line mode".
Drive command "Execute SMART Short self-test routine immediately in off-line mode" successful.
Testing has begun.
Please wait 1 minutes for test to complete.
Test will complete after Thu Aug  1 23:11:05 2013

Use smartctl -X to abort test.

humax# smartctl -l selftest /dev/sda
smartctl 5.41 2011-06-09 r3365 [7405b0-smp-linux-2.6.18-7.1] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA                                                                                        _of_first_error
# 1  Short offline       Completed: read failure       90%      8890         7
# 2  Short offline       Completed: read failure       90%      8889         6
# 3  Short offline       Completed: read failure       90%      8889         6
# 4  Short offline       Completed: read failure       90%      8889         6
# 5  Short offline       Completed: read failure       90%      8889         6
# 6  Short offline       Completed: read failure       90%      8889         6
# 7  Short offline       Completed: read failure       90%      8889         6
# 8  Short offline       Completed: read failure       90%      8889         6

humax#

PH111 · Aug 1, 2013

xyz321 just seen your new post - will do that in the morning - thanks

af123 · Aug 1, 2013

You have a new error on the disk at sector 7 that was exposed by the latest short test. You need to fix that one too.

Code:

humax# hdparm --repair-sector 7 --yes-i-know-what-i-am-doing /dev/sda

Then another short test to see if there are any more. Rinse and repeat.

xyz321 · Aug 1, 2013

I think you should ignore my post since the numbers from sector 0 look to be correct.

Edit: Follow af123's advice to fix any broken sectors first, then a reboot should fix the partition table. With any luck there may not be too many

Is my disc bust?

Member

Member

Member

Well-Known Member

Well-Known Member

Member

Well-Known Member

Member

Well-Known Member

Administrator

Member

Well-Known Member

Well-Known Member

Administrator

Well-Known Member

Well-Known Member

Member

Member

Administrator

Well-Known Member