RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 694800 - Anaconda gets EDD information wrong
Summary: Anaconda gets EDD information wrong
Keywords:
Status: CLOSED DUPLICATE of bug 621175
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.1
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Ales Kozumplik
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On: 668737
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-08 13:16 UTC by Martin Wilck
Modified: 2014-09-30 23:40 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-24 15:41:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
anaconda install.log (64.62 KB, text/plain)
2011-04-08 13:17 UTC, Martin Wilck 		no flags Details
install.log.syslog (11.81 KB, text/plain)
2011-04-08 13:18 UTC, Martin Wilck 		no flags Details
sosreport (592.60 KB, application/x-xz)
2011-04-08 13:18 UTC, Martin Wilck 		no flags Details
View All

Description Martin Wilck 2011-04-08 13:16:25 UTC 
Description of problem:
I have a system with 2 megaraid_sas controllers which is con figured to boot from the 2nd drive on the 1st controller (sdb). The BIOS edd information is correct. Anaconda misinterprets the EDD information and gets the grub disk numbers wrong.

hd1: /dev/sdb

correct would be:
hd0: /dev/sdb
hd1: /dev/sda

Version-Release number of selected component (if applicable):
RHEL6.1 beta snap shot 2

How reproducible:
always

Steps to Reproduce:
1. install RHEL6.1
  
Actual results:
System fails to boot after installation because grub disk ordering is wrong

Expected results:
System boots

Additional info:
The info in sysfs clearly shows that sda=int13_dev81, sdb=int13_dev80:

[root@RX600S5-B578 ~]# cat /sys/block/sd[abc]/size^M
70582272^M
285671424^M
284557312^M
[root@RX600S5-B578 ~]# cat /sys/firmware/edd/s^H^[[K*/sectors^M
285671424^M
70582272^M
[root@RX600S5-B578 ~]# cat /sys/block/sda/size^M
70582272^M
[root@RX600S5-B578 ~]# cat /sys/block/sdb/size^M
285671424^M
[root@RX600S5-B578 ~]# cat /sys/firmware/edd/int13_dev80/sectors^M
285671424^M
[root@RX600S5-B578 ~]# cat /sys/firmware/edd/int13_dev81/sectors^M
70582272^M
Comment 1 Martin Wilck 2011-04-08 13:17:24 UTC 
Created attachment 490789 [details]
anaconda install.log
Comment 2 Martin Wilck 2011-04-08 13:18:05 UTC 
Created attachment 490790 [details]
install.log.syslog
Comment 3 Martin Wilck 2011-04-08 13:18:35 UTC 
Created attachment 490791 [details]
sosreport
Comment 6 Ales Kozumplik 2011-04-11 15:16:13 UTC 
Until this is fixed in kernel (bug 668737) everything we can do in Anaconda is hack around this by guessing (which is what we do already and it fails on certain occasions).
Comment 8 Martin Wilck 2011-04-12 07:10:59 UTC 
Could you open up bug 668737 for me, please?
Comment 9 Martin Wilck 2011-04-12 08:34:20 UTC 
(In reply to comment #6)
> Until this is fixed in kernel (bug 668737) everything we can do in Anaconda is
> hack around this by guessing (which is what we do already and it fails on
> certain occasions).

Your guessing algorithm doesn't appear to be perfect. For example, you don't seem to use the device size in your heuristic. As I tried to point out in the bug description, the size heuristic would have worked fine in my case (Obviously, it won't work all the time, but in many cases).
Comment 10 Ales Kozumplik 2011-04-12 10:42:22 UTC 
(In reply to comment #9)
> Your guessing algorithm doesn't appear to be perfect. For example, you don't
> seem to use the device size in your heuristic. As I tried to point out in the
> bug description, the size heuristic would have worked fine in my case
> (Obviously, it won't work all the time, but in many cases).

We are not attempting to make the guessing perfect, if will always be a hack. We want kernel to expose the information to us instead.
Comment 11 Ales Kozumplik 2011-05-24 15:05:04 UTC 
This bug has the same root cause as bug 621175, that is Anaconda is unable to correctly guess bios device order from the edd information exposed by kernel. Closing as a dup.

Note this issue is in fact waiting on bug 668737 to be resolved. Once kernel provides the complete information there will be changes in Anaconda necessary to accommodate the kernel changes. Reporter, if you can't see the kernel bug 668737 please let me know and I'll add you there.

*** This bug has been marked as a duplicate of bug 621175 ***
Comment 12 Gleb Natapov 2011-05-24 15:21:57 UTC 
(In reply to comment #10)
> (In reply to comment #9)
> > Your guessing algorithm doesn't appear to be perfect. For example, you don't
> > seem to use the device size in your heuristic. As I tried to point out in the
> > bug description, the size heuristic would have worked fine in my case
> > (Obviously, it won't work all the time, but in many cases).
> 
> We are not attempting to make the guessing perfect, if will always be a hack.
> We want kernel to expose the information to us instead.

Kernel does not have more information that anaconda. There are cases when there is not way to know boot device for certain. Kernel already expose all information anaconda needs to make educated guess. Kernel is not a place to do guesses.
Comment 13 Martin Wilck 2011-05-24 15:37:01 UTC 
I conclude from the last remark that anaconda indeed needs to improve the guessing algorithm. The example in the bug description is pretty obvious - if all BIOS devices have different sizes, the disk size is a very good guessing heuristic that anaconda should use. Together with the information EDD provides about the PCI device and the MBR signature, a good guess should be available in many more situations than now.
Comment 14 Ales Kozumplik 2011-05-24 15:41:17 UTC 
Please keep this closed. In any case this still is the same issue as bug 621175 which already has more information than this one.

*** This bug has been marked as a duplicate of bug 621175 ***
Comment 15 Gleb Natapov 2011-05-24 15:46:00 UTC 
(In reply to comment #14)
> Please keep this closed. In any case this still is the same issue as bug 621175
> which already has more information than this one.
> 
> *** This bug has been marked as a duplicate of bug 621175 ***

FWIW I agree with the closing of the bug as a dup of 621175. 621175 should be promoted to be "improve anaconda heuristics for choosing of boot device" or something.
Note You need to log in before you can comment on or make changes to this bug.