jedibrand

[Log in to get rid of this advertisement]

Hi,

I followed all of the steps (to the tee) here:

http://fedoraproject.org/wiki/YumUpgradeFaq

And the entire yum upgrade process completed successfully. Problem is, now that I try to boot with the fc9 kernel, it just can't seem to find the boot partition. That partition was previously at /dev/VolGroup00/LogVol00. I've tried changing the "mount /sysroot" imperative in the kernel img to point to /dev/VolGroup00/LogVol00, by path and UUID. Both do not work. I got the UUID, btw, using a system rescue CD with blkid. I can mount the partition just fine in the system rescue environment using "mount -U [UUID]."

I should also say that during boot, just before failing, I see a happy message that says something along the lines of "VolGroup00 group created successfully", and even says that there are two members for the group, presumably the root partition and the swap partition.

Help LinuxQuestions, you're my only hope!

reickler

I've seen similar issues which were caused by the "label" on the device changing. If /etc/fstab is configured to use labels, would cause this sort of problem. If in /etc/fstab it says "LABEL=boot" or something along those lines in the first column, then you should confirm that that label matches what's on the drive.

You can type this to see the current label:

[code]
e2label /dev/sda1 # Replace sda1 with the device you're boot partition is configured on
[code]

If fstab doesn't match, you can either change fstab or change the label on the device with:

[code]
e2label /dev/sda1 boot # Changing "sda1" and "boot" to match your device and label from fstab
[code]

jedibrand

Thanks for the suggestion! The boot partition does in fact have a label in fstab. Thing is, the machine boots just fine, so that should not be an issue. Sysroot, on the other hand, does not have any label. Here's what fstab looks like:

# UUID=91194191-6090-4280-87b5-6c2cb80cfae8
/dev/VolGroup00/LogVol00 / ext3 defaults,usrquota,grpquota 1 1
# UUID=f9d21fa7-f4a1-4771-945a-d86aa7b981db
LABEL=/boot /boot ext3 defaults 1 2
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
/dev/VolGroup00/LogVol01 swap swap defaults 0 0

Like I said before, grub finds the boot partition just fine--that's why I see the kernel loading. The kernel even finds VolGroup00 *and* activates the two member volumes, LogVol00 and LogVol01. It does appear, however, as if when the volumes are activated for some reason they are not present in /dev. What I'd like to do to verify this possibility is somehow peek into dev at this stage of the boot process. unfortunately, however, it appears interactive mode only lets one do some limited things during boot, but perhaps I need to look into that more.

John VV

you do know that fedora 9 is , and has ben, UNSUPPORTED it hit end of life about 6 months ago .
fedora 11 is the current and fedora 12 will be in a few weeks

jedibrand

I do, indeed. What I'm trying to do, in fact, is bring the whole thing current to f11. I can't do a clean install, and I'd like to go it the safe way and upgrade incrementally. I've heard of others doing f8->f10, and I may try that yet.

John VV

make sure that EVERYTHING is fully 100% backed up
fedora's "upgrade" option only works correctly about 50% of the time

jedibrand

Eesh! Yeah, everything is backed up. Still, I'd rather not have to restore but perhaps it will be easier to simply install f11 from scratch.

Anywho, I'm going to try and see if there's some way I can see what boot sees in dev, b/c it seems everything else is working OK. After all, I can still boot using fc8, and everything is running fine, apache, mysql, etc, etc.