<br><br><div class="gmail_quote">On Thu, Jun 2, 2011 at 9:29 PM, Kevin J. Cummings <span dir="ltr"><<a href="mailto:cummings@kjchome.homeip.net">cummings@kjchome.homeip.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On 06/02/2011 09:00 PM, GeeKer Wang wrote:<br>
> Hello, Kevin<br>
><br>
> I can't enter my system now, however, I check the upgraded system using<br>
> livecd.<br>
> After login in my system by chroot in livecd, by checking "rpm -qa |grep<br>
> fc15 ", I am sure that many fc15 packages have installed.<br>
> And all the 3 steps you mentioned have passed, which takes a couple of<br>
> hours. So at least most fc15 packages have installed.<br>
<br>
</div>OK, so while looking at the live system chrooted to your system, what is<br>
the response to:<br>
<br>
rpm -q kernel<br>
<br>
Let's find out if the proper kernel got installed. If so, then we'll<br>
have a look at your /etc/grub.conf (which is just a symlink to:<br>
/boot/grub/grub.conf). And then we'll try and figure out how to install<br>
it by running grubby by hand....<br>
<div class="im"><br></div></blockquote><div>There is no fc15 kernel, only<br> kernel-2.6.35.12-88.fc14.i686<br> kernel-2.6.35.12-90.fc14.i686<br> kernel-2.6.35.13-91.fc14.i686<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">
> I just found a empty upgrade directory in /boot, and nothing related to<br>
> fc15 there. I guess preupgrade must forget to install kernel.<br>
<br>
</div>Not likely, though its possible in some bizarre set of circumstances.<br>
<br>
Are you 100% sure that preupgrade didn't stop prematurely with some sort<br>
of error message?<br>
<div class="im"><br></div></blockquote><div>It halted halfway because of installing openjpeg-devel. I renamed related files and preupgrade continued without other problem.<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">
> So what I should do to rescue it is to upgrade/install kernel in chroot<br>
> environment. But I don't know how to upgrade kernel with a kernel RPM<br>
> file. Any advice?<br>
<br>
</div>Let's find out if it got installed first. If it did, and it didn't<br>
install an entry in the grub menu, then it was a script-let of the<br>
kernel RPM which errored.<br>
<br>
If it did not get installed, it should be easy enough to install one by<br>
hand (with RPM) and see if it installs without any errors (and correctly<br>
modifies your /etc/grub.conf file). If it requires dependencies to<br>
install, then you will have other problems.<br>
<br></blockquote><div> When I tried "rpm -ivh kernel-2.6.38.6-fc15.i686.rpm", it failed with "<span><span>grubby
fatal error: unable to
find a suitable template</span></span>". But it created some files(eg.
vmlinuz-xxx-fc15, initramfs-xxx.img) in /boot and /lib/modules. However,
grub-install didn't recognize these files.<br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
What I've ended up doing in circumstances like these is to plow ahead<br>
and continue the upgrade in pieces, by hand after ensuring that:<br>
<br>
0) I have read the Fedora release notes for the version I am<br>
installing, looking for gotcha's that I may have tripped over!<br>
<br>
1) I have a proper kernel installed and working (bootable), and the<br>
fedora-release RPM is the proper version and architecture.<br>
<br>
2) yum and rpm (and all of their dependants) are up-to-date.<br>
<br>
3) my network is up and running so I can do (yum) updates over the network.<br>
<br>
4) essentially finish the upgrade by updating all of the remaining<br>
out-of-date RPMs on the system. Yes, you could try and continue from<br>
that point with "yum -y update", but you would most likely need to do it<br>
in pieces (to get around all of the broken packages) and also use the<br>
--skip-broken option to yum. I like to try it alphabetically (ie yum -y<br>
update a*), but usually end up breaking down each leading letter looking<br>
for packages that update nicely, and then figure out what's wrong with<br>
the packages that don't. This is not a quick and easy process. I've<br>
sometimes spent weeks cleaning up my server or my laptop from a failed<br>
upgrade in this fashion, but, in the end, my system has been upgraded,<br>
and not re-installed (for some reason, an updated system seems to me to<br>
be less likely to have some necessary local configuration lost than an<br>
installed update, but, I could be wrong). In the end, I learn a *lot*<br>
about Fedora, how it works (and how it sometimes doesn't work B^), and<br>
how to fix it.<br>
<br>
What doesn't work in this process is if some new set of packages<br>
obsoletes an installed set of packages, this method may not properly<br>
install the new set of packages. That's ultimately because Anaconda<br>
failed during preupgrade, but didn't leave a sufficient amount of<br>
information to properly fix the upgrade.<br>
<br>
If you are not able to install/boot a proper f15 kernel, let us know,<br>
there are ways (even more nefarious that a "yum upgrade") to update your<br>
system piecemeal, even from an f14 kernel....<br>
<div class="im"><br>
> On Thu, Jun 2, 2011 at 4:41 PM, Kevin J. Cummings<br>
</div><div><div></div><div class="h5">> <<a href="mailto:cummings@kjchome.homeip.net">cummings@kjchome.homeip.net</a> <mailto:<a href="mailto:cummings@kjchome.homeip.net">cummings@kjchome.homeip.net</a>>> wrote:<br>
><br>
> On 06/02/2011 10:13 AM, GeeKer Wang wrote:<br>
> > Hello, guys,<br>
> > I used preupgrade to upgrade fc14 to fc15, and everything<br>
> seemed<br>
> > fine. But when I reboot, I just find that kernel-fc15 is not<br>
> installed.<br>
><br>
> I can't tell from what you written above, but, pre-upgrade is a multi<br>
> step process. Here are the steps in a nut-shell:<br>
><br>
> 1) run preupgrade and have it download packages to a local repository on<br>
> your machine. It should also modify your /etc/grub.conf file to add an<br>
> entry which will continue the upgrade in step 2. When this step<br>
> completes, it should ask you to reboot your computer.<br>
><br>
> 2) when you reboot, it should automatically select the F15 upgrade entry<br>
> and boot into the second stage installer and start installing the<br>
> downloaded packages on to your system. This is the step that fails for<br>
> many people. Places to look for problems are in /etc/grub.conf and in<br>
> /boot/upgrade/. In the latter you should have at least 3 files:<br>
> initrd.img, ks.cfg, and vmlinuz. If not, something else has gone wrong<br>
> for you to look into. If everything goes right, when the packages are<br>
> finished installing (and yet another change is made to your<br>
> /etc/grub.conf file), the system will reboot yet again....<br>
><br>
> 3) The final reboot will run a script called firstboot which should<br>
> clean up from the upgrade process, and remove the old kernel versions<br>
> from your system. It will also check to make sure that any new packages<br>
> are configured properly (or prompt you for their configuration)<br>
> so that F15 will run correctly for you upon subsequent reboots. If you<br>
> get this far, preupgrade has done its job correctly and you should be<br>
> all set.<br>
><br>
> > There are no vmlinuz-xxx.fc15.i686 and<br>
> initramfs-xxxx-fc15.i686.img in<br>
> > /boot, no entry about fc-15 written in grub.conf, and nothing<br>
> related to<br>
> > fc15 is found in /lib/modules.<br>
> ><br>
> > I just try to download kernel and install it manually. But I<br>
> don't know<br>
> > whether there are any other packages forgotten.<br>
><br>
> What does "rpm -qa | grep fc15" tell you? (there should be *lots*<br>
> of hits).<br>
><br>
> If it can't find any fc15 packages installed, you haven't upgraded yet.<br>
><br>
> > --<br>
> > Bob<br>
><br>
> --<br>
> Kevin J. Cummings<br>
</div></div>> <a href="mailto:kjchome@rcn.com">kjchome@rcn.com</a> <mailto:<a href="mailto:kjchome@rcn.com">kjchome@rcn.com</a>><br>
> <a href="mailto:cummings@kjchome.homeip.net">cummings@kjchome.homeip.net</a> <mailto:<a href="mailto:cummings@kjchome.homeip.net">cummings@kjchome.homeip.net</a>><br>
<div class="im">> <a href="mailto:cummings@kjc386.framingham.ma.us">cummings@kjc386.framingham.ma.us</a><br>
</div>> <mailto:<a href="mailto:cummings@kjc386.framingham.ma.us">cummings@kjc386.framingham.ma.us</a>><br>
<div class="im">> Registered Linux User #1232 (<a href="http://counter.li.org" target="_blank">http://counter.li.org</a>)<br>
> --<br>
> users mailing list<br>
</div>> <a href="mailto:users@lists.fedoraproject.org">users@lists.fedoraproject.org</a> <mailto:<a href="mailto:users@lists.fedoraproject.org">users@lists.fedoraproject.org</a>><br>
<div class="im">> To unsubscribe or change subscription options:<br>
> <a href="https://admin.fedoraproject.org/mailman/listinfo/users" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/users</a><br>
> Guidelines: <a href="http://fedoraproject.org/wiki/Mailing_list_guidelines" target="_blank">http://fedoraproject.org/wiki/Mailing_list_guidelines</a><br>
><br>
><br>
><br>
><br>
> --<br>
> Bob<br>
><br>
<br>
<br>
</div>--<br>
<div><div></div><div class="h5">Kevin J. Cummings<br>
<a href="mailto:kjchome@rcn.com">kjchome@rcn.com</a><br>
<a href="mailto:cummings@kjchome.homeip.net">cummings@kjchome.homeip.net</a><br>
<a href="mailto:cummings@kjc386.framingham.ma.us">cummings@kjc386.framingham.ma.us</a><br>
Registered Linux User #1232 (<a href="http://counter.li.org" target="_blank">http://counter.li.org</a>)<br>
--<br>
users mailing list<br>
<a href="mailto:users@lists.fedoraproject.org">users@lists.fedoraproject.org</a><br>
To unsubscribe or change subscription options:<br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/users" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/users</a><br>
Guidelines: <a href="http://fedoraproject.org/wiki/Mailing_list_guidelines" target="_blank">http://fedoraproject.org/wiki/Mailing_list_guidelines</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Bob<br>