Grub - Debian 7.1 및 Software Raid1이 설치된 서버에서 두 디스크가 모두 부팅됩니까?

Grub - Debian 7.1 및 Software Raid1이 설치된 서버에서 두 디스크가 모두 부팅됩니까?

내 raid1 소프트웨어(Debian 7.1 운영 체제가 설치된 ovh 전용 서버)의 두 디스크 중 하나에 문제가 있습니다. 며칠 내로 교체될 예정입니다. 내 질문은 Grub을 사용하여 두 개의 디스크가 부팅 가능한지 확인하는 방법입니다. mdadm을 통해 raid1 소프트웨어를 재구축한 후 서버가 정상적으로 시작되는지 알고 싶습니다.

몇 가지 정보를 추가할 수 있습니다.

1) BIOS는 있지만 Uefi는 없습니다.

2) 이것은 grub 구성 파일 "grub.cfg"의 텍스트입니다.

if [ -s $prefix/grubenv ]; then   
load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then

set saved_entry="${prev_saved_entry}"

save_env saved_entry

set prev_saved_entry=

save_env prev_saved_entry

set boot_once=true

fi

function savedefault {

if [ -z "${boot_once}" ]; then

saved_entry="${chosen}"

save_env saved_entry

fi

}

function load_video {

insmod vbe

insmod vga

insmod video_bochs

insmod video_cirrus

}

insmod raid

insmod mdraid09

insmod part_gpt

insmod part_gpt

insmod ext2

set root='(mduuid/9bad0377260a5b69a4d2adc226fd5302)'

search --no-floppy --fs-uuid --set=root adcd0e04-e6ee-4a7d-abd2-a8880e6ba90d

if loadfont /usr/share/grub/unicode.pf2 ; then

set gfxmode=640x480

load_video

insmod gfxterm

insmod raid

insmod mdraid09

insmod part_gpt

insmod part_gpt

insmod ext2

set root='(mduuid/9bad0377260a5b69a4d2adc226fd5302)'

search --no-floppy --fs-uuid --set=root adcd0e04-e6ee-4a7d-abd2-a8880e6ba90d

set locale_dir=($root)/boot/grub/locale

set lang=

insmod gettext

fi

terminal_output gfxterm

set timeout=5

set menu_color_normal=cyan/blue

set menu_color_highlight=white/blue

menuentry "Debian GNU/Linux, OVH kernel 3.8.13-xxxx-grs-ipv6-64" {

insmod raid

insmod mdraid09

insmod part_gpt

insmod part_gpt

insmod ext2

set root='(mduuid/9bad0377260a5b69a4d2adc226fd5302)'

search --no-floppy --fs-uuid --set=root adcd0e04-e6ee-4a7d-abd2-a8880e6ba90d

linux /boot/bzImage-3.8.13-xxxx-grs-ipv6-64 root=/dev/md2 ro quiet

}

if [ -f $prefix/custom.cfg ]; then

source $prefix/custom.cfg;

fi

3) 다운로드한 스크립트(bootscriptinfo)를 실행하여 다음과 같은 결과를 얻었습니다.

============================= Boot Info Summary: ===============================
=> No boot loader is installed in the MBR of /dev/sda.
 => No boot loader is installed in the MBR of /dev/sdb.


sda1: __________________________________________________________________________

    File system:       BIOS Boot partition
    Boot sector type:  -
    Boot sector info: 

sda2: __________________________________________________________________________

    File system:       linux_raid_member
    Boot sector type:  -
    Boot sector info: 

sda3: __________________________________________________________________________

    File system:       linux_raid_member
    Boot sector type:  -
    Boot sector info: 

sda4: __________________________________________________________________________

    File system:       swap
    Boot sector type:  -
    Boot sector info: 

sdb1: __________________________________________________________________________

    File system:       BIOS Boot partition
    Boot sector type:  Grub2's core.img
    Boot sector info: 

sdb2: __________________________________________________________________________

    File system:       linux_raid_member
    Boot sector type:  -
    Boot sector info: 

sdb3: __________________________________________________________________________

    File system:       linux_raid_member
    Boot sector type:  -
    Boot sector info: 

sdb4: __________________________________________________________________________

    File system:       swap
    Boot sector type:  -
    Boot sector info: 

md3: ___________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info: 
    Operating System:  
    Boot files:        

md2: ___________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info: 
    Mounting failed:   mount: /dev/md2 already mounted or MDRaid/md2 busy

============================ Drive/Partition Info: =============================

Drive: sda _____________________________________________________________________

Disk /dev/sda: 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

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sda1                   1 3,907,029,167 3,907,029,167  ee GPT


GUID Partition Table detected.

Partition    Start Sector    End Sector  # of Sectors System
/dev/sda1              40         2,048         2,009 BIOS Boot partition
/dev/sda2           4,096   307,202,047   307,197,952 RAID partition (Linux)
/dev/sda3     307,202,048 3,845,582,847 3,538,380,800 RAID partition (Linux)
/dev/sda4   3,845,582,848 3,907,020,799    61,437,952 Swap partition (Linux)

Drive: sdb _____________________________________________________________________

Disk /dev/sdb: 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 / 4096 bytes

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sdb1                   1 3,907,029,167 3,907,029,167  ee GPT


GUID Partition Table detected.

Partition    Start Sector    End Sector  # of Sectors System
/dev/sdb1              40         2,048         2,009 BIOS Boot partition
/dev/sdb2           4,096   307,202,047   307,197,952 RAID partition (Linux)
/dev/sdb3     307,202,048 3,845,582,847 3,538,380,800 RAID partition (Linux)
/dev/sdb4   3,845,582,848 3,907,020,799    61,437,952 Swap partition (Linux)

"blkid" output: ________________________________________________________________

Device           UUID                                   TYPE       LABEL

/dev/md2         adcd0e04-e6ee-4a7d-abd2-a8880e6ba90d   ext4       
/dev/md3         adfbad7d-c8c3-4b04-884a-87d2d35e3a62   ext4       
/dev/sda2        9bad0377-260a-5b69-a4d2-adc226fd5302   linux_raid_member 
/dev/sda3        cca07bac-0ea8-99e8-a4d2-adc226fd5302   linux_raid_member 
/dev/sda4        05de1987-d6cb-4baa-87f8-3b008e05de8e   swap       
/dev/sdb2        9bad0377-260a-5b69-a4d2-adc226fd5302   linux_raid_member 
/dev/sdb3        cca07bac-0ea8-99e8-a4d2-adc226fd5302   linux_raid_member 
/dev/sdb4        7b1315b8-dcf4-4bd6-9379-ffbcf3014aa6   swap       


=============================== StdErr Messages: ===============================

  No volume groups found

4) group.cfg 파일을 확인하여 파티션 sda2 및 sdb2 앞과 md2 뒤(두 번째 줄) uuid로 식별된 두 줄을 주석 처리했습니다.

set root='(mduuid/9bad0377260a5b69a4d2adc226fd5302)'
search --no-floppy --fs-uuid --set=root adcd0e04-e6ee-4a7d-abd2-a8880e6ba90d

5) bootscriptinfo의 출력을 확인하여 두 가지 세부 사항을 발견했습니다.

첫 번째:

=> No boot loader is installed in the MBR of /dev/sda.
=> No boot loader is installed in the MBR of /dev/sdb.

두번째:

  The first parttion of both disks is dedicated to a Bios Boot Partition and only for sdb1 there is this value in Boot Sector type
    Boot sector type:  Grub2's core.img
Core.img is a file in the same folder of grub.cfg (\boot\grub). Why does it appear only in sdb1?

이 정보가 제 질문에 충분한 답변이 되었기를 바랍니다.

관련 정보