From owner-freebsd-current@FreeBSD.ORG Sat Jun 28 03:57:25 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 76CB61065671 for ; Sat, 28 Jun 2008 03:57:25 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.154]) by mx1.freebsd.org (Postfix) with ESMTP id D43668FC0A for ; Sat, 28 Jun 2008 03:57:24 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so450765fgb.35 for ; Fri, 27 Jun 2008 20:57:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=7Im61JZRx38e3NGx+9YdMWwWyLCpDfmK528TgN+9l6U=; b=klcznZ9kgSpNw3T7AH2rvc58E5rbtf2P/K9Yt4SH8tBm5wKnxohzyAcH75znMU7FcF dQOWaIXSnUrmScrJ0OPA1k4I3eBhBwLUWTUycOTwga84MRzBllqxmzXnDkx+B91gz/er dL/qDJuuw/NESyzNVXITVeIRpSKWOAxqngtAU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=YQiPvwxm9D7U6J4HJK1yJzhMNYfb0jCAeYHfyo/9dEvq14mhD5TMx0zfXVrocqQStf SYviwJfk5+mIk5kVSEV3UIYE72wRmq+x/EewiNETLTkHfe1NZ+RADj9SYm2WCWeFGlMg k/FCvBf149Zg3X4vVO6iegy2Ni8Wz67YiB16w= Received: by 10.86.73.7 with SMTP id v7mr2942758fga.37.1214625443671; Fri, 27 Jun 2008 20:57:23 -0700 (PDT) Received: by 10.86.51.1 with HTTP; Fri, 27 Jun 2008 20:57:23 -0700 (PDT) Message-ID: <7d6fde3d0806272057p795277a2ie60ac7d7d10f0a6e@mail.gmail.com> Date: Fri, 27 Jun 2008 20:57:23 -0700 From: "Garrett Cooper" To: "Derek Ragona" In-Reply-To: <6.0.0.22.2.20080627170323.02591528@mail.computinginnovations.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <7d6fde3d0806260649t6619521bv92b65c472ddb7e1@mail.gmail.com> <1214492963.35536.22.camel@localhost> <4863B968.4040805@clearchain.com> <7d6fde3d0806262004u171bf9dx179564be5a76d9c7@mail.gmail.com> <6.0.0.22.2.20080627170323.02591528@mail.computinginnovations.com> Cc: Tom Evans , Benjamin Close , current@freebsd.org Subject: Re: URGENT: Need help rebuilding iir RAID5 array with failed drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jun 2008 03:57:25 -0000 On Fri, Jun 27, 2008 at 3:05 PM, Derek Ragona wrote: > At 10:04 PM 6/26/2008, Garrett Cooper wrote: > > On Thu, Jun 26, 2008 at 8:44 AM, Benjamin Close > wrote: >> Tom Evans wrote: >>> >>> On Thu, 2008-06-26 at 06:49 -0700, Garrett Cooper wrote: >>> >>>> >>>> Hello, >>>> First off sorry for the cross-post. I typically don't do this >>>> but this is an important question, so please bear with me. I'm just >>>> trying to get more eyes on the subject so I can (maybe) get a reply >>>> quicker... >>>> I'm running 8-CURRENT on my machine and it appears that one of >>>> the disks in my RAID5 array has taken a nose dive (BIOS recognizes >>>> that it exists, but Intel Matrix Manager claims that the disk is an >>>> "Offline Member"). After doing some reading it appears that it's >>>> kaput, so I need to get a replacement disk to fix this one... >>>> That aside, I need to determine how to rebuild the array in a >>>> Unix environment because Intel only provides instructions for how to >>>> use their Windows matrix manager. If anyone can point me to some links >>>> or provide me with some pointers on how to correct this issue, I'd owe >>>> you a lot; in fact the next time you come by Santa Cruz, CA I'll >>>> gladly treat you to some beers or something else you might want :)... >>>> Linux solutions (if there isn't a proper one for FreeBSD) are valid, >>>> as long as the core data remains uncorrupted and I can do what I need >>>> to from a LiveCD. I'm just scared to boot up OS and have it do some >>>> irrevocable operation like fsck -y and assume parity errors are ok or >>>> something along those lines (I don't remember if I set rc.conf to >>>> fsck -y and I know I can change that from single-user mode, but I want >>>> to play things conservatively if at all possible) :\... >>>> Filesystem is UFS2 with softupdates of course. >>>> Point proven that I need to backup my data more often :(... >>>> TIA, >>>> -Garrett >>>> >>>> PS If replying on the questions@ list, please CC me as I'm not >>>> subscribed to that list. >>>> >>> >>> I'm fairly sure that Intel Matrix metadata cant be created/modified by >>> fbsd, only read. You should be able to do whatever rebuild operations >>> you need in the BIOS I believe, but that would be an offline operation, >>> clearly. >>> >>> I may be mistaken, and the driver can handle array rebuilds for matrix. >>> If it can, the command you are looking for is 'atacontrol rebuild ar0', >>> see atacontrol(8). >>> >>> Tom >>> >> >> Please DONT use FreeBSD to rebuild this RAID5 unit. FreeBSD will detect it >> as a raid 5 Unit and even allow you to use it, add the new disk to it and >> even let you rebuild the raid. >> However the ata driver does not have support parity for Raid5. From >> ataraid(4): >> >> RAID5 is not supported at this time. Code exists, but it neither uses >> nor maintains parity information. >> >> You can confirm this in code, just look for the Swedish comments in >> ataraid.c >> Hence writing to the raidset will give you a glorified raid0. >> >> Cheers, >> Benjamin > > So.. wait a sec? Are you saying I'm fscked because my RAID5 is nothing > more than RAID0 under FreeBSD?!?! > -Garrett > > Most if these RAID's are done in the BIOS so the OS sees just a volume. The > RAID 5 or RAID 1, or RAID 0, or various combinations are left to the BIOS. > > Also these are considered software RAIDS not hardware as the BIOS uses the > Motherboard CPU. > > -Derek Grabbed a 1TB drive on sale just for kicks to see if I could rebuild the array, but I don't see any option at all under FreeBSD (sadly enough). So, if I did the following when I setup the RAID, I'm essentially screwed, aren't I? 1. Configure RAID in Matrix manager. 2. Boot into FreeBSD. 3. Note new device called /dev/ar0. 4. newfs ... /dev/ar0 # Does this mean I did this with RAID0? -Garrett