Description of problem: Using preupgrade to upgrade my fully-updated F10 system to F11, I get the following message during the preupgrade reboot: "Upgrade root not found" "The root for the previously installed system was not found." I first tried this the week after F11 was released, and at least one each week since. The observed behaviour is consistent. Version-Release number of selected component (if applicable): How reproducible: Every time! Steps to Reproduce: 1. Run preupgrade as root 2. reboot 3. Observe anaconda messages Actual results: "Upgrade root not found" Expected results: Expect / to be found! Additional info: During my F9->F10 upgrade, done using yum, anaconda recommended I convert all my storage to LVM, so I did, and I have not touched the LVM configuration since. A: F10 fstab ------------ # # /etc/fstab # Created by anaconda on Mon Dec 1 04:02:35 2008 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or vol_id(8) for more info # UUID=91229076-8038-4fd9-ac70-a897a38193cc / ext3 defaults 1 1 UUID=9809bfed-9a0f-49b9-a797-4252cb170045 /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 UUID=be5c0d54-e813-446f-81e2-52bfff08de89 swap swap defaults 0 0 /dev/cdrom /media/cdrom auto noauto,ro,user 0 0 B. Output from F10 mount: ------------------------- # mount /dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) /dev/sda1 on /boot type ext3 (rw) tmpfs on /dev/shm type tmpfs (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) gvfs-fuse-daemon on /home/bobc/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=bobc) C. grub.conf ------------ # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 # initrd /initrd-version.img #boot=/dev/sda default=1 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title Upgrade to Fedora 11 (Leonidas) kernel /upgrade/vmlinuz preupgrade repo=hd::/var/cache/yum/preupgrade stage2=hd:UUID=9809bfed-9a0f-49b9-a797-4252cb170045:/upgrade/install.img ks=hd:UUID=9809bfed-9a0f-49b9-a797-4252cb170045:/upgrade/ks.cfg initrd /upgrade/initrd.img title Fedora10 (2.6.27.25-170.2.72.fc10.i686) root (hd0,0) kernel /vmlinuz-2.6.27.25-170.2.72.fc10.i686 ro root=UUID=91229076-8038-4fd9-ac70-a897a38193cc vga=795 rhgb quiet initrd /initrd-2.6.27.25-170.2.72.fc10.i686.img title Fedora10 (2.6.27.24-170.2.68.fc10.i686) root (hd0,0) kernel /vmlinuz-2.6.27.24-170.2.68.fc10.i686 ro root=UUID=91229076-8038-4fd9-ac70-a897a38193cc vga=795 rhgb quiet initrd /initrd-2.6.27.24-170.2.68.fc10.i686.img title Fedora10 (2.6.27.21-170.2.56.fc10.i686) root (hd0,0) kernel /vmlinuz-2.6.27.21-170.2.56.fc10.i686 ro root=UUID=91229076-8038-4fd9-ac70-a897a38193cc vga=795 rhgb quiet initrd /initrd-2.6.27.21-170.2.56.fc10.i686.img
reassigning to anaconda - is there something magic/broken here or is preupgrade setting up a state anaconda can't cope with?
*** This bug has been marked as a duplicate of bug 499321 ***
From sifting through many linked bugs, it seems the underlying cause is that anaconda has forgotten how to find/use some pre-existing filesystems, including LVM. As of today, nobody seems to have a fix or a workaround that works (for me).
I have the exact same problem. A workaround or a fix that would enable me to upgrade would be very appreciated.
I have renamed the volume group and logical volumes. The original installation set them to VolGroup00 and LogVol00 and so on. After that the update procedure goes on till the graphical dialog where I can chose the data/installation media. I have set all devices as installation media and then I get the error again: The update procedure cannot find the previous root directory. /dev/sda1 * 1 654 5253223+ 83 Linux /dev/sda2 655 91201 727318777+ 8e Linux LVM /dev/sdb1 1 91201 732572001 8e Linux LVM pvscan: PV /dev/sdb1 VG PhOSCo lvm2 [698,62 GB / 64,00 MB free] PV /dev/sda2 VG PhOSCo lvm2 [693,62 GB / 205,38 GB free] Total: 2 [1,36 TB] / in use: 2 [1,36 TB] / in no VG: 0 [0 ] vgscan: Reading all physical volumes. This may take a while... Found volume group "PhOSCo" using metadata type lvm2 lvscan ACTIVE '/dev/PhOSCo/root' [401,34 GB] inherit ACTIVE '/dev/PhOSCo/local' [293,28 GB] inherit ACTIVE '/dev/PhOSCo/home' [195,31 GB] inherit ACTIVE '/dev/PhOSCo/localhome' [292,97 GB] inherit ACTIVE '/dev/PhOSCo/swap' [3,91 GB] inherit The /boot directory comes from /dev/sda1.