hello, F11 x86_64 updated. Installed preupgrade package and run preupgrade successfully with target F12 (Costantine).
When I boot and choose the line created in grub.conf:
title Upgrade to Fedora 12 (Constantine) kernel /upgrade/vmlinuz preupgrade repo=hd::/var/cache/yum/preupgrade stage2=hd:UUID=4d1780d4-6bbd-449c-8932-f12bb1d40990:/upgrade/install.img ks=hd:UUID=4d1780d4-6bbd-449c-8932-f12bb1d40990:/upgrade/ks.cfg initrd /upgrade/initrd.img
I get an error that previous root device could not be found, forced to exit installer....
Reboot in F11, doing some debug:
df -k gives: [root ~]# df -k Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/vg_virtfed-lv_root 12381360 8580336 3172108 74% / /dev/cciss/c0d0p1 198333 163474 34859 83% /boot tmpfs 6104292 0 6104292 0% /dev/shm
root filesystem (on LV, I imagine supported...) [root ~]# tune2fs -l /dev/mapper/vg_virtfed-lv_root | grep UU Filesystem UUID: fa312b21-9db9-4ddc-b8eb-684cfb076941
/boot filesystem on partition: [root ~]# tune2fs -l /dev/cciss/c0d0p1 | grep UU Filesystem UUID: 4d1780d4-6bbd-449c-8932-f12bb1d40990
[root ~]# ll /boot/upgrade/ total 146584 -rw-r--r-- 1 root root 23540852 2009-11-09 01:06 initrd.img -rw-r--r-- 1 root root 122544128 2009-11-09 01:07 install.img -rw-r--r-- 1 root root 276 2009-11-17 17:26 ks.cfg -rw-r--r-- 1 root root 3423296 2009-11-09 01:06 vmlinuz
ks.cfg created by preupgrade contains: # ks.cfg generated by preupgrade lang en_US.UTF-8 keyboard us bootloader --upgrade --location=none upgrade --root-device=UUID=fa312b21-9db9-4ddc-b8eb-684cfb076941 reboot
%post grubby --remove-kernel=/boot/upgrade/vmlinuz rm -rf /boot/upgrade /var/cache/yum/preupgrade* %end
so the rott device and other things seems ok.... Only the bootloader string is not quite clear... donna if created wrong or not...
Thanks for help, Gianluca
On Tue, Nov 17, 2009 at 6:19 PM, Gianluca Cecchi gianluca.cecchi@gmail.com wrote:
[snip]
I get an error that previous root device could not be found, forced to exit installer.... [snip]
Expanding initrd.img inside /boot/upgrade/ directory, I notice that there is no reference to LVM.... Could it be the reason of not finding root device, that is on LVM? Any way to rebuild this initrd.img including LVM? Thanks, Gianluca
Could it be the reason of not finding root device, that is on LVM? Any way to rebuild this initrd.img including LVM?
It turned out that it depended on "stupid" me recently modifying the file /etc/redhat-release to accomplish a "stupid" check of an application. So when I got the message:
the root for the previously installed system was not found --> exit installer I switched to console 2 searching through information inside files in /tmp I saw at the end of storage.log something like this:
INFO: product Red Hat Enterprise Linux Server version 5.4 found on vg_virtfed-lv_root is not upgradable
I changed the file to its original F11 contents and the upgrade went through smoothly without changing anything of what automatically created by the preupgrade phase. So LVM was perfectly working ootb too
Until about at mid of install I get an unrecoverable error because of a corrupted package (libgcj). I downlaoded from a mirror and after a chroot I ran "rpm -Uvh" of it successfully.... Any hint to proceed? Can I restart and have the upgrade restart from where it arrived? How to check if any other package is corrupted? Thanks, Gianluca
At the end I re-set /etc/redhat-release to F11 and restarted the upgrade grub line and the upgrade proceeded and system rebooted... but now I have a stop with dracut that seems not able to see my LVM based root..... I try to start with "rdinitdebug rdshell" command line parameters, then manually mount my /boot partition and save over there init.log and output of dmesg
Relevant first error message at boot is dracut: /var/log/lvm2.log: fopen failed: No such file or directory
from rdshell I'm able to mount /boot but I get error trying LVM commands. For example. lvm pvdisplay File descriptor 9 (/.console_lock) leaked on lvm invocation. parent PID 751: sh /var/log/lvm2.log: fopen failed: No such file or directory
so I manually create /var/log/lvm2.log with
cat > /var/log/lvm2.log
Ctrl+d
and then the command
lvm pvdisplay works.... (with the file descriptor message and that it is ffalling back to local file-based locking)
so now I can activate my volume group and mount my root file system
I think after all this pain, that all the problem is in /var/log directory missing from initramfs embedded tree So I need to recreate initramfs file with /var/log directory.....
I'm able to make this with mkinitrd but not with dracut...... any hints? I think I'm going to bugzilla against dracut anyway..... because probably the ones that upgrade with an LVM root will encounter the same scenario... correct?
Gianluca
On 11/19/2009 12:16 AM, Gianluca Cecchi wrote:
I think I'm going to bugzilla against dracut anyway..... because probably the ones that upgrade with an LVM root will encounter the same scenario... correct?
Hi Gianluca, I experienced the same as you when I preupgraded to rawhide with anaconda 13.8. But I just retested it, the preupgrade upgraded the old system to f12 with anaconda 12.46. Then I didn't encounter this again.
Can you confirm your anaconda version when reboot after preupgrade?
-
Gianluca Cecchi -
He Rui