Bug 111336

Summary:	FC1 fails to install with LVM
Product:	[Fedora] Fedora	Reporter:	djh <djh>
Component:	anaconda	Assignee:	Jeremy Katz <katzj>
Status:	CLOSED NEXTRELEASE	QA Contact:	Mike McLean <mikem>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-03-22 06:40:24 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:

Description djh 2003-12-02 11:37:41 UTC

Description of problem:
Anaconda fails to mkfs the root partition.  The following error dialog 
pops up:

"An error occurred trying to format Volume00/LogVol00.  This problem 
is serious, and the install cannot continue..."

The following error is on vt5:
"mke2fs: No such device or address while trying to determine 
filesystem size."



How reproducible:
100% (with GUI and VNC installs)



Additional info:
The system is a crappy old P233, 64M, currently only 1x 9G harddrive.

The partition layout is:
/dev/hda1 /boot 100M
/dev/hda2 swap 128M
/dev/hda3 LVM ~8G
(I've tried various LV configurations - all fail)

FC1 will install on this system if I don't use LVM.
I've tried the same config with the RH9 installer - it works okay.

Comment 1 Jeremy Katz 2003-12-02 17:28:26 UTC

Can you switch to tty2 and check if the device node exists?  If so,
can you run mke2fs by hand and see if it fails?

Comment 2 djh 2003-12-03 02:13:33 UTC

The device nodes are there, and mke2fs works.

The device name in the error dialog doesn't have the "/dev/" prefix - 
should it?

Comment 3 djh 2003-12-03 03:16:31 UTC

Here's some more info..

- The installer got up to where it's about to start installing packages.
- I switched to vt2 and successfully ran mke2fs on all three LVs.
- I then clicked to continue the installation process, and it failed
to mke2fs on LogVol01.
- I switched back to vt2 and now mke2fs fails on all three LVs (No
such file or address).

The VG is now unavailable.  By running vgchange -ay Volume00 on vt2, I 
can mke2fs again.

The first line in /tmp/lvmout is about Volume00 being successfully 
deactivated.  There's no mention of it being re-activated.

Comment 4 djh 2004-03-22 06:40:24 UTC

Just FYI, the only way I could get it to work was to do a fresh RH9
install with LVM, then upgrade it to FC1.

Closing.