Patrick O'Callaghan wrote: > I recently upgraded F16->F17 using preupgrade. I booted into F17 and > everything seemed to work until I tried rebooting, whereupon I got a > Kernel panic with a lot of stuff about missing files (mdadm, sh, > cat, ...) and a panic backtrace. This was completely reproducible. > > I then noticed that the running kernel was still > kernel-3.3.7-1.fc16.x86_64, despite the fact that > kernel-3.3.7-1.fc17.x86_64 had been installed by preupgrade, i.e. > grub.cfg had not been changed to reflect the new kernel. I updated to > F17 3.4 from updates-testing and the problem appears to have gone away, > i.e. grub is now correct. > > So it looks like the issue was that grub.cfg should have been changed > during the preupgrade, but wasn't. Has anyone else seen this? > > On a related note: how does one capture the console output when a panic > like this occurs? It isn't in any log files (maybe by this time there > isn't a filesystem) and it's a chore to have to copy it all by hand, > which is why I haven't bothered in this case. > Yep, me, too. (See prior thread on "laptop won't boot." My situation turned out to be more of a mess than you report, with I installed the F17 kernel from the install DVD (as some folks suggested), and this indeed solved the panic-on-shutdown issue, but still left many, many FC16 packages still installed and the yum repo's still pointed to FC16. I gave up and did a fresh install of F17. -- Tim Evans, TKEvans.com, Inc. | 5 Chestnut Court UNIX System Admin Consulting | Owings Mills, MD 21117 http://www.tkevans.com/ | 443-394-3864 http://www.come-here.com/News/ | tkevans@xxxxxxxxxxx -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
