From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 9 00:27:24 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 F10B437B401 for ; Wed, 9 Apr 2003 00:27:23 -0700 (PDT) Received: from priv-edtnes12-hme0.telusplanet.net (outbound03.telus.net [199.185.220.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23F1743F85 for ; Wed, 9 Apr 2003 00:27:23 -0700 (PDT) (envelope-from sh@planetquake.com) Received: from REASON ([154.5.106.237]) by priv-edtnes12-hme0.telusplanet.netSMTP <20030409072722.SMGN29647.priv-edtnes12-hme0.telusplanet.net@REASON>; Wed, 9 Apr 2003 01:27:22 -0600 Message-ID: <002b01c2fe69$776a6dc0$0300000a@slugabed.org> From: "Sean Hamilton" To: "Soeren Schmidt" , References: <200304090659.h396x6YB034830@spider.deepcore.dk> Date: Wed, 9 Apr 2003 00:27:24 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 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:27:24 -0000 Soeren Schmidt wrote: | It seems Sean Hamilton wrote: || Soeren Schmidt wrote: ||| It seems Sean Hamilton wrote: |||| [ Undeletable ATA RAID ] ||| ||| What kind of controller do you have since that is vital for how ||| ATA RAID's are setup ? || || It's using software RAID on a Promise ATA100 controller. | | 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. 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. ...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. sh