Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 18 May 2000 08:08:49 -0400 (EDT)
From:      David Miller <dmiller@search.sparks.net>
To:        Mike Boto <bl29x5@earthlink.net>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Partition size
Message-ID:  <Pine.BSF.4.21.0005180756580.24997-100000@search.sparks.net>
In-Reply-To: <000f01bfc078$50cbb840$1252d03f@oemcomputer>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 17 May 2000, Mike Boto wrote:

> I tried using several alternate setups in the BIOS config, and it always
> reverted back to the same thing:
> "Mode: User
>  Cylinder: 4092
>  ...et al
> "
> As for a second partition, I cannot add anything whatsoever because fdisk
> believes the capacity of the hard drive to be entirely mapped out (900MB in
> DOS
> and 1100 in BSD), leaving another 14GB free yet ignored.

What version of FreeBSD are you running?  What does disklabel report?

When I recently setup a 20 GB maxtor to dual boot NT and FreeBSD I was
having a really hard time getting the boot sections of both within the
1024 cylinder limit, and my bios wasn't giving me much assistance.

Eventually I found I could, on the original installation, partition the
disk with a 64 MB partition for unix root, then a 5 GB partition for NT,
then the balance for unix.  NT then had to break it down to a 1 and 4 GB
partitions.  So the big unix partition ended up being slice 4.

su-2.03# disklabel ad0
# /dev/ad0c:
type: ESDI
disk: wd2s1
label: 
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 32
sectors/cylinder: 2016
cylinders: 64
sectors/unit: 130977
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0           # milliseconds
track-to-track seek: 0  # milliseconds
drivedata: 0 

8 partitions:
#        size   offset    fstype   [fsize bsize bps/cpg]
  a:   130977        0    4.2BSD        0     0     0   # (Cyl.    0 -
64*)
  c:   130977        0    unused        0     0         # (Cyl.    0 -
64*)


and

# /dev/ad0s4c:
type: ESDI
disk: wd2s4
label: 
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 32
sectors/cylinder: 2016
cylinders: 14707
sectors/unit: 29649312
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0           # milliseconds
track-to-track seek: 0  # milliseconds
drivedata: 0 

8 partitions:
#        size   offset    fstype   [fsize bsize bps/cpg]
  b:  1048576        0      swap                        # (Cyl.    0 -
520*)
  c: 29649312        0    unused        0     0         # (Cyl.    0 -
14706)
  e:  8388608  1048576    4.2BSD     1024  8192    16   # (Cyl.  520*-
4681*)
  f: 20212128  9437184    4.2BSD     1024  8192    16   # (Cyl. 4681*-
14706*)

This makes the fstab look a little funny:

su-2.03# cat /etc/fstab
# Device                Mountpoint      FStype  Options         Dump
Pass#
/dev/ad0s4b             none            swap    sw              0       0
/dev/ad0s1a             /               ufs     rw              1       1
/dev/ad0s4f             /usr            ufs     rw              2       2
/dev/ad0s4e             /usr2           ufs     rw              2       2
/dev/cd0c               /cdrom  cd9660  ro,noauto       0       0
proc                    /proc           procfs  rw              0       0


The generic kernel should see the whole drive when booting, allowing you
to setup the disk partitions like I did.  My dmesg has this:

ad0: 19541MB <Maxtor 52049U4> [39703/16/63] at ata0-master using UDMA33
ad2: 29311MB <Maxtor 53073U6> [59554/16/63] at ata1-master using UDMA33


which certainly makes it look like freebsd is seeing the whole drive, not
just what the bios is reporting.

HTH,

--- David



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0005180756580.24997-100000>