Date: Thu, 11 Jan 2007 20:59:31 -0800 From: Jo Rhett <jrhett@svcolo.com> To: Jan Mikkelsen <janm@transactionware.com> Cc: freebsd-stable@freebsd.org Subject: Re: 2.4TB disk - MBR and GPT coexist? Message-ID: <5F856114-C2FC-4567-BBBF-3AEC86AFCD90@svcolo.com> In-Reply-To: <000901c735fc$d180ac10$3301a8c0@janmxp> References: <45A5FD8A.6080409@svcolo.com><2918081F-D376-410B-B6FD-42BDD3323575@svcolo.com><20070111213444.GB17185@zone3000.net><D0D0CE06-B991-4945-B12B-152BA930106B@svcolo.com><20070112005510.2e145462.torfinn.ingolfsen@broadpark.no> <669E8D5D-E286-42DC-800F-24D7DDB2469F@svcolo.com> <000901c735fc$d180ac10$3301a8c0@janmxp>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 11, 2007, at 7:50 PM, Jan Mikkelsen wrote: > For example, on an Areca 8 port controller, I have 8 disks in a > RAID-6 array, and within that "RAID set", I have three volumes. > The three volumes appear to FreeBSD as da0, da1 and da2, respectively. > > CLI> rsf info I would like to note that you're showing me post-boot information. All of the problems I am describing prevent bootup. I have the 3ware controller splitting the array into two LUNS. I can't configure it except to tell it to split on the 2TB boundary, so I end up with the large disk as the first device, when I'd rather put the OS and everything on a smaller disk. And from what I'm guessing (with no useful information from the boot2 prompt) I won't be able to boot from the second disk, probably because it's created by the twa device driver which doesn't exist yet. So... array volume management that comes into play after booting is irrelevant to my needs :-( -- Jo Rhett senior geek Silicon Valley Colocation
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5F856114-C2FC-4567-BBBF-3AEC86AFCD90>