Мой рейд-контроллер вышел из строя, и мой хостер OVH заменил его. Они предлагают только поддержку оборудования, поэтому после замены контроллера они оставили машину в режиме восстановления. Когда я перевожу его в обычный режим загрузки HD, он не загружается.
У меня было программное обеспечение RAID1 с двумя дисками, на котором размещались файлы CentOS.
И у меня было программное обеспечение RAID10 с 4 дисками, на котором были мои файлы.
В режиме восстановления я проверил массив с помощью:
cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath] [faulty]
unused devices: <none>
и fdisk показывает:
root@rescue:/mnt# fdisk -l
Disk /dev/ram0: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram1: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram2: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram3: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram4: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram5: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram6: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram7: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram8: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram9: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram10: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram11: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram12: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram13: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram14: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram15: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/sda: 447.1 GiB, 480103981056 bytes, 937703088 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 7D555295-0B10-4D4B-9A17-6EEFBBA3CB99
Device Start End Sectors Size Type
/dev/sda1 2048 1048575 1046528 511M EFI System
/dev/sda2 1048576 42006527 40957952 19.5G Linux RAID
/dev/sda3 42006528 936644607 894638080 426.6G Linux RAID
/dev/sda4 936644608 937691135 1046528 511M Linux swap
Disk /dev/sdb: 447.1 GiB, 480103981056 bytes, 937703088 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 63C7B674-C42F-4F25-A610-F72AFACD5134
Device Start End Sectors Size Type
/dev/sdb1 2048 1048575 1046528 511M EFI System
/dev/sdb2 1048576 42006527 40957952 19.5G Linux RAID
/dev/sdb3 42006528 936644607 894638080 426.6G Linux RAID
/dev/sdb4 936644608 937691135 1046528 511M Linux swap
Disk /dev/sde: 10.9 TiB, 12000138625024 bytes, 23437770752 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 6FDD3C33-DE0C-4DF0-9554-677826FC34F6
Device Start End Sectors Size Type
/dev/sde1 2048 23437770718 23437768671 10.9T Linux RAID
Disk /dev/sdf: 10.9 TiB, 12000138625024 bytes, 23437770752 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 433686A7-5E89-4AE4-8BF8-3AAC9E9BDD82
Device Start End Sectors Size Type
/dev/sdf1 2048 23437770718 23437768671 10.9T Linux RAID
Disk /dev/sdd: 10.9 TiB, 12000138625024 bytes, 23437770752 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 638E004E-798E-4C77-BEFD-5FF5AADEA855
Device Start End Sectors Size Type
/dev/sdd1 2048 23437770718 23437768671 10.9T Linux RAID
Disk /dev/sdc: 10.9 TiB, 12000138625024 bytes, 23437770752 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 42B1E5D7-697E-4BD5-8B9B-86B664022E25
Device Start End Sectors Size Type
/dev/sdc1 2048 23437770718 23437768671 10.9T Linux RAID
Все диски целы, поэтому все файлы остались. Но просто настройки рейда больше нет. Как я могу воссоздать мои настройки RAID1 и RAID10, чтобы снова загрузиться в CentOS?
Мой хостер предлагает 0 поддержки, OVH действительно ужасен.
Должен ли я просто использовать mdadm для создания нового массива? Боюсь, что что-то сломаю. Я видел несколько предупреждений, поэтому не нажимал продолжить:
root@rescue:/mnt# mdadm --create /dev/md127 --level raid10 --name data --raid-disks 4 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1
mdadm: /dev/sdc1 appears to be part of a raid array:
level=raid10 devices=4 ctime=Mon Oct 7 12:02:49 2019
mdadm: partition table exists on /dev/sdc1 but will be lost or
meaningless after creating array
mdadm: /dev/sdd1 appears to be part of a raid array:
level=raid10 devices=4 ctime=Mon Oct 7 12:02:49 2019
mdadm: partition table exists on /dev/sdd1 but will be lost or
meaningless after creating array
mdadm: /dev/sde1 appears to be part of a raid array:
level=raid10 devices=4 ctime=Mon Oct 7 12:02:49 2019
mdadm: partition table exists on /dev/sde1 but will be lost or
meaningless after creating array
mdadm: /dev/sdf1 appears to be part of a raid array:
level=raid10 devices=4 ctime=Mon Oct 7 12:02:49 2019
mdadm: partition table exists on /dev/sdf1 but will be lost or
meaningless after creating array
Continue creating array?