I just did that. It didn’t ask me anything about putting the Grub or anything else. I going to begin the installation. Let’s see what happens on reboot.
Update: After the installation, it showed the Grub menu like this:
Wasn’t this the dirty SATA connector?
For me the best lite linux is
Linux Mint 21 Xfce
Runs fine on 2 gb memory older machines
Thanks for the recommendation Bill
Nope. Before installing my new graphics card, I thoroughly cleaned everything including the inside of my SMPS by disassembling it and the motherboard, the processor, the heatsink, the fans and their protective sponge cover, all the connectors and ports on the motherboard and then assembled everything from scratch, just like assembling a new PC. Now it looks like a new PC.
Update 1: I pressed the ‘e’ button on my keyboard to see what comes up and this showed:
Grub >
Then I typed ‘reboot’ and it rebooted and then it showed the Grub Menu again and when I selected Fedora from the menu and pressed enter, it showed:
no filesystem (something was written before these words which I can’t remember)
Press any key to continue…
And within seconds it booted into Fefora. Then without entering Fedora, I restarted the PC from the login screen and after rebooting, selected Fedora from the Grub Menu and entered, it booted into Fedora without any error. Now inside Fedora I opened a terminal and ran this command:
sudo os-prober
Which gave the following result:
/dev/sda1:Debian GNU/Linux 12 (bookworm) : Debian: linux
Now what?
@Skywalker71 That means it found Debian. Now reboot and see if from GRUB you can boot to each of them. You might need to set the timeout to longer, I think 5 sec is default. I usually set it to 10 to give me time to select the OS I wish to boot.
Sheila
Right and there this problem arised. See the picture below:
1.
sudo nano /etc/default/grub
Then changed the time to 20 seconds (which is being shown in the picture above) and saved the file and then ran the command:
sudo update-grub
And the result:
sudo: update-grub: command not found
How strange!!! Now how can I update the grub?! Plus though ‘os-prober’ showed the result, there is no entry related to ‘os-prober’ in the grub file!!!
Update: I rebooted the PC. Selected the Debian, pressed enter and see the result below:
Grub >
And then I typed ‘reboot’. It rebooted, Grub Menu showed and I entered Fedora without any error. The problem is arising when I am trying to enter Debian.
You never showed your new disk partitions. You did create the EFI partition, right?
Your grub does not look like mine this is on my Linux Mint pc as my MX/Garuda machine is busy backing up right now:
myviolinsings@mint-desktop:~$ sudo cat /etc/default/grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`( . /etc/os-release; echo ${NAME:-Ubuntu} ) 2>/dev/null || echo Ubuntu`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
# If your computer has multiple operating systems installed, then you
# probably want to run os-prober. However, if your computer is a host
# for guest OSes installed via LVM or raw disk devices, running
# os-prober can cause damage to those guest OSes as it mounts
# filesystems to look for things.
#GRUB_DISABLE_OS_PROBER=false
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
# Uncomment to disable graphical terminal
#GRUB_TERMINAL=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
My grub_disable_recovery=“true” is commented out as I DO want recovery options.
Grub default should be 0 if Fedora was installed first, or 1 for Debian. But we are using the Fedora grub menu to access Debian, right? That is how you ran os-prober from Fedora? Cannot tell with “saved” showing.
@nevj will have to help from here as it seems you have or had Grub 2.12 running earlier.
Sheila
In thev79th post here, I gave the details of my new disk partition. I did not used UEFI because if I would use UEFI in BIOS and GPT as partition table, the OS would not be able to ‘see’ other drives / partitions with MBR partition table.
This is also strange to me because earlier installation when Debian took over and ‘os-prober’ could not find Fedora (the filesystem of that Fedora was btrfs, but now it is ext4), then in Debian, the grub was just like yours. But this time, it is different and now when I am giving the command:
sudo update-grub
it showed:
sudo: update-grub: command not found
and when I ran this command:
sudo dnf update-grub
it showed:
Unknown argument “update-grub” for command “dnf5”. Add “–help” for more information about the arguments. It could be a command provided by a plugin, try: dnf5 install ‘dnf5-command(update-grub)’
@nevj Friend, where are you? I am stuck. 
That’s so strange!
Quite self-explanatory 
It suggests dnf --help to look at real options.
He lives in Australia, probably different timezone, has a wife to care about, may have some work in the garden or on the farm, whatever…
He’ll answer, you can be sure.
Is it??!! I thought this is normal. I did it once and got that result. I will check again later.
I have updated grub as per the Fedora-way but the problem remains at its position. Now it is 1:23 a.m. i.e. past midnight. I have to sleep. See you tomorrow.
Goodnight.
Try reading this thread about someone needing help with which command to use in Fedora to update grub and she had used Debian which is “sudo update-grub.”
Maybe you can try the commands and read the explanations there:
I use the following command to edit grub:
sudo nano /etc/default/grub
Results of Google Search have given me two different ways to update grub.
They are:
1. sudo grub2-mkconfig -o /etc/grub2.cfg
followed by
sudo grub2-mkconfig -o /etc/grub2-efi.cfg
reboot machine
2. sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
reboot machine
Which is correct: (1) or (2)?
No. (1) did the same (correct) job twice. Either half of (1) gets it done. (2) was incorrect. /boot/efi/EFI/fedora/grub.cfg is a file, not a link. The main purpose of that file is to tell grub2 how to find grub2/grub.cfg (which partition it is in). Your command incorrectly puts the contents that should be in grub2/grub.cfg into EFI/fedora/grub.cfg instead. That might then seem to work (or might be badly messed up). But even if it seems to work, unless something later restores or corrects the EFI/fedora/grub.cfg file, future automatic updates will be messed up.
Sheila
Just a thought, but I had to use update-grub2 to get grub to update. I think it was Redcore Linux.
I would not use windows to do partitioning.
Use gparted from a live usb drive
As Laszlo said you need 3 partitions
Then do your installs, with the bios set to uefi boot ( and, as Laszlo says choose Normal in Ventoy)
The basic first step to learning to use multi boot , is to learn to use gparted. Other approaches that hide the issues are not desirable. You need to learn what the partitioning requirements are, and how to impliment them.
Then, you need to learn how to use grub.
Then you need to cope with the quirks if installing each distro… they are all different.
But he said he disabled it.
Sheila
Yes, so the installers will write grub to the MBR if bios is set to legacy boot.
He can do that, if he has an msdos partition table,but
I want him to use uefi boot and a gpt partition table and write grub to the efi partition, and use ext4 formatted linux partitions, not exfat.
because
I have no idea how btrfs would interact with msdos partitions?
If Windows is on msdos and he switches to gpt, Windows will have to be reinstalled!!! I have a feeling that @Skywalker71 needs to pull all but one drive and do a standalone Linux install, by then he will have learned Linux partioning!!!
I thought windows was on a separate disk?
Exactly.
It does not matter, if you change to gpt and slap on a fat32 partition, then Windows will try and mount the drive and fail to boot!! @Skywalker71 can still work with Windows on a separate along with Linux, as long as both are msdos, but using gpt for Linux and msdos for Windows,does not work well, so if you change the bios to boot UEFI then Windows is not going to boot!!!
OK, you know.
I had Win and Linux together once. Win was msdos partitions. I cant remember what Linux was.
I still do and all are on msdos!!!