From owner-freebsd-questions  Wed Jul 29 16:01:52 1998
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA22958
          for freebsd-questions-outgoing; Wed, 29 Jul 1998 16:01:52 -0700 (PDT)
          (envelope-from owner-freebsd-questions@FreeBSD.ORG)
Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA22921
          for <questions@FreeBSD.ORG>; Wed, 29 Jul 1998 16:01:42 -0700 (PDT)
          (envelope-from dwhite@resnet.uoregon.edu)
Received: from localhost (dwhite@localhost)
          by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id QAA17827;
          Wed, 29 Jul 1998 16:01:04 -0700 (PDT)
          (envelope-from dwhite@resnet.uoregon.edu)
Date: Wed, 29 Jul 1998 16:01:04 -0700 (PDT)
From: Doug White <dwhite@resnet.uoregon.edu>
To: Jim Van Baalen <vansax@mail.websidestory.com>
cc: questions@FreeBSD.ORG
Subject: Re: Can't Newfs Disk
In-Reply-To: <Pine.BSI.3.96.980728154846.18204E-100000@mail.websidestory.co
 m>
Message-ID: <Pine.BSF.4.00.9807291559070.24795-100000@resnet.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On Tue, 28 Jul 1998, Jim Van Baalen wrote:

> I have just added a second disk to a machine and I can't newfs a
> filesystem on this disk. I have been through this process several
> times in the last week on different machines and have not had this
> problem. The machine is running 2.2.6-RELEASE. It sees the second 
> disk at boot time
> 
> Jul 28 13:49:07 host2 /kernel: sd1(ahc0:2:0): Direct-Access 4340MB (8888924 512 byte sectors)
> 
> It seems to accept a disklabel. I added 
> 
> st34572w|Seagate ST34572W SCSI: \
>         :dt=SCSI:ty=winchester:se#512:nt#8:ns#176:nc#6300: \
>         :pc#8870400:oc#0:
> 
> to /etc/disktab.
> 
> disklabel -r -w sd1 st34572w

Um, you just overwote your slice table.  You should have said

disklabel -r -w sd1s4 st .... 

> returns no errors, but newfs fails.
> 
> newfs -N /dev/rsd1c
> newfs: ioctl (GDINFO): Invalid argument
> newfs: /dev/rsd1c: can't read disk label; disk type must be specified

Try /dev/rsd1s4c instead.

> The data for partition 4 is:
> sysid 165,(FreeBSD/NetBSD/386BSD)
>     start 1, size 8870399 (4331 Meg), flag 80
>         beg: cyl 0/ sector 2/ head 0;
>         end: cyl 155/ sector 48/ head 7

This is fudged, but the entire slice table is fubar'd.  :(  I don't know
if you'll be able to reboot your system until you fix the fdisk damage you
caused with disklabel (unless this is a Dangerously Dedicated disk).

See http://www.freebsd.org/tutorials/diskformat/.

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major


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