Apesar de ser capaz de fazer isso funcionar, não posso administrar desta vez.
Eu tenho um único array de raids de disco:
$ sudo mdadm --examine --verbose /dev/sdc**
/dev/sdc:
MBR Magic : aa55
Partition[0] : 4980087 sectors at 63 (type fd)
Partition[1] : 1044225 sectors at 4980150 (type fd)
Partition[2] : 3900742650 sectors at 6281415 (type fd)
$ sudo mdadm --examine --verbose /dev/sdc3
/dev/sdc3:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : a13d34aa:32872fcf:9675f885:aa092f93
Name : MJ2CubeStation:3
Creation Time : Sun Dec 18 22:22:56 2016
Raid Level : raid1
Raid Devices : 1
Avail Dev Size : 3900740602 (1860.02 GiB 1997.18 GB)
Array Size : 1950370112 (1860.02 GiB 1997.18 GB)
Used Dev Size : 3900740224 (1860.02 GiB 1997.18 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 9435f6c2:42b4dd1c:69fddf4a:a7358539
Update Time : Mon Mar 13 17:21:09 2017
Checksum : 5494bd40 - correct
Events : 18
Device Role : Active device 32768
Array State : . ('A' == active, '.' == missing)
$ more /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md127 : inactive sdc3[0](S)
1950370301 blocks super 1.2
unused devices: none
PERGUNTA: Alguma idéia de como começar o array começou e montou?
Para tentar montar o array, fiz o seguinte:
Primeiro parei o array md127:
$ sudo mdadm --stop /dev/md127 --verbose**
mdadm: stopped /dev/md127
Então eu executei o fdisk:
$ sudo fdisk -l /dev/sdc
Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xd48b0300
Device Boot Start End Blocks Id System
/dev/sdc1 63 4980149 2490043+ fd Linux RAID autodetect
/dev/sdc2 4980150 6024374 522112+ fd Linux RAID autodetect
/dev/sdc3 6281415 3907024064 1950371325 fd Linux RAID autodetect
Então eu executei o mdadm em / dev / sdc:
$ sudo mdadm --examine --verbose /dev/sdc
/dev/sdc:
MBR Magic : aa55
Partition[0] : 4980087 sectors at 63 (type fd)
Partition[1] : 1044225 sectors at 4980150 (type fd)
Partition[2] : 3900742650 sectors at 6281415 (type fd)
Eu então tentei montar o array:
$ sudo mdadm --assemble --verbose /dev/md127 /dev/sdc3
mdadm: looking for devices for /dev/md127
mdadm: /dev/sdc3 is identified as a member of /dev/md127, slot 32768.
mdadm: No suitable drives found for /dev/md127
PERGUNTA: Alguma idéia de porque eu recebo o erro "Nenhuma unidade apropriada encontrada para / dev / md127"?
Estou nervoso sobre a tentativa de usar as opções build ou assume-clean para o mdadm, até que fique claro porque recebo o erro acima para montar. Qualquer entrada seria muito bem vinda.
Eu também executei o sudo sgdisk --print /dev/sdc
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory.
***************************************************************
Disk /dev/sdc: 3907029168 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 8A621939-773C-44BB-952C-0705618461DF
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 8-sector boundaries
Total free space is 262139 sectors (128.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 63 4980149 2.4 GiB FD00 Linux RAID
2 4980150 6024374 509.9 MiB FD00 Linux RAID
3 6281415 3907024064 1.8 TiB FD00 Linux RAID
PERGUNTA: O GPT inválido é um motivo para os problemas? Devo tentar corrigir isso com o gdisk?