LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
Reload this Page smartd: "Currently unreadable (pending) sectors" errors LVM thin pool
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 01-31-2020, 07:10 PM   #1
ken1102
LQ Newbie
 
Registered: Jan 2020
Posts: 2

Rep: Reputation: Disabled
smartd: "Currently unreadable (pending) sectors" errors LVM thin pool

I got these messages:

Code:
rrdcached[1725]: flushing old values
Jan 30 22:10:59 pve rrdcached[1725]: rotating journals
Jan 30 22:10:59 pve rrdcached[1725]: started new journal /var/lib/rrdcached/journal/rrd.journal.1580458259.514261
Jan 30 22:10:59 pve rrdcached[1725]: removing old journal /var/lib/rrdcached/journal/rrd.journal.1580451059.514255

Jan 30 09:36:59 pve smartd[1242]: Device: /dev/sdb [SAT], 8 Currently unreadable (pending) sectors
Jan 30 09:36:59 pve smartd[1242]: Device: /dev/sdb [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 76 to 75

Jan 31 00:10:11 pve kernel: ata2: COMRESET failed (errno=-16)
Jan 31 00:10:11 pve kernel: ata2: limiting SATA link speed to 1.5 Gbps
Jan 31 00:10:11 pve kernel: ata2: hard resetting link
Jan 31 00:10:16 pve kernel: ata2: COMRESET failed (errno=-16)
Jan 31 00:10:16 pve kernel: ata2: reset failed, giving up
Jan 31 00:10:16 pve kernel: ata2.00: disabled
Jan 31 00:10:16 pve kernel: ata2: EH complete
Jan 31 00:10:16 pve kernel: sd 1:0:0:0: [sdb] tag#27 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jan 31 00:10:16 pve kernel: sd 1:0:0:0: [sdb] tag#27 CDB: Synchronize Cache(10) 35 00 00 00 00 00 00 00 00 00
Jan 31 00:10:16 pve kernel: blk_update_request: I/O error, dev sdb, sector 0
I ran a full scan
Code:
smartctl -t long /dev/sdb
and got this result:
Code:
root@pve:~# smartctl -a /dev/sdb
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.10.17-2-pve] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba 3.5" DT01ACA... Desktop HDD
Device Model:     TOSHIBA DT01ACA200
Serial Number:    73TTML1GS
LU WWN Device Id: 5 000039 ff3d949eb
Firmware Version: MX4OABB0
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Fri Jan 31 07:20:59 2020 HST
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:  (0x85) Offline data collection activity
                                        was aborted by an interrupting command from host.
                                        Auto Offline Data Collection: Enabled.
Self-test execution status:      ( 119) The previous self-test completed having
                                        the read element of the test failed.
Total time to complete Offline
data collection:                (15109) seconds.
Offline data collection
capabilities:                    (0x5b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No 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:        (   1) minutes.
Extended self-test routine
recommended polling time:        ( 252) minutes.
SCT capabilities:              (0x003d) SCT Status supported.
                                        SCT Error Recovery Control 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     0x000b   091   091   016    Pre-fail  Always       -       1376291
  2 Throughput_Performance  0x0005   139   139   054    Pre-fail  Offline      -       70
  3 Spin_Up_Time            0x0007   126   126   024    Pre-fail  Always       -       301 (Average 301)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       82
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       109
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   124   124   020    Pre-fail  Offline      -       33
  9 Power_On_Hours          0x0012   093   093   000    Old_age   Always       -       49700
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       68
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       129
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       129
194 Temperature_Celsius     0x0002   253   253   000    Old_age   Always       -       20 (Min/Max 11/48)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       151
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       8
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 164 (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 164 occurred at disk power-on lifetime: 49601 hours (2066 days + 17 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 00 e7 50 08  Error: UNC at LBA = 0x0850e700 = 139519744

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 e8 00 e7 50 40 00   4d+13:40:31.609  READ FPDMA QUEUED
  60 08 d0 00 10 20 40 00   4d+13:40:31.609  READ FPDMA QUEUED
  61 08 c8 a8 ab 4d 40 00   4d+13:40:31.609  WRITE FPDMA QUEUED
  ef 10 02 00 00 00 a0 00   4d+13:40:31.607  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00   4d+13:40:31.607  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

Error 163 occurred at disk power-on lifetime: 49601 hours (2066 days + 17 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 00 e7 50 08  Error: WP at LBA = 0x0850e700 = 139519744

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 08 a0 a8 ab 4d 40 00   4d+13:40:28.149  WRITE FPDMA QUEUED
  60 08 98 00 10 20 40 00   4d+13:40:27.792  READ FPDMA QUEUED
  60 08 90 00 e7 50 40 00   4d+13:40:27.756  READ FPDMA QUEUED
  60 08 88 78 c0 c1 40 00   4d+13:40:27.756  READ FPDMA QUEUED
  60 08 80 70 c0 c1 40 00   4d+13:40:27.756  READ FPDMA QUEUED

Error 162 occurred at disk power-on lifetime: 49601 hours (2066 days + 17 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 00 e7 50 08  Error: UNC at LBA = 0x0850e700 = 139519744

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 d8 00 e7 50 40 00   4d+13:40:22.829  READ FPDMA QUEUED
  60 08 c0 08 e2 46 40 00   4d+13:40:22.829  READ FPDMA QUEUED
  61 80 b8 38 4f a7 40 00   4d+13:40:22.829  WRITE FPDMA QUEUED
  61 40 b0 10 27 f4 40 00   4d+13:40:22.829  WRITE FPDMA QUEUED
  ef 10 02 00 00 00 a0 00   4d+13:40:22.825  SET FEATURES [Enable SATA feature]

Error 161 occurred at disk power-on lifetime: 49601 hours (2066 days + 17 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 00 e7 50 08  Error: WP at LBA = 0x0850e700 = 139519744

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 40 90 10 27 f4 40 00   4d+13:40:18.981  WRITE FPDMA QUEUED
  61 80 88 38 4f a7 40 00   4d+13:40:18.980  WRITE FPDMA QUEUED
  60 08 80 08 e2 46 40 00   4d+13:40:18.980  READ FPDMA QUEUED
  60 08 78 00 e2 46 40 00   4d+13:40:18.980  READ FPDMA QUEUED
  60 08 70 00 e7 50 40 00   4d+13:40:18.980  READ FPDMA QUEUED

Error 160 occurred at disk power-on lifetime: 49601 hours (2066 days + 17 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 00 e7 50 08  Error: WP at LBA = 0x0850e700 = 139519744

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 70 b8 80 09 7d 40 00   4d+13:40:13.966  WRITE FPDMA QUEUED
  61 80 b0 c8 48 75 40 00   4d+13:40:13.966  WRITE FPDMA QUEUED
  61 70 a8 90 e4 80 40 00   4d+13:40:13.966  WRITE FPDMA QUEUED
  61 d0 a0 30 9b 6d 40 00   4d+13:40:13.966  WRITE FPDMA QUEUED
  61 40 98 a0 e5 28 40 00   4d+13:40:13.966  WRITE FPDMA QUEUED

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       70%     49699         944826112

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.
Code:
Code: 
# sfdisk -luS /dev/sdb  or # 'fdisk -ul /dev/sdb'

Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
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: 1918C323-3472-48F1-874C-51B690C763F3

Device          Start        End   Sectors  Size Type
/dev/sdb1        2048  828377087 828375040  395G Linux LVM
/dev/sdb2   828377088 1656752127 828375040  395G Linux LVM
/dev/sdb3  1656752128 2485127167 828375040  395G Linux LVM
/dev/sdb4  2485127168 3313502207 828375040  395G Linux LVM
/dev/sdb5  3313502208 3907029134 593526927  283G Linux LVM
I followed to these instruction to find in which LVM2 logical partition is used the PE number 14214
(944826112 - 828377088) = 116449024/ 8192 = 14214.96875


https://www.linuxquestions.org/quest...rs-4175659756/
https://www.smartmontools.org/wiki/B...wto#LVMrepairs

at step :
Code:
lvdisplay --maps |egrep 'Physical|LV Name|Type'
Code:
LV Name                swap
    Type                linear
    Physical volume     /dev/sda3
    Physical extents    0 to 16383
  LV Name                root
    Type                linear
    Physical volume     /dev/sda3
    Physical extents    16384 to 44927
i havent found sdb2

Could you please help me this problem
 
Old 02-03-2020, 10:03 PM   #2
rknichols
Senior Member
 
Registered: Aug 2009
Distribution: Rocky Linux
Posts: 4,823

Rep: Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242
Quote:
Originally Posted by ken1102 View Post
Code:
Jan 31 00:10:16 pve kernel: sd 1:0:0:0: [sdb] tag#27 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jan 31 00:10:16 pve kernel: sd 1:0:0:0: [sdb] tag#27 CDB: Synchronize Cache(10) 35 00 00 00 00 00 00 00 00 00
Jan 31 00:10:16 pve kernel: blk_update_request: I/O error, dev sdb, sector 0
That suggests that something is seriously wrong at the start of sdb. See whether the beginning of the drive and the beginning of each partition can be read without error. There should be no I/O errors reported by this:
Code:
for P in "" 1 2 3 4 5; do dd if=/dev/sdb$P count=2048 of=/dev/null; done
 
1 members found this post helpful.
Old 02-04-2020, 06:29 AM   #3
beachboy2
Senior Member
 
Registered: Jan 2007
Location: Wild West Wales, UK
Distribution: Linux Mint 22 MATE, Peppermint OS-Devuan, EndeavourOS, antiX
Posts: 4,429
Blog Entries: 49

Rep: Reputation: 1647Reputation: 1647Reputation: 1647Reputation: 1647Reputation: 1647Reputation: 1647Reputation: 1647Reputation: 1647Reputation: 1647Reputation: 1647Reputation: 1647
ken1102,

The output from SMART 5 and SMART 197 suggests a problematic drive.

See post #19 on:
https://www.linuxquestions.org/quest...927/page2.html

Reallocated Sector Count:
https://harddrivegeek.com/reallocated-sector-count/

Current Pending Sector Count:
https://kb.acronis.com/content/9133
Last edited by beachboy2; 02-04-2020 at 01:33 PM.
 
1 members found this post helpful.
  


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
smartd: "Currently unreadable (pending) sectors" errors Robert S Linux - Hardware 15 05-20-2021 12:25 AM
smartd: "Currently unreadable (pending) sectors" errors LVM thin pool ken1102 Linux - Newbie 1 02-01-2020 07:56 AM
Currently unreadable (pending) sectors axiomtek123 Linux - Server 4 01-26-2018 08:41 PM
Currently unreadable (pending) sectors ravindert Linux - Newbie 1 09-16-2013 08:51 PM
Smartd Error Message generated by Smartd Daemon Proces rexjenny Red Hat 1 11-29-2006 07:12 PM

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

All times are GMT -5. The time now is 07:20 AM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
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