From owner-freebsd-questions Thu Aug 17 16:55:14 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id QAA18771 for questions-outgoing; Thu, 17 Aug 1995 16:55:14 -0700 Received: from io.org (io.org [142.77.70.2]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id QAA18759 for ; Thu, 17 Aug 1995 16:55:09 -0700 Received: from trepan.io.org (apollo@trepan.io.org [198.133.36.8]) by io.org (8.6.12/8.6.12) with SMTP id TAA12438; Thu, 17 Aug 1995 19:54:59 -0400 Date: Thu, 17 Aug 1995 19:54:59 -0400 (EDT) From: Andrew Herdman To: "Charles N. Owens" cc: questions list FreeBSD Subject: Re: HELP!: adding second disk In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: questions-owner@freebsd.org Precedence: bulk On Thu, 17 Aug 1995, Charles N. Owens wrote: > Hello, > I've tried to figure this out, but am having trouble. I'm trying to add > a second drive to my system. It's a Seagate ST15230W SCSI-2 WIDE 4 GIG > drive. The controller and FBSD recognize it's existence fine, but I'm > having trouble attacking it with fdisk and disklabel. > > Is the correct procedure for me to: > 1. fdisk -u > Make one partition, type 165, using whole drive. > 2. Add entry to /etc/disktab defining my drive. > 3. do a disklabel -r -w /dev/sd1 st15320w > ? > > I tried the fdisk step, and it seems to be fixated on what the BIOS > thinks. Does it mean the SCSI controller BIOS or the system BIOS? I > don't think that the system BIOS should know a thing about either of my > SCSI drives. Fdisk kept telling my that the #of tracks is 90, when I know > it's 114, and when I try to tell it differently, it doesn't budge. > > Here is my new /etc/disktab entry: > > st15230w|Seagate ST15230W 4 Gig SCSI-2 WIDE:\ > :dt=SCSI:ty=winchester:se#512:nt#19:ns#114:nc#3992:\ > :pa#192774:oa#0:ta=swap:\ > :pb#197106:ob#192774:bb#4096:fa#512:tb=4.2BSD:\ > :pc#8646672:oc#0:\ > :pd#8256792:od#389880:bd#4096:fd#512:td=4.2BSD:\ > > Should this be OK? Of course, when I tried to run disklabel, I get the > following: ioctl DIOCWLABEL: Operation not supported by device, > but I wouldn't expect it to work in light of the trouble I'm having with > fdisk. > > Could someone shed some light on this situation? I get this error as well from my WORM drive (it has a controller that emulates a normal disk). This is the error i get with both disklabel and fdisk disklabel: ioctl DIOCWDINFO: Operation not supported by device as the above author stated... HELP! Andrew