Created attachment 437671 [details] from anaconda via scp Description of problem: upon opening vnc window, anaconda was displaying it had a problem Version-Release number of selected component (if applicable): RHEL6.0-20100715.2-Server-x86_64-DVD1.iso Steps to Reproduce: 1. extract install.img, vmlinux, initrd.img, put on nfs server with kickstart file 2. kickstart file content: install nfs --server=192.168.1.242 --dir=/var/spool/up2date/r6 vnc --password=foo key foo lang en_US.UTF-8 keyboard us network --device 00:16:36:7E:CA:7A --bootproto static --ip 209.999.82.2 --gateway 209.999.82.14 --netmask 255.255.255.240 --hostname bleep.999.net network --device 00:16:36:7E:CA:7B --bootproto static --ip 192.168.2.43 --nameserver 192.168.2.42 --netmask 255.255.255.0 rootpw --iscrypted $1$qtu.AIJq$YToV.foo authconfig --enableshadow --enablemd5 selinux --disabled timezone --utc America/Chicago firstboot --disable %packages @base @core @basic-desktop @network-file-system-client @x11 %end 3. boot parameters: quiet panic=30 ksdevice=00:16:36:7E:CA:7B netmask=255.255.255.0 ip=192.168.2.43 gateway=192.168.2.42 dns=192.168.2.42 ks=nfs:192.168.2.42:/path/r6/bleep.ks Actual results: open vnc connection, find problem report, save via scp Expected results: continue install
*** This bug has been marked as a duplicate of bug 610769 ***
tried again without kickstart, boot parameters: quiet panic=30 ksdevice=00:16:36:7E:CA:7B netmask=255.255.255.0 ip=192.168.2.43 gateway=192.168.2.42 dns=192.168.2.42 hostname=pecan vnc vncpassword=foo lang=en_US keymap=us repo=nfs:192.168.2.42:/path/r6 maybe same bug or maybe not, anaconda signature follows. these disks have a bad raid superblock, that may be what's tripping up anaconda, i was hoping/expecting the installer would offer to start fresh.
Created attachment 437684 [details] another from anaconda via scp, this one without kickstart
i don't know about the first anaconda attachment but the second signature attachment is probably related to bad raid superblocks on disk, when i removed those partitions anaconda was able to continue.
in other words, probably not a duplicate of the ethernet device bug.
Please don't use a single bug report as a dumping ground for every issue you run across. The initial bug you reported is identical to 610769. Both used kickstart, both displayed the same traceback. Obviously when you switched to not using kickstart but instead specified everything on the command line, the traceback went away because kicsktart.py was no longer involved.
sorry, my submission of comment#2 was a "mid air collision", so i resubmitted it anyway, the only choice offered by bugzilla other than to lose it. might be nicer for bugzilla to output the comment text i'd submitted, so i could then paste it into a new bug. now of course you'll say i should submit a bug against bugzilla. anyway now you know why i submitted the second attachment here anyway. maybe tomorrow i'll get time to resubmit it as a separate bug, gotta go now..