我的 SSD 驱动器出现故障了吗?

我的 SSD 驱动器出现故障了吗?

我正在使用一个相当新的 SSD(5 个月前购买),最近遇到了读取失败。以下是内核报告的内容:

Jul  1 01:02:44 tryphon kernel: [1554891.463590] ata2.00: exception Emask 0x0 SAct 0x1000000 SErr 0x0 action 0x0
Jul  1 01:02:44 tryphon kernel: [1554891.478096] ata2.00: irq_stat 0x40000008
Jul  1 01:02:44 tryphon kernel: [1554891.486388] ata2.00: failed command: READ FPDMA QUEUED
Jul  1 01:02:44 tryphon kernel: [1554891.497141] ata2.00: cmd 60/80:c0:00:18:2c/05:00:02:00:00/40 tag 24 ncq dma 720896 in
Jul  1 01:02:44 tryphon kernel: [1554891.497141]          res 41/40:80:00:18:2c/00:05:02:00:00/40 Emask 0x409 (media error) <F>
Jul  1 01:02:44 tryphon kernel: [1554891.530266] ata2.00: status: { DRDY ERR }
Jul  1 01:02:44 tryphon kernel: [1554891.538714] ata2.00: error: { UNC }
Jul  1 01:02:44 tryphon kernel: [1554891.586520] ata2.00: configured for UDMA/133
Jul  1 01:02:44 tryphon kernel: [1554891.586576] sd 1:0:0:0: [sdb] tag#24 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul  1 01:02:44 tryphon kernel: [1554891.586581] sd 1:0:0:0: [sdb] tag#24 Sense Key : Medium Error [current]
Jul  1 01:02:44 tryphon kernel: [1554891.586585] sd 1:0:0:0: [sdb] tag#24 Add. Sense: Unrecovered read error - auto reallocate failed
Jul  1 01:02:44 tryphon kernel: [1554891.586590] sd 1:0:0:0: [sdb] tag#24 CDB: Read(10) 28 00 02 2c 18 00 00 05 80 00
Jul  1 01:02:44 tryphon kernel: [1554891.586593] blk_update_request: I/O error, dev sdb, sector 36444160

几分钟后,smartd守护进程向 root 发送了一封电子邮件:

Subject: SMART error (OfflineUncorrectableSector) detected on host: tryphon

This message was generated by the smartd daemon running on:

   host name:  tryphon
   DNS domain: home

The following warning/error was logged by the smartd daemon:

Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors

Device info:
LDLC, S/N:07072217A1171, FW:Q0601B, 120 GB

For details see host's SYSLOG.

You can also use the smartctl utility for further investigation.
Another message will be sent in 24 hours if the problem persists.

由于它是在带有 HDD 的 RAID 1 配置中使用,所以情况并不是特别糟糕,但听起来仍然很糟糕。

无论如何,我想检查我的 SSD 的可读性,dd if=/dev/sdb of=/dev/null但遇到了更多读取失败。以下是下一个读取错误的内核日志:

Jul  3 19:28:24 tryphon kernel: [ 4398.319485] ata2.00: exception Emask 0x0 SAct 0x180 SErr 0x0 action 0x0
Jul  3 19:28:24 tryphon kernel: [ 4398.332971] ata2.00: irq_stat 0x40000008
Jul  3 19:28:24 tryphon kernel: [ 4398.340961] ata2.00: failed command: READ FPDMA QUEUED
Jul  3 19:28:24 tryphon kernel: [ 4398.351416] ata2.00: cmd 60/00:38:08:23:80/01:00:00:00:00/40 tag 7 ncq dma 131072 in
Jul  3 19:28:24 tryphon kernel: [ 4398.351416]          res 41/40:00:08:23:80/00:01:00:00:00/40 Emask 0x409 (media error) <F>
Jul  3 19:28:24 tryphon kernel: [ 4398.383720] ata2.00: status: { DRDY ERR }
Jul  3 19:28:24 tryphon kernel: [ 4398.391853] ata2.00: error: { UNC }
Jul  3 19:28:24 tryphon kernel: [ 4398.439236] ata2.00: configured for UDMA/133
Jul  3 19:28:24 tryphon kernel: [ 4398.439258] sd 1:0:0:0: [sdb] tag#7 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul  3 19:28:24 tryphon kernel: [ 4398.439261] sd 1:0:0:0: [sdb] tag#7 Sense Key : Medium Error [current] 
Jul  3 19:28:24 tryphon kernel: [ 4398.439264] sd 1:0:0:0: [sdb] tag#7 Add. Sense: Unrecovered read error - auto reallocate failed
Jul  3 19:28:24 tryphon kernel: [ 4398.439268] sd 1:0:0:0: [sdb] tag#7 CDB: Read(10) 28 00 00 80 23 08 00 01 00 00
Jul  3 19:28:24 tryphon kernel: [ 4398.439270] blk_update_request: I/O error, dev sdb, sector 8397576
Jul  3 19:28:24 tryphon kernel: [ 4398.451841] ata2: EH complete
Jul  3 19:28:24 tryphon kernel: [ 4398.831494] ata2.00: exception Emask 0x0 SAct 0x1000 SErr 0x0 action 0x0
Jul  3 19:28:24 tryphon kernel: [ 4398.845137] ata2.00: irq_stat 0x40000008
Jul  3 19:28:24 tryphon kernel: [ 4398.853069] ata2.00: failed command: READ FPDMA QUEUED
Jul  3 19:28:24 tryphon kernel: [ 4398.863461] ata2.00: cmd 60/08:60:78:23:80/00:00:00:00:00/40 tag 12 ncq dma 4096 in
Jul  3 19:28:24 tryphon kernel: [ 4398.863461]          res 41/40:08:78:23:80/00:00:00:00:00/40 Emask 0x409 (media error) <F>
Jul  3 19:28:24 tryphon kernel: [ 4398.895577] ata2.00: status: { DRDY ERR }
Jul  3 19:28:24 tryphon kernel: [ 4398.903692] ata2.00: error: { UNC }
Jul  3 19:28:24 tryphon kernel: [ 4398.951089] ata2.00: configured for UDMA/133
Jul  3 19:28:24 tryphon kernel: [ 4398.951111] sd 1:0:0:0: [sdb] tag#12 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul  3 19:28:24 tryphon kernel: [ 4398.951116] sd 1:0:0:0: [sdb] tag#12 Sense Key : Medium Error [current] 
Jul  3 19:28:24 tryphon kernel: [ 4398.951119] sd 1:0:0:0: [sdb] tag#12 Add. Sense: Unrecovered read error - auto reallocate failed
Jul  3 19:28:24 tryphon kernel: [ 4398.951125] sd 1:0:0:0: [sdb] tag#12 CDB: Read(10) 28 00 00 80 23 78 00 00 08 00
Jul  3 19:28:24 tryphon kernel: [ 4398.951128] blk_update_request: I/O error, dev sdb, sector 8397688
Jul  3 19:28:24 tryphon kernel: [ 4398.963674] Buffer I/O error on dev sdb, logical block 1049711, async page read
Jul  3 19:28:24 tryphon kernel: [ 4398.978559] ata2: EH complete
Jul  3 19:28:24 tryphon kernel: [ 4399.051447] ata2.00: exception Emask 0x0 SAct 0x80000 SErr 0x0 action 0x0
Jul  3 19:28:24 tryphon kernel: [ 4399.065213] ata2.00: irq_stat 0x40000008
Jul  3 19:28:24 tryphon kernel: [ 4399.073159] ata2.00: failed command: READ FPDMA QUEUED
Jul  3 19:28:24 tryphon kernel: [ 4399.083555] ata2.00: cmd 60/08:98:78:23:80/00:00:00:00:00/40 tag 19 ncq dma 4096 in
Jul  3 19:28:24 tryphon kernel: [ 4399.083555]          res 41/40:08:78:23:80/00:00:00:00:00/40 Emask 0x409 (media error) <F>
Jul  3 19:28:24 tryphon kernel: [ 4399.115655] ata2.00: status: { DRDY ERR }
Jul  3 19:28:24 tryphon kernel: [ 4399.123792] ata2.00: error: { UNC }
Jul  3 19:28:24 tryphon kernel: [ 4399.171197] ata2.00: configured for UDMA/133
Jul  3 19:28:24 tryphon kernel: [ 4399.171223] sd 1:0:0:0: [sdb] tag#19 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul  3 19:28:24 tryphon kernel: [ 4399.171228] sd 1:0:0:0: [sdb] tag#19 Sense Key : Medium Error [current] 
Jul  3 19:28:24 tryphon kernel: [ 4399.171232] sd 1:0:0:0: [sdb] tag#19 Add. Sense: Unrecovered read error - auto reallocate failed
Jul  3 19:28:24 tryphon kernel: [ 4399.171237] sd 1:0:0:0: [sdb] tag#19 CDB: Read(10) 28 00 00 80 23 78 00 00 08 00
Jul  3 19:28:24 tryphon kernel: [ 4399.171240] blk_update_request: I/O error, dev sdb, sector 8397688
Jul  3 19:28:24 tryphon kernel: [ 4399.183787] Buffer I/O error on dev sdb, logical block 1049711, async page read
Jul  3 19:28:24 tryphon kernel: [ 4399.198659] ata2: EH complete

和:

Jul  5 12:28:06 tryphon kernel: [    5.513650] ata2.00: exception Emask 0x0 SAct 0x4000 SErr 0x0 action 0x0
Jul  5 12:28:06 tryphon kernel: [    5.527221] ata2.00: irq_stat 0x40000008
Jul  5 12:28:06 tryphon kernel: [    5.535114] ata2.00: failed command: READ FPDMA QUEUED
Jul  5 12:28:06 tryphon kernel: [    5.545448] ata2.00: cmd 60/08:70:98:af:32/00:00:00:00:00/40 tag 14 ncq dma 4096 in
Jul  5 12:28:06 tryphon kernel: [    5.545448]          res 41/40:08:98:af:32/00:00:00:00:00/40 Emask 0x409 (media error) <F>
Jul  5 12:28:06 tryphon kernel: [    5.577373] ata2.00: status: { DRDY ERR }
Jul  5 12:28:06 tryphon kernel: [    5.585423] ata2.00: error: { UNC }
Jul  5 12:28:06 tryphon kernel: [    5.632752] ata2.00: configured for UDMA/133
Jul  5 12:28:06 tryphon kernel: [    5.632778] sd 1:0:0:0: [sdb] tag#14 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul  5 12:28:06 tryphon kernel: [    5.632784] sd 1:0:0:0: [sdb] tag#14 Sense Key : Medium Error [current] 
Jul  5 12:28:06 tryphon kernel: [    5.632790] sd 1:0:0:0: [sdb] tag#14 Add. Sense: Unrecovered read error - auto reallocate failed
Jul  5 12:28:06 tryphon kernel: [    5.632797] sd 1:0:0:0: [sdb] tag#14 CDB: Read(10) 28 00 00 32 af 98 00 00 08 00
Jul  5 12:28:06 tryphon kernel: [    5.632801] blk_update_request: I/O error, dev sdb, sector 3321752
Jul  5 12:28:06 tryphon kernel: [    5.645296] md/raid1:md1: sdb3: rescheduling sector 173976
Jul  5 12:28:06 tryphon kernel: [    5.656333] ata2: EH complete
Jul  5 12:28:06 tryphon kernel: [    5.695829] md/raid1:md1: redirecting sector 173976 to other mirror: sda3

然后,我查看了驱动器通过 SMART 系统报告的内容。结果如下:

# smartctl -a /dev/sdb
smartctl 6.4 2014-10-07 r4002 [x86_64-linux-4.9.0-0.bpo.6-amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     LDLC
Serial Number:    07072217A1171
Firmware Version: Q0601B
User Capacity:    120,034,123,776 bytes [120 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-2 T13/2015-D revision 3
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Wed Jul 11 00:43:45 2018 CEST
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:  (0x00)     Offline data collection activity
                                    was never started.
                                    Auto Offline Data Collection: Disabled.
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:            (  120) seconds.
Offline data collection
capabilities:                        (0x11) SMART execute Offline immediate.
                                    No Auto Offline data collection support.
                                    Suspend Offline collection upon new
                                    command.
                                    No Offline surface scan supported.
                                    Self-test supported.
                                    No Conveyance Self-test supported.
                                    No Selective Self-test supported.
SMART capabilities:            (0x0002)     Does not save 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:    (  10) minutes.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x0032   100   100   050    Old_age   Always       -       0
  5 Reallocated_Sector_Ct   0x0032   100   100   050    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   050    Old_age   Always       -       3828
 12 Power_Cycle_Count       0x0032   100   100   050    Old_age   Always       -       18
160 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       6
161 Unknown_Attribute       0x0033   100   100   050    Pre-fail  Always       -       99
163 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       60
164 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       3268
165 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       2
166 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       1
167 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       1
168 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       1500
169 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       100
175 Program_Fail_Count_Chip 0x0032   100   100   050    Old_age   Always       -       0
176 Erase_Fail_Count_Chip   0x0032   100   100   050    Old_age   Always       -       0
177 Wear_Leveling_Count     0x0032   100   100   050    Old_age   Always       -       18
178 Used_Rsvd_Blk_Cnt_Chip  0x0032   100   100   050    Old_age   Always       -       1
181 Program_Fail_Cnt_Total  0x0032   100   100   050    Old_age   Always       -       0
182 Erase_Fail_Count_Total  0x0032   100   100   050    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   050    Old_age   Always       -       7
194 Temperature_Celsius     0x0022   100   100   050    Old_age   Always       -       40
195 Hardware_ECC_Recovered  0x0032   100   100   050    Old_age   Always       -       11868576
196 Reallocated_Event_Count 0x0032   100   100   050    Old_age   Always       -       6
197 Current_Pending_Sector  0x0032   100   100   050    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0032   100   100   050    Old_age   Always       -       6
199 UDMA_CRC_Error_Count    0x0032   100   100   050    Old_age   Always       -       0
232 Available_Reservd_Space 0x0032   100   100   050    Old_age   Always       -       99
241 Total_LBAs_Written      0x0030   100   100   050    Old_age   Offline      -       10975
242 Total_LBAs_Read         0x0030   100   100   050    Old_age   Offline      -       29075
245 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       2904

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

Selective Self-tests/Logging not supported

据我了解,Offline_Uncorrectable值为 6 的属性看起来很糟糕,因为在我看来某些数据丢失了 6 次。我遗漏了什么吗?

此外,该属性的原始值Hardware_ECC_Recovered看起来巨大的,尤其是与属性相比时Total_LBAs_Read

我应该担心我的 SSD 驱动器吗?我应该更换它吗?

不管怎么说,这是一个 TLC 驱动器。我知道它们不如 MLC(或更好的 SLC)驱动器耐用,但我没想到仅仅几个月后数据就丢失了。

答案1

部分答案:

你有 6 个Offline_uncorrectable应该在离线测试期间发生)和 6 Reallocated_Event_Count,但为零Reallocated_Sector_Ct。我将其理解为“在离线测试期间尝试重新分配一个块六次,但每次都失败”。

内核日志中的错误消息也显示“自动重新分配失败”,尽管这是一个在线的事件,不是一个离线一。

所以:

1)用于smartctl查看离线测试的结果,特别是运行的时间以及是否发生错误。

2) 使用smartctl开始另一个离线测试(过夜等)。查看结果。

3) 您在评论中提到“一些新的读取失败”。它们的块号是多少?它们总是同一个块吗?

如果某个块由于某种原因无法自动重新分配,我会考虑在文件系统中将该块标记为坏块(大多数文件系统都有此功能)。现在通常不会这样做,因为所有硬盘都会自动重新分配,无论是机械硬盘还是 SSD,但此功能正是为此目的而存在的。

虽然我更担心自动重新分配失败;这可能意味着包含重新分配元信息的(不可见)块是坏的。

我不知道该怎么办;如果 SDD 的供应商有一个可供下载的特殊工具,您可以通过它调整低级内容(有些供应商有),这可能会有所帮助。

相关内容