From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 9 00:41:03 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5523037B401 for ; Wed, 9 Apr 2003 00:41:03 -0700 (PDT) Received: from spider.deepcore.dk (cpe.atm2-0-56339.0x50c6aa0a.abnxx2.customer.tele.dk [80.198.170.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB2B043F75 for ; Wed, 9 Apr 2003 00:39:37 -0700 (PDT) (envelope-from sos@spider.deepcore.dk) Received: (from sos@localhost) by spider.deepcore.dk (8.12.8p1/8.12.8) id h397dZS4045212; Wed, 9 Apr 2003 09:39:35 +0200 (CEST) (envelope-from sos) From: Soeren Schmidt Message-Id: <200304090739.h397dZS4045212@spider.deepcore.dk> In-Reply-To: <002b01c2fe69$776a6dc0$0300000a@slugabed.org> To: Sean Hamilton Date: Wed, 9 Apr 2003 09:39:35 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL98b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 cc: hackers@FreeBSD.ORG Subject: Re: Undeletable ATA RAID X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Apr 2003 07:41:03 -0000 It seems Sean Hamilton wrote: > | Hmm, with both disks connected, atacontrol delete whatever arrays it > | see there, then make a new array with atacontrol covering both disks, > | then delete that. That should make certain all array information si > | overwritten... > I can't, because the second disk is gone. (I probably should have deleted > the array before removing it...) I could add another disk, or whatever, but > this problem should probably be fixed. Then just do it on the part that is there. > Anyhow, sequence of events: > > - Create SPAN array ar0 on ad4,ad6. (the only disks in the system) > - Install freebsd onto array. > - Get new disks, install as ad0 and ad1. > - Create stripe ar1 on ad0,ad1. > - Forgetting having done so, remove ad1. > - Boot, now ar0 and ar1 are reversed. ar0 is broken, ar1 works fine > (but fstab is confused, of course.) > > It can boot fine if I unplug ad0, so I'm guessing it looks at the first disk > for raid info? Hm, perhaps a better naming system is in order. I never liked > how it stores array info in the disk like this... seems trouble-prone... > like this. Well, the arrays are numbered in the sequence they are found.. > ...Ah, seems booting into single-user, deleting ar0, creating at0 as a > single-disk span array, and deleting that, has things working. Where does it > store the array info? Seems strange that zeroing the disk kept it, does it > just choose a disk and use that for all info? Or is it at the end of the > disk? I ^Cd the dd after a few seconds. For a Promise ATA RAID the config info is at MAXLBA-63 and the info is on *all* disks in the array. -Søren