On Sun, 2009-11-08 at 19:59 -0600, Jim Haynes wrote: > On Sun, 8 Nov 2009, Adam Williamson wrote: > > >> On Sat, 7 Nov 2009, Adam Williamson wrote: > >> > >>> Can you try: > >>> > >>> a) booting with kernel parameter 'nodmraid' > >> > >> That works. Both disks appear in the disk configuration section of > >> anaconda. > > > > In that case, the behavior is intentional. See > > https://bugzilla.redhat.com/show_bug.cgi?id=499733 . Your disk was > > previously part of a BIOS RAID set, and you never removed the metadata. > > anaconda ignoring such drives is not a bug - > > https://bugzilla.redhat.com/show_bug.cgi?id=499733#c22 . booting > > 'nodmraid' is a workaround, using 'dmraid -x' to remove the metadata > > Well, OK, but the drive was bought new and installed in the machine and > was never touched by Linux until I used Fedora 10 to set up a couple of > partitions. > > When I did dmraid -x it said > ERROR: ddf1: wrong # of devices in RAID set "ddf1_...." [1/2] on /dev/sdb > About to delete RAID set ddf1_... > WARNING: The metadata stored on the raidset(s) will not be > accessible after deletion > Do you want to continue? [y/n] : y > ERROR: Raid set deletion is not supported in "ddf1" format see my later comment on the bug, there's an improved command. It rather sounds like the drive you bought may have been not as new as advertised...I wouldn't want to make that accusation official, but not sure what else to think, that parameter would _only_ work if somehow there were stale RAID metadata on it. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
