You might have a look at your partition layout: fdisk -l /dev/sda
Also, your UEFI motherboard could be booting in legacy BIOS mode.

A couple of months back, I had to re-arrange a borked Debian install.  This is a
4 TB Western Digital Black drive on a UEFI motherboard:
[0:root@TUX ~]$ fdisk -l /dev/sda
Disk /dev/sda: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 170B3F1A-BFD5-4785-B5E8-803B2B036244

Device          Start        End    Sectors   Size Type
/dev/sda1        2048       6143       4096     2M BIOS boot
/dev/sda2        6144   67115007   67108864    32G Linux swap
/dev/sda3    67115008   68114432     999425   488M Microsoft basic data
/dev/sda4    68116480 7812083341 7743966862   3.6T Linux RAID
/dev/sda5  7812083712 7814037134    1953423 953.8M Linux filesystem

I don't remember why I had to define /dev/sda3.  I think Debian insisted on it.
If the disk doesn't use EFI, you need the 'BIOS boot' partition.  It only has to
be 1 MB (maybe less) but this was my first time doing this and I wanted to be
sure I didn't have to re-arrange partitions again.  Lots of copying files and
waiting, waiting, waiting.  Breaking mirrors and re-syncing them.  Lots of fun.

If you are using it as an EFI disk, you need a different partition other than
the 'BIOS boot' but don't rememer what it is.


On 6/27/2017 9:35 PM, William Mattison wrote:
(replying to all three messages)

When I boot, the bios display says it is UEFI.  Am I mis-understanding what that means?  Am I mis-using the term?

My /boot directory has only two sub-directories: "grub" and "grub2", no sub-directory "efi".

Each of the two sub-directories has a file called "grub.cfg".  The two files are identical, except for permissions.

In /etc/fstab, the UUIDs are already correct, based on output by both the blkid command and the lsblk command (which blkid's man page says I really should use instead).

I tried the grub2-mkconfig command in both sub-directories.  Then I rebooted.  The new menu has Fedora, other Fedora options, Windows 7 (on /dev/sda1), and Windows 7 (on /dev/sda2).  Each option appears to boot up correctly, though I did not attempt to actually log in to a windows account.

Why are there two menu entries for windows?  On this system, sda1 is the master boot record, sda2 is the windows partition.

After signing in to Fedora, I get a crash message saying vmlinuz crashed.  I couldn't catch the whole message.  Yet the system does seem to work.  What's going on?

users mailing list --
To unsubscribe send an email to