Bug 519098
| Summary: | grub cannot write bootrecord on linear filesystem (RAID0,dmraid): ERROR 18 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Winfrid Tschiedel <Winfrid.Tschiedel> | ||||
| Component: | grub | Assignee: | Peter Jones <pjones> | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Release Test Team <release-test-team-automation> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 6.0 | CC: | gasmith | ||||
| Target Milestone: | alpha | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2010-07-08 14:41:30 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion. (In reply to comment #2) > This request was evaluated by Red Hat Product Management for inclusion in a Red > Hat Enterprise Linux major release. Product Management has requested further > review of this request by Red Hat Engineering, for potential inclusion in a Red > Hat Enterprise Linux Major release. This request is not yet committed for > inclusion. I don't understand this answer - it is bug, and not a request for a feature. Winfrid Can you show us what "parted $PATH_TO_DISK p" says on that device? Also, please try: 1) write out a correct /boot/grub/device.map. It should have something like this in it: (hd0) /dev/mapper/pdc_bjfeeibeeb 2) run "grub-install /dev/mapper/pdc_bjfeeibeeb". See if this works better. Hi Peter / Winfrid Winfrid retired from Fujitsu some months back, so he may not have access to this system any longer. I have a TX150S5 with Promise Fastrak TX4 Fake RAID controller in the Farnborough Lab, that was used to resolve another issue on Fedora/RHEL5 in BZ#509962. It may be that this issue in RHEL6 was also resolved, so I'll try the latest RHEL6 build when I get an opportunity, and report back. Regards, Gary Hi Peter, Gary is right - I have currently no system to test rhel 6 with linear raid. Please try to get support from Gary. Thank you, Winfrid Hi Peter Sorry, I've not had an opportunity to test this out on the RX220 (not TX150) we have in FAB. Otherwise, I'm sure I can arrange remote access if that would be suitable? I'll get back to looking into asap next week. Regards, Gary Hi Gary, any progress on testing this? |
Created attachment 358527 [details] grub commands to write the bootrecord into the rootpartition Description of problem: I have Fujitsu rx220 with Promise FastTrak S150 TX4 SATA Raidcontroller. I tried to install with grub a bootrecord into the rootpartition. Assignment of the rootpartition fails with Error 18: Selected cylinder exceeds maximum supported by BIOS Version-Release number of selected component (if applicable): grub-0.97-50.fc11.x86_64 How reproducible: always Steps to Reproduce: 1. Have a system with SATA-RAID 2. Install rhel6 as a second system - bootrecord placed in rootpartition 3. write a new boot record into the rootpartition Actual results: grub fails to write a bootrecord Expected results: successful completion Additional info: There was no problem to write the bootrecord with openSUSE 11.2 uname -a Linux rx220a 2.6.31-rc6-3-desktop #1 SMP PREEMPT 2009-08-17 21:11:11 +0200 x86_64 x86_64 x86_64 GNU/Linux rx220a:~ # rpm -qa | grep grub grub-0.97-160.3 Installation of rhel6 finished without problems, but I suppose that writing of bootrecord was not sucessful or format was incorrect - because I could not boot with chainloading - I could only boot rhel6 via configfile /boot/grub/grub.conf