Bug 125266
| Summary: | Installer crashes after formatting partitions | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 3 | Reporter: | Andrew Hill <andrew> | ||||||
| Component: | anaconda | Assignee: | Jeremy Katz <katzj> | ||||||
| Status: | CLOSED NOTABUG | 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: | 2005-02-02 12:44:36 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: |
|
||||||||
Created attachment 100863 [details]
anacdump.txt file generated by anaconda after crash
Created attachment 100864 [details]
syslog file created by anaconda after crash
Is this reproducible? Is this with the original RHEL3 or one of the update releases? Yes, it happens every time. The PXE boot images were generated using the Enterprise Linux 3 ES Update 2 CDROMs. If you switch to tty2 at the poit of the crash, does /dev/vg01/lv_root exist? At this stage, I cannot get the kickstart boot over PXE to proceed as far as listed above - the installation dies immediately after obtaining the hostname information stage with a "signal 11". Suspect that there may be a NIC/switch error. Will confirm once I have another Dell 2650 to test with (may be a few weeks away). Also, note that I am able to install the machine by using the original CD-ROM to boot with, and by putting the kickstart file on a floppy disk... Did you have a chance to investigate with another machine? Yes -- the machine died shortly after my last post, and after it was replaced, the process worked fine, so I think this might have been a case of strange hardware faults. |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 Description of problem: While installing RHEL 3 ES on a Dell PowerEdge 2650, via a kickstart file, anaconda crashes after formatting the partitions. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Boot Dell PE2650 using PXE to obtain IP address/RHEL 3 ES boot image. 2. Use ks.cfg file with configuration: bootloader --location=mbr clearpart --linux part /boot --size=100 --asprimary part swap --recommended --asprimary part pv.01 --size=500 --grow --asprimary volgroup vg01 pv.01 logvol / --vgname=vg01 --size=2000 --name=lv_root logvol /home --vgname=vg01 --size=500 --name=lv_home logvol /var --vgname=vg01 --size=21000 --name=lv_var logvol /tmp --vgname=vg01 --size=1800 --name=lv_tmp logvol /usr --vgname=vg01 --size=5000 --name=lv_usr Actual Results: Anaconda crashes after partitioning the drives/formatting the partitions, with the following message: Traceback (most recent call last): File "/usr/bin/anaconda", line 1081, in ? intf.run(id, dispatch, configFileData) File "/usr/src/build/315542-i386/install//usr/lib/anaconda/text.py", line 471, in run File "/usr/src/build/315542-i386/install//usr/lib/anaconda/dispatch.py", line 157, in gotoNext File "/usr/src/build/315542-i386/install//usr/lib/anaconda/dispatch.py", line 225, in moveStep File "/usr/src/build/315542-i386/install//usr/lib/anaconda/packages.py", line 492, in turnOnFilesystems File "/usr/src/build/315542-i386/install//usr/lib/anaconda/fsset.py", line 1428, in mountFilesystems File "/usr/src/build/315542-i386/install//usr/lib/anaconda/iutil.py", line 377, in copyDeviceNode OSError: [Errno 2] No such file or directory: '/dev/vg01/lv_root' Expected Results: Expected install to continue. Additional info: Note that if the machine is rebooted, and the system is booted from the CD-ROM, then all of the partitions have actually been created, and formatted, and the installation can be carried out on the existing partitions. Note that the exact same partition configuration works on a Dell PE1750.