Bug 502633

Summary: I see bad_sectors on my disk, yet I cannot find them
Product: [Fedora] Fedora Reporter: ritz <rkhadgar>
Component: libatasmartAssignee: Lennart Poettering <lpoetter>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: lpoetter
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-05-26 17:39:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
skdump blob none

Description ritz 2009-05-26 15:07:22 UTC 
Description of problem:
palimpsest shows my disk has a problem

Version-Release number of selected component (if applicable):
libatasmart-0.12-3.fc11.x86_64

How reproducible:
always

Steps to Reproduce:
1. login to system

Actual results:
warning

Expected results:
no warning

Additional info:
I have a dell d630 laptop. Ran Dell diagnostic on it overnight, hdd health came out fine, with no error. Toshibha does not provide any disk utility.

# skdump   /dev/sda
Device: /dev/sda
Type: 16 Byte SCSI ATA SAT Passthru
Size: 152627 MiB
Model: [TOSHIBA MK1651GSY]
Serial: [38IGT0G5T]
Firmware: [LD001D]
SMART Available: yes
Quirks:
Awake: yes
SMART Disk Health Good: yes
Off-line Data Collection Status: [Off-line data collection activity was never started.]
Total Time To Complete Off-Line Data Collection: 120 s
Self-Test Execution Status: [The self-test routine was aborted by the host.]
Percent Self-Test Remaining: 60%
Conveyance Self-Test Available: no
Short/Extended Self-Test Available: yes
Start Self-Test Available: yes
Abort Self-Test Available: yes
Short Self-Test Polling Time: 2 min
Extended Self-Test Polling Time: 71 min
Conveyance Self-Test Polling Time: 0 min
Bad Sectors: 1 sectors
Powered On: 43.1 years
Power Cycles: 503
Average Powered On Per Power Cycle: 1.0 months
Temperature: 41.0 C
Overall Status: BAD_SECTOR
ID# Name                        Value Worst Thres Pretty      Raw            Type    Updates Good
  1 raw-read-error-rate         100   100    50   0           0x000000000000 prefail online  yes
  3 spin-up-time                100   100     1   2.0 s       0xe90700000000 prefail online  yes
  5 reallocated-sector-count    100   100    50   1 sectors   0x010000000000 prefail online  no 
  9 power-on-hours               85    85     0   43.1 years  0xe6c205000000 old-age online  n/a
 12 power-cycle-count           100   100     0   503         0xf70100000000 old-age online  n/a
191 g-sense-error-rate          100   100     0   15203       0x633b00000000 old-age online  n/a
192 power-off-retract-count     100   100     0   477         0xdd0100000000 old-age online  n/a
193 load-cycle-count             92    92     0   87230       0xbe5401000000 old-age online  n/a
194 temperature-celsius-2       100   100     0   41.0 C      0x29000f003500 old-age online  n/a
199 udma-crc-error-count        100   100     0   42894131    0x33838e020000 old-age online  n/a
200 multi-zone-error-rate       100   100     0   105131632   0x702e44060000 old-age online  n/a
240 head-flying-hours            87    87     0   35.9 years  0x90cd04000000 old-age online  n/a
241 attribute-241               100   100     0   n/a         0xc0b9f5fe0000 old-age online  n/a
242 attribute-242               100   100     0   n/a         0x3803d7a40100 old-age online  n/a
254 attribute-254               100   100     0   n/a         0x930100000000 old-age online  n/a
Comment 1 Lennart Poettering 2009-05-26 17:39:25 UTC 
(In reply to comment #0)

>   5 reallocated-sector-count    100   100    50   1 sectors   0x010000000000

That's your bad sector. The sector got reallocated.

libatamsart is correctly reporting an issue here. If I were you I'd probably not trust that disk anymore.
Comment 2 Lennart Poettering 2009-05-26 17:41:16 UTC 
Oh, could you provide me with the smart blob data you can generate with 'skdump --save=blob /dev/sda' please? As it appears libatasmart fails to parse attribute 9 and 240 correctly. That's something I should fix.

How old is that drive, roughly?
Comment 3 ritz 2009-05-27 08:59:00 UTC 
Created attachment 345579 [details]
skdump blob

The disk is about an year old.