Bug 1299248 - grub2 reports "failure reading sector 0x0 from `hd4`" after choosing kernel
Summary: grub2 reports "failure reading sector 0x0 from `hd4`" after choosing kernel
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 23
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1481668
TreeView+ depends on / blocked
 
Reported: 2016-01-17 19:50 UTC by Alex Regan
Modified: 2022-03-13 14:00 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
: 1481668 (view as bug list)
Environment:
Last Closed: 2016-12-20 17:58:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Alex Regan 2016-01-17 19:50:01 UTC
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?

Comment 1 Alex Regan 2016-01-24 19:11:19 UTC
Is there any update on this? How can I provide more information to help troubleshoot this?

Comment 2 Kimmo Vuorinen 2016-10-05 11:57:33 UTC
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.

Comment 3 Kimmo Vuorinen 2016-10-05 12:21:50 UTC
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

Comment 4 Kimmo Vuorinen 2016-10-05 20:50:51 UTC
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.

Comment 5 Fedora End Of Life 2016-11-24 15:00:46 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2016-12-20 17:58:02 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.