Bug 104796
Summary: | Anaconda terminated | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Need Real Name <emil.chan> |
Component: | anaconda | Assignee: | Michael Fulbright <msf> |
Status: | CLOSED RAWHIDE | QA Contact: | Mike McLean <mikem> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | s390x | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-09-22 19:10:28 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: |
Did you have to initialize the dasd first? If so, this is fixed in our current codebase (and rerunning the installer should allow it to work fine as well) We tried ICKDSF and CMS FORMAT the 3338 cylinder minidisk, and the anaconda program failed to pick the mindisk (One of the release notes indicated that anaconda would not pick CMS format disk). Anaconda was finally able to pick up the minidisk after I wiped out cylinder zero. We have 8 Linux guests set up with same configuration, and most of them failed with the reported problem with Beta 2. What dasd initialization that you are referring to? - Emil Yes, that's the cause of it then. There were cases when we checked the initial format of the dasd to see if dasdfmt needed to be run where the device node got removed erroneously -- fixed in our current codebase. I'm new the RedHat. The current version EL3 is beta 2, and I experiencd the problem on beta 2. What exactly is the current codebase? Thank you - Emil |
Description of problem: After I pushed the Enter Key (OK checked) from the screen below during the install process of EL 3 Beta 2. ---------------------------------------- Installation to begin A complete log of your installation will be in /root/install.log after rebooting your system. You may want to keep this file for later reference. OK ---------------------------------------- I then received the following messages, then the PuTTY session closed, and the install process terminated. Traceback (most recent call last): File "/usr/bin/anaconda", line 1082, in ? intf.run(id, dispatch, configFileData) File "/usr/lib/anaconda/text.py", line 471, in run dispatch.gotoNext() File "/usr/lib/anaconda/dispatch.py", line 157, in gotoNext self.moveStep() File "/usr/lib/anaconda/dispatch.py", line 225, in moveStep rc = apply(func, self.bindArgs(args)) File "/usr/lib/anaconda/packages.py", line 475, in turnOnFilesystems diskset.savePartitions () File "/usr/lib/anaconda/partedUtils.py", line 696, in savePartitions disk.commit() error: Error: Error opening /tmp/dasda: No such file or directory > /usr/lib/anaconda/partedUtils.py(696)savePartitions() -> disk.commit() (Pdb) Then I lost the PuTTY session. See the following message from the VM Linux console log. sshd(pam_unix)Ã58¨: session closed for user root Version-Release number of selected component (if applicable): Linux version 2.4.21-1.1931.2.399.ent (bhcompile.redhat.com) (gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-16)) #1 SMP Wed Aug 20 15:23:46 EDT 2003 How reproducible: During the anaconda loader process. Steps to Reproduce: 1. See the description. 2. 3. Actual results: Expected results: Additional info: