LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 02-27-2017, 05:09 PM   #1
Hungry ghost
Senior Member
 
Registered: Dec 2004
Posts: 1,222

Rep: Reputation: 667Reputation: 667Reputation: 667Reputation: 667Reputation: 667Reputation: 667
Buffer I/O error on /dev/sdb1 (...) async page read


Since some months ago I have been seeing the following error message every time I reboot:

Code:
Buffer I/O error on dev sdb1, logical block 11, async page read
I'm about to do a disk check from Windows, since this is a data partition in NTFS, but in any case, I would like to know if this is serious (HDD damaged/failing) or something that can be solved with chkdsk or a similar utility.

BTW, I am backing up the data contained in this partition from Debian with rsync and the system is lagging a lot. I don't remember this behavior while using rsync previously but I usually let it do its job while I do other things away from the computer.

Any thoughts?
 
Old 02-27-2017, 08:15 PM   #2
rknichols
Senior Member
 
Registered: Aug 2009
Distribution: CentOS
Posts: 4,579

Rep: Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097
Please post the output from "smartctl -a /dev/sdb" (run as root), and please wrap that in [CODE] ... [/CODE] tags to preserve formatting.
 
Old 02-28-2017, 04:22 AM   #3
Hungry ghost
Senior Member
 
Registered: Dec 2004
Posts: 1,222

Original Poster
Rep: Reputation: 667Reputation: 667Reputation: 667Reputation: 667Reputation: 667Reputation: 667
Hi rknichols, thanks for your answer. This is the output of the smartctl command:

Code:
smartctl -a /dev/sdb
smartctl 6.2 2013-11-07 r3856 [x86_64-linux-4.4.49-16-default] (SUSE RPM)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Caviar Blue Serial ATA
Device Model:     WDC WD3200AAJS-00L7A0
Serial Number:    WD-WCAV2C563757
LU WWN Device Id: 5 0014ee 102416107
Firmware Version: 01.03E01
User Capacity:    320.072.933.376 bytes [320 GB]
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.5, 3.0 Gb/s
Local Time is:    Tue Feb 28 05:14:03 2017 VET
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:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever 
                                        been run.
Total time to complete Offline 
data collection:                ( 6180) 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:        (  75) minutes.
Conveyance self-test routine
recommended polling time:        (   5) minutes.
SCT capabilities:              (0x3037) 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   197   051    Pre-fail  Always       -       30
  3 Spin_Up_Time            0x0027   134   133   021    Pre-fail  Always       -       4300
  4 Start_Stop_Count        0x0032   097   097   000    Old_age   Always       -       3833
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   100   253   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   069   069   000    Old_age   Always       -       22748
 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       -       3052
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       155
193 Load_Cycle_Count        0x0032   199   199   000    Old_age   Always       -       3833
194 Temperature_Celsius     0x0022   113   090   000    Old_age   Always       -       30
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       8
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       8
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   198   000    Old_age   Offline      -       8

SMART Error Log Version: 1
Warning: ATA error count 3663 inconsistent with error log pointer 1

ATA Error Count: 3663 (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 3663 occurred at disk power-on lifetime: 22748 hours (947 days + 20 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 08 58 08 00 e0  Error: UNC 8 sectors at LBA = 0x00000858 = 2136

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 58 08 00 e0 08      00:01:00.107  READ DMA

Error 3662 occurred at disk power-on lifetime: 22748 hours (947 days + 20 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 08 58 08 00 e0  Error: UNC 8 sectors at LBA = 0x00000858 = 2136

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 58 08 00 e0 08      00:00:57.871  READ DMA
  c8 00 08 50 08 00 e0 08      00:00:57.871  READ DMA
  c8 00 08 48 08 00 e0 08      00:00:57.871  READ DMA
  c8 00 08 40 08 00 e0 08      00:00:57.841  READ DMA

Error 3661 occurred at disk power-on lifetime: 22748 hours (947 days + 20 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 38 58 08 00 e0  Error: UNC 56 sectors at LBA = 0x00000858 = 2136

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 38 40 08 00 e0 08      00:00:54.583  READ DMA
  c8 00 18 20 08 00 e0 08      00:00:54.583  READ DMA
  c8 00 08 10 08 00 e0 08      00:00:54.583  READ DMA
  c8 00 08 78 08 00 e0 08      00:00:54.558  READ DMA
  c8 00 08 38 08 00 e0 08      00:00:54.558  READ DMA

Error 3660 occurred at disk power-on lifetime: 22748 hours (947 days + 20 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 08 58 08 00 e0  Error: UNC 8 sectors at LBA = 0x00000858 = 2136

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 58 08 00 e0 08      00:00:43.201  READ DMA
  ec 00 00 00 00 00 a0 08      00:00:43.197  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      00:00:43.197  SET FEATURES [Set transfer mode]

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     10921         -
# 2  Short offline       Completed without error       00%      1510         -
# 3  Short offline       Completed without error       00%      1081         -

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.
It looks a bit cryptic to me. Any ideas?
 
Old 02-28-2017, 04:40 AM   #4
jsbjsb001
Senior Member
 
Registered: Mar 2009
Location: Earth, unfortunately...
Distribution: Currently: OpenMandriva. Previously: openSUSE, PCLinuxOS, CentOS, among others over the years.
Posts: 3,869

Rep: Reputation: 2053Reputation: 2053Reputation: 2053Reputation: 2053Reputation: 2053Reputation: 2053Reputation: 2053Reputation: 2053Reputation: 2053Reputation: 2053Reputation: 2053
Quote:
Originally Posted by odiseo77 View Post
Hi rknichols, thanks for your answer. This is the output of the smartctl command:

Code:
smartctl -a /dev/sdb
smartctl 6.2 2013-11-07 r3856 [x86_64-linux-4.4.49-16-default] (SUSE RPM)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Caviar Blue Serial ATA
Device Model:     WDC WD3200AAJS-00L7A0
Serial Number:    WD-WCAV2C563757
LU WWN Device Id: 5 0014ee 102416107
Firmware Version: 01.03E01
User Capacity:    320.072.933.376 bytes [320 GB]
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.5, 3.0 Gb/s
Local Time is:    Tue Feb 28 05:14:03 2017 VET
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:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever 
                                        been run.
Total time to complete Offline 
data collection:                ( 6180) 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:        (  75) minutes.
Conveyance self-test routine
recommended polling time:        (   5) minutes.
SCT capabilities:              (0x3037) 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   197   051    Pre-fail  Always       -       30
  3 Spin_Up_Time            0x0027   134   133   021    Pre-fail  Always       -       4300
  4 Start_Stop_Count        0x0032   097   097   000    Old_age   Always       -       3833
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   100   253   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   069   069   000    Old_age   Always       -       22748
 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       -       3052
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       155
193 Load_Cycle_Count        0x0032   199   199   000    Old_age   Always       -       3833
194 Temperature_Celsius     0x0022   113   090   000    Old_age   Always       -       30
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       8
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       8
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   198   000    Old_age   Offline      -       8

SMART Error Log Version: 1
Warning: ATA error count 3663 inconsistent with error log pointer 1

ATA Error Count: 3663 (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 3663 occurred at disk power-on lifetime: 22748 hours (947 days + 20 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 08 58 08 00 e0  Error: UNC 8 sectors at LBA = 0x00000858 = 2136

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 58 08 00 e0 08      00:01:00.107  READ DMA

Error 3662 occurred at disk power-on lifetime: 22748 hours (947 days + 20 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 08 58 08 00 e0  Error: UNC 8 sectors at LBA = 0x00000858 = 2136

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 58 08 00 e0 08      00:00:57.871  READ DMA
  c8 00 08 50 08 00 e0 08      00:00:57.871  READ DMA
  c8 00 08 48 08 00 e0 08      00:00:57.871  READ DMA
  c8 00 08 40 08 00 e0 08      00:00:57.841  READ DMA

Error 3661 occurred at disk power-on lifetime: 22748 hours (947 days + 20 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 38 58 08 00 e0  Error: UNC 56 sectors at LBA = 0x00000858 = 2136

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 38 40 08 00 e0 08      00:00:54.583  READ DMA
  c8 00 18 20 08 00 e0 08      00:00:54.583  READ DMA
  c8 00 08 10 08 00 e0 08      00:00:54.583  READ DMA
  c8 00 08 78 08 00 e0 08      00:00:54.558  READ DMA
  c8 00 08 38 08 00 e0 08      00:00:54.558  READ DMA

Error 3660 occurred at disk power-on lifetime: 22748 hours (947 days + 20 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 08 58 08 00 e0  Error: UNC 8 sectors at LBA = 0x00000858 = 2136

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 58 08 00 e0 08      00:00:43.201  READ DMA
  ec 00 00 00 00 00 a0 08      00:00:43.197  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      00:00:43.197  SET FEATURES [Set transfer mode]

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     10921         -
# 2  Short offline       Completed without error       00%      1510         -
# 3  Short offline       Completed without error       00%      1081         -

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.
It looks a bit cryptic to me. Any ideas?
It looks like your hard disk may be failing;

Code:
Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 58 08 00 e0 08      00:00:43.201  READ DMA
  ec 00 00 00 00 00 a0 08      00:00:43.197  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      00:00:43.197  SET FEATURES [Set transfer mode]
This explains the error message your are getting, in your kernel log.
 
Old 02-28-2017, 10:26 AM   #5
rknichols
Senior Member
 
Registered: Aug 2009
Distribution: CentOS
Posts: 4,579

Rep: Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097
It looks like you have a single block of 8 bad sectors at LBA 2136. The good news is that this should be easy to fix. I first need to confirm my assumptions that:
  1. This is an ext3 or ext4 filesystem in a partition that begins at sector 2048,
  2. These sectors are being used by inode 7 (EXT2_RESIZE_INO).
If that is true, then simply writing zeros to those sectors and running fsck will get that block reassigned to spare sectors and all will be well.

First, look at the output from "fdisk -l /dev/sdb" and confirm that partition 1 starts at sector 2048. If true, that means that LBA 2136 is at sector offset 88 in that partition. For a filesystem with the usual 4K blocksize, that would be filesystem block 11.

Verify that block 11 is assigned to inode 7. Run the following (as root) to confirm (the part you type is in blue):
Code:
# debugfs /dev/sdb1
debugfs 1.41.12 (17-May-2010)
debugfs:  icheck 11
Block	Inode number
11	7
debugfs:  q
If that is as shown, then you can zero that block safely:
Code:
dd if=/dev/zero of=/dev/sdb1 count=8 seek=88
Now, you need to reboot and force an fsck. I don't know how to force an interactive fsck at boot time in Debian. You'll have to look it up, or perhaps an Debian expert can chime in here.
 
1 members found this post helpful.
Old 02-28-2017, 03:03 PM   #6
Hungry ghost
Senior Member
 
Registered: Dec 2004
Posts: 1,222

Original Poster
Rep: Reputation: 667Reputation: 667Reputation: 667Reputation: 667Reputation: 667Reputation: 667
Hi guys, thanks for your help so far.

rknichols, this is the output of fdisk -l /dev/sdb:

Code:
Disco /dev/sdb: 298,1 GiB, 320072933376 bytes, 625142448 sectores
Unidades: sectores de 1 * 512 = 512 bytes
Tamaño de sector (lógico/físico): 512 bytes / 512 bytes
Tamaño de E/S (mínimo/óptimo): 512 bytes / 512 bytes
Tipo de etiqueta de disco: dos
Identificador del disco: 0x80a400ea

Disposit.  Inicio  Comienzo     Final  Sectores Tamaño Id Tipo
/dev/sdb1  *           2048 501364735 501362688 239,1G  7 HPFS/NTFS/exFAT
/dev/sdb2         501366782 625142447 123775666    59G  5 Extendida
/dev/sdb5         501366784 541157375  39790592    19G 83 Linux
/dev/sdb6         541159424 586080255  44920832  21,4G 83 Linux
/dev/sdb7         586080319 625142447  39062129  18,6G 83 Linux
The partition begins at sector 2048, but it's an NTFS partition. Is there some way to fix it, maybe from Windows, or does it necessarily need to be formatted in ext3-4 to be able to invalidate that block?
 
Old 02-28-2017, 07:36 PM   #7
rknichols
Senior Member
 
Registered: Aug 2009
Distribution: CentOS
Posts: 4,579

Rep: Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097
Quote:
Originally Posted by odiseo77 View Post
The partition begins at sector 2048, but it's an NTFS partition.
Does Windows still run OK without complaint? Have you tried running "chkdsk" on that drive? Note that the "chkdsk" that runs when you've told Windows to "automatically repair" errors is much more thorough and actually verifies that all files can be read.

I'm not an expert on NTFS. I did try zeroing those 8 sectors in an NTFS filesystem, and Windows chkdsk did find and repair some errors. Of course my filesystem isn't your filesystem, and I really have no way to know whether any files were permanently lost or corrupted (I did it in a snapshot of a VM). You don't have a lot to lose (those sectors can't be read), so without any advice from someone more knowledgeable, that's all I can suggest doing.
 
1 members found this post helpful.
Old 02-28-2017, 07:59 PM   #8
Hungry ghost
Senior Member
 
Registered: Dec 2004
Posts: 1,222

Original Poster
Rep: Reputation: 667Reputation: 667Reputation: 667Reputation: 667Reputation: 667Reputation: 667
Hi again!

Windows doesn't complain about that partition, but this is a data partition I use to share my files between Windows and Linux in my dual-boot setup (Windows is installed in another partition on /dev/sda).

Yesterday I ran chkdsk /F on the troubled partition from Windows and it found no errors at all. It's Linux which complains about /dev/sdb1 when booting the system, but other than that I have no problems whatsoever with this partition (all my data can be read/saved without issues from Linux and Windows).

Since this is a NTFS partition, I will do some research to see what other tools are available on Windows to diagnose and repair NTFS problems. Thanks a lot for your help!

Last edited by Hungry ghost; 02-28-2017 at 08:01 PM.
 
Old 02-28-2017, 09:59 PM   #9
rknichols
Senior Member
 
Registered: Aug 2009
Distribution: CentOS
Posts: 4,579

Rep: Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097
If you do not need to save the data currently in the partition, what I would do is zero the entire partition (dd if=/dev/zero of=/dev/sdb1 bs=1M oflag=direct), then run "smartctl -t long /dev/sdb" and examine the results of "smartctl -a /dev/sdb" to see if the drive seems healthy, then make a new NTFS filesystem there (from Windows, probably).
 
Old 03-01-2017, 02:18 AM   #10
jsbjsb001
Senior Member
 
Registered: Mar 2009
Location: Earth, unfortunately...
Distribution: Currently: OpenMandriva. Previously: openSUSE, PCLinuxOS, CentOS, among others over the years.
Posts: 3,869

Rep: Reputation: 2053Reputation: 2053Reputation: 2053Reputation: 2053Reputation: 2053Reputation: 2053Reputation: 2053Reputation: 2053Reputation: 2053Reputation: 2053Reputation: 2053
I would still consider replacing the disk in question, if possible. As I have a Western Digital Caviar SE (Device Model: WDC WD2000JS-00PDB0), which has never reported any SMART errors (I have had it for about 10 or so years now, transplanted form my first PC), so the fact yours is reporting bad sectors, is not a good sign of things that may come. I can't guarantee that it will fail, but having said that, once again suggest you look at replacing it, if you can.
 
Old 03-01-2017, 10:01 AM   #11
rknichols
Senior Member
 
Registered: Aug 2009
Distribution: CentOS
Posts: 4,579

Rep: Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097
There are many transient events, both mechanical and electrical, that can cause a few sequential sectors to appear bad. Many of those are not an indication of future problems. Right now, a single block of 8 sectors is being reported as bad, and the drive has not seen any bad sectors elsewhere. Of course this drive is pretty small (320GB) by today's standards, and might be due for an upgrade. But, at this point I haven't seen anything else that would warrant replacing it. Do keep in mind that every new drive comes with the non-zero chance of infant mortality. At 22748 hours, the one is in the middle of its life.
 
Old 03-01-2017, 11:25 AM   #12
Hungry ghost
Senior Member
 
Registered: Dec 2004
Posts: 1,222

Original Poster
Rep: Reputation: 667Reputation: 667Reputation: 667Reputation: 667Reputation: 667Reputation: 667
I will try the suggestion to zero out the entire partition in a few days, when I have some time to do the backups and restore my data. In any case, I do regular backups of my data, so if something goes wrong, I will still be able to recover my data.

I'll keep you posted on how this goes after I zero out and reformat the partition.

Thanks for your help, guys!

Cheers
 
Old 04-01-2017, 07:01 PM   #13
Hungry ghost
Senior Member
 
Registered: Dec 2004
Posts: 1,222

Original Poster
Rep: Reputation: 667Reputation: 667Reputation: 667Reputation: 667Reputation: 667Reputation: 667
Sorry for the late reply.

This is just to let you know that after zeroing the partition and reformatting it (in NTFS), the message I was getting disappeared, so all is good.

Cheers.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] usb drive: cannot remount block device /dev/sdb1 read-write, is write-protected schneidz Linux - Hardware 5 01-06-2015 04:15 PM
Format /dev/sdb1 fails but /dev/sdb succeeds? Lop3 Linux - Hardware 2 02-09-2014 06:06 PM
My pendrive suddenly changed from /dev/sda1 to /dev/sdb1! stf92 Slackware 10 08-08-2012 06:02 PM
mdadm --manage /dev/md0 --add /dev/sdb1 returns device busy JeepingAZ Linux - Desktop 2 02-17-2011 01:18 PM
Buffer I/O error on device sdb1 tikit Linux - Hardware 2 02-04-2010 02:55 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 03:11 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration