누군가가 재구축/동기화 문제를 안내해 줄 수 있기를 바랍니다. mdadm 4 디스크에 raid 5 3개를 구축했는데, md0(활성, 저하), md1(활성, 저하), md2(클린) 각각에 데이터가 없어서 신경쓰지 않습니다.
12개 드라이브는 모두 LSI 9750-8i 카드에 연결되어 있습니다. 모든 다이빙은 단일 "단위"로 이 카드에 연결됩니다. 드라이브 하나에 오류가 발생하고 LSI 3dm2 인터페이스가 누락된 것으로 나타났습니다. 또한 어레이는 Mdadm에서 드라이브를 "삭제됨"으로 표시합니다.
문제를 더욱 복잡하게 만드는 것은 두 번째 어레이도 활성화되어 다이빙 "제거"로 인해 다운그레이드된 것으로 보입니다.
시스템을 종료하고 고장난 3TB 드라이브를 다른 새 드라이브로 교체했습니다. 장애가 발생하기 전에 어떤 드라이브가 존재했는지 알고 있으므로 어떤 드라이브가 더 이상 어레이의 일부가 아닌지 알 수 있습니다. sdh = 어레이 중 하나에서 튀어나온 드라이브입니다. sd0 = 새 물리적 드라이브가 마운트되었습니다. 슈퍼 블록은 지속적입니다.
질문 1. 서브의 일련 번호를 쿼리할 수 있지만 sdh가 원래 어떤 배열에 속해 있었는지 알 수 없는 것 같습니다. 올바른 배열에 다시 추가할 수 있기를 바랍니다.
질문 #2. sdf가 속한 항목에 따라 sdo를 md'x' 배열에 추가합니다.
LSI 3dm2에 일부 물리적 드라이브 오류가 보고되었지만 다시 검색한 후에는 이러한 오류가 사라지고 이 수준의 모든 드라이브는 이제 "정상"을 보고합니다. 그러나 이것이 처음에 배열에서 "떨어지는" sdf 문제의 일부일 수 있습니까?
제 생각에는 gpart를 사용하여 3TB 드라이브를 포맷한 다음 다른 어레이에 추가해야 합니까? 프로덕션 NAS의 백업이 있습니다. 실수로 재건축을 일으키고 싶지는 않은데...
누구든지 이에 대한 방법에 대해 조언을 해줄 수 있다면 좋을 것입니다! 티아
고양이/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>
보통의
[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/sdd1
MD1
[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
답변1
질문 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 문제가 발생하기 전에 디스크를 교체할 수 있도록 디스크에 대해 스마트 장기 테스트를 자주 실행하는 것이 좋습니다. (Seagate Barracuda 3TB 디스크도매우 신뢰할 수 없음...내 생각에는 이것이 당신이 가지고 있는 것이고 mdadm의 잘못이 아닌 것 같습니다. 스마트 테스트를 추가하면 이러한 유형의 문제에도 도움이 될 것입니다. )
이런 종류의 문제에 대한 최고의 실시간 도움을 받으려면 irc.freenode.net #linux-raid를 방문하는 것이 좋습니다.