Bug 156902 - lvm install still doesn't work
lvm install still doesn't work
Status: CLOSED CANTFIX
Product: Fedora
Classification: Fedora
Component: grub (Show other bugs)
4
x86_64 Linux
medium Severity high
: ---
: ---
Assigned To: Anaconda Maintenance Team
Mike McLean
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-05-04 22:05 EDT by Neal Becker
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-09-21 17:06:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Neal Becker 2005-05-04 22:05:40 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.3; Linux) (KHTML, like Gecko)

Description of problem:
I did a totally clean install.  I have a parallel ide on /dev/hdc with ntfs, 
and I installed FC4T2 onto a pair of sata drives.  I used anaconda to setup 
lvm on 2 partitions, 1 on each sata drive. 
 
Install seemed OK, but on reboot all I got was a grub> prompt. 
 
I booted rescue, and ran grub-install /dev/hdc.  There was some complaint 
about some /dev/sdb1 or something not being in bios. 
 
I ran grub-install --recheck /dev/hdc. 
 
Now it's running OK. 
 

Version-Release number of selected component (if applicable):
b

How reproducible:
Didn't try

Steps to Reproduce:
1.install 
2.boot 
3. 
   

Additional info:
Comment 1 Jeremy Katz 2005-05-05 17:40:19 EDT
Which is your first drive according to the BIOS?  Did you go to the advanced
boot loader screen and ensure the drive order matched?  What are the contents of
/boot/grub/device.map?
Comment 2 Jeremy Katz 2005-09-21 17:06:52 EDT
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received the feedback we
requested, we will assume the problem was not reproduceable or has been fixed in
a later update for this product.  If you have further details, feel free to
reopen the report with the additional details attached.

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