On 02/08/2013 10:09 AM, Charles Amey wrote: > In the f17 anaconda, it clearly shows the hard drive. When you create > the software raid partitions, its pretty obvious on which hard drive the > partition is located on. The root of the tree is the hard drive device > name, and underneath it are the partitions. When you create a raid > device, it lists all the raid members and one can pick the ones they > want. With f18 anaconda, one does not have the ability to create a > raid partition if there's only one hard drive. The use case here is testing/training, not actual usage. Do you think we should give the majority of users intending to really use the OS a false sense of security by allowing them to configure RAID in a way that doesn't make sense for the benefit of a few? (See Star Trek III? :) https://www.youtube.com/watch?v=Xa6c3OTr6yA ) How about these options, would any of these be do-able to you? If not, why? - Create a VM - you're doing this for testing purposes - and mount as many virtual disks as you like to it. I do this all the time to test out the storage functionality of Anaconda. It's quite easy, and free; I use the virt-manager UI to make all the spare disks. If you need a tutorial on how to do this I could make a screencast for you. - Buy another disk - you could use a $5 USD 4 GB USB key available at corner pharamacies if you're just setting this up for testing. Heck, if you send me your postal address off-list I'll try to send you a Fedora or Red Hat branded one. - Configure RAID post-install for learning purposes - hey you'll need to use the same tools to admin/maintain the array post-install, so why rely solely on the installer? This tutorial seems to indicate this is quite possible post-install: http://www.linuxhomenetworking.com/wiki/index.php/Quick_HOWTO_:_Ch26_:_Linux_Software_RAID ~m _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
