From owner-freebsd-questions@FreeBSD.ORG Wed Nov 19 06:18:07 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 CBF3F16A4CE for ; Wed, 19 Nov 2003 06:18:07 -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 1899943F3F for ; Wed, 19 Nov 2003 06:18:06 -0800 (PST) (envelope-from freebsd@anything-inc.com) X-AuthUser: freebsd@anything-inc.com Received: from neo.anything-inc.com (68.153.193.50:1450)Server] ; Wed, 19 Nov 2003 09:27:24 -0500 Message-Id: <5.2.0.9.0.20031119090506.00a9c6a8@anything-inc.com> X-Sender: freebsd@anything-inc.com@anything-inc.com X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Wed, 19 Nov 2003 09:13:43 -0500 To: Greg 'groggy' Lehey From: Bob Collins In-Reply-To: <20031118034624.GH32042@wantadilla.lemis.com> References: <5.2.0.9.0.20031114105727.00a9d6d8@anything-inc.com> <5.2.0.9.0.20031114105727.00a9d6d8@anything-inc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Status: No, hits=-2.5 required=3.5 tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, REPLY_WITH_QUOTES version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: FreeBSD Subject: Re: 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: Wed, 19 Nov 2003 14:18:07 -0000 At 10:46 PM 11/17/2003, Greg 'groggy' Lehey wrote: >On Friday, 14 November 2003 at 11:50:09 -0500, Bob Collins wrote: > > 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. > >Do you have device nodes for da4? Has it been labelled at all? > >Greg >-- I did not have `all' the nodes for da4 in /dev. So, I ran #sh MAKEDEV da4 in the /dev directory. After that, there were what appeared to be all the device nodes for da4. I was able to label the drive and use it with vinum under 5.0-RELEASE FWIW. Under 4.9-RELEASE (which is what I now run) it will not label through /stand/sysinstall. I can now newfs the drive and mount it and copy files to and fro, however I cannot use it with vinum. I did umount the drive and then disklabel -e da4 and changed the e: to h: and the filesystem type to vinum. It was da4s1e. When I create the vinum configuration, I either get that drive d (da4s1h) is referenced and in the down state while the other three drives are up, or the other three drives a b c are referenced and in the down state while drive d is up. Thank you. Bob