On Sat, 2012-06-09 at 16:11 +0200, Martin Sourada wrote:
I used preupgrade for the first time and had a similar experience,
but
nothing one cannot fix...
1. Prepared the preupgrade process (f16->f17)
2. reboot and start upgrade
3. upgrade gets stuck on some package (IIRC it was something lisp
related). No CPU or HDD usage for about half an hour
4. got impatient, do a hard reboot start upgrade again
Don't do this, if you can possibly avoid it. It's never a good idea to
abort an upgrade and restart it (it results in the other weirdness you
hit later). When anaconda is running, a console is available on tty2;
you can fiddle about with processes there to try and unstuck whatever's
stuck. That sounds somewhat like
https://bugzilla.redhat.com/show_bug.cgi?id=822008 ; there's a fix in
for that bug, but it only got pushed to stable in the last day or so.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net