Bug 157428
Summary: | Tried (and failed) to create Volume Group even after I changed my mind about using LVM | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Derek Poon <dpoon> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED CANTFIX | QA Contact: | Mike McLean <mikem> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | dlpolanco |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-01-13 20:18:06 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
Derek Poon
2005-05-11 15:44:22 UTC
Can you please post the entire anaconda dump file? Having a similar problem and not sure if I should post on a different thread but here is what it is. My set up: MSI K8N Platinum, AMD 3500+, 1GB RAM, Audigy ZS Gamer, Sony CD-RW Burner, a 120GB Seagate IDE (Master), and a 250GB Hitachi (Slave). I'm a newb to Fedora so sorry if I'm just making a simple mistake but the problem lies here. My 120GB is dedicated to MS XP and the new drive(250GB)was partitioned with Partition Commander to have a 150GB fat32 partition. After rebooted and started up with FC4, went through setup installing a Workstation with some extra goodies. When Disk Druid came up, ran it auto through only the 250GB Hitachi so it would be as a fresh install but when I came to the final screen before install it bugs out. I would hit the next button and it would start to setup when this Exception rang out: ------------------------------------------------------- Traceback (most recent call last): File "/usr/lib/anaconda/gui.py", line 1137, in handleRendeCallback self.currentWindow.renderCallback() File "/usr/lib/anaconda/iw/progress_gui.py", line 244, in renderCallback self.intf.icw.nextClicked() File "usr/lib/anaconda/gui.py", line 873, in nextClicked self.dispatch.gotoNext() File"/usr/lib/anaconda/dispatch.py", line 174, in goNext self.moveStep() File "/usr/lib/anaconda/dispatch.py" line 242, in moveStep rc = apply(func, self.bindArgs(args)) File "/usr/lib/anaconda/packages.py", line 582, in turnOnFilesystems thefsset.createLogicalVolumes(instPath) File "/usr/lib/anaconda/fsset.py", line 1472, in createLogicalVolumes entry.device.setupDevice(chroot) File "/usr/lib/anaconda/fsset.py", line 2088, in setupDevice raise SystemError, "vgcreate failed for %s" %(self.name,) SystemError: vgcreate failed for VolGroup00 --------------------------------------------------------------- I am going to try and install it without the fat32 because I imagine that will fix it easy, and as well... I imagine it says somewhere you aren't suppose to put a fat32 partition with Linux and I just didn't see it. But yea, this problem is consistent and runs through the same way every time. THX! Scratch that. Deleted fat32 partition and still came up with same problem. Going to try one last thing... going to try and do manual install. If this doesn't work, I'm done for now. I would think it would be a hardware issue but I had already installed FC4 once and it didn't work because of other issues... but System Commander is enabled so maybe there? Dunno... anyway here goes nothing. Went a different route and the problem was bypassed. All throughout this process, my P/S2 mouse was not being identified for whatever reason. So instead of using GUI, went through text mode with auto Disk Droid for only the slave, and seemingly it ran through. Only problem is now... that System Commander says it doesn't have a operating system I think I'm going to be forced to instal GRUB... But I really have no clue... OUT. (This is a mass update of bugs which have been in the NEEDINFO state unmodified for over a year and have not been confirmed for a still supported version of Fedora Core.) Closing per lack of response to previous request for information. This bug was originally filed against a much earlier version of Fedora Core, and significant changes have taken place since the last version for which this bug is confirmed. Note that FC3 and FC4 are supported by Fedora Legacy for security fixes only. Please install a still supported version and retest. If it still occurs on FC5 or FC6, please reopen and assign to the correct version. Otherwise, if this a security issue, please change the product to Fedora Legacy. Thanks, and we are sorry that we did not get to this bug earlier. |