>>> Anaconda proceeded fine until after the networking >>> was setup, then it failed. ... I didn't get a >>> chance to save it or anything ... >> Confirmed again this morning, trying to find storage devices and it >> failed. I tried to save or send it to bugzilla but it wouldn't go >> through. If you have physical access to keyboard and a USB port, then use the debug shell (on VT2: <Ctrl><Alt>F2) to create a directory and mount a USB flash memory device. Many times this will work even if anaconda has trouble finding "disks." [For instance: https://bugzilla.redhat.com/show_bug.cgi?id=488984 ] If anaconda does not force an immediate reboot, then you may be able to save information directly to a file on flash memory, or via Copy+Paste into an editor, or by hand keying. Many bugs still occur in non-graphical mode (text mode install) and/or with a text console. Type a <TAB> at the GRUB boot screen, then append " text console=ttyS0,115200 console=tty0" to the kernel comand line, and boot. Capture by using a null modem cable to another machine running minicom, etc. -- -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
