search for: bios_boot

...protective > BSD: not present > APM: not present > GPT: present > > Found valid GPT with protective MBR; using GPT. > Disk /dev/vdc: ... > ... > Number Start (sector) End (sector) Size Code Name > 1 2048 6143 2.0 MiB EF02 BIOS_Boot > 2 411648 1435647 500.0 MiB 8300 GPT_Boot > 3 1435648 22646783 10.1 GiB 8300 GPT_Root > 4 22646784 25163775 1.2 GiB 8200 GPT_Swap > > > boot: chain label=GPT_Boot > OK > > ~~~~~~~~~~~~~~~~~~~~~~~~~~...

The idea is to boot a disk in an mbr fashion while using the GPT (not filesystem) label to detect the disk. That is useful when you use grub2 & gpt. I was in case where my nodes (100s) have 8 disks each and no guarantee of which disk is "bootable" in the disk. This way I can tell "please boot the disk that have one partition labelled "xyz"". So nothing related

...-l /dev/vdc ... Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk /dev/vdc: ... ... Number Start (sector) End (sector) Size Code Name 1 2048 6143 2.0 MiB EF02 BIOS_Boot 2 411648 1435647 500.0 MiB 8300 GPT_Boot 3 1435648 22646783 10.1 GiB 8300 GPT_Root 4 22646784 25163775 1.2 GiB 8200 GPT_Swap boot: chain label=GPT_Boot OK ~~~~~~~~~~~~~~~~~~~~~~~~~~ As opposed to "label", "d...

...ent >> APM: not present >> GPT: present >> >> Found valid GPT with protective MBR; using GPT. >> Disk /dev/vdc: ... >> ... >> Number Start (sector) End (sector) Size Code Name >> 1 2048 6143 2.0 MiB EF02 BIOS_Boot >> 2 411648 1435647 500.0 MiB 8300 GPT_Boot >> 3 1435648 22646783 10.1 GiB 8300 GPT_Root >> 4 22646784 25163775 1.2 GiB 8200 GPT_Swap >> >> >> boot: chain label=GPT_Boot >> OK >>...

On 01/24/17 19:00, Gordon Messmer wrote: > On 01/24/2017 02:14 PM, m.roth at 5-cent.us wrote: >> So, it installed happily. >> Then wouldn't boot. > > What did the storage configuration look like, exactly? I'd guess that you put > one partition on each disk, combined those in a RAID1 MD array, made than an > LVM physical volume, and then created filesystems and

...protective > BSD: not present > APM: not present > GPT: present > > Found valid GPT with protective MBR; using GPT. > Disk /dev/vdc: ... > ... > Number Start (sector) End (sector) Size Code Name > 1 2048 6143 2.0 MiB EF02 BIOS_Boot > 2 411648 1435647 500.0 MiB 8300 GPT_Boot > 3 1435648 22646783 10.1 GiB 8300 GPT_Root > 4 22646784 25163775 1.2 GiB 8200 GPT_Swap > > > > # gdisk -l /dev/vdd > ... > Partition table scan: >...

Hi all! I'm still on C6. I'm using a RAID1 configuration (Linux software RAID) and I'd like to either use the same one, or possibly configure it on new drives (larger) when I upgrade to C7. (I'm really feeling the need to move off C6.) But it isn't at all obvious how one would do a new RAID1 setup in Anaconda, and I don't find any user reports or other info on this in the

...MBR with no partitions. I > can, however, mount /dev/md127p3 as /mnt/sysimage, and all is there. I assume you're booting with BIOS, then? One explanation for fdisk showing nothing is that you're using GPT instead of MBR (I think). In order to boot on such a system, you'd need a bios_boot partition at the beginning of the RAID volume to provide enough room for grub2 not to stomp on the first partition with a filesystem. The other explanation that comes to mind is that you're using an mdadm metadata version stored at the beginning of the drive instead of the end. Do you know...

...ent >> APM: not present >> GPT: present >> >> Found valid GPT with protective MBR; using GPT. >> Disk /dev/vdc: ... >> ... >> Number Start (sector) End (sector) Size Code Name >> 1 2048 6143 2.0 MiB EF02 BIOS_Boot >> 2 411648 1435647 500.0 MiB 8300 GPT_Boot >> 3 1435648 22646783 10.1 GiB 8300 GPT_Root >> 4 22646784 25163775 1.2 GiB 8200 GPT_Swap >> >> >> >> # gdisk -l /dev/vdd >> ... >&...