I can't remember exactly what I did, but I think I copied an F31 install onto an existing F31 install on a hard drive that had Windows 10 on it. I did this in early 2020. Didn't keep notes. :(
Now I have a hard drive that will boot Windows 10 fine, via the Windows 10 Boot Manager.
When I go into the BIOS manager, it shows 2 boot options: Windows 10 via the Windows 10 Boot Manager and the hard drive device itself.
If I choose Windows 10, Win 10 boots fine. :( If I choose the hard drive device itself, the BIOS says to insert a valid boot device.
When I look at the hard drive with GParted, I see this:
Samsung SSD 850 EVO mSATA 500 GB with: /dev/sdb1 ntfs Recovery (Windows) /dev/sdb2 fat32 EFI System Partition Has a boot flag /dev/sdb3 unknown type Microsoft Reserved Partition /dev/sdb4 ntfs Basic data partition /dev/sdb5 ext4 <--- this is the boot partition, has the boot stuff on it. Has a boot flag. /dev/sdb6 lvm2 pv fedora
A fedora "device" which has 3 partitions: /dev/fedora/home ext4 the home directory /dev/fedora/root ext4 /dev/fedora/swap linuxswap
I used a live USB version to facilitate the copy. I suspect that the live boot got installed (thus the FAT32 partition) instead of the real boot partition, which is /dev/sda5 right now.
How do I fix this ?
Thanks
On 11/2/20 10:35 PM, linux guy wrote:
I can't remember exactly what I did, but I think I copied an F31 install onto an existing F31 install on a hard drive that had Windows 10 on it. I did this in early 2020. Didn't keep notes. :(
Now I have a hard drive that will boot Windows 10 fine, via the Windows 10 Boot Manager.
When I go into the BIOS manager, it shows 2 boot options: Windows 10 via the Windows 10 Boot Manager and the hard drive device itself.
If I choose Windows 10, Win 10 boots fine. :( If I choose the hard drive device itself, the BIOS says to insert a valid boot device.
When I look at the hard drive with GParted, I see this:
Samsung SSD 850 EVO mSATA 500 GB with: /dev/sdb1 ntfs Recovery (Windows) /dev/sdb2 fat32 EFI System Partition Has a boot flag /dev/sdb3 unknown type Microsoft Reserved Partition /dev/sdb4 ntfs Basic data partition /dev/sdb5 ext4 <--- this is the boot partition, has the boot stuff on it. Has a boot flag. /dev/sdb6 lvm2 pv fedora
A fedora "device" which has 3 partitions: /dev/fedora/home ext4 the home directory /dev/fedora/root ext4 /dev/fedora/swap linuxswap
I used a live USB version to facilitate the copy. I suspect that the live boot got installed (thus the FAT32 partition) instead of the real boot partition, which is /dev/sda5 right now.
The FAT32 partition is the EFI boot partition. Did this disk ever work with Fedora? I expect that you didn't copy the Fedora files that were in that partition on wherever you copied it from. It's tricky to fix that. Do you still have whatever drive you copied it from originally?
I believe that the files in /dev/sdb5 are the proper boot files. Would it be as simple as moving the files from that directory to the FAT32 partition ?
On Tue, Nov 3, 2020 at 1:43 AM Samuel Sieb samuel@sieb.net wrote:
On 11/2/20 10:35 PM, linux guy wrote:
I can't remember exactly what I did, but I think I copied an F31 install onto an existing F31 install on a hard drive that had Windows 10 on it. I did this in early 2020. Didn't keep notes. :(
Now I have a hard drive that will boot Windows 10 fine, via the Windows 10 Boot Manager.
When I go into the BIOS manager, it shows 2 boot options: Windows 10 via the Windows 10 Boot Manager and the hard drive device itself.
If I choose Windows 10, Win 10 boots fine. :( If I choose the hard drive device itself, the BIOS says to insert a valid boot device.
When I look at the hard drive with GParted, I see this:
Samsung SSD 850 EVO mSATA 500 GB with: /dev/sdb1 ntfs Recovery (Windows) /dev/sdb2 fat32 EFI System Partition Has a boot flag /dev/sdb3 unknown type Microsoft Reserved Partition /dev/sdb4 ntfs Basic data partition /dev/sdb5 ext4 <--- this is the boot partition, has the boot stuff on it. Has a boot flag. /dev/sdb6 lvm2 pv fedora
A fedora "device" which has 3 partitions: /dev/fedora/home ext4 the home directory /dev/fedora/root ext4 /dev/fedora/swap linuxswap
I used a live USB version to facilitate the copy. I suspect that the live boot got installed (thus the FAT32 partition) instead of the real boot partition, which is /dev/sda5 right now.
The FAT32 partition is the EFI boot partition. Did this disk ever work with Fedora? I expect that you didn't copy the Fedora files that were in that partition on wherever you copied it from. It's tricky to fix that. Do you still have whatever drive you copied it from originally? _______________________________________________ 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
Here is in /dev/sdb5:
ls 520f44320ac640c68996d2e055036d31 config-5.3.11-200.fc30.x86_64 config-5.3.11-300.fc31.x86_64 config-5.4.8-200.fc31.x86_64 efi elf-memtest86+-5.01 extlinux grub2 initramfs-0-rescue-6e82390ebac04e6ebc14c7543a31c1e8.img initramfs-5.3.11-200.fc30.x86_64.img initramfs-5.3.11-300.fc31.x86_64.img initramfs-5.4.8-200.fc31.x86_64.img loader lost+found memtest86+-5.01 System.map-5.3.11-200.fc30.x86_64 System.map-5.3.11-300.fc31.x86_64 System.map-5.4.8-200.fc31.x86_64 vmlinuz-0-rescue-6e82390ebac04e6ebc14c7543a31c1e8 vmlinuz-5.3.11-200.fc30.x86_64 vmlinuz-5.3.11-300.fc31.x86_64 vmlinuz-5.4.8-200.fc31.x86_64
The efi directory is empty.
Here is what is in /dev/sdb2: ls 6e82390ebac04e6ebc14c7543a31c1e8 EFI mach_kernel System
ls EFI Boot fedora Microsoft
On Tue, Nov 3, 2020 at 2:00 AM Samuel Sieb samuel@sieb.net wrote:
On 11/2/20 10:50 PM, linux guy wrote:
I believe that the files in /dev/sdb5 are the proper boot files. Would it be as simple as moving the files from that directory to the FAT32 partition ?
In particular, you're looking for a path like EFI/fedora/grubx64.efi _______________________________________________ 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
On 11/2/20 11:19 PM, linux guy wrote:
Here is in /dev/sdb5:
The efi directory is empty.
Right, that's the mount point for /dev/sdb2.
Here is what is in /dev/sdb2:
ls EFI Boot fedora Microsoft
What's in "fedora"? You might actually have all the files and just need to add the boot entry. That can sometimes be done directly in the BIOS, or else you need to boot a live image and use "efibootmgr" to add it. On the installed system, look in /var/log/anaconda/program.log to find the original command used.
I'm looking at it with a live image right now.
This is what is in fedora:
ls BOOTIA32.CSV fwupia32.efi grub.cfg grubx64.efi shimia32.efi BOOTX64.CSV fwupx64.efi grub.cfg.rpmsave mmia32.efi shimia32-fedora.efi fonts gcdia32.efi grubenv mmx64.efi shimx64.efi fw gcdx64.efi grubia32.efi shim.efi shimx64-fedora.efi
On 11/2/20 11:28 PM, linux guy wrote:
I'm looking at it with a live image right now.
This is what is in fedora:
ls BOOTIA32.CSV fwupia32.efi grub.cfg grubx64.efi shimia32.efi BOOTX64.CSV fwupx64.efi grub.cfg.rpmsave mmia32.efi shimia32-fedora.efi fonts gcdia32.efi grubenv mmx64.efi shimx64.efi fw gcdx64.efi grubia32.efi shim.efi shimx64-fedora.efi
Ok, then you're all set. Find that "efibootmgr" command from the log, run it, and it should boot.
I'm confused. Exactly what do I do ?
Thanks for the help, btw !
It's late here. I'll run it in the morning.
On 11/2/20 11:32 PM, linux guy wrote:
I'm confused. Exactly what do I do ?
In the /fedora/root partition, you need to find /var/log/anaconda/program.log. In there is the efibootmgr command that was run on install to setup the boot. Run that command again to add the Fedora boot option to the BIOS.
cat program.log | grep efi 06:41:48,437 INFO program: Running [15] lvm vgs --noheadings --nosuffix --nameprefixes --unquoted --units=b -o name,uuid,size,free,extent_size,extent_count,free_count,pv_count fedora --config= devices { preferred_names=["^/dev/mapper/", "^/dev/md/", "^/dev/sd"] } log {level=7 file=/tmp/lvm.log} ... 06:41:48,651 INFO program: Running [18] lvm vgs --noheadings --nosuffix --nameprefixes --unquoted --units=b -o name,uuid,size,free,extent_size,extent_count,free_count,pv_count fedora --config= devices { preferred_names=["^/dev/mapper/", "^/dev/md/", "^/dev/sd"] } log {level=7 file=/tmp/lvm.log} ... 06:41:49,718 INFO program: Running [20] lvm vgs --noheadings --nosuffix --nameprefixes --unquoted --units=b -o name,uuid,size,free,extent_size,extent_count,free_count,pv_count fedora --config= devices { preferred_names=["^/dev/mapper/", "^/dev/md/", "^/dev/sd"] } log {level=7 file=/tmp/lvm.log} ... 06:49:25,569 INFO program: Running... /usr/sbin/authconfig --update --nostart --enableshadow --passalgo=sha512 --enablefingerprint
??
So the boot process is supposed to find /dev/sdb5 and then mount /dev/sdb2 to the efi directory in it. Then it finds /fedora/root, and mount /fedora/home to /fedora/root/home ?
On 11/2/20 11:30 PM, linux guy wrote:
So the boot process is supposed to find /dev/sdb5 and then mount /dev/sdb2 to the efi directory in it. Then it finds /fedora/root, and mount /fedora/home to /fedora/root/home ?
The boot process finds the kernel and initramfs from /dev/sdb5, loads them and starts the kernel. In the initramfs is code to mount the /fedora/root partition and start everything. Part of that process will be mounting /dev/sdb2 and /fedora/home as described in the /etc/fstab file.
I just realized now, that all this refers to /dev/sdb. What's on /dev/sda?
/dev/sda is the live USB drive.
On Tue, Nov 3, 2020 at 2:39 AM Samuel Sieb samuel@sieb.net wrote:
On 11/2/20 11:30 PM, linux guy wrote:
So the boot process is supposed to find /dev/sdb5 and then mount /dev/sdb2 to the efi directory in it. Then it finds /fedora/root, and mount /fedora/home to /fedora/root/home ?
The boot process finds the kernel and initramfs from /dev/sdb5, loads them and starts the kernel. In the initramfs is code to mount the /fedora/root partition and start everything. Part of that process will be mounting /dev/sdb2 and /fedora/home as described in the /etc/fstab file.
I just realized now, that all this refers to /dev/sdb. What's on /dev/sda? _______________________________________________ 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
I'm running a live install via USB.
I'm looking in /dev/fedora/root mounted as root on my live session. /home/liveuser/root/var/log/anaconda
cat program.log | grep boot 12:39:33,557 INFO program: No FCoE boot disk information is found in EDD! 06:41:50,804 INFO program: Running... mount -t ext4 -o defaults /dev/sda1 /mnt/sysimage/boot 06:41:53,970 INFO program: Running... rsync -pogAXtlHrDx --exclude /dev/ --exclude /proc/ --exclude /sys/ --exclude /run/ --exclude /boot/*rescue* --exclude /etc/machine-id /run/install/source/ /mnt/sysimage 06:49:24,131 INFO program: Running... grub2-mkconfig -o /boot/grub2/grub.cfg 06:49:24,925 INFO program: Found linux image: /boot/vmlinuz-4.5.5-300.fc24.x86_64 06:49:24,925 INFO program: Found initrd image: /boot/initramfs-4.5.5-300.fc24.x86_64.img 06:49:24,925 INFO program: Found linux image: /boot/vmlinuz-0-rescue-c1d3ebaecd08428ba86f4aba3749efca 06:49:24,925 INFO program: Found initrd image: /boot/initramfs-0-rescue-c1d3ebaecd08428ba86f4aba3749efca.img
On 11/2/20 11:49 PM, linux guy wrote:
I'm running a live install via USB.
I'm looking in /dev/fedora/root mounted as root on my live session. /home/liveuser/root/var/log/anaconda
cat program.log | grep boot 06:49:24,131 INFO program: Running... grub2-mkconfig -o /boot/grub2/grub.cfg
That's curious. It appears the original install was not EFI, so where did the EFI bits come from? Hopefully everything is correctly setup for EFI. Try this command and see if it works: efibootmgr -c -w -L Fedora -d /dev/sdb -p 2 -l \EFI\fedora\shimx64.efi
"Try this command and see if it works: efibootmgr -c -w -L Fedora -d /dev/sdb -p 2 -l \EFI\fedora\shimx64.efi"
What directory should I run this from ?
On Tue, Nov 3, 2020 at 2:55 AM Samuel Sieb samuel@sieb.net wrote:
On 11/2/20 11:49 PM, linux guy wrote:
I'm running a live install via USB.
I'm looking in /dev/fedora/root mounted as root on my live session. /home/liveuser/root/var/log/anaconda
cat program.log | grep boot 06:49:24,131 INFO program: Running... grub2-mkconfig -o
/boot/grub2/grub.cfg
That's curious. It appears the original install was not EFI, so where did the EFI bits come from? Hopefully everything is correctly setup for EFI. Try this command and see if it works: efibootmgr -c -w -L Fedora -d /dev/sdb -p 2 -l \EFI\fedora\shimx64.efi _______________________________________________ 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
On Tue, Nov 3, 2020 at 9:11 AM linux guy linuxguy123@gmail.com wrote:
"Try this command and see if it works: efibootmgr -c -w -L Fedora -d /dev/sdb -p 2 -l \EFI\fedora\shimx64.efi"
What directory should I run this from ?
Doesn't matter. But you might just report what you get for 'efibootmgr -v' first.
If that returns a bunch of lines, you can proceed. But those backslashes need backslashes i.e. double them. \EFI\fedora\shimx64.efi
If you get a single line error message from efibootmgr then we need to figure out what's going on. Seems like Windows 10 is installed with UEFI "enabled" and somehow Fedora got installed with a "Legacy BIOS" mode enabled. In which case it's easier to just reinstall - don't forget to backup /home though first.
efibootmgr -v BootCurrent: 0002 Timeout: 2 seconds BootOrder: 0002,0001,0000 Boot0000* Windows Boot Manager HD(2,GPT,96f20e7f-6e16-47ff-bf8c-41fab591e17d,0xfa000,0x32000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...a................ Boot0001* Hard Drive BBS(HD,,0x0)..GO..NO........o.S.a.m.s.u.n.g. .S.S.D. .8.5.0. .E.V.O. .m.S.A.T.A. .5.0.0.G.B....................A...........................>..Gd-.;.A..MQ..L.2.S.7.4.X.N.G.A.1.7.3.5.5.5. .D. . . . ........BO..NO........o.W.D.C. .W.D.1.0.J.P.V.T.-.1.6.A.1.Y.T.0....................A...........................>..Gd-.;.A..MQ..L. . . . .W. .-.D.X.W.1.2.C.A.4.2.6.6.0.2........BO..NO........i. .P.a.t.r.i.o.t. .M.e.m.o.r.y. .P.M.A.P....................A.............................6..Gd-.;.A..MQ..L.0.7.A.B.0.B.0.1.1.9.6.3.8.8.E.0........BO Boot0002* UEFI: Patriot Memory PMAP PciRoot(0x0)/Pci(0x1d,0x0)/USB(0,0)/USB(0,0)/HD(1,MBR,0x7aa014a1,0xac,0x54d4)..BO
I don't understand where \EFI\fedora\shimx64.efi is supposed to be.
Remember, I am running on a live USB. I did not boot from the drive that I am trying to fix.
On 11/3/20 8:39 AM, linux guy wrote:
efibootmgr -v BootCurrent: 0002 Timeout: 2 seconds BootOrder: 0002,0001,0000
I don't understand where \EFI\fedora\shimx64.efi is supposed to be.
It's not there yet. It will get added after you run the command. And Chris is right, I forgot about the backslashes. Open the Terminal program and run the following command (copy and paste): sudo efibootmgr -c -w -L Fedora -d /dev/sdb -p 2 -l '\EFI\fedora\shimx64.efi'
On 11/3/20 8:25 AM, Chris Murphy wrote:
If you get a single line error message from efibootmgr then we need to figure out what's going on. Seems like Windows 10 is installed with UEFI "enabled" and somehow Fedora got installed with a "Legacy BIOS" mode enabled. In which case it's easier to just reinstall - don't forget to backup /home though first.
It's confusing. The anaconda log shows a legacy install, but all the EFI files are there. If adding the boot entry doesn't work, then a reinstall would be the next step.
Here's the result:
efibootmgr -c -w -L Fedora -d /dev/sdb -p 2 -l '\EFI\fedora\shimx64.efi' BootCurrent: 0002 Timeout: 2 seconds BootOrder: 0003,0002,0001,0000 Boot0000* Windows Boot Manager Boot0001* Hard Drive Boot0002* UEFI: Patriot Memory PMAP Boot0003* Fedora
I'm rebooting right now.
On Tue, Nov 3, 2020 at 12:59 PM Samuel Sieb samuel@sieb.net wrote:
On 11/3/20 8:25 AM, Chris Murphy wrote:
If you get a single line error message from efibootmgr then we need to figure out what's going on. Seems like Windows 10 is installed with UEFI "enabled" and somehow Fedora got installed with a "Legacy BIOS" mode enabled. In which case it's easier to just reinstall - don't forget to backup /home though first.
It's confusing. The anaconda log shows a legacy install, but all the EFI files are there. If adding the boot entry doesn't work, then a reinstall would be the next step. _______________________________________________ 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
IT WORKED !
You guys just saved me hours and hours of time reinstalling and setting up a new install on this computer. Thanks for the help !
Linux rocks. Fedora rocks !
-
Chris Murphy -
linux guy -
Samuel Sieb