From owner-freebsd-questions@FreeBSD.ORG Fri Nov 14 08:54:26 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8424C16A4CE for ; Fri, 14 Nov 2003 08:54:26 -0800 (PST) Received: from yoda.anything-inc.com (adsl-068-153-193-052.sip.bct.bellsouth.net [68.153.193.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2306043FE5 for ; Fri, 14 Nov 2003 08:54:23 -0800 (PST) (envelope-from freebsd@anything-inc.com) X-AuthUser: freebsd@anything-inc.com Received: from neo.anything-inc.com (68.153.193.50:3099)Server] ; Fri, 14 Nov 2003 12:03:21 -0500 Message-Id: <5.2.0.9.0.20031114105727.00a9d6d8@anything-inc.com> X-Sender: freebsd@anything-inc.com@anything-inc.com X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Fri, 14 Nov 2003 11:50:09 -0500 To: FreeBSD From: Bob Collins Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Status: No, hits=0.0 required=3.5 tests=none version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) Subject: Disklabel problem IBM SCSI3 disks, vinum too X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Nov 2003 16:54:26 -0000 Running FBSD 4.9 on an Intel SMP mobo w/ 2 Intel PII 350s. Onboard SCSI is recognized and sees all my drives. One SCSI 3 drive is 4.5G for the OS and /usr. I have 4 identical IBM SCSI3 disks 9G each, however one of those 4 will not disklabel. The other three will. This leads to troubles then, obviously, to setting the 4 drives for vinum use. Was using these 4 drives on 5.0-RELEASE with vinum previously no troubles....downgraded for some backup software (bacula) compatibility reasons. In dmesg, da1, da2, da3, da4 all show as identical drives, model number, capacity, etc. I have not removed the drive to see if there is a special jumper to protect such things, I shall do this later today. When I try to `disklabel -e da4', I get the info open, I can change whatever I like, then when I save the file it complains; that the device does not support this feature. The other 3 drives all did `disklabel -e dax' with no trouble. One note, when I `disklabel -e da4' (the drive in question) it has Name: "DNES something" and for Label: "IBM"? The other 3 did not have this..... TIA Bob