我希望有人能带我到这里来解决重建/同步问题。我有一个3 raid 5's构建在mdadm 4磁盘在每个md0 (活动,降级),md1 (活动,降级)和md2 (清洁) -no数据,所以我不在乎它。
所有12个驱动器都连接到LSI 9750-8i卡上。潜水都作为单一的“单位”附在这张卡片上。一个驱动器发生故障,显示为从LSI 3dm2接口中丢失。在Mdadm中,数组还将驱动器显示为“已删除”。
为了使事情进一步复杂化,第二个数组也显示为活动的,降级为潜水“删除”。
我已经关闭了系统,并用另一个新驱动器替换了故障的3TB驱动器。因为我知道在故障之前存在哪些驱动器,所以我知道哪两个驱动器不再是数组的一部分。从其中一个阵列中跳出来的驱动器。sd0 =已安装的新物理驱动器。超级块是持久的。
问题1。我可以查询潜水的序列号,但我似乎找不出sdh最初是哪个数组的一部分,希望能把它添加回正确的数组中。
问题2.根据sdf所属的不同,将sdo添加到md'x‘数组中。
在LSI 3dm2内报告了一些物理驱动器错误,但是在重新扫描这些驱动器之后,这些错误消失了,并且在这个级别上的所有驱动器现在都报告“OK”。然而,这可能是sdf最初“退出”数组的问题之一吗?
我假设Sdo,我必须使用gpart来格式化3TB驱动器,然后将它添加到其他数组中?我有备份这是生产NAS。我不想黑它是一个错误,导致重建.
如果有人能就如何去做提出一些建议,那就太好了!提亚
来自cat /proc
[root@pithos dev]# cat /proc/mdstat Personalities : [raid6] [raid5 [raid4]
md0 : active raid5 sdc1[0] sdd1[4] sde1[2]
8789025216 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/3] [U_UU]
md1 : active raid5 sdf1[0] sdi1[4] sdg1[1]
8789025216 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/3] [UU_U]
md2 : active raid5 sdj1[0] sdm1[4] sdl1[2] sdk1[1]
8789025216 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
unused devices: <none>Md0
[root@pithos dev]# mdadm --detail /dev/md0
/dev/md0:
Version : 1.2
Creation Time : Fri May 31 10:46:54 2013
Raid Level : raid5
Array Size : 8789025216 (8381.87 GiB 8999.96 GB)
Used Dev Size : 2929675072 (2793.96 GiB 2999.99 GB)
Raid Devices : 4
Total Devices : 3
Persistence : Superblock is persistent
Update Time : Fri Jul 8 18:07:27 2016
State : active, degraded
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 64K
Name : pithos.dougallmedia.com:0 (local to host pithos.dougallmedia.com)
UUID : f1e42a86:7fc791f8:7cf63ab8:065ffa92
Events : 3543
Number Major Minor RaidDevice State
0 8 33 0 active sync /dev/sdc1
1 0 0 1 removed
2 8 65 2 active sync /dev/sde1
4 8 49 3 active sync /dev/sdd1Md1
[root@pithos dev]# mdadm -D /dev/md1
/dev/md1:
Version : 1.2
Creation Time : Fri May 31 17:44:49 2013
Raid Level : raid5
Array Size : 8789025216 (8381.87 GiB 8999.96 GB)
Used Dev Size : 2929675072 (2793.96 GiB 2999.99 GB)
Raid Devices : 4
Total Devices : 3
Persistence : Superblock is persistent
Update Time : Tue Jul 12 11:31:52 2016
State : clean, degraded
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 64K
Name : pithos.dougallmedia.com:1 (local to host pithos.dougallmedia.com)
UUID : 58ba8949:bed7be0b:ba4dcc3e:8e6bc5e2
Events : 9779
Number Major Minor RaidDevice State
0 8 81 0 active sync /dev/sdf1
1 8 97 1 active sync /dev/sdg1
2 0 0 2 removed
4 8 129 3 active sync /dev/sdi1
[root@pithos dev]# mdadm --assemble --scan -v
mdadm: looking for devices for /dev/md2
mdadm: Cannot assemble mbr metadata on /dev/sdo
mdadm: cannot open device /dev/dm-10: Device or resource busy
mdadm: cannot open device /dev/dm-9: Device or resource busy
mdadm: cannot open device /dev/dm-8: Device or resource busy
mdadm: cannot open device /dev/dm-7: Device or resource busy
mdadm: cannot open device /dev/dm-6: Device or resource busy
mdadm: cannot open device /dev/dm-5: Device or resource busy
mdadm: cannot open device /dev/md0: Device or resource busy
mdadm: cannot open device /dev/md1: Device or resource busy
mdadm: no recogniseable superblock on /dev/md2
mdadm: Cannot assemble mbr metadata on /dev/sdn
mdadm: cannot open device /dev/dm-4: Device or resource busy
mdadm: cannot open device /dev/dm-3: Device or resource busy
mdadm: cannot open device /dev/dm-2: Device or resource busy
mdadm: cannot open device /dev/dm-1: Device or resource busy
mdadm: cannot open device /dev/dm-0: Device or resource busy
mdadm: cannot open device /dev/sdk1: Device or resource busy
mdadm: cannot open device /dev/sdk: Device or resource busy
mdadm: cannot open device /dev/sdm1: Device or resource busy
mdadm: cannot open device /dev/sdm: Device or resource busy
mdadm: cannot open device /dev/sdl1: Device or resource busy
mdadm: cannot open device /dev/sdl: Device or resource busy
mdadm: cannot open device /dev/sdj1: Device or resource busy
mdadm: cannot open device /dev/sdj: Device or resource busy
mdadm: cannot open device /dev/sdg1: Device or resource busy
mdadm: cannot open device /dev/sdg: Device or resource busy
mdadm: cannot open device /dev/sdi1: Device or resource busy
mdadm: cannot open device /dev/sdi: Device or resource busy
mdadm: /dev/sdh1 has wrong uuid.
mdadm: Cannot assemble mbr metadata on /dev/sdh
mdadm: cannot open device /dev/sdd1: Device or resource busy
mdadm: cannot open device /dev/sdd: Device or resource busy
mdadm: cannot open device /dev/sde1: Device or resource busy
mdadm: cannot open device /dev/sde: Device or resource busy
mdadm: cannot open device /dev/sdf1: Device or resource busy
mdadm: cannot open device /dev/sdf: Device or resource busy
mdadm: cannot open device /dev/sdc1: Device or resource busy
mdadm: cannot open device /dev/sdc: Device or resource busy
mdadm: cannot open device /dev/sdb: Device or resource busy
mdadm: cannot open device /dev/sda: Device or resource busy
mdadm: looking for devices for /dev/md1
mdadm: Cannot assemble mbr metadata on /dev/sdo
mdadm: cannot open device /dev/dm-10: Device or resource busy
mdadm: cannot open device /dev/dm-9: Device or resource busy
mdadm: cannot open device /dev/dm-8: Device or resource busy
mdadm: cannot open device /dev/dm-7: Device or resource busy
mdadm: cannot open device /dev/dm-6: Device or resource busy
mdadm: cannot open device /dev/dm-5: Device or resource busy
mdadm: cannot open device /dev/md0: Device or resource busy
mdadm: cannot open device /dev/md1: Device or resource busy
mdadm: no recogniseable superblock on /dev/md2
mdadm: Cannot assemble mbr metadata on /dev/sdn
mdadm: cannot open device /dev/dm-4: Device or resource busy
mdadm: cannot open device /dev/dm-3: Device or resource busy
mdadm: cannot open device /dev/dm-2: Device or resource busy
mdadm: cannot open device /dev/dm-1: Device or resource busy
mdadm: cannot open device /dev/dm-0: Device or resource busy
mdadm: cannot open device /dev/sdk1: Device or resource busy
mdadm: cannot open device /dev/sdk: Device or resource busy
mdadm: cannot open device /dev/sdm1: Device or resource busy
mdadm: cannot open device /dev/sdm: Device or resource busy
mdadm: cannot open device /dev/sdl1: Device or resource busy
mdadm: cannot open device /dev/sdl: Device or resource busy
mdadm: cannot open device /dev/sdj1: Device or resource busy
mdadm: cannot open device /dev/sdj: Device or resource busy
mdadm: cannot open device /dev/sdg1: Device or resource busy
mdadm: cannot open device /dev/sdg: Device or resource busy
mdadm: cannot open device /dev/sdi1: Device or resource busy
mdadm: cannot open device /dev/sdi: Device or resource busy
mdadm: /dev/sdh1 has wrong uuid.
mdadm: Cannot assemble mbr metadata on /dev/sdh
mdadm: cannot open device /dev/sdd1: Device or resource busy
mdadm: cannot open device /dev/sdd: Device or resource busy
mdadm: cannot open device /dev/sde1: Device or resource busy
mdadm: cannot open device /dev/sde: Device or resource busy
mdadm: cannot open device /dev/sdf1: Device or resource busy
mdadm: cannot open device /dev/sdf: Device or resource busy
mdadm: cannot open device /dev/sdc1: Device or resource busy
mdadm: cannot open device /dev/sdc: Device or resource busy
mdadm: cannot open device /dev/sdb: Device or resource busy
mdadm: cannot open device /dev/sda: Device or resource busy
mdadm: looking for devices for /dev/md0
mdadm: Cannot assemble mbr metadata on /dev/sdo
mdadm: cannot open device /dev/dm-10: Device or resource busy
mdadm: cannot open device /dev/dm-9: Device or resource busy
mdadm: cannot open device /dev/dm-8: Device or resource busy
mdadm: cannot open device /dev/dm-7: Device or resource busy
mdadm: cannot open device /dev/dm-6: Device or resource busy
mdadm: cannot open device /dev/dm-5: Device or resource busy
mdadm: cannot open device /dev/md0: Device or resource busy
mdadm: cannot open device /dev/md1: Device or resource busy
mdadm: no recogniseable superblock on /dev/md2
mdadm: Cannot assemble mbr metadata on /dev/sdn
mdadm: cannot open device /dev/dm-4: Device or resource busy
mdadm: cannot open device /dev/dm-3: Device or resource busy
mdadm: cannot open device /dev/dm-2: Device or resource busy
mdadm: cannot open device /dev/dm-1: Device or resource busy
mdadm: cannot open device /dev/dm-0: Device or resource busy
mdadm: cannot open device /dev/sdk1: Device or resource busy
mdadm: cannot open device /dev/sdk: Device or resource busy
mdadm: cannot open device /dev/sdm1: Device or resource busy
mdadm: cannot open device /dev/sdm: Device or resource busy
mdadm: cannot open device /dev/sdl1: Device or resource busy
mdadm: cannot open device /dev/sdl: Device or resource busy
mdadm: cannot open device /dev/sdj1: Device or resource busy
mdadm: cannot open device /dev/sdj: Device or resource busy
mdadm: cannot open device /dev/sdg1: Device or resource busy
mdadm: cannot open device /dev/sdg: Device or resource busy
mdadm: cannot open device /dev/sdi1: Device or resource busy
mdadm: cannot open device /dev/sdi: Device or resource busy
mdadm: no recogniseable superblock on /dev/sdh1
mdadm: Cannot assemble mbr metadata on /dev/sdh
mdadm: cannot open device /dev/sdd1: Device or resource busy
mdadm: cannot open device /dev/sdd: Device or resource busy
mdadm: cannot open device /dev/sde1: Device or resource busy
mdadm: cannot open device /dev/sde: Device or resource busy
mdadm: cannot open device /dev/sdf1: Device or resource busy
mdadm: cannot open device /dev/sdf: Device or resource busy
mdadm: cannot open device /dev/sdc1: Device or resource busy
mdadm: cannot open device /dev/sdc: Device or resource busy
mdadm: cannot open device /dev/sdb: Device or resource busy
mdadm: cannot open device /dev/sda: Device or resource busy发布于 2016-07-15 14:16:22
问题1。我可以查询潜水的序列号,但我似乎找不出sdh最初是哪个数组的一部分,希望能把它添加回正确的数组中。
使用mdadm -E /dev/sdh1 (检查)。然后可以使用mdadm --re-add ...或--add。
另外,如果您的其他磁盘运行良好,即使它已经有数据,您也可以简单地重新构建这个磁盘。
如果这样做不起作用,您可能必须使用mdadm --create --assume-clean ...在旧数据的基础上创建一个新的数组,重用数据,这是危险的。确保保存详细信息(-D),并首先检查所有磁盘的输出。您必须显式地设置在检查或详细输出中看到的许多内容,如布局、级别、驱动器顺序、块大小等。要安全地使用--create,请确保使用覆盖层进行良好测试,而不是冒着数据风险。使用--assume-clean意味着它将保留您的旧数据。
问题2.根据sdf所属的不同,将sdo添加到md'x‘数组中。
您可以在使用mdadm -E知道要将其添加到哪个数组之后执行此步骤,即使没有完成覆盖,它也只是mdadm --add /dev/md0 /dev/sdo
此外,我还建议您经常在磁盘上运行智能长测试,这样您就可以在磁盘引发raid问题之前替换磁盘。(还有希捷梭鱼3TB磁盘是非常不可靠.我猜这就是你所拥有的,这不是mdadm的错;添加智能测试也有助于解决这些类型的问题。)
我建议您访问irc.freenode.net #linux,以获得解决此类问题的最佳实时帮助。
https://unix.stackexchange.com/questions/295481
复制相似问题