Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 21 Aug 2000 10:51:15 -0500
From:      "Travis Leuthauser" <travis-lists@winconx.com>
To:        "Greg Lehey" <grog@lemis.com>, "John Paul Lonie" <jplonie@optushome.com.au>
Cc:        <freebsd-questions@FreeBSD.ORG>
Subject:   Re: Large Hard drives > 45GB
Message-ID:  <00c301c00b87$a39734a0$20503cd0@travis>
References:  <001001c009af$d127ff00$14cea8c0@whitestar> <20000820104457.B4230@wantadilla.lemis.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Along the lines of a large IDE drives under 3.X.  I added 2 45 Gig IDE
drives to a 3.5 system which during the newfs and/or mounting gave no
apparent problems, but when when writing to them they developed bad
superblocks and just generally freaked out on me.  The upgrade to 4.0 solved
all of my problems.

Travis Leuthauser
Network Administrator
WinConX Online, Inc.

----- Original Message -----
From: "Greg Lehey" <grog@lemis.com>
To: "John Paul Lonie" <jplonie@optushome.com.au>
Cc: <freebsd-questions@FreeBSD.ORG>
Sent: Saturday, August 19, 2000 8:14 PM
Subject: Re: Large Hard drives > 45GB


> [Format recovered--see http://www.lemis.com/email/email-format.html]
>
> > X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
> > X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
>
> On Saturday, 19 August 2000 at 17:33:48 +1000, John Paul Lonie wrote:
> > Hello all,
> >
> > Can some one tell me the current state of large IDE HD's under
> > FreeBSD 3.5 and 4.x I have a nice new IBM 45 GB hard drive and it
> > doesn't want to play ball under 3.5 ...
>
> 4.x has a new IDE driver, which doesn't have any documented problems
> with large drives.
>
> > I have split it up to 3 partitions, ( 20, 20, 5 ) and I can
> > mkfs all of the fine . and mount them too ... but a cd to the first
> > partition causes the error listed below..
> >
> > su-2.03# uname -a
> > FreeBSD babylon5.lonie.dropbear.id.au 3.5-STABLE FreeBSD 3.5-STABLE #7:
Tue
> > Aug 15 23:14:26 EST 2000
> > root@babylon5.lonie.dropbear.id.au:/usr/src/sys/compile/BABYLON  i386
> >
> > bash-2.03$ df
> > Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
> > /dev/wd2s1e  19849974        1 18261976     0%    /mnt/a
> > /dev/wd2s1f  19849974        1 18261976     0%    /mnt/b
> > /dev/wd2s1g   3944145        1  3628613     0%    /mnt/c
> >
> > bash-2.03$ cd /mnt/a
> > bash: cd: /mnt/a: Not a directory
>
> Is this the error you're implying?  It would be nice to know whether
> you had any problems with newfs or mount.  Are there any files on it?
> What other history?  How does your treatment of this partition compare
> to that of partitions f or g?
>
> > bash-2.03$ fdisk /dev/wd2
> > ******* Working on device /dev/wd2 *******
> > parameters extracted from in-core disklabel are:
> > cylinders=5606 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=5606 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,(FreeBSD/NetBSD/386BSD)
> >     start 63, size 90060327 (43974 Meg), flag 80 (active)
> >         beg: cyl 0/ sector 1/ head 1;
> >         end: cyl 1023/ sector 63/ head 254
> > The data for partition 2 is:
> > <UNUSED>
> > The data for partition 3 is:
> > <UNUSED>
> > The data for partition 4 is:
> > <UNUSED>
> >
> > su-2.03# disklabel -r wd2
> > 8 partitions:
>
> Please don't wrap these lines.
>
> > #        size   offset    fstype   [fsize bsize bps/cpg]
> >   c: 90060327        0    unused        0     0         # (Cyl.    0 -
5605*)
> >   e: 40960000        0    4.2BSD     1024  8192    16   # (Cyl.    0 -
2549*)
> >   f: 40960000 40960000    4.2BSD     1024  8192    16   # (Cyl. 2549*-
5099*)
> >   g:  8140327 81920000    4.2BSD     1024  8192    16   # (Cyl. 5099*-
5605*)
>
> There's nothing particularly surprising about the disk label.  It
> might be yet another "big drive" problem with the wd driver.  I'd hope
> that the ad driver would do better.
>
> Greg
> --
> When replying to this message, please copy the original recipients.
> For more information, see http://www.lemis.com/questions.html
> Finger grog@lemis.com for PGP public key
> See complete headers for address and phone numbers
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-questions" in the body of the message
>



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?00c301c00b87$a39734a0$20503cd0>