On 1/11/19 3:22 AM, Gary Stainburn wrote:
I then installed grub2 on sdb
yum install yum install grub2-efi-modules
grub2-install /dev/sdb
If you want to manually provide redundant EFI system partitions (no
RAID1), all you need to do is run efibootmgr to add a second entry. You
don't need
On Friday 11 January 2019 15:16:12 Simon Matter via CentOS wrote:
> If you boot, istn't there a way to get into an EFI boot menu where you can
> see the different EFI boot entries? Maybe you can see there what is wrong
> now.
>
> On the other hand, maybe you could even reinstall and try to
> I completed the install as described below which went well.
>
> I then copied the contents of /boot/efi to /boot/efi_copy using
>
> cd /boot
> rsync -acr efi/ efi_copy
>
> I then installed grub2 on sdb
>
> yum install yum install grub2-efi-modules
> grub2-install /dev/sdb
>
> everything ran as
I completed the install as described below which went well.
I then copied the contents of /boot/efi to /boot/efi_copy using
cd /boot
rsync -acr efi/ efi_copy
I then installed grub2 on sdb
yum install yum install grub2-efi-modules
grub2-install /dev/sdb
everything ran as expected with no
On 1/10/19 10:20 AM, Simon Matter via CentOS wrote:
RAID1 is going to have type FD00 (Linux RAID) whereas EFI firmware
expects type EF00 (EFI System Partition) to boot from.
I think you're referring to MBR partition types. I'm not certain, but I
don't see those values in a GPT.
No, it's GPT.
> It doesn't specifically. Anaconda will create two EFI boot entries,
> each referring to one of the mirror components:
>
> # efibootmgr -v
> BootCurrent: 0001
> Timeout: 1 seconds
> BootOrder: 0001,
> Boot* CentOS Linux
>
On 1/10/19 8:35 AM, Simon Matter via CentOS wrote:
Are you sure?
Yes.
How is the EFI firmware going to know about the RAID1?
It doesn't specifically. Anaconda will create two EFI boot entries,
each referring to one of the mirror components:
# efibootmgr -v
BootCurrent: 0001
Timeout:
On Thu, 10 Jan 2019 at 11:35, Simon Matter via CentOS
wrote:
> > On 1/9/19 2:30 AM, Gary Stainburn wrote:
> >> 1) The big problem with this is that it is dependant on sda for booting.
> >> I
> >> did find an aritcle on how to set up boot loading on multiple HDD's,
> >> including cloning
> On 1/9/19 2:30 AM, Gary Stainburn wrote:
>> 1) The big problem with this is that it is dependant on sda for booting.
>> I
>> did find an aritcle on how to set up boot loading on multiple HDD's,
>> including cloning /boot/efi but I now can't find it. Does anyone know
>> of a
>> similar article?
On 2019-01-09, Gordon Messmer wrote:
> On 1/9/19 2:30 AM, Gary Stainburn wrote:
>
>> 2) is putting SWAP in a RAID a good idea? Will it help, will it cause
>> problems?
>
> The only "drawback" that I'm aware of is that RAID consistency checks
> become meaningless, because it's common for swap
On 1/9/19 2:30 AM, Gary Stainburn wrote:
1) The big problem with this is that it is dependant on sda for booting. I
did find an aritcle on how to set up boot loading on multiple HDD's,
including cloning /boot/efi but I now can't find it. Does anyone know of a
similar article?
Use RAID1 for
> I've just finished installing a new Bacula storeage server. Prior to doing
> the
> install I did some research and ended up deciding to do the following
> config.
>
> 6x4TB drives
> /boot/efi efi_fs sda1
> /boot/efi_copyefi_fs sdb1
> /boot xfs
I've just finished installing a new Bacula storeage server. Prior to doing the
install I did some research and ended up deciding to do the following
config.
6x4TB drives
/boot/efi efi_fs sda1
/boot/efi_copy efi_fs sdb1
/boot xfs RAID1 sda2 sdb2
VG
13 matches
Mail list logo
