Description of problem:
Upgrade FC2 -> FC3rc5 upgrade fails
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Take working FC2 i686 smp system using LVM on root
2.Upgrade via FC3rc5 Rescue CD doing an install via HTTP.
3.Reboot to failure.
I tried to upgrade an FC2 SMP i686 system on an LVM managed disk.
The system did not update grub properly. When I hand edited grub to
point at the only installed kernel, the
system then panicked.
I tried re-updating the system. I got the same error:
After NASH loads:
mount: error 6 mounting ext3
mount: error 2 mounting none
switchroot: mount failed: 22
umount /initrd/dev failed 2
Kernel panic - not syncing: Attempted to kill init!
I'll keep the system this way for awhile waiting for someone's
response to these messages. Otherwise I'll scrub the drive and restart
from scratch. Bear in mind that this system was running fine under
FC2 -> FC3rc5 upgrade should work perfectly. This system has run
Redhat since the days of 6.*.
You tell me. The system will boot under the FC3rc5 Rescue disc. The
disk is readable. What do you want?
Can you grab /root/upgrade.log by booting into rescue mode, mounting
your disk and then chroot'ing into /mnt/sysimage?
Created attachment 106023 [details]
Here is a gzipped tar archive of every file in /root
More than you asked for... every file in the directory.
I await your next request.
That upgrade.log only has a couple of packages being upgraded and
isn't the full system upgrade... did you try doing another upgrade
Yes, I thought that the upgrade went wonky and that reapplying the upgrade would
automagically fix things. If, due to the second upgrade, things are hopeless, I would be
willing to reinstall FC2 and do the upgrade again to see if this is repeatable.
It, unfortunately, at least clobbers the chances I have of seeing
what's going on. My FC2-> FC3 upgrades are working here, but there
definitely could be oddness involved (the dev->udev transition being
the primary culprit of such a thing).
If you could reproduce it and then grab /root/upgrade.log and
/var/log/anaconda*, that would help
OK, I'll try to reproduce. Here is my basic plan:
Scrub machine and perform new install of FC2. I'll try to select the same packages.
Setup run level 3.
Upgrade all packages.
Turn on smartd.
Install the only piece of user compiled code: djbdns' dnscache.
Do the same FC2 -> FC3rc5 over http upgrade.
Cross fingers and toes for failure. ;-)
This will take some time. Probably won't be done until later this evening.
Thanks for working this with me,
Created attachment 106075 [details]
New root Logs
I've reinstalled FC2 on a newly formatted drive with three primary partitions:
/boot, swap and / (as an LVM2 logical volume). I then upgraded via yum to the
latest FC2 packages. I verified that basic trhings function like X, ncftp, etc.
I then rebooted with FC3rc5 rescue CD and did an upgrade install via HTTP. Upon
rebooting, grub is still looking for the old FC2 kernel 2.6.8-1.521smp. No
other kernels are listed. This is the same behavior I noticed the first time I
did this. Other than gzipping the /root directory, the system is untouched.
Tell me what you need and I'll try to get it for you.
Created attachment 106077 [details]
New Anaconda Logs
Oops....forgot to get you these...
Okay, I see what's going on. In the dev -> udev transition, the
trigger doesn't do enough to make sure that the right device nodes get
created for mkinitrd to be able to find stuff.
Added an lvm vgmknodes to the udev trigger and built.
Thanks for looking into this.
OK. I'm glad it is a real problem.
I will go ahead and reinstall FC2 to prepare to test if the bug is fixed with the next FC3
I've been able to successfully update FC2 to FC3 with the final FC3.