Am 26.07.2014 18:09, schrieb [email protected]:
> Volker Armin Hemmann <[email protected]> [14-07-26 18:00]:
>> Am 26.07.2014 14:16, schrieb [email protected]:
>>> Volker Armin Hemmann <[email protected]> [14-07-26 14:08]:
>>>> Am 26.07.2014 12:26, schrieb [email protected]:
>>>>> Mick <[email protected]> [14-07-26 11:28]:
>>>>>> On Saturday 26 Jul 2014 02:49:15 [email protected] wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> After running smartctl for an extended offline test I got
>>>>>>> a badblock (information extracted from the report):
>>>>>>>
>>>>>>> SMART Self-test log structure revision number 1
>>>>>>> Num  Test_Description    Status                  Remaining  
>>>>>>> LifeTime(hours)
>>>>>>>  LBA_of_first_error # 1  Extended offline    Completed: read failure    
>>>>>>>   
>>>>>>> 90%     14460         4288352511 197 Current_Pending_Sector  0x0032   
>>>>>>> 200 
>>>>>>>  200   000    Old_age   Always       -       1
>>>>>>>
>>>>>>> I found a explanation to map the LBA to a partition here:
>>>>>>> http://smartmontools.sourceforge.net/badblockhowto.html
>>>>>>>
>>>>>>> My partition layout is:
>>>>>>> #> sudo fdisk -lu /dev/sda
>>>>>>>
>>>>>>> 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: 0x07ec16a2
>>>>>>>
>>>>>>> Device     Boot      Start        End    Blocks  Id System
>>>>>>> /dev/sda1  *          2048     104447     51200  83 Linux
>>>>>>> /dev/sda2           104448   12687359   6291456  82 Linux swap / Solaris
>>>>>>> /dev/sda3         12687360  222402559 104857600  83 Linux
>>>>>>> /dev/sda4        222402560 1953525167 865561304   5 Extended
>>>>>>> /dev/sda5        222404608  232890367   5242880  83 Linux
>>>>>>> /dev/sda6        232892416  442607615 104857600  83 Linux
>>>>>>> /dev/sda7        442609664  652324863 104857600  83 Linux
>>>>>>> /dev/sda8        652326912  862042111 104857600  83 Linux
>>>>>>> /dev/sda9        862044160 1071759359 104857600  83 Linux
>>>>>>> /dev/sda10      1071761408 1281476607 104857600  83 Linux
>>>>>>> /dev/sda11      1281478656 1491193855 104857600  83 Linux
>>>>>>> /dev/sda12      1491195904 1953525167 231164632  83 Linux
>>>>>>>                 4288352511  <<< The number reported by smartctl
>>>>>>>
>>>>>>>
>>>>>>> Following the linked document...
>>>>>>> It seems the bad LBA is not on the checked harddisk.
>>>>>>>
>>>>>>> Or (more obvious) I did something wrong...
>>>>>> You are probably comparing different units.  The Start and End of fdisk 
>>>>>> are 
>>>>>> reporting sectors, each sector being 512 bytes.  Therefore if the LBA is 
>>>>>> reported by smartctl in bytes, you have:
>>>>>>
>>>>>> 4,288,352,511 ÷ 512 = 8,375,688.5
>>>>>>
>>>>>> which would place it within your swap partition.
>>>>>>
>>>>>> I would do this:
>>>>>>
>>>>>>  swapoff /dev/sda2
>>>>>>
>>>>>>  dd if=/dev/zero of=/dev/sda2 bs=512 conv=notrunc
>>>>>>
>>>>>>  mkswap -L swap -c /dev/sda2
>>>>>>
>>>>>>  swapon /dev/sda2
>>>>>>
>>>>>> and hopefully the problem will be gone when you run the next smartctl 
>>>>>> test.
>>>>>>
>>>>>> -- 
>>>>>> Regards,
>>>>>> Mick
>>>>> Sorry for stuutering postings...overlocked this one:
>>>>> #>dd if=/dev/zero of=/dev/sda2 bs=512 conv=notrunc
>>>>> dd: error writing ‘/dev/sda2’: Input/output error
>>>>>
>>>>> Hrrrmpfff...
>>>>>
>>>>> Why does it nt remap those ones?
>>>>>
>>>>> Best regards,
>>>>> mcc
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>> smartctl -a /dev/sda
>>>>
>>>> without those information: crystal ball.
>>>>
>>>> that said: it is swap. You shouldn't have to do anything. Don't touch dd.
>>>>
>>>>
>>>>
>> so you got one defective sector, the drive knows about it, it has 200
>> spares and will use one when the need arises.
>>
>
> Unfortunaltely: No it doesnt.
>
> I did a dd (as reported previously) of zeroes accross the affected
> partition and dd fails to write ot the sector in question (IO error).
>
> The selftest following again reports that sector as bad.
>
> So...?
>
> Best regards,
> mcc
>
>
>
>

you can try hdparm's write-sector command to force a reallocation. But I
would backup first. Just in case.

Reply via email to