Hey, please forgive me for posting a question that is not Debian-specific, but maybe somebody here can explain this to me. Ten years ago I would have posted to Usenet instead.
I have two disks in a RAID-1:
| $ cat /proc/mdstat
| Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4]
[raid10]
| md0 : active raid1 sdb1[2] sdc1[0]
| 5860390400 blocks super 1.2 [2/2] [UU]
| bitmap: 5/44 pages [20KB], 65536KB chunk
|
| unused devices: <none>
During the latest monthly check I got kernel messages like this:
| Oct 06 00:57:01 jigsaw kernel: md: data-check of RAID array md0
| Oct 06 14:27:11 jigsaw kernel: ata3.00: exception Emask 0x0 SAct 0x4000000
SErr 0x0 action 0x0
| Oct 06 14:27:11 jigsaw kernel: ata3.00: irq_stat 0x40000008
| Oct 06 14:27:11 jigsaw kernel: ata3.00: failed command: READ FPDMA QUEUED
| Oct 06 14:27:11 jigsaw kernel: ata3.00: cmd
60/80:d0:80:74:f9/08:00:2d:02:00/40 tag 26 ncq dma 1114112 in
| res
41/40:00:50:77:f9/00:00:2d:02:00/00 Emask 0x409 (media error) <F>
| Oct 06 14:27:11 jigsaw kernel: ata3.00: status: { DRDY ERR }
| Oct 06 14:27:11 jigsaw kernel: ata3.00: error: { UNC }
| Oct 06 14:27:11 jigsaw kernel: ata3.00: configured for UDMA/133
| Oct 06 14:27:11 jigsaw kernel: sd 2:0:0:0: [sdb] tag#26 FAILED Result:
hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=7s
| Oct 06 14:27:11 jigsaw kernel: sd 2:0:0:0: [sdb] tag#26 Sense Key : Medium
Error [current]
| Oct 06 14:27:11 jigsaw kernel: sd 2:0:0:0: [sdb] tag#26 Add. Sense:
Unrecovered read error - auto reallocate failed
| Oct 06 14:27:11 jigsaw kernel: sd 2:0:0:0: [sdb] tag#26 CDB: Read(16) 88 00
00 00 00 02 2d f9 74 80 00 00 08 80 00 00
| Oct 06 14:27:11 jigsaw kernel: I/O error, dev sdb, sector 9361257600 op
0x0:(READ) flags 0x0 phys_seg 150 prio class 3
| Oct 06 14:27:11 jigsaw kernel: ata3: EH complete
The sector number mentioned at the bottom is increasing during the
check.
The way I understand these messages is that some sectors cannot be read
from sdb at all and the disk is unable to reallocate the data somewhere
else (probably because it doesn't know what the data should be in the
first place).
The disk has been running continuously for seven years now and I am
running out of space anyway, so I already ordered a replacement. But I
do not fully understand what is happening.
Two of these message blocks end with this:
| Oct 07 10:26:12 jigsaw kernel: md/raid1:md0: sdb1: rescheduling sector
10198068744
What does that mean for the other instances of this error? The data
is still readable from the other disk in the RAID, right? Why doesn't md
mention it? Why is the RAID still considered healthy? At some point I
would expect the disk to be kicked from the RAID.
I unmounted the filesystem and performed a bad blocks scan (fsck.ext4
-fcky) that did not find anything of importance (only "Inode x extent
tree (at level 1) could be shorter/narrower"), and it also did not yield
any of the above kernel messages. But another RAID check triggers these
messages again, just with different sector numbers. The RAID is still
healthy, though.
Should this tell me that it is new sectors are dying all the time, or
should this lead me to believe that a cable / the SATA controller is at
fault? I don't even see any errors with smartctl:
| # smartctl -a /dev/sdb
| smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-25-amd64] (local build)
| Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org
|
| === START OF INFORMATION SECTION ===
| Model Family: Western Digital Red
| Device Model: WDC WD60EFRX-68L0BN1
| Serial Number: WD-xxxxxxxxxxxx
| LU WWN Device Id: 5 0014ee 263faee8c
| Firmware Version: 82.00A82
| User Capacity: 6,001,175,126,016 bytes [6.00 TB]
| Sector Sizes: 512 bytes logical, 4096 bytes physical
| Rotation Rate: 5700 rpm
| Device is: In smartctl database 7.3/5319
| ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b
| SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
| Local Time is: Tue Oct 8 15:15:22 2024 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: (0x85) Offline data collection activity
| was aborted by an interrupting
command from host.
| Auto Offline Data Collection: Enabled.
| Self-test execution status: ( 245) Self-test routine in progress...
| 50% of test remaining.
| Total time to complete Offline
| data collection: ( 1904) 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: ( 673) minutes.
| Conveyance self-test routine
| recommended polling time: ( 5) minutes.
| SCT capabilities: (0x303d) 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 0x002f 199 169 051 Pre-fail Always
- 81
| 3 Spin_Up_Time 0x0027 198 197 021 Pre-fail Always
- 9100
| 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always
- 83
| 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 016 016 000 Old_age Always
- 61794
| 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always
- 0
| 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always
- 0
| 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always
- 82
| 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always
- 54
| 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always
- 2219
| 194 Temperature_Celsius 0x0022 119 116 000 Old_age Always
- 33
| 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always
- 0
| 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always
- 0
| 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline
- 0
| 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always
- 0
| 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline
- 43
|
| SMART Error Log Version: 1
| No Errors Logged
|
| 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% 61789 -
| # 2 Short offline Completed without error 00% 61758 -
| # 3 Short offline Completed without error 00% 61752 -
| # 4 Extended offline Completed without error 00% 61726 -
| # 5 Short offline Completed without error 00% 61710 -
| # 6 Short offline Completed without error 00% 61686 -
| # 7 Short offline Completed without error 00% 61662 -
| # 8 Short offline Completed without error 00% 61638 -
| # 9 Short offline Completed without error 00% 61615 -
| #10 Short offline Completed without error 00% 61591 -
| #11 Short offline Completed without error 00% 61567 -
| #12 Extended offline Completed without error 00% 61559 -
| #13 Short offline Completed without error 00% 61543 -
| #14 Short offline Completed without error 00% 61519 -
| #15 Short offline Completed without error 00% 61495 -
| #16 Short offline Completed without error 00% 61471 -
| #17 Short offline Completed without error 00% 61447 -
| #18 Short offline Completed without error 00% 61423 -
| #19 Short offline Completed without error 00% 61399 -
| #20 Extended offline Completed without error 00% 61391 -
| #21 Short offline Completed without error 00% 61375 -
|
| 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.
I am still waiting for the result of a long self-test.
Do you think I should do remove the drive from the RAID immediately? Or
should I suspect something else is at faula?t I perfer not to run the
risk of losing the RAID completely when I keep on running on one disk
while the new one is being shipped. I do have backups, but it would be
great if I didn't need to restore.
Regards,
Jochen
--
I see weapons of mass destruction as shameful but necessary.
[Agree] [Disagree]
<http://archive.slowlydownward.com/NODATA/data_enter2.html>
signature.asc
Description: PGP signature
