From owner-freebsd-scsi Tue Oct 8 15: 3:21 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A06837B401 for ; Tue, 8 Oct 2002 15:03:20 -0700 (PDT) Received: from russell.hamline.edu (russell.hamline.edu [138.192.24.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id D059D43E65 for ; Tue, 8 Oct 2002 15:03:19 -0700 (PDT) (envelope-from rjohanne@piper.hamline.edu) Received: from piper.hamline.edu (piper.hamline.edu [138.192.2.101]) by russell.hamline.edu (8.11.6+Sun/8.11.6) with ESMTP id g97JKD727515 for ; Mon, 7 Oct 2002 14:20:14 -0500 (CDT) Received: from mendeleev.hamline.edu (mendeleev [138.192.2.109]) by piper.hamline.edu (8.12.6/8.12.6) with ESMTP id g97JKMaP001954 for ; Mon, 7 Oct 2002 14:20:22 -0500 (CDT) Received: from localhost (rjohanne@localhost) by mendeleev.hamline.edu (8.9.1b+Sun/8.9.1) with ESMTP id OAA01323 for ; Mon, 7 Oct 2002 14:19:48 -0500 (CDT) X-Authentication-Warning: mendeleev.hamline.edu: rjohanne owned process doing -bs Date: Mon, 7 Oct 2002 14:19:48 -0500 (CDT) From: Robert Johannes X-X-Sender: rjohanne@mendeleev.hamline.edu To: freebsd-scsi Subject: Adding a second scsi drive In-Reply-To: <200210071802.g97I2ddY087822@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I just physically installed a second scsi drive. It is a quantum viking II 9.1 gig, target 6, lun0. The scsi controller is tekram's xx875, using the sym driver. The driver sees the drive as da1, recognizes the cyl/heads/sectors, and all that stuff. When I try to add the drive to freebsd (4.7-Prerelease, which I think is 4.6-stable) using /stand/sysinstall, fdisk fails saving the label to disk, and so does disklabel. If I try it via the command line, with dd and disklabel, I get "/dev/da1: permission denied". I know that the drive is not write protected, because the jumber is not installed to write protect it. It is also a new drive. Is there a step I'm missing? My intuition tells me that maybe there's nothing at /dev/da1, but if that's the case, then the system should not report in the boot messages that there's a da1? Help would ve very appreciated. robert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message