Description of problem: Attempted to install on Toshiba Portege 7100 series notebook. Video is Trident CyberBlade (generic). Attempt one. X server started - black screen, no responce on any known keystoke combination. Hard reset. Attempt two. X server started - I happen to move the mouse and saw X cursor for short time, then X server apparently crashed: XIO: fatal IO error 104 (Connection reset by peer) on X server ":1.0" after 0 requests (0 known processed) with 0 events remaining. Then install sends termination/kill signals and unmounts all filesystems leaving me unable to examine X log. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. make X crash Actual results: unable to examine X log file to determine the cause of a crash. Expected results: at least one VT should be left active (or anything else in order to examine/copy log files)
We have to kill the shell to be able to be guaranteed to be able to unmount filesystems (which is important to ensure that, eg, your rootfs gets unmounted cleanly). Booting with 'linux nokill' will not kill the shell, but this is a debugging aid only. It looks like you were seeing bug 108777, though.
I think you are right. I am positive I am seeing bug 108777. That bug also lists 'ctrl s' trick to delay shell kill. I think anaconda should upon abnormal termination always pause and ask user to capture log files (and submit them to bugzilla?) and then kill the shell.