On 06/30/2009 01:07 AM, Andrew Parker wrote:
On Sat, Jun 27, 2009 at 9:10 PM, Sam Varshavchik<mrsam@xxxxxxxxxxxxxxx> wrote:
Anaconda is barfing when I try to upgrade my existing F10. The machine has
an IDE drive that contains a single Windows partitions, and two SCSI drives,
hanging off an Adaptec 29320 HBA, with F10 on both drives in a RAID-1
configuration.
When Anaconda gets to the "checking storage" phase, it spins for a while,
then proceeds immediately to do a new install.
The partitioning screen has only /dev/sda listed, which is the existing
Windows partition. /dev/sdb and /dev/sdc, the two SCSI drives, are not
shown. HOWEVER:
When I flip over to ALT-F2, "fdisk /dev/sdb" and "fdisk /dev/sdc" read the
partition table of the two SCSI drives. So, what I have is:
1) The kernel sees the SCSI drives
2) On some other ALT-F screen I see all the soothing messages from the md
subsystem concerning registering various md personalities.
However,
3) mdadm isn't running
4) Anaconda sees neither the softraid partitions, nor the actual underlying
/dev/sd? devices at all.
You may want to bugzilla this. Anaconda had all sorts of storage
changes during f11 and had numerous problems. I believe it was (one
of?) the reasons that F11 slipped. A few days before the f11 release
anaconda was trying to resize one of my partitions that wasn't even
being used in the install.
I had a major problem with installing on a system with Raid partitions as well,
due to my use of a kickstart install. This is noted in the Install notes
I know.
Will a "fixed" anaconda package be release soon to fix these issues so we can
roll our own "fixed" F11 ?
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
