Re: Drops to command prompt; configfile /grub2/grub.cfg needed to boot

[Brian J. Murrell]

On Thu, 2024-07-25 at 01:40 +0200, Pascal Hambourg wrote:
> 
> You should have regenerated grub.cfg with update-grub(2) instead.

Fair enough.  But I don't think Fedora has update-grub.  I think that's
a Debian/Ubuntu-ism.  /boot/grub2/grub.cfg refers to grub2-mkconfig. 
When I do that and compare the newly generated grub.cfg with the one I
edited they are the same.  :-P

> It should be --boot-directory (or nothing, as /boot is the default).

Just tried that and it now boots to the menu.  So either the above (or
the new kernel update that has happened in the meanwhile) fixed it. 
Thanks either way!

> PS: I advise against using a logical partition for /boot. When
> installed
> on the same disk, GRUB uses the partition number to identify the boot
> partition but logical partition nombers are not stable, they may
> change
> on creation or removal of another logical partition.

Unfortunately I don't have a choice.  The /boot that I replaced (sda5)
was logical (extended) also because the computer vendor used up 3
primary partitions themselves:

Device     Boot     Start        End   Sectors   Size Id Type
/dev/sda1            4096      79871     75776    37M de Dell Utility
/dev/sda2  *        80325   30800324  30720000  14.6G  7 HPFS/NTFS/exFAT
/dev/sda3        30801920  235601919 204800000  97.7G  7 HPFS/NTFS/exFAT
/dev/sda4       235601920 1000214527 764612608 364.6G  5 Extended
/dev/sda5       235603968  236627967   1024000   500M 83 Linux
/dev/sda6       236630016  461910015 225280000 107.4G 8e Linux LVM
/dev/sda7       998166528 1000214527   2048000  1000M 83 Linux

As much as I don't think I have ever booted the Windows that is on this
machine, it is at least licensed for it and so if a time ever came
where I was in a pinch and needed Windows for something stupid, I have
it at least.

Cheers,
b.