Changes between Version 9 and Version 10 of Howto_ReadSmartctlReports_ATA_542.1

Timestamp:

Mar 27, 2017, 12:17:23 PM (8 years ago)

Author:

Gabriele Pohl

Comment:

Point to new BadBlockHowto wiki page

Howto_ReadSmartctlReports_ATA_542.1

@@ -106 +106 @@
   ER ST SC SN CL CH DH
   -- -- -- -- -- -- --
-  40 51 52 9b d9 3f 05  Error: <b><a href="#UNC" title="UNC (UNCorrectable): data is uncorrectable. This refers to data which has been read from the disk, but for which the Error Checking and Correction (ECC) codes are inconsistent. In effect, this means that the data can not be read."><font color="red">UNC<font></a></b> at <b><a href="#LBA" title="LLogical Block Address (LBA) at which the error occurred printed in base 16 and base 10."><font color="blue">LBA</font></a></b>) = 0x053fd99b = 88070555
+  40 51 52 9b d9 3f 05  Error: <b><a href="#UNC" title="UNC (UNCorrectable): data is uncorrectable. This refers to data which has been read from the disk, but for which the Error Checking and Correction (ECC) codes are inconsistent. In effect, this means that the data can not be read."><font color="red">UNC<font></a></b> at <b><a href="#LBA" title="Logical Block Address (LBA) at which the error occurred printed in base 16 and base 10."><font color="blue">LBA</font></a></b>) = 0x053fd99b = 88070555
 
   Commands leading to the command that caused the error were:
@@ -186 +186 @@
 
 SMART Self-test log structure revision number 1
-Num  Test_Description    Status                  Remaining  LifeTime(hours) <b><a href="/browser/trunk/www/badblockhowto.xml" title="If you find not a hyphen, but a number in this row, then the test found a /bad block/ at the listed logical block address (LBA). Follow this link to read our /Bad block HOWTO/. It gives instructions to solve this sort of problem."><font color="red">LBA_of_first_error</font></a></b>
+Num  Test_Description    Status                  Remaining  LifeTime(hours) <b><a href="/wiki/BadBlockHowto" title="If you find not a hyphen, but a number in this row, then the test found a /bad block/ at the listed logical block address (LBA). Follow this link to read our /Bad block HOWTO/. It gives instructions to solve this sort of problem."><font color="red">LBA_of_first_error</font></a></b>
 # 1  Short offline       Completed without error       00%      7465         -
 
@@ -231 +231 @@
 In the error log the Logical Block Address (<b><a href="#LBA" title="Logical Block Address"><font color="blue">LBA</font></a></b>) at which the error occurred will be printed in base 16 and base 10.
 <a name="LBA"></a><h4>Logical Block Address</h4>
-The LBA is a linear address, which counts 512-byte sectors on the disk, starting from zero. (Because of the limitations of the SMART error log, if the LBA is greater than 0xfffffff, then either no error log entry will be made, or the error log entry will have an incorrect LBA. This may happen for drives with a capacity greater than 128 GiB or 137 GB.) For Linux systems the smartmontools web page has <a href="/browser/trunk/www/badblockhowto.xml" title="Bad block HOWTO">instructions</a> about how to convert the LBA address to the name of the disk file containing the erroneous disk sector.
+The LBA is a linear address, which counts 512-byte sectors on the disk, starting from zero. (Because of the limitations of the SMART error log, if the LBA is greater than 0xfffffff, then either no error log entry will be made, or the error log entry will have an incorrect LBA. This may happen for drives with a capacity greater than 128 GiB or 137 GB.) For Linux systems the smartmontools web page has <a href="/wiki/BadBlockHowto" title="Bad block HOWTO">instructions</a> about how to convert the LBA address to the name of the disk file containing the erroneous disk sector.
 }}}