Date: Tue, 30 Nov 2004 23:06:59 +0000 From: David O'Brien <obrien@FreeBSD.ORG> To: Bob Bishop <rb@gid.co.uk> Cc: stable@freebsd.org Subject: Re: No RAID for VT8237? Message-ID: <20041130230659.GA30089@hub.freebsd.org> In-Reply-To: <6.2.0.14.2.20041130110542.03fdced0@gid.co.uk> References: <4013.172.16.0.200.1101790160.squirrel@172.16.0.200> <41AC1A0D.1020705@speakeasy.net> <4460.172.16.0.200.1101798279.squirrel@172.16.0.200> <6.2.0.14.2.20041130110542.03fdced0@gid.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Nov 30, 2004 at 11:09:34AM +0000, Bob Bishop wrote: > You might try an 'atacontrol create <etc>'. I had a problem where I'd > defined RAID1 in the BIOS, but 5.3 wouldn't see it (specifically saw the > drives individually but no ar0); after atacontrol create... it all works. > Go fig. This isn't weird. By using 'atacontrol create' yourself, you have a pure-software RAID same as you would have with ccd(4). The difference from defineing it in your software-assist "RAID" BIOS is that you can boot off the RAID. With the pure-software RAID you cannot[*]. [*] Unless your PATA/SATA "RAID" controller just happens to understand the metadata used by 'atacontrol create'. A 'atacontrol create' RAID1 (mirror) might also be bootable, I'm not sure about that; but a RAID0 (stripe) certainly isn't. There are many new SATA "RAID" controllers that our ATA driver doesn't yet understand the metadata. Soren is working on support for these newer chipsets. -- -- David (obrien@FreeBSD.org)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041130230659.GA30089>