Description of problem: Running net install: Anaconda locks up/freezes at formatting partition to ext3. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Not a lot to go on in this report. Is this reproducible? Can you switch ttys by pressing ctrl-alt-f2 at all? If so, can you grab /tmp/anaconda.log, /tmp/syslog, and /tmp/program.log and attach them to this bug report?
Reproduced it twice, but I really can't give you much more than that. It locks up tighter than a bulls bum in fly season. The only solution is to hold the power button for 10 seconds and then start over. The pragmatic solution was to boot into MINT and create/format the partition there (in Gparted), and then restart the install and label but not format the partition. That's worked. It's setting up the install process now. Wish I could give you more than that, Chris. I know it's damn near useless as is, but the lockup was solid.
FYI: Laptop is an HP dv4217cl. http://h10025.www1.hp.com/ewfrf/wc/document?docname=c00491571&tmp_task=prodinfoCategory&lc=en&dlc=en&cc=us&site=null&key=null&product=1130594
Does your partitioning layout involve lvm? Did your previous layout involve lvm?
Nope. All partitions are formatted as ext3. I haven't used LVM since I unwittingly let Anaconda create LVMs on me way back in FC6. It really seems to have limited usage on a laptop. I can see it on a server farm, but I haven't found a need for it otherwise. After the Net-install failed at the end of the install (no bootloader nor kernel packages installed) I blew the partition back to chaos and installed from the Beta TC1 liveCD. Only a few crashes, and it did come to GUI,so I've updated it and I think the install is stable now, but I'm not pressing into it very hard either. Spoke too soon. NetworkManager is still borked. Unable to connect to hidden wireless. See this bug: https://bugzilla.redhat.com/show_bug.cgi?id=692226 and this bug: https://bugzilla.redhat.com/show_bug.cgi?id=692611 and this bug: https://bugzilla.redhat.com/show_bug.cgi?id=693454
Bug confirmed (lvm and x64)
Did this happen with the final release of F15 media? We can't fix released install media, so if it is still happening it is probably worth trying the upcoming F16 Beta
No update in 5 months. If you can recreate this with the F17 Alpha installer, please open a new bug with the relevant details.