Date: Fri, 6 Feb 2004 14:32:34 -0500 From: "Philippe Dorman" <phil@skyscrapes.com> To: <freebsd-fs@freebsd.org> Subject: WD160 + Drive geometry problem Message-ID: <20040206193318.DA11443D4C@mx1.FreeBSD.org>
next in thread | raw e-mail | index | archive | help
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=20 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 =A01K-blocks =A0 =A0 Used =A0 =A0 Avail Capacity =A0Mounted = on /dev/ad4s1a =A0 =A0253678 =A0 251702 =A0 =A0-18318 =A0 108% =A0 =A0/ devfs =A0 =A0 =A0 =A0 =A0 =A0 =A0 1 =A0 =A0 =A0 =A01 =A0 =A0 =A0 =A0 0 = =A0 100% =A0 =A0/dev /dev/ad4s1e =A0 =A0253678 =A0 =A0 =A0 =A02 =A0 =A0233382 =A0 =A0 0% =A0 = =A0/tmp /dev/ad4s1f =A018121388 =A02997228 =A013674450 =A0 =A018% =A0 =A0/usr /dev/ad4s1d =A0 =A0253678 =A0 =A033436 =A0 =A0199948 =A0 =A014% =A0 = =A0/var /dev/ad7s1 =A0151368706 =A0 =A0 =A0 =A02 139259208 =A0 =A0 0% =A0 = =A0/hd1 /dev/ad6s1 =A0 38879438 32184422 =A0 3584662 =A0 =A090% =A0 =A0/hd2 /dev/ad5s1 =A0 75685352 69630522 =A0 =A0 =A0 =A0 2 =A0 100% =A0 =A0/hd3 Then disklabel ad7s1 (starts to get interesting here - 8 partitions?) # /dev/ad7s1: 8 partitions: # =A0 =A0 =A0 =A0size =A0 offset =A0 =A0fstype =A0 [fsize bsize bps/cpg] =A0c: 312576642 =A0 =A0 =A0 63 =A0 =A0unused =A0 =A0 =A0 =A00 =A0 =A0 0 = =A0 =A0 =A0 =A0 # "raw" part, don't edit =A0d: 312576642 =A0 =A0 =A0 63 =A0 =A04.2BSD =A0 =A0 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040206193318.DA11443D4C>