我今天早上刚刚检查了我的 RAID 阵列，得到的结果是：
$ cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
md1 : active raid1 sdc7[0]
238340224 blocks [2/1] [U_]
md0 : active raid1 sdc6[0]
244139648 blocks [2/1] [U_]
md127 : active raid1 sdc3[0]
390628416 blocks [2/1] [U_]
unused devices: <none>
$
我相信，这意味着我的阵列中的一个磁盘已坏，这是真的吗？
我该如何进行正确的故障排除？我的/etc/mdadm/mdadm.conf情况如下：
$ cat /etc/mdadm/mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for MD superblocks. alternatively, specify devices to scan, using
# wildcards if desired.
#DEVICE partitions containers
# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes
# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# instruct the monitoring daemon where to send mail alerts
MAILADDR root
# definitions of existing MD arrays
ARRAY /dev/md127 UUID=124cd4a5:2965955f:cd707cc0:bc3f8165
ARRAY /dev/md0 UUID=91e560f1:4e51d8eb:cd707cc0:bc3f8165
ARRAY /dev/md1 UUID=0abe503f:401d8d09:cd707cc0:bc3f8165
我如何找出哪个物理驱动器已损坏并需要更换？
谢谢
编辑1
# mdadm --detail /dev/md0
/dev/md0:
Version : 0.90
Creation Time : Tue Sep 1 19:15:33 2009
Raid Level : raid1
Array Size : 244139648 (232.83 GiB 250.00 GB)
Used Dev Size : 244139648 (232.83 GiB 250.00 GB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Mon Sep 21 07:11:24 2015
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
UUID : 91e560f1:4e51d8eb:cd707cc0:bc3f8165
Events : 0.76017
Number Major Minor RaidDevice State
0 8 38 0 active sync /dev/sdc6
1 0 0 1 removed
root@regDesktopHome:~#
为什么会这么说呢Failed Devices : 0？
编辑2
打开 Gparted，我可以看到两个驱动器，/dev/sdb以及/dev/sdc它们都是我的两个RAID驱动器。但是，mdadm 认为它们/dev.sdb已被删除，原因不明……这很奇怪。我尝试在“/dev/sdb”上安装一个分区，并得到以下结果
$sudo mount /dev/sdb7 test
[sudo] password for ron:
mount: unknown filesystem type 'linux_raid_member'
看起来一切都正确。如何恢复 RAID 阵列的顺序？
编辑3
我运行了，smartctl -a /dev/sdc并且smartctl -a /dev/sdb我还做了badblocks /dev/sdc，并且badblocks /dev/sdb虽然sdc看起来 100% 干净，但sdb返回了一些坏块：
# badblocks /dev/sdb
16130668
16130669
16130670
16130671
这可能是导致我所见故障的原因吗？有什么方法可以修复/忽略这些坏块，还是我应该更换驱动器？
编辑4
# smartctl --all /dev/sdb
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-62-generic] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.12
Device Model: ST31000528AS
Serial Number: 6VP0308B
LU WWN Device Id: 5 000c50 013d3ae45
Firmware Version: CC34
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 7200 rpm
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 2.6, 3.0 Gb/s
Local Time is: Sat Sep 26 11:35:02 2015 PDT
==> WARNING: A firmware update for this drive may be available,
see the following Seagate web pages:
http://knowledge.seagate.com/articles/en_US/FAQ/207931en
http://knowledge.seagate.com/articles/en_US/FAQ/213891en
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: (0x82) Offline data collection activity
was completed without error.
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: ( 600) 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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 195) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x103f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 114 099 006 Pre-fail Always - 78420742
3 Spin_Up_Time 0x0003 095 095 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 099 099 020 Old_age Always - 1240
5 Reallocated_Sector_Ct 0x0033 099 099 036 Pre-fail Always - 60
7 Seek_Error_Rate 0x000f 082 060 030 Pre-fail Always - 199357441
9 Power_On_Hours 0x0032 052 052 000 Old_age Always - 42401
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 099 037 020 Old_age Always - 1240
183 Runtime_Bad_Block 0x0000 098 098 000 Old_age Offline - 2
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 094 094 000 Old_age Always - 6
188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0
189 High_Fly_Writes 0x003a 050 050 000 Old_age Always - 50
190 Airflow_Temperature_Cel 0x0022 062 046 045 Old_age Always - 38 (Min/Max 30/38)
194 Temperature_Celsius 0x0022 038 054 000 Old_age Always - 38 (0 17 0 0 0)
195 Hardware_ECC_Recovered 0x001a 030 012 000 Old_age Always - 78420742
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 1
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 1
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 73332271657814
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 2822963046
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 2361465529
SMART Error Log Version: 1
ATA Error Count: 6 (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 6 occurred at disk power-on lifetime: 42372 hours (1765 days + 12 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 d9 44 ec 01 Error: UNC at LBA = 0x01ec44d9 = 32261337
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 00 08 d8 44 ec 41 00 09:26:28.967 READ FPDMA QUEUED
27 00 00 00 00 00 e0 00 09:26:28.941 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 00 09:26:28.940 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 09:26:28.928 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 00 09:26:28.901 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 5 occurred at disk power-on lifetime: 42372 hours (1765 days + 12 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 d9 44 ec 01 Error: UNC at LBA = 0x01ec44d9 = 32261337
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 00 08 d8 44 ec 41 00 09:26:26.095 READ FPDMA QUEUED
27 00 00 00 00 00 e0 00 09:26:26.069 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 00 09:26:26.068 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 09:26:26.055 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 00 09:26:26.029 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 4 occurred at disk power-on lifetime: 42372 hours (1765 days + 12 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 d9 44 ec 01 Error: UNC at LBA = 0x01ec44d9 = 32261337
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 00 08 d8 44 ec 41 00 09:26:23.222 READ FPDMA QUEUED
27 00 00 00 00 00 e0 00 09:26:23.195 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 00 09:26:23.194 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 09:26:23.182 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 00 09:26:23.137 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 3 occurred at disk power-on lifetime: 42372 hours (1765 days + 12 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 d9 44 ec 01 Error: UNC at LBA = 0x01ec44d9 = 32261337
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 00 08 d8 44 ec 41 00 09:26:20.351 READ FPDMA QUEUED
60 00 80 e8 44 ec 41 00 09:26:20.350 READ FPDMA QUEUED
27 00 00 00 00 00 e0 00 09:26:20.324 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 00 09:26:20.323 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 09:26:20.311 SET FEATURES [Set transfer mode]
Error 2 occurred at disk power-on lifetime: 42372 hours (1765 days + 12 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 d9 44 ec 01 Error: UNC at LBA = 0x01ec44d9 = 32261337
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 00 80 e8 44 ec 41 00 09:26:17.478 READ FPDMA QUEUED
60 00 40 a8 44 ec 41 00 09:26:17.478 READ FPDMA QUEUED
60 00 20 88 44 ec 41 00 09:26:17.476 READ FPDMA QUEUED
60 00 08 80 44 ec 41 00 09:26:17.453 READ FPDMA QUEUED
27 00 00 00 00 00 e0 00 09:26:17.427 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
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.
#
编辑5
我意识到拔掉电源后/dev/sdb，以前的/dev/sdc是现在的/dev/sdb。我确认smartctl -a /dev/sdb在拔掉坏盘后启动时序列号已经改变。我很不幸，驱动器是超出保修期，所以我将购买一个新的替换驱动器。
答案1
看到您在输出中没有看到损坏的驱动器（标记为 F）cat /proc/mdstat，因为阵列已降级，所以您已经启动了服务器。
您可以使用 获取信息mdadm --detail /dev/md0。这可能会告诉您其中应该包含哪个其他驱动器。
回应您的编辑：
我会/dev/sdb先进行分析。使用smartctl -a检查（特别是）重新分配的扇区数和错误日志。使用 进行自检smartctl -t long /dev/sdb。使用badblocks等。
然后：
- 如果替换
/dev/sdb，请从 复制分区表/dev/sdc。如果它们不是 GPT，您可以使用sfdisk -d /dev/sdc | sfdisk /dev/sdb。或者，如果它们是 GPT，您可以使用gdisk将分区表保存到文件，然后加载它。它隐藏在高级功能下。 - 需要考虑的一般事项：如果你的（新）驱动器有 4k 扇区，请确保分区4k 对齐。
- 如果您要重新添加现有的
/dev/sdb，您可能需要mdadm --zero-superblock在所有现有分区上运行。 - 然后你可以
mdadm --manage /dev/md0 --add /dev/sdb6和同样的md1事情sdb7
不用说，如果你混淆了驱动器，某些命令会清除你的数据。所以，一定要确定什么sdc是sdb...
编辑：关于坏块：如果任何软件级工具发现坏块，则表示驱动器已损坏。通常，磁盘通过在写入时透明地重新分配它们来隐藏它们。谷歌搜索“硬盘驱动器扇区重新分配”。您的smartctl -a输出应显示重新分配的扇区sdb。所以是的，您的sdb已被踢出阵列，您需要替换它。
编辑：关于smartctl -a输出。其中有两件事至关重要：
- 它显示有 60 个重新分配的扇区。尽管标准值仍为 99，并且只有当它达到 36（倒计时）时才会正式成为“坏的”，但您不应该信任开始重新分配扇区的磁盘。因此，特别是当这个值开始改变时，原始值就很重要了。您甚至可以配置
smartd来为您监控它。 - 错误日志显示 42372 小时后的条目。您可以判断这是最近的，因为参数 9（在您的例子中），。
Power on hours有些无害的事情可能会导致 SMART 错误日志条目，例如给出错误的 ATA 命令，但在这种情况下，由于您的阵列已降级，因此它们可能是相关的。
至于确定系统中的哪个磁盘；例如，执行dmesg |grep -i sdb会有所帮助。您的系统中可能有三个磁盘，并且sdb是第二个 SATA 控制器上的磁盘，可以命名为 1 或 2，具体取决于它是从零开始还是从一开始。
因为您可能从 启动sda，所以您只需替换sdb并执行我上面概述的操作即可。如果您的启动驱动器损坏，您希望您有：
- 在其他磁盘上也安装了 grub。
- 拥有一个实际上可以从另一个磁盘启动的服务器。
sdb前几天，我使用戴尔服务器时，发现当其中有空白时，它不愿意从那里启动sda。这需要一些说服和改进。
有时您需要将名称转换ata1.01为真实设备名称。例如，故障磁盘将给出内核错误，提示“ATA 异常出现在 ata1.01”或类似内容。阅读这个答案为此。（我配置了我们的中央日志系统来警告我这些内核错误，因为它们是即将发生磁盘故障的可靠指示）。