Bug 110285
Summary: | Unhandled exception when assigning partitions to LVM | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Mark Eackloff <meackloff> | ||||||
Component: | anaconda | Assignee: | Jeremy Katz <katzj> | ||||||
Status: | CLOSED WORKSFORME | QA Contact: | Mike McLean <mikem> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 3.0 | ||||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | i686 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2004-02-12 16:24:17 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: |
|
Description
Mark Eackloff
2003-11-17 22:15:21 UTC
Can you attach the dump information? Created attachment 96033 [details]
One of two files created by the anaconda "Unhandled Exception" routine.
Created attachment 96034 [details]
One of two files created by the anaconda "Unhandled Exception" routine.
Did you somehow try to create two volume groups named the same thing? Or did you have a volume group by that name before beginning the install? No. At least the first time around. (I tried this twice.) It's hard to say what may have been left over from the first attempt. But the first attempt was on drives left over from a RHL9 installation when I had not used LVM. To make sure you understand, the two partitions were on separate drives. But I was trying to assign them to the same logical volume. Did you go back and forth into partitioning a couple of times? I'm trying to track down what happened based on the amount of logging that's done here. Can you provide the set of steps you used to get this to occur? Did you ever go beyond the partitioning screen before starting to go back? At this point I am probably not much help in remembering exactly what happened in what sequence. At that time I just went around the problem by not using LVM. But since your 2003-13-16 post I decided I needed to try to reproduce this on the same machine. I don't have a tape drive so the backup was somewhat of a pain using Zip and CD-RW media. This time the install went fine. Two physical volumes on sda and two on sdb. One volume group. But the re-install refreshed my memory a little. My first attempt in November failed during the actual formatting operation after the selecting packages and just before the packages start loading. The progress bar ("Formatting . . . .") stopped. No sounds of disk activity. After about 15 minutes I tried breaking out of it (don't remember how) only to find that the keyboard and mouse were completely unresponsive. Also, the NumLock and ScrollLock LEDs on the keyboard were flashing. Forced a reboot by hitting the reset button on the box. On my second attempt when I got to Disk Druid it appeared my partitions were already set up as phsical volumes but I was unable to assign mount points to the volumes. I got some error message that I don't remember. I think I backed up to Disk Druid to delete the partitions but it would not let me. So I backed up further and used fdisk from the shell to delete all partitions. Returned to the gui and continued used Disk Druid again to set up my volumes. This is to the best of my recollection but I couldn't swear to it. The rest of the story picks up step #3 in my original post. The current status is that I've got my volume group working fine. Since I can't remember exactly what happened and since my volume group is working and since I can't reproduce the problem, I wouldn't persue this further unless other people are having the same problem. I haven't been able to reproduce this either. If you see it again, please reopen with better details on how you hit it. |