I have problem when using preupgrade to upgrade to F15 during reboot: the immediate problem is at the very beginning of anaconda to find kickstart config file. Here is some background info:
1. This machine has SATA disks: 2 TB disks (ext4 for data) and 1 250G disk for FC14. BIOS is configured as AHCI mode for disk controller. FC wasn't configured any raid; so dmraid returns no raid disks. The disks are recognized as sda (250G), sdb, sdc. sda is further partitioned as follow:
a. sda1: /boot, 1GB and only 20% is used.
b. sda2: /home
c. sda3: /
there is also a 12GB swap disk allocated from sda.
2. preupgrade download stage is fine and it creates a /boot/upgrade folder having ks.cfg and vmlinuz and initrd.img in it. It also modified grub.conf as following addition:
title Upgrade to Fedora 15 (Lovelock)
kernel /upgrade/vmlinuz preupgrade repo=hd::/var/cache/yum/preupgrade ks=hd:UUID=1e275441-a289-4a52-8f43-dd2ce317711b:/upgrade/ks.cfg
3. reboot repeatedly gets to cannot download ks.cfg. A broad search results in many twists around kernel parameters: ks=file:/dev/sda1/upgrade/ks.cfg; ks=file:/boot/upgrade/ks.cfg; ks=hd:/dev/sda1:/upgrade/ks.cfg; ks=hd:UUID=boot_uuid:/upgrade/ks.cfg. Additional effort is to copy the /upgrade folder into a usb stick and given ks=hd:sdd:/upgrade/ks.cfg; now anaconda complains cannot find old installation.
So this leads me to this guess; anaconda doesn't recognize the /boot partition at all. so, tried mountfs kernel parameter, still yield nothing. One important thing that might be the root of the problem is: whenever anaconda dies, exit message shows "mdraid is cleaning bit ..." or similar message. This sounds that in anaconda, the boot process considers the system as raid disks, which is not true since there is really no raid at all. I knew that preupgrade doesn't work well with raid disks. Adding additional kernel parameter with root=root_uuid rd_NO_LUKS rd_NO_MD rd_NO_DM still doesn't help here.
So I am really running out of my ideas here. Any help please that can advance anaconda moving forward.
Many thanks first.
---------- Post added at 08:06 PM ---------- Previous post was at 02:30 PM ----------
Bump. Still waiting for help: how to move on to anaconda?
---------- Post added 28th May 2011 at 07:16 AM ---------- Previous post was 27th May 2011 at 08:06 PM ----------
Problem solved: this is Lenovo workstation; it has special workaround for the raid issue discussed here: http://forums.lenovo.com/t5/Linux-Di...D20/m-p/127002
Anaconda ran smoothly to finish. but it has other problem in boot into F15. I think it is display driver problem.