From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [OT] Badblocks on my harddisk
Date: Sat, 26 Jul 2014 17:56:03 +0200 [thread overview]
Message-ID: <53D3CF93.3000407@googlemail.com> (raw)
In-Reply-To: <20140726121632.GA5406@solfire>
Am 26.07.2014 14:16, schrieb meino.cramer@gmx.de:
> Volker Armin Hemmann <volkerarmin@googlemail.com> [14-07-26 14:08]:
>> Am 26.07.2014 12:26, schrieb meino.cramer@gmx.de:
>>> Mick <michaelkintzios@gmail.com> [14-07-26 11:28]:
>>>> On Saturday 26 Jul 2014 02:49:15 meino.cramer@gmx.de 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.
>>
>>
>>
>
> Hi Volker,
>
> what happens if swapped is used and the write access tapped on the
> bad area?
nothing. As soon as someone tries to write on that sector, the drive
will map it out.
That means 'pending'. Nobody tried to write on it yet, so the drive had
no reason to 'reallocate' it so far.
> Here is the output of smartctl:
>
>
> smartctl 6.1 2013-03-16 r3800 [x86_64-linux-3.14.13-RT] (local build)
> Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
>
> === START OF INFORMATION SECTION ===
> Model Family: Western Digital Caviar Green (AF)
> Device Model: WDC WD10EARS-00Y5B1
> Serial Number: WD-WMAV51276611
> LU WWN Device Id: 5 0014ee 001f5fb47
> Firmware Version: 80.00A80
> 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: ATA8-ACS (minor revision not indicated)
> SATA Version is: SATA 2.6, 3.0 Gb/s
> Local Time is: Sat Jul 26 14:16:19 2014 CEST
> 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
>
> General SMART Values:
> Offline data collection status: (0x84) Offline data collection activity
> was suspended by an interrupting command from host.
> Auto Offline Data Collection: Enabled.
> 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: (19380) seconds.
> Offline data collection
> capabilities: (0x7b) SMART execute Offline immediate.
> Auto Offline data collection on/off support.
> Suspend Offline collection upon new
> command.
> 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: ( 2) minutes.
> Extended self-test routine
> recommended polling time: ( 223) minutes.
> Conveyance self-test routine
> recommended polling time: ( 5) minutes.
> SCT capabilities: (0x3031) SCT Status supported.
> SCT Feature Control supported.
> SCT Data Table supported.
>
> SMART Attributes Data Structure revision number: 16
> Vendor Specific SMART Attributes with Thresholds:
> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
> 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0
> 3 Spin_Up_Time 0x0027 129 113 021 Pre-fail Always - 6508
> 4 Start_Stop_Count 0x0032 097 097 000 Old_age Always - 3957
> 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
> 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
> 9 Power_On_Hours 0x0032 081 081 000 Old_age Always - 14476
> 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0
> 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0
> 12 Power_Cycle_Count 0x0032 097 097 000 Old_age Always - 3808
> 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 324
> 193 Load_Cycle_Count 0x0032 196 196 000 Old_age Always - 14602
> 194 Temperature_Celsius 0x0022 115 101 000 Old_age Always - 32
> 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
> 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 1
> 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 1
> 199 UDMA_CRC_Error_Count 0x0032 200 197 000 Old_age Always - 13300
> 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 1
so you got one defective sector, the drive knows about it, it has 200
spares and will use one when the need arises.
>
> SMART Error Log Version: 1
> No Errors Logged
>
> SMART Self-test log structure revision number 1
> Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
> # 1 Conveyance offline Completed: read failure 90% 14472 4288352511
> # 2 Extended offline Completed: read failure 90% 14460 4288352511
> # 3 Extended offline Completed without error 00% 13954 -
> # 4 Short offline Completed without error 00% 13935 -
> # 5 Extended offline Completed without error 00% 7051 -
> # 6 Extended offline Completed without error 00% 2205 -
> # 7 Short offline Completed without error 00% 463 -
>
> 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.
>
>
> Best regards,
> mcc
>
>
>
>
next prev parent reply other threads:[~2014-07-26 15:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-26 1:49 [gentoo-user] [OT] Badblocks on my harddisk meino.cramer
2014-07-26 3:39 ` Dale
2014-07-26 8:13 ` meino.cramer
2014-07-31 16:58 ` Frank Steinmetzger
2014-08-01 22:12 ` Stroller
2014-07-26 9:25 ` Mick
2014-07-26 10:11 ` meino.cramer
2014-07-26 10:23 ` meino.cramer
2014-07-26 10:26 ` meino.cramer
2014-07-26 12:06 ` Volker Armin Hemmann
2014-07-26 12:16 ` meino.cramer
2014-07-26 15:56 ` Volker Armin Hemmann [this message]
2014-07-26 16:09 ` meino.cramer
2014-07-26 17:18 ` Volker Armin Hemmann
2014-07-26 15:36 ` meino.cramer
2014-07-26 12:27 ` Mick
2014-07-26 12:04 ` Volker Armin Hemmann
2014-07-26 12:11 ` Dale
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53D3CF93.3000407@googlemail.com \
--to=volkerarmin@googlemail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox