Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 14 Apr 2000 17:48:28 -0400
From:      Otter <otter@otter.cc>
To:        Oscar Ricardo Silva <oscars@mail.utexas.edu>
Cc:        freebsd-questions@FreeBSD.ORG
Subject:   Re: Large disks (34GB), mounting and newfs problems
Message-ID:  <38F7922C.B936D566@otter.cc>
References:  <4.2.2.20000414161740.00a82a60@mail.utexas.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
Oscar Ricardo Silva wrote:
> 
> I was following the question of problems mounting a drive and now, I'm
> having some of the same problems.  This is a second drive in the system,
> connected as a slave to the first IDE drive.  It's an IBM Deskstar 34GXP,
> DPTA-373420.  I apologize for the length of the message but I did want to
> demonstrate that I followed the previous suggestions and was getting the
> right responses.  Here's the output from /var/log/messages:
> 
> Apr 14 16:22:16 amanda /kernel: wdc0 at 0x1f0-0x1f7 irq 14 on isa
> Apr 14 16:22:16 amanda /kernel: wdc0: unit 0 (wd0): <WDC WD136AA>
> Apr 14 16:22:16 amanda /kernel: wd0: 12971MB (26564832 sectors), 26354
> cyls, 16 heads, 63 S/T, 512 B/S
> Apr 14 16:22:16 amanda /kernel: wdc0: unit 1 (wd1): <IBM-DPTA-373420>
> Apr 14 16:22:17 amanda /kernel: wd1: 32634MB (66835440 sectors), 66305
> cyls, 16 heads, 63 S/T, 512 B/S
> 
> I issued the command "fdisk wd1" and received the following:
> 
> amanda# fdisk wd1
> ******* Working on device /dev/rwd1 *******
> parameters extracted from in-core disklabel are:
> cylinders=66305 heads=16 sectors/track=63 (1008 blks/cyl)
> 
> Figures below won't work with BIOS for partitions not in cyl 1
> parameters to be used for BIOS calculations are:
> cylinders=66305 heads=16 sectors/track=63 (1008 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 0, size 66835440 (32634 Meg), flag 80 (active)
>          beg: cyl 0/ sector 1/ head 0;
>          end: cyl 1023/ sector 63/ head 15
> The data for partition 2 is:
> <UNUSED>
> The data for partition 3 is:
> <UNUSED>
> The data for partition 4 is:
> <UNUSED>
> 
> I then issued the command "disklabel wd1s1" and received the following:
> 
> amanda# disklabel wd1s1
> # /dev/rwd1s1c:
> type: ESDI
> disk: wd1s1
> label:
> flags:
> bytes/sector: 512
> sectors/track: 63
> tracks/cylinder: 16
> sectors/cylinder: 1008
> cylinders: 66305
> sectors/unit: 66835440
> 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]
>    c: 66835440        0    unused        0     0         # (Cyl.    0 - 66304)
> 
> OK, so far so good.  I can then mount the drive without any problems:
> 
> amanda# mount /dev/wd1s1c /dump
> 
> which returns without any errors.
> 
> Here's the big problem, I try to run "newfs" with the following command,
> and when I get to the same block each time, 66781216, the machine reboots
> itself.  Here's the output from the command:
> 
> amanda# newfs -b 8192 -f 1024 /dev/wd1s1c
> newfs: /dev/wd1s1c: not a character-special device
> Warning: 3088 sector(s) in last cylinder unallocated
> /dev/wd1s1c:    66835440 sectors in 16318 cylinders of 1 tracks, 4096 sectors
>          32634.5MB in 1020 cyl groups (16 c/g, 32.00MB/g, 7936 i/g)
> super-block backups (for fsck -b #) at:
>   32, 65568, 131104, 196640, 262176, 327712, 393248, 458784, 524320, 589856,
> ...
>   65601568, 65667104, 65732640, 65798176, 65863712, 65929248, 65994784,
> 66060320,
>   66125856, 66191392, 66256928, 66322464, 66388000, 66453536, 66519072,
> 66584608,
>   66650144, 66715680, 66781216,
> 
> If anybody has any information or pointers on where I can find the
> solution, I would VERY much appreciate it.
> 
> Thanks,
> 
> Oscar
> 
IIRC, there was a bug in the wd driver that made it hiccup on disks
>27GB. If you're running under 3.x or 4.0, try upgrading to the ata (ad) driver for a fix.
-Otter


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?38F7922C.B936D566>