So, I decided to do a clean installation of F26 over my F25
installation. My old configuration was:
Dual boot HP laptop: Win 10, F25.
F25 had an encrypted /home partition, a separate /swap partition (I know
I don't have to have one, but I'm old), and an unencrypted / partition
where, I thought, /boot/efi lived.
I do the installation using the GUI from "Install to Hard Drive" on the
USB live distro ((KDE spin), and choose "delete everything associated
with only F25." I am required to create a /boot/efi partition by the
GUI. So I do (I vaguely remembered that F25 was happy using the system
uefi partition, but I don't remember).
I install, and everything seems to go well.
Then I reboot, and my old F25 boot options come up (i.e. a list of F25
kernels and the Win 10 bootloader). Of course, it can no longer find
the F25 kernel. The Win 10 boots up fine.
So... I'm figuring I mis-configured where to put the boot directory, and
somehow it's finding the old one (which may well be in the system uefi
partition -- I don't remember).
The last time I had a problem with this, I ended up trying to move
directories by hand, and wrote over the Windows boot loader, which
caused me no end of headaches. I don't want to make that mistake again.
Here's what's on my hard drive:
sda1: "EFI system partition", containing BOOTSECT.BAK EFI
FSCK0000.REC FSCK0001.REC FSCK0002.REC FSCK0003.REC FSCK0004.REC
mach_kernel System 'System Volume Information' 260 MB
sda2: Microsoft reserved partition (I can't mount it) 128 MB
sda3: Windows data partition 103.42 GB
sda4: Windows recovery partition 731 MB
sda5: Windows recovery partition (another one, apparently) 25.43 GB
sda6: This looks like my old F25 boot partition (I thought it was
deleted) 18 GB It contains:
config-4.8.16-300.fc25.x86_64
config-4.9.3-200.fc25.x86_64
config-4.9.5-200.fc25.x86_64
efi
elf-memtest86+-5.01
extlinux
grub2
initramfs-0-rescue-95f65550951744038812b588382884c8.img
initramfs-4.8.16-300.fc25.x86_64.img
initramfs-4.9.3-200.fc25.x86_64.img
initramfs-4.9.5-200.fc25.x86_64.img
initrd-plymouth.img
lost+found
memtest86+-5.01
System.map-4.8.16-300.fc25.x86_64
System.map-4.9.3-200.fc25.x86_64
System.map-4.9.5-200.fc25.x86_64
vmlinuz-0-rescue-95f65550951744038812b588382884c8
vmlinuz-4.8.16-300.fc25.x86_64
vmlinuz-4.9.3-200.fc25.x86_64
vmlinuz-4.9.5-200.fc25.x86_64
sda7: "EFI system partition" 23.28 GB. Ut contains:
EFI
mach_kernel
System
sda8: This looks like the F26 boot partition that is not being called.
9 G
9cd45473cdd74075934e438993760520
config-4.11.8-300.fc26.x86_64
efi
elf-memtest86+-5.01
extlinux
grub2
initramfs-0-rescue-ea56b271f5994ca7b63e2028c325a528.img
initramfs-4.11.8-300.fc26.x86_64.img
lost+found
memtest86+-5.01
System.map-4.11.8-300.fc26.x86_64
vmlinuz-0-rescue-ea56b271f5994ca7b63e2028c325a528
vmlinuz-4.11.8-300.fc26.x86_64
sda9: Encrypted /home partition, 760 GB
So, it looks like I've managed to create two System EFI partitions. Who
knew?
Two questions:
Is there a simple fix-by-hand for this?
If I have to re-install from the USB, what mistake did I make and how to
I not do it again?
Thanks!
billo
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
