Description of problem:
First attempt at install failed after selecting language and keyboard (english, us) it started anaconda then my monitor said 'no signal' and the dvd was no longer being accessed BUT the HDD light was still coming on. Same result on my internal (somewhat flakey) dvd drive and external ASUS dvd drive.
During the 2nd install attempt it got further, but said x startup failed, falling to text mode and after I selected the option of /dev/sda5 (replacing RHEL v6 beta1) it crashed again with a message 'Exception occurred' See below for output.
Version-Release number of selected component (if applicable):
?? I don't know if it's my system, Nvidia or other issues.
Steps to Reproduce:
Install crashes moments after starting anaconda or get message of Exception occurred using basic video driver.
Install of RHEL v6 is accomplished.
My system: AMD phenom 8650 triple core 2.3GHz, 2gb RAM
graphics: Nvidia GEForce 6150SE nForce 430
monitor: Acer x193W 1440x900 LCD
hard drive is a nearly new Seagate 500gb
On the install attempt using basic video driver, it had a message that X startup failed, falling to text mode. [ok] Then after I selected the install location of /dev/sda5 rather than the 'reinstall system' option, it brought up the 'Exception occurred' screen which said:
anaconda 13.21.50 exception report
Traceback (most recent call first):
File "/usr/lib/anaconda/text.py" line 595 in run (file, class names)=
File "/usr/bin/anaconda", line 1122, in <module>
anaconda.intf.run (anaconda) KeyError: 'cleardiskssel'
with choices of [ok] [save] [debug] and when I selected save it had an option to submit a bug report which failed, with the message 'unable to file bug [Errno -3] Temporary failure in name resolution. [ok]
Please attach the complete /tmp/anaconda-tb-* file to this bug report so I can see some more context on what you did. THanks.
Created attachment 429830 [details]
copy of /tmp/anaconda-tb-*
Does adding updates=http://clumens.fedorapeople.org/611000.img to your command line arguments fix this problem?
(In reply to comment #4)
> Does adding updates=http://clumens.fedorapeople.org/611000.img to your command
> line arguments fix this problem?
I'll check tonight or tomorrow morning and get back to you. I'm guessing you mean editing the boot command line and adding that? (If so, no need to respond, if not then please clarify.)
Created attachment 430530 [details]
The short answer is 'no' the updates=command didn't fix this problem. The long answer is that the vesa boot got a little further along, still required a text install, and gave a message 'the following file systems for your Linux system were not unmounted cleanly. Please boot your Linux installation, let the file system be checked and shut down cleanly to upgrade /dev/sda7 [ok]'
/dev/sda7 is a shared data partition, so I booted to Fedora 13, used the disk utility and unmounted it, then checked the fs and it came back after a few moments and said the file system is clean.
I left it unmounted, rebooted and on the 2nd attempt with the updates= command it got past finding storage devices, to Installer detecting a GRUB bootloader on /dev/sda5 (location for the rhel v6 beta1 install and where I selected to install this), then I selected option to Update boot loader configuration, which brought up a new Exception occurred message. The new /tmp/anaconda-tb-* is attached.
This second one looks like bad media or a bad optical drive to me. Did you run the media check and did it pass?
(In reply to comment #7)
> This second one looks like bad media or a bad optical drive to me. Did you run
> the media check and did it pass?
In the 2nd paragraph I noted:
I booted to Fedora 13, used the disk
utility and unmounted it, then checked the fs and it came back after a few
moments and said the file system is clean.
Same media and optical drive as the first one, though the drive is actually a bit suspect. It writes cd's fine but not dvd's, but the dvd was written on my external asus drive. Please see next comment for an update.
I read the most recent attachment and it appeared it was using the fstab from the beta1 install on /dev/sda5. It showed sda3 as an ext3 partition; and ext3 is no longer ext3 but is now ZFS for Open Solaris. I edited the file and commented out that line, re-tried the install and while X wouldn't start again and it went to text install -- it appears to have installed or upgraded the beta1 install.
It showed install of all 704 packages, and said it was updating install, and then a new 'Exception occurred'. That lead to filing a new bugzilla, see bug 612802.
I booted to the upgraded install, and as I was typing an update to this bugzilla the desktop froze, hard shutdown required. That may or may not lead to new issues. I'm typing this on my laptop.
Yeah - the second traceback is definitely unrelated to the initial comment. The initial comment is about a failure to skip the cleardisks UI in text mode, whereas the second traceback is media read errors that are probably nothing to do with anaconda. Since you got to the reposetup steps, you're past where the cleardisks UI would try to appear.
I'm willing to declare victory over this bug.
Thanks. I wasn't given a reposetup step, probably since X wouldn't start. I used my external DVD to check the dvd media and it checked out fine, then re-did the vesa install request with the updates= option, and it skipped most of what it had done previously and went right to 'post upgrade configuration' and bootloader and Complete.
I'm typing this from the beta2 desktop. So feel free to declare victory over this bug.
Closing per comments #10 and #11.
fwiw, Fresh install (not an upgrade) of the 'refresh' of beta2 went without a hitch on this machine, gui install and everything.
Moving to VERIFIED per comment #18
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.