#1558 closed enhancement (fixed)
WDC WD6401AALS-00L3B2 needs '-l xerrorlba'
| Reported by: | Geina3ee | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | Release 7.3 |
| Component: | drivedb | Version: | 7.2 |
| Keywords: | hdd | Cc: |
Description
I play with unreadable sector at LBA 768453424.
But the following command displays wrong LBA:
smartctl -i -l xerror
...
40 -- 51 00 00 00 2d ab 00 cd 30 40 00 Error: UNC at LBA = 0x2dab00cd30 = 196142484784
Note, that 768453424 = 0x2dcdab30, not 0x2dab00cd30 !
So calculated LBA is wrong: 196142484784 <> 768453424
I've just downloaded and build fresh 7.2 version from https://deac-ams.dl.sourceforge.net/project/smartmontools/smartmontools/7.2/smartmontools-7.2.tar.gz
Attachments (3)
Change History (8)
Changed 17 months ago by
| Attachment: | bugreport-7.2.txt added |
|---|
comment:1 Changed 17 months ago by
| Component: | all → drivedb |
|---|---|
| Keywords: | hdd added; xerror UNC LBA removed |
| Milestone: | → undecided |
| Summary: | xerror log wrong UNC LBA calculation → xerror log wrong UNC LBA calculation (WDC WD6401AALS-00L3B2) |
| Type: | defect → enhancement |
Please provide output of smartctl -F xerrorlba -x -a /dev/sdd as an attachment.
Changed 17 months ago by
| Attachment: | xerrorlba.txt added |
|---|
the output of: smartctl -F xerrorlba -x -a /dev/sdd
comment:3 Changed 17 months ago by
| Milestone: | undecided → unscheduled |
|---|---|
| Summary: | xerror log wrong UNC LBA calculation (WDC WD6401AALS-00L3B2) → WDC WD6401AALS-00L3B2 needs '-l xerrorlba' |
This is a typical drive firmware bug: Using little endian instead of ATA register byte ordering in the error log.
Could be fixed by adding -F xerrorlba to the existing drivedb entry.
Note that in this case this does not fix the LBA info in the Commands leading to the command that caused the error... list. It uses another byte ordering.
comment:4 Changed 17 months ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Added xerrorlba flag to the WD Caviar Black family in r5301. I am not sure if other drives in this line are impacted by this bug but there is no enough data yet, so lets assume this atm.
command, os, configure, make, install details