I noticed that there was a grub2 update.
From prior experience I know that one needs to manually run grub2-install to actually update the bootloader. Additionally I run mdraid, so I need the bootloader on both /dev/sda and /dev/sdb.
But:
[root@jack ~]# grub2-install /dev/sda grub2-install: error: /usr/lib/grub/x86_64-efi/modinfo.sh doesn't exist. Please specify --target or --directory.
Searching for "modinfo.sh", I find it in:
[root@jack ~]# locate modinfo.sh /usr/lib/grub/i386-pc/modinfo.sh
Which is installed by:
[root@jack ~]# rpm -q -f /usr/lib/grub/i386-pc/modinfo.sh grub2-pc-modules-2.06-118.fc39.noarch
A noarch package. Doesn't sound right.
After search poking, I see that there's a grub2-efi-x64-modules package package that I can install. So, I did, then:
[root@jack ~]# grub2-install /dev/sda Installing for x86_64-efi platform. grub2-install: error: This utility should not be used for EFI platforms because it does not support UEFI Secure Boot. If you really wish to proceed, invoke the --force option. Make sure Secure Boot is disabled before proceeding.
So, what now?
On 3/19/24 16:05, Sam Varshavchik wrote:
I noticed that there was a grub2 update.
From prior experience I know that one needs to manually run grub2-install to actually update the bootloader. Additionally I run mdraid, so I need the bootloader on both /dev/sda and /dev/sdb.
[root@jack ~]# grub2-install /dev/sda Installing for x86_64-efi platform. grub2-install: error: This utility should not be used for EFI platforms because it does not support UEFI Secure Boot. If you really wish to proceed, invoke the --force option. Make sure Secure Boot is disabled before proceeding.
If you have an EFI system, you normally don't do anything. Is the EFI partition part of the RAID?
Samuel Sieb writes:
On 3/19/24 16:05, Sam Varshavchik wrote:
I noticed that there was a grub2 update.
From prior experience I know that one needs to manually run grub2-install to actually update the bootloader. Additionally I run mdraid, so I need the bootloader on both /dev/sda and /dev/sdb.
[root@jack ~]# grub2-install /dev/sda Installing for x86_64-efi platform. grub2-install: error: This utility should not be used for EFI platforms because it does not support UEFI Secure Boot. If you really wish to proceed, invoke the --force option. Make sure Secure Boot is disabled before proceeding.
If you have an EFI system, you normally don't do anything. Is the EFI partition part of the RAID?
Yes, /boot/efi is a RAID partition.
/dev/md123 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=winnt,errors=remount- ro)
Which is /dev/sda4 and /dev/sdb4
Both the bootloader and /boot/efi is raided across two disks, so if one fails the other one can still be used to boot. This actually happened on another system with me, last year. I just popped out the failed HD, popped in another one, booted off the functional drive, and reassembled all the raid partitions.
On 3/19/24 16:50, Sam Varshavchik wrote:
Samuel Sieb writes:
On 3/19/24 16:05, Sam Varshavchik wrote:
I noticed that there was a grub2 update.
From prior experience I know that one needs to manually run grub2-install to actually update the bootloader. Additionally I run mdraid, so I need the bootloader on both /dev/sda and /dev/sdb.
[root@jack ~]# grub2-install /dev/sda Installing for x86_64-efi platform. grub2-install: error: This utility should not be used for EFI platforms because it does not support UEFI Secure Boot. If you really wish to proceed, invoke the --force option. Make sure Secure Boot is disabled before proceeding.
If you have an EFI system, you normally don't do anything. Is the EFI partition part of the RAID?
Yes, /boot/efi is a RAID partition.
/dev/md123 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=winnt,errors=remount-ro)
Which is /dev/sda4 and /dev/sdb4
Both the bootloader and /boot/efi is raided across two disks, so if one fails the other one can still be used to boot. This actually happened on another system with me, last year. I just popped out the failed HD, popped in another one, booted off the functional drive, and reassembled all the raid partitions.
Then there's nothing you need to do. grub has been updated.
But what do you mean by the "bootloader" though?
Samuel Sieb writes:
On 3/19/24 16:50, Sam Varshavchik wrote:
Samuel Sieb writes:
On 3/19/24 16:05, Sam Varshavchik wrote:
I noticed that there was a grub2 update.
From prior experience I know that one needs to manually run grub2-install to actually update the bootloader. Additionally I run mdraid, so I need the bootloader on both /dev/sda and /dev/sdb.
[root@jack ~]# grub2-install /dev/sda Installing for x86_64-efi platform. grub2-install: error: This utility should not be used for EFI platforms because it does not support UEFI Secure Boot. If you really wish to proceed, invoke the --force option. Make sure Secure Boot is disabled before proceeding.
If you have an EFI system, you normally don't do anything. Is the EFI partition part of the RAID?
Yes, /boot/efi is a RAID partition.
/dev/md123 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=winnt,errors=remount- ro)
Which is /dev/sda4 and /dev/sdb4
Both the bootloader and /boot/efi is raided across two disks, so if one fails the other one can still be used to boot. This actually happened on another system with me, last year. I just popped out the failed HD, popped in another one, booted off the functional drive, and reassembled all the raid partitions.
Then there's nothing you need to do. grub has been updated.
But what do you mean by the "bootloader" though?
Well, what actually loads grub and runs it. On my other, BIOS system, the one that I replaced a failed disk, recently – after I reassembled and resynced all RAID partitions, I ran grub2-install and I'm fairly certain there was a definitive change in grub's behavior, afterwards. Originally three periods were initially shown, for a few seconds, before the grub menu opened. I have a recollection that the number of periods is a diagnostic indications what went wrong if grub fails to start for some reason. This changed to a "Welcome to grub" banner.
So, it looks to me like years of regular grub updates, and countless Fedora releases, did not really end up updating …everything, on a BIOS system.
On Tue, 19 Mar 2024 19:05:51 -0400 Sam Varshavchik wrote:
[root@jack ~]# grub2-install /dev/sda
That is the way you install grub for old MSDOS partitions.
To install grub with GPT and use EFI, it needs different arguments. Something like:
grub2-install --target x86_64-efi --removable --boot-directory=/mnt/boot --efi-directory=/mnt
Though that's from my notes for making a bootable USB stick, so probably not all of those are needed for a hard disk. Read about the options in the grub2 info docs.
On 3/19/24 17:28, Sam Varshavchik wrote:
Samuel Sieb writes:
Then there's nothing you need to do. grub has been updated.
But what do you mean by the "bootloader" though?
Well, what actually loads grub and runs it. On my other, BIOS system, the one that I replaced a failed disk, recently – after I reassembled and resynced all RAID partitions, I ran grub2-install and I'm fairly certain there was a definitive change in grub's behavior, afterwards. Originally three periods were initially shown, for a few seconds, before the grub menu opened. I have a recollection that the number of periods is a diagnostic indications what went wrong if grub fails to start for some reason. This changed to a "Welcome to grub" banner.
So, it looks to me like years of regular grub updates, and countless Fedora releases, did not really end up updating …everything, on a BIOS system.
That's the difference between a BIOS (legacy) system and a UEFI system. On the legacy system, the bootloader is embedded in the boot sector and elsewhere and needs to be specially updated. On UEFI, the "BIOS" loads the grub executable from the EFI partition and runs it directly. So if you update that file, the new code is run on the next boot. And that file is managed by the package.
rpm -ql grub2-efi-x64
On 3/19/24 17:29, Tom Horsley wrote:
On Tue, 19 Mar 2024 19:05:51 -0400 Sam Varshavchik wrote:
[root@jack ~]# grub2-install /dev/sda
That is the way you install grub for old MSDOS partitions.
To install grub with GPT and use EFI, it needs different arguments. Something like:
grub2-install --target x86_64-efi --removable --boot-directory=/mnt/boot --efi-directory=/mnt
Though that's from my notes for making a bootable USB stick, so probably not all of those are needed for a hard disk. Read about the options in the grub2 info docs.
That's only if you're making some sort of bootable media. The installed system does not use grub2-install at all. See the other thread for details.
On 20/3/24 11:28, Sam Varshavchik wrote:
Samuel Sieb writes:
On 3/19/24 16:50, Sam Varshavchik wrote:
Samuel Sieb writes:
On 3/19/24 16:05, Sam Varshavchik wrote:
I noticed that there was a grub2 update.
From prior experience I know that one needs to manually run grub2-install to actually update the bootloader. Additionally I run mdraid, so I need the bootloader on both /dev/sda and /dev/sdb.
[root@jack ~]# grub2-install /dev/sda Installing for x86_64-efi platform. grub2-install: error: This utility should not be used for EFI platforms because it does not support UEFI Secure Boot. If you really wish to proceed, invoke the --force option. Make sure Secure Boot is disabled before proceeding.
If you have an EFI system, you normally don't do anything. Is the EFI partition part of the RAID?
Yes, /boot/efi is a RAID partition.
/dev/md123 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=winnt,errors=remount-ro)
Which is /dev/sda4 and /dev/sdb4
Both the bootloader and /boot/efi is raided across two disks, so if one fails the other one can still be used to boot. This actually happened on another system with me, last year. I just popped out the failed HD, popped in another one, booted off the functional drive, and reassembled all the raid partitions.
Then there's nothing you need to do. grub has been updated.
But what do you mean by the "bootloader" though?
Well, what actually loads grub and runs it. On my other, BIOS system, the one that I replaced a failed disk, recently – after I reassembled and resynced all RAID partitions, I ran grub2-install and I'm fairly certain there was a definitive change in grub's behavior, afterwards. Originally three periods were initially shown, for a few seconds, before the grub menu opened. I have a recollection that the number of periods is a diagnostic indications what went wrong if grub fails to start for some reason. This changed to a "Welcome to grub" banner.
So, it looks to me like years of regular grub updates, and countless Fedora releases, did not really end up updating …everything, on a BIOS system.
If I can ask a silly question, given that on UEFI systems grub2-install is redundant, and the initial messages you were getting were indicating you are booting in a UEFI environment, why are you running grub2-install at all? Given that you are indicating that you are booting off a raid environment and hence have Fedora installed on raid, I'm assuming you are using Fedora server, is that correct? I'm just curious because I played around with using Raid 10 a couple of years ago and ran into issues where Fedora workstation would not install on raid only Fedora server had support for doing that.
regards, Steve
-- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On 3/20/24 15:30, Stephen Morris wrote:
Given that you are indicating that you are booting off a raid environment and hence have Fedora installed on raid, I'm assuming you are using Fedora server, is that correct? I'm just curious because I played around with using Raid 10 a couple of years ago and ran into issues where Fedora workstation would not install on raid only Fedora server had support for doing that.
I don't know why there would be a difference. The installer and drivers are the same in both cases. I've never used the server install and I've been using software raid for a long time.
Stephen Morris writes:
resynced all RAID partitions, I ran grub2-install and I'm fairly certain there was a definitive change in grub's behavior, afterwards. Originally three periods were initially shown, for a few seconds, before the grub menu opened. I have a recollection that the number of periods is a diagnostic indications what went wrong if grub fails to start for some reason. This changed to a "Welcome to grub" banner.
So, it looks to me like years of regular grub updates, and countless Fedora releases, did not really end up updating …everything, on a BIOS system.
If I can ask a silly question, given that on UEFI systems grub2-install is redundant, and the initial messages you were getting were indicating you are booting in a UEFI environment, why are you running grub2-install at all?
Because, my experience on my other, bios, system was that grub rpm updates were not updating "everything".
Given that you are indicating that you are booting off a raid environment and hence have Fedora installed on raid, I'm assuming you are using Fedora server, is that correct?
Nope. Workstation.
I'm just curious because I played around with using Raid 10 a couple of years ago and ran into issues where Fedora workstation would not install on raid only Fedora server had support for doing that.
Not sure about the current fedora installer, but the installer that preceded Anaconda had no trouble with creating partitions on two drives and setting them up on raid 1, with mdadm. That's what I have.
One of them is of such vintage is that it went through the experience of grub growing too big for its britches. Years ago grub could no longer fit in the default amount of space before the 1st partition that fedora's installer was using. Existing fedora seats could not be updated to the new release.
No problem. Boot the installer. Assemble the raid. Resize the ext3 filesystem. Make it smaller. Shrink the raid volume. Remove one partition from the raid. Recreatw it on the hd, starting at a higher address. Add it back to the raid volume. Wait for the resync. Repeat with the other hd partition. Now there's more room for the grub bootloader on both hds.
All with stock fedora workstation.
regards, Steve
-- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of- conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora- infrastructure/new_issue
On Mar 20, 2024, at 20:10, Sam Varshavchik mrsam@courier-mta.com wrote:
Stephen Morris writes:.
If I can ask a silly question, given that on UEFI systems grub2-install is redundant, and the initial messages you were getting were indicating you are booting in a UEFI environment, why are you running grub2-install at all?
Because, my experience on my other, bios, system was that grub rpm updates were not updating "everything".
If your only experience is with the legacy CSM, it might be worth looking up how UEFI systems boot.
The tl;dr story is that the system firmware has some variables that say where to look for EFI volumes, and it launches EFI executables from those volumes. No tiny boot sectors or second stage loaders, just EFI executables on a FAT32 filesystem.
On 21/3/24 09:38, Samuel Sieb wrote:
On 3/20/24 15:30, Stephen Morris wrote:
Given that you are indicating that you are booting off a raid environment and hence have Fedora installed on raid, I'm assuming you are using Fedora server, is that correct? I'm just curious because I played around with using Raid 10 a couple of years ago and ran into issues where Fedora workstation would not install on raid only Fedora server had support for doing that.
I don't know why there would be a difference. The installer and drivers are the same in both cases. I've never used the server install and I've been using software raid for a long time.
Sorry, I was referring to physical raid from a motherboard that provided built in Raid 10 support. At the time I was doing this it was documented that Fedora workstation did support installing on Raid but Fedora Server did. I was just playing around with the environment and one issue I had was you had to install drivers into the installer for it to see the raid partition, and the motherboard only built drivers for windows, so I finished up installing the boot partition for Fedora on a non-raid devices and the rest of the partitions on raid.
regards, Steve
-- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On 3/21/24 15:06, Stephen Morris wrote:
On 21/3/24 09:38, Samuel Sieb wrote:
On 3/20/24 15:30, Stephen Morris wrote:
Given that you are indicating that you are booting off a raid environment and hence have Fedora installed on raid, I'm assuming you are using Fedora server, is that correct? I'm just curious because I played around with using Raid 10 a couple of years ago and ran into issues where Fedora workstation would not install on raid only Fedora server had support for doing that.
I don't know why there would be a difference. The installer and drivers are the same in both cases. I've never used the server install and I've been using software raid for a long time.
Sorry, I was referring to physical raid from a motherboard that provided built in Raid 10 support. At the time I was doing this it was documented that Fedora workstation did support installing on Raid but Fedora Server did. I was just playing around with the environment and one issue I had was you had to install drivers into the installer for it to see the raid partition, and the motherboard only built drivers for windows, so I finished up installing the boot partition for Fedora on a non-raid devices and the rest of the partitions on raid.
That's why I mentioned that the drivers are the same in both cases. I don't know why Workstation wouldn't be able to do it. But also, the OP specifically mentioned that he was using software raid anyway.
On 22/3/24 09:10, Samuel Sieb wrote:
On 3/21/24 15:06, Stephen Morris wrote:
On 21/3/24 09:38, Samuel Sieb wrote:
On 3/20/24 15:30, Stephen Morris wrote:
Given that you are indicating that you are booting off a raid environment and hence have Fedora installed on raid, I'm assuming you are using Fedora server, is that correct? I'm just curious because I played around with using Raid 10 a couple of years ago and ran into issues where Fedora workstation would not install on raid only Fedora server had support for doing that.
I don't know why there would be a difference. The installer and drivers are the same in both cases. I've never used the server install and I've been using software raid for a long time.
Sorry, I was referring to physical raid from a motherboard that provided built in Raid 10 support. At the time I was doing this it was documented that Fedora workstation did support installing on Raid but Fedora Server did. I was just playing around with the environment and one issue I had was you had to install drivers into the installer for it to see the raid partition, and the motherboard only built drivers for windows, so I finished up installing the boot partition for Fedora on a non-raid devices and the rest of the partitions on raid.
That's why I mentioned that the drivers are the same in both cases. I don't know why Workstation wouldn't be able to do it. But also, the OP specifically mentioned that he was using software raid anyway.
Sorry, I missed that bit.
regards, Steve
-- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
-
Jonathan Billings -
Sam Varshavchik -
Samuel Sieb -
Stephen Morris -
Tom Horsley