From owner-freebsd-questions Thu Jul 30 14:25:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27464 for freebsd-questions-outgoing; Thu, 30 Jul 1998 14:25:55 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from mail.websidestory.com (mail.websidestory.com [209.75.20.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27434 for ; Thu, 30 Jul 1998 14:25:37 -0700 (PDT) (envelope-from vansax@mail.websidestory.com) Received: from localhost (vansax@localhost) by mail.websidestory.com (8.8.7/8.8.5) with SMTP id OAA23683; Thu, 30 Jul 1998 14:25:27 -0700 (PDT) Date: Thu, 30 Jul 1998 14:25:27 -0700 (PDT) From: Jim Van Baalen To: Doug White cc: questions@FreeBSD.ORG Subject: Re: Can't Newfs Disk In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Perhaps I am making progress. I followed the procedures in http://www.freebsd.org/tutorials/diskformat/ Upon completion of section 2.2 step 9 I receive the response "Wrote FDISK partion infomation out successfully." Simulteneously Jul 30 14:00:58 spare /kernel: sd1(ncr0:2:0): Deferred Error: HARDWARE FAILURE asc:3,0 Peripheral device write fault field replaceable unit: 4 sks:80,e3 Jul 30 14:01:00 spare /kernel: sd1(ncr0:2:0): Deferred Error: HARDWARE FAILURE asc:3,0 Peripheral device write fault field replaceable unit: 4 sks:80,e3 was written to /var/log/messages. Thus, I assume that the response from /stand/sysinstall was inaccurate. Does this imply a hardware problem (ie. the disk is bad)? Jim On Wed, 29 Jul 1998, Doug White wrote: > > 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