I'm installing Fedora Server 24 onto an old Lenovo M91p (intel i5). It came with an installation of Windows 10, which I've wiped, and I'm using the gui installer from Fedora Server.
In the BIOS, I have changed
BOOT MODE from
After booting up on the USB drive containing the Fedora Server 24 iso, I walk through the installation procedure flawlessly. In particular,
The installation source is detected. It finds the
/dev/sdb. Verifying the installation media returns a
The installation destination is automatically found. A western digital hard drive:
ATA WDC WD2003FYYS-0.
During the installation, I opted to reclaim space but allow the installer to automatically configure the partitioning. During the reclamation, I deleted all the previous partitions. The desk partition scheme looks like this:
gdisk -l /dev/sda GPT fdisk (gdisk) version 1.0.1 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT Disk /dev/sda: 3907029168 sectors, 1.8 TiB Logical sector size: 512 bytes Disk identified (GUID): [...] Partition table holds up to 128 entries First usable sector is 34, last usable sector is 3907029134 Partitions will be aligned on 2048-sector boundries Total free space is 2157 sectors (1.1 MiB) Number Start (sector) End (sector) Size Code Name 1 2048 411647 200.0 MiB EF00 EFI System Partition 2 411648 1435647 500.0 MiB 8300 3 1435648 3907028991 1.8 TiB 8300
After the installation completes, I reboot, and I'm greeted with the following screen:
Error 1962: No operating system found. Press any key to repeat boot sequence.
After browsing around, I've tried the following:
BOOT MODE(as above) both ways.
EFIand back again.
- Changed the boot sequence order
According to this, the M92p ThinkCentre has a whitelist of efi labels. It apparently only boots from a label called "Red Hat Enterprise Linux."
I don't know how to specify the
bootloader-id during Fedora installations. Before trying an arch installation, I was wondering if anyone else has any suggestions on what to diagnose, where to go, or what's wrong.
When I first received the machine, it successfully booted Windows 10, which makes me thing this is not an issue with the
SATA cable or the drive itself.