+++ This bug was initially created as a clone of Bug #1299248 +++
Description of problem:
After booting a kernel on a fedora23 system with no other OS installed, grub2 apparently reports:
error: failure reading sector 0xfc from `hd4'.
error: failure reading sector 0xe0 from `hd4'.
error: failure reading sector 0x0 from `hd4'.
Press any key to continue...
The system boot fine if I press any key or just let it go.
Version-Release number of selected component (if applicable):
fedora23 x86_64
How reproducible:
Every boot.
Steps to Reproduce:
1. Reboot.
2.
3.
Actual results:
Expected results:
Additional info:
The system is a Supermicro SYS-6018R-MTR with X10DRL-i and two E5-2623 processors. It's configured to use EFI.
I've tried recreating the /boot/efi/EFI/fedora/grub.cfg
All four disks are Samsung SSD 850 PRO 512GB.
The system only has four disks, and according to grub "ls", it's hd0 through hd3. Where does it think there is an hd4?
Can I do a regular BIOS install on this system?
--- Additional comment from Alex Regan on 2016-01-24 14:11:19 EST ---
Is there any update on this? How can I provide more information to help troubleshoot this?
--- Additional comment from Kimmo Vuorinen on 2016-10-05 07:57:33 EDT ---
I stumbled into this when converting my Fedora 23 installation from BIOS boot into EFI boot. In my case this was caused by optical drive being detected as (hd2) when hard drives were (hd0) and (hd1). When no media in optical drive, those errors were reported. I have found no solution so far to remedy this problem.
--- Additional comment from Kimmo Vuorinen on 2016-10-05 08:21:50 EDT ---
I found out that a patch that should fix this problem has been committed upstream.
https://lists.gnu.org/archive/html/help-grub/2016-02/msg00075.html
--- Additional comment from Kimmo Vuorinen on 2016-10-05 16:50:51 EDT ---
Problem with Grub EFI boot errors received when there is no media in drive is fixed in grub2-2.02-0.34.fc24.src.rpm which I built for Fedora 23.
--- Additional comment from Fedora End Of Life on 2016-11-24 10:00:46 EST ---
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
We can see these issues reported for RHEL 7.3 and RHEL 7.4