1TB issue

[Brooks Davis]

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:
> > > 
> > > 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).
> > > > > 
> > > > > See another recent message on this list from Brooks Davis.  It sounds like
> > > > > sysinstall has issues with large arrays in -current, but fdisk works okay.
> > > > > 
> > > > > Try doing your installation on a smaller fdisk partition within sysinstall,
> > > > > and then once you're installed, use the command line fdisk to create
> > > > > another slice and use up the rest of the array.
> > > > > 
> > > > 	This is a 2nd drive, so its ok. I already have 5.2.1-RELEASE-p4 
> > > > installed on /dev/da1.
> > > > 
> > > > 	If I just do :
> > > > 
> > > > vjofn2# fdisk da0
> > > > ******* Working on device /dev/da0 *******
> > > > parameters extracted from in-core disklabel are:
> > > > cylinders=135154 heads=255 sectors/track=63 (16065 blks/cyl)
> > > > 
> > > > Figures below won't work with BIOS for partitions not in cyl 1
> > > > parameters to be used for BIOS calculations are:
> > > > cylinders=135154 heads=255 sectors/track=63 (16065 blks/cyl)
> > > > 
> > > > 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>
> > > > 
> > > > 
> > > > 	So what config to command line fdisk should I use?
> > > > 
> > > > p	1	0	0	0
> > > > p	1	165	1	2171249010
> > > > 
> > > 
> > > It looks like you may already have a partition there...it looks like it's
> > > about 1TB.
> > > 
> > > Do things work when you attempt to disklabel it?
> > > 
> > Fatal Error: Partitions are larger than actual chunk?? - PRESS ANY KEY TO QUIT
> > 
> > 
> > 	Won't let me go any farther.
> 
> You might try "dangerously dedicated" mode, assuming it works.  First, blow
> away your fdisk table:
> 
> dd if=/dev/zero of=/dev/da0 bs=1m count=1
> 
> Then try generating a label automatically:
> 
> bsdlabel -wr da0 auto
> 
> Then edit the label, and fix up the partition type, etc.:
> 
> bsdlabel -e da0
> 
> 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

-- 
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-scsi/attachments/20040601/072d0275/attachment.bin