|Tu...@Beach House||Jun 1, 2004 4:04 pm|
|Kenneth D. Merry||Jun 1, 2004 4:40 pm|
|Tu...@Beach House||Jun 1, 2004 4:53 pm|
|Kenneth D. Merry||Jun 1, 2004 5:43 pm|
|Tu...@Beach House||Jun 1, 2004 5:52 pm|
|Kenneth D. Merry||Jun 1, 2004 5:56 pm|
|Brooks Davis||Jun 1, 2004 6:03 pm|
|Tu...@Beach House||Jun 1, 2004 6:12 pm|
|Paul Saab||Jun 1, 2004 11:36 pm|
|David Malone||Jun 2, 2004 2:49 am|
|Bruce Evans||Jun 2, 2004 3:51 am|
|Kenneth D. Merry||Jun 2, 2004 6:11 am|
|Dan Strick||Jun 2, 2004 6:35 am|
|From:||Tu...@Beach House (...@)|
|Date:||Jun 1, 2004 5:52:35 pm|
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.