FWIW, we have a 6.0-RELEASE machine running now with two 2TB
partitions, using disklabel(bsdlabel) rather than gpt. This is with
the 3ware driver. Could the problem you're having be with the arcmsr
driver in some way? Anyone else on the list using that card able to
confirm it?
On 11/11/05, David Kirchner [EMAIL PROTECTED] wrote:
On 11/10/05, Xin LI [EMAIL PROTECTED] wrote:
Would you please consider to try gpt instead of bsdlabel?
BTW. The dmesg meesage indicates that your array is degraded :-(
Is it possible to have sysinstall use gpt instead of bsdlabel, and
On 11/9/05, Barkley Vowk [EMAIL PROTECTED] wrote:
I've got a 3TB (7 x 500GB w/ hot-spare) array on an areca board in amd64.
Under 5.4-R I could have 1TB filesystems without an issue. I recall not
having problems with 6.0-BETA5 too.
[snip]
Would you please consider to try gpt instead of
On 11/9/05, Barkley Vowk [EMAIL PROTECTED] wrote:
I've got a 3TB (7 x 500GB w/ hot-spare) array on an areca board in amd64.
Under 5.4-R I could have 1TB filesystems without an issue. I recall not
having problems with 6.0-BETA5 too.
However, 6.0-R gives me a tragic:
/dev/da0s1d723G
On 11/9/05, Barkley Vowk [EMAIL PROTECTED] wrote:
No. The installer showed only one slice da0s1d, and the whole disk was
assigned to it.
I'd check on the running box but:
koth# disklabel -e /dev/da0
disklabel: disks with more than 2^32-1 sectors are not supported
/dev only shows:
koth# ls
On 11/10/05, Xin LI [EMAIL PROTECTED] wrote:
Would you please consider to try gpt instead of bsdlabel?
BTW. The dmesg meesage indicates that your array is degraded :-(
Is it possible to have sysinstall use gpt instead of bsdlabel, and
then to boot from a gpt based array? I haven't had luck
I've got a 3TB (7 x 500GB w/ hot-spare) array on an areca board in amd64.
Under 5.4-R I could have 1TB filesystems without an issue. I recall not
having problems with 6.0-BETA5 too.
However, 6.0-R gives me a tragic:
/dev/da0s1d723G 54G611G 8%/home
Certainly not what I
No. The installer showed only one slice da0s1d, and the whole disk was
assigned to it.
I'd check on the running box but:
koth# disklabel -e /dev/da0
disklabel: disks with more than 2^32-1 sectors are not supported
/dev only shows:
koth# ls /dev/da0*
/dev/da0/dev/da0s1 /dev/da0s1c
On Wed, Nov 09, 2005 at 01:09:50PM -0700, Barkley Vowk wrote:
No. The installer showed only one slice da0s1d, and the whole disk was
assigned to it.
I'd check on the running box but:
koth# disklabel -e /dev/da0
disklabel: disks with more than 2^32-1 sectors are not supported
Exactly from
