Date: Tue, 1 Jun 2004 18:03:39 -0700 From: Brooks Davis <brooks@one-eyed-alien.net> To: "Kenneth D. Merry" <ken@kdm.org> Cc: Tuc at Beach House <tuc@ttsg.com> Subject: Re: 1TB issue Message-ID: <20040602010339.GA29173@Odin.AC.HMC.Edu> In-Reply-To: <20040602005625.GA73344@panzer.kdm.org> References: <20040602004318.GA73188@panzer.kdm.org> <200406020052.i520qhXc038253@himinbjorg.tucs-beachin-obx-house.com> <20040602005625.GA73344@panzer.kdm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--zhXaljGHf11kAtnf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 01, 2004 at 06:56:25PM -0600, Kenneth D. Merry wrote: > On Tue, Jun 01, 2004 at 20:52:43 -0400, Tuc at Beach House wrote: > > >=20 > > > On Tue, Jun 01, 2004 at 19:53:24 -0400, Tuc at Beach House wrote: > > > > > > What can I do to get this configured properly? It seems= that if I > > > > > > bring it down to RAID-1+0, it configures up fine (Not sure what= the > > > > > > geometry shows as, sorry). > > > > >=20 > > > > > See another recent message on this list from Brooks Davis. It so= unds like > > > > > sysinstall has issues with large arrays in -current, but fdisk wo= rks okay. > > > > >=20 > > > > > Try doing your installation on a smaller fdisk partition within s= ysinstall, > > > > > and then once you're installed, use the command line fdisk to cre= ate > > > > > another slice and use up the rest of the array. > > > > >=20 > > > > This is a 2nd drive, so its ok. I already have 5.2.1-RELEASE-p4=20 > > > > installed on /dev/da1. > > > >=20 > > > > If I just do : > > > >=20 > > > > vjofn2# fdisk da0 > > > > ******* Working on device /dev/da0 ******* > > > > parameters extracted from in-core disklabel are: > > > > cylinders=3D135154 heads=3D255 sectors/track=3D63 (16065 blks/cyl) > > > >=20 > > > > Figures below won't work with BIOS for partitions not in cyl 1 > > > > parameters to be used for BIOS calculations are: > > > > cylinders=3D135154 heads=3D255 sectors/track=3D63 (16065 blks/cyl) > > > >=20 > > > > Media sector size is 512 > > > > Warning: BIOS sector numbering starts with sector 1 > > > > Information from DOS bootblock is: > > > > The data for partition 1 is: > > > > sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > > > > start 63, size 2171248947 (1060180 Meg), flag 80 (active) > > > > beg: cyl 0/ head 1/ sector 1; > > > > end: cyl 1023/ head 254/ sector 63 > > > > The data for partition 2 is: > > > > <UNUSED> > > > > The data for partition 3 is: > > > > <UNUSED> > > > > The data for partition 4 is: > > > > <UNUSED> > > > >=20 > > > >=20 > > > > So what config to command line fdisk should I use? > > > >=20 > > > > p 1 0 0 0 > > > > p 1 165 1 2171249010 > > > >=20 > > >=20 > > > It looks like you may already have a partition there...it looks like = it's > > > about 1TB. > > >=20 > > > Do things work when you attempt to disklabel it? > > >=20 > > Fatal Error: Partitions are larger than actual chunk?? - PRESS ANY KEY = TO QUIT > >=20 > >=20 > > Won't let me go any farther. >=20 > You might try "dangerously dedicated" mode, assuming it works. First, bl= ow > away your fdisk table: >=20 > dd if=3D/dev/zero of=3D/dev/da0 bs=3D1m count=3D1 >=20 > Then try generating a label automatically: >=20 > bsdlabel -wr da0 auto >=20 > Then edit the label, and fix up the partition type, etc.: >=20 > bsdlabel -e da0 >=20 > If that works you should be able to newfs da0a, or whatever letter > partition you setup in the previous step. I'm not sure what the limit of a BSD label is, but it my be 1TB unless you can up the block size (512K blocks plus signed ints yeilds 1TB limits). You may want to use fdisk to make a slice for any large partitions rather then trying to use disklabel. On the 2TB system I have, I have one slice that is around 40GB that contains a disklabel and the partions making up a normal OS install. A second slice that has a 1.8TB UFS file system and no disklabel. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --zhXaljGHf11kAtnf Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFAvSdrXY6L6fI4GtQRAmkOAKC5JQr9IxW+OaZjfDOU3EMB0zzytQCfaE1m Y0S4MrcJzZAdje9k6W6pQFM= =8iZe -----END PGP SIGNATURE----- --zhXaljGHf11kAtnf--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040602010339.GA29173>