Quoting Soeren Schmidt <[EMAIL PROTECTED]>: | man atacontrol :)
I did that but it sounded too easy :) | | However if you want to use RAID1+0 and you want to be able to | boot from it you *need* a RAID capable controller BIOS, there is | no way to make a stock BIOS boot from a RAID0... | If you need it on install you probably also need at RAID capable | controller, if you define the RAID BIOS there, it will show up | in sysinstall.. The solution that pops into my mind is to have a small ad0 for boot and / partition. and ad1,ad2,ad3 as raid0+1 or ad1 and 2 as raid1 raid1 should solve my problem. Would either of these be configurable on sysinstall to have the /var and /usr partitions on the raid disks? If not that should be easy enough after a minimal install and reboot on ad0. | | > I haven't used vinum because of the root partition limitations and | > the complexity of the first configuration although I have been on the | > verge several times. BTW, is this an integration of vinum? To not | > have to be limited to hw raid by having similar flexibility and ease | > of use with software raid will be/is, IMO, fantastic. | | No, the RAID part of the ATA driver has nothing to do with vinum. | Vinum has several limitations that make it useless in this context. | Mainly that the RAID config layout on disk need to be of different | formats depending on what controller BIOS we have, and there is no | place to put all the extra volume stuff that vinum needs. | The ATA RAID code is very generic instead, with backends that converts | the internal RAID info to/from the needed info on disk depending | on controller type. Thanks for the clarification, Søren. Please forgive my basic, uninitiated questions. I really should probably have been paying more attention as these features were being added. ed ------------------------------------------------- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
