Description of problem: Installing RHEL6.0 beta2 from a DVD, after selecting the Basic Storage radio button, the install process displayed an 'unhandled exception' window. The Key Error indicated 'cciss/c'.
Version-Release number of selected component (if applicable): RHEL6.0-20100622.1-Server-x86_64-DVD1.iso
How reproducible: Three attempts to install produced the same results.
Steps to Reproduce:
1. Attach a DVD to a Proliant blade server
2. Boot to the DVD and start the installation process.
3. Choose the "Basic Storage" radio button and click on Next.
Install process displays an 'unhandled exception' window with as described above in the Description of problem. I cannot get past this error regardless of the choices utilized at the 'unhandled exception' window. After choosing any of the choices, the only way to get rid of the screen is to choose Exit; this will reboot the server and the installation process starts over again. This process appears to be behaving like an iterative loop.
Successful completion of the installation process.
Investigation into the issue appears to indicate that all needed install files and/or image components are not available to the installer.
Please attach the anaconda dump.
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
(In reply to comment #2)
> Please attach the anaconda dump.
Hi Bill, I attempted to capture the anaconda dump by using the scr and save capabilities within the Details selection; they did not work for me. Could you advise me on how to capture the dump? Currently I'm doing progressive screen captures but I'm concerned that the file will be too large for your site to handle unless I could ftp it to a location. Thanks.
Those methods probably didn't work because the network wasn't up. If you can readily reproduce this issue, switch over to tty2, bring the network up, and then use scp to transfer /tmp/anaconda-tb-* to another machine. You can then attach it to this bug report from there.
(In reply to comment #5)
> Those methods probably didn't work because the network wasn't up. If you can
> readily reproduce this issue, switch over to tty2, bring the network up, and
> then use scp to transfer /tmp/anaconda-tb-* to another machine. You can then
> attach it to this bug report from there.
I attempted to go to the debug screen and do those tasks. I wasn't successful. How do you folks do this? I'm continuing to try to find the steps on google.
Created attachment 432971 [details]
Anaconda debug dump
This is the anaconda installer dump, data reproduced today - 11/19/2010.
Sorry for the typo: date = 7/19/2020
Thanks for the extra data. With that, I'm able to verify that this is a duplicate of another bug fixed in the build of anaconda immediately after the one you are testing (see the top of the exception dump for the anaconda version).
*** This bug has been marked as a duplicate of bug 559507 ***
(In reply to comment #9)
> Thanks for the extra data. With that, I'm able to verify that this is a
> duplicate of another bug fixed in the build of anaconda immediately after the
> one you are testing (see the top of the exception dump for the anaconda
> *** This bug has been marked as a duplicate of bug 559507 ***
I'm glad the data helped. However, you mentioned that this bug is fixed in the anaconda build immediately following the build I was using. I'm not sure what this will mean to me as far as moving forward is concerned. Do I get the newer anaconda bits in a beta3 release, for example, or a newer copy of some beta2 variant? Please advise. My instructions here are to test beta2 with snapshot7 added after the installation..