WD160 + Drive geometry problem
Philippe Dorman
phil at skyscrapes.com
Fri Feb 6 11:33:20 PST 2004
Hiya,
I recently got a 160 gig hard drive, it seems to be mounted
properly, partitions and slices "seem" fine, yet I cant write more than 2k
to the disk, it's just as if there wasn't any free space left. I'm using a
Promise Ultra ATA/133 controller, which does support drives greater than 137
gigs so that shouldn't be the problem. I'm running 5.1-Current. Here's the
output to a couple commands
First from dmesg
ad4: 19546MB <FUJITSU MPG3204AT E> [39714/16/63] at ata2-master UDMA100
ad5: 76319MB <WDC WD800BB-00CAA1> [155061/16/63] at ata2-slave UDMA100
ad6: 39205MB <Maxtor 6E040L0> [79656/16/63] at ata3-master UDMA133
ad7: 152627MB <WDC WD1600JB-00EVA0> [310101/16/63] at ata3-slave UDMA100
df
Filesystem 1K-blocks Used Avail Capacity Mounted on
/dev/ad4s1a 253678 251702 -18318 108% /
devfs 1 1 0 100% /dev
/dev/ad4s1e 253678 2 233382 0% /tmp
/dev/ad4s1f 18121388 2997228 13674450 18% /usr
/dev/ad4s1d 253678 33436 199948 14% /var
/dev/ad7s1 151368706 2 139259208 0% /hd1
/dev/ad6s1 38879438 32184422 3584662 90% /hd2
/dev/ad5s1 75685352 69630522 2 100% /hd3
Then disklabel ad7s1 (starts to get interesting here - 8 partitions?)
# /dev/ad7s1:
8 partitions:
# size offset fstype [fsize bsize bps/cpg]
c: 312576642 63 unused 0 0 # "raw" part, don't
edit
d: 312576642 63 4.2BSD 2048 16384 28552
partition c: partition extends past end of unit
disklabel: partition c doesn't start at 0!
disklabel: An incorrect partition c may cause problems for standard system
utilities
partition d: partition extends past end of unit
I'm not sure if it has to do with the drive geometry, I stuck the drive in
my windows box and got the following geometry, 16709/255/63 (however it
wasn't recognizing more than 137gig). When I use the fdisk utility it tells
me that the geometry of 310101/16/63 (which is what you can find on the
western digital website in the drive specs) is incorrect, and that it is
using a more likely geometry. I try to set it back to the default, but the
changes don't seem to "stick", or change the fact that I can't use the hard
disk. Any help is appreciated!
-Phil
More information about the freebsd-fs
mailing list