Question [HELP] HDD Bad Blocks in EFI Partition

Sep 24, 2021
3
0
10
0
Hi, My laptop has a WD 1TB HDD and is around 3 years old. Recently ( since 4-5 months) I am experiencing frequent BSODs with error code related to hardware fault. Hence i decided to do a S.M.A.R.T Diagnosis.
I have a dual boot configuration of Ubuntu 20 and Windows 10, These are the partitions
Code:
aswin@Aswin:~$ sudo fdisk -lu /dev/sda
Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD10SPZX-21Z
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 7253F4C9-4BD0-49A7-B5E5-F20EFE1748A4

Device          Start        End    Sectors   Size Type
/dev/sda1        2048     206847     204800   100M EFI System
/dev/sda2      206848     239615      32768    16M Microsoft reserved
/dev/sda3      239616 1655228415 1654988800 789.2G Microsoft basic data
/dev/sda4  1951424512 1953521663    2097152     1G Windows recovery environment
/dev/sda5  1655228416 1951424511  296196096 141.2G Linux filesystem
I ran a S.M.A.R.T Diagnosis from Ubuntu using sudo smartctl -t short /dev/sda
Code:
aswin@Aswin:~$ sudo smartctl -a  /dev/sda
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.8.0-63-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Blue
Device Model:     WDC WD10SPZX-21Z10T0
Serial Number:    WD-WX21A5771RKT
LU WWN Device Id: 5 0014ee 607abefb8
Firmware Version: 02.01A02
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Fri Sep 24 16:30:47 2021 IST
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
See vendor-specific Attribute list for marginal Attributes.

General SMART Values:
Offline data collection status:  (0x00)    Offline data collection activity
                    was never started.
                    Auto Offline Data Collection: Disabled.
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:         ( 3120) seconds.
Offline data collection
capabilities:              (0x71) SMART execute Offline immediate.
                    No Auto Offline data collection support.
                    Suspend Offline collection upon new
                    command.
                    No 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:      ( 169) minutes.
Conveyance self-test routine
recommended polling time:      (   1) minutes.
SCT capabilities:            (0x3035)    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   074   001   051    Pre-fail  Always   In_the_past 7534
  3 Spin_Up_Time            0x0027   191   187   021    Pre-fail  Always       -       1425
  4 Start_Stop_Count        0x0032   066   066   000    Old_age   Always       -       34798
  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       -       14549
 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   096   096   000    Old_age   Always       -       4718
191 G-Sense_Error_Rate      0x0032   001   001   000    Old_age   Always       -       148933
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       198
193 Load_Cycle_Count        0x0032   179   179   000    Old_age   Always       -       64207
194 Temperature_Celsius     0x0022   101   092   000    Old_age   Always       -       42
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       52
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age   Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 43 (device log contains only the most recent five errors)
    CR = Command Register [HEX]
    FR = Features Register [HEX]
    SC = Sector Count Register [HEX]
    SN = Sector Number Register [HEX]
    CL = Cylinder Low Register [HEX]
    CH = Cylinder High Register [HEX]
    DH = Device/Head Register [HEX]
    DC = Device Command Register [HEX]
    ER = Error register [HEX]
    ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 43 occurred at disk power-on lifetime: 14538 hours (605 days + 18 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 00 59 01 40  Error:

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------

Error 42 occurred at disk power-on lifetime: 14538 hours (605 days + 18 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 00 59 01 40  Error:

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------

Error 41 occurred at disk power-on lifetime: 14538 hours (605 days + 18 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 00 59 01 40  Error:

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------

Error 40 occurred at disk power-on lifetime: 14538 hours (605 days + 18 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 00 59 01 40  Error:

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------

Error 39 occurred at disk power-on lifetime: 14538 hours (605 days + 18 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 00 59 01 40  Error:

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------

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%     14549         88320
# 2  Short offline       Completed: read failure       90%     14549         88320
# 3  Short offline       Completed without error       00%     14549         -
# 4  Short offline       Completed: read failure       90%     14549         88320
# 5  Extended offline    Completed: read failure       90%     14549         88320
# 6  Extended offline    Completed: read failure       90%     14549         88320
# 7  Short offline       Completed: read failure       90%     14549         88320
# 8  Extended offline    Completed: read failure       90%     14549         88320
# 9  Short offline       Completed: unknown failure    90%     14542         -
#10  Conveyance offline  Completed: unknown failure    90%     14542         -
#11  Short offline       Completed: unknown failure    90%     14542         -
#12  Extended offline    Completed: unknown failure    90%     14542         -
#13  Short offline       Completed: unknown failure    90%     14542         -
#14  Extended offline    Completed: unknown failure    90%     14542         -
#15  Short offline       Completed without error       00%     10323         -
#16  Short offline       Aborted by host               70%     10323         -
#17  Short offline       Completed without error       00%      1660         -
#18  Short offline       Completed without error       00%      1409         -
#19  Short offline       Completed without error       00%       345         -
#20  Short offline       Completed without error       00%        13         -

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.
The S.M.A.R.T seems to be failing whenever i do it using CMD, however it worked one time when i tried short test from the inbuilt Disk App in Ubuntu. But failed again when i tried an extender diagnosis from the Disk App.
From the LBA i figured theres an error in block 88320, and from the disk partitions i attached above it looks like the error is in dev/sda1 which is an EFI System.
So i ran badblocks on dev/sda1 and found 4 bad blocks
Code:
aswin@Aswin:~$ sudo badblocks -v /dev/sda1 > badblocks.txt
Checking blocks 0 to 102399
Checking for bad blocks (read-only test): done                                                 
Pass completed, 4 bad blocks found. (4/0/0 errors)
aswin@Aswin:~$ cat badblocks.txt
43136
43137
43138
43139
However these block numbers are different from that shown during SMART LBA. I have no idea how bad my disk is right now, I did these steps through articles online, and not sure what to make out of all these test results.
If someone has an idea how to repair this, please help

Thanks in advance!!
 
Sep 24, 2021
3
0
10
0
Thanks for the reply!
Raw read error rate is high. Could be drive overheating.
The drive temp seems to be around 48-50°C , is that normal?
G-Sense error rate is very high. Looks like you're playing soccer with your laptop.
I have had to travel a lot with this laptop, but I seldom use it during travel, mostly it's shut down. But yeah it could have got damaged during travel unfortunately :(
There are 52 pending sectors. Those need to be resolved.
This can be done with mhdd - scan with relocate or
with victoria software.
Thanks, I have installed Victoria software and started a full disk scan, I will update the results once it's done.
 
Sep 24, 2021
3
0
10
0
If you have to travel with your laptop a lot, then consider upgrading to SSD.
SSD would not care about occasional shaking.
Yeah, I'm planning to upgrade the laptop soon, so will try to run this one till it gives up.

I tried running Victoria software, and by the time it scanned around 50 GB out of the total 1TB, it was showing 300+ orange, 40 red and around 10 blue sectors. But I've got a few normal background processes running so I'm not sure how accurate it will be hence stopped the scan for now.

I tried MHDD through a bootable USB for a more accurate scan, but it doesn't seem to recognise my HDD. Might be since my bios doesn't let me change SATA mode to IDE.
Do you know any work around to this ?
 

ASK THE COMMUNITY

TRENDING THREADS