From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 19:30:56 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 622081065677 for ; Sun, 29 Jun 2008 19:30:56 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.156]) by mx1.freebsd.org (Postfix) with ESMTP id 8E81B8FC13 for ; Sun, 29 Jun 2008 19:30:55 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so772237fgb.35 for ; Sun, 29 Jun 2008 12:30:54 -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=QlXikIyYXZPj5GJuFrVFavDZauCGdQmFGTJI3SLXhDY=; b=C3j8GlAl92Sbj2jsoJMgwq7OO+E5Q7HqSqQw/HMjzoXdPOaCXfcebY9WGJ6vyA02o5 p+wG83zVXaMQagnNlkD3oIb1voWmPh1rklmBmgWsyiz2NJVO+BEU8wONkbtF/1+kMWQs NtebAnwlAVjVfehjJxNLUhfpM65kOeqC8U+FE= 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=fuwbnGwu4TLiTgF+oNhKE9gy2Ra/mnoJv1cr8cVW4qNHQEqFxgzn/DWGFgsFnYdcZ6 uzTXt/V677RqWheurKE7eDVl7/KbTJs4LABp8w56xVDuaPOXcWGORtewEmhbM1Ptonr8 rDl088cSG7m0MTdYT1x6HygXYw0IhDNcmjGUY= Received: by 10.86.33.19 with SMTP id g19mr2031048fgg.30.1214767854131; Sun, 29 Jun 2008 12:30:54 -0700 (PDT) Received: by 10.86.51.1 with HTTP; Sun, 29 Jun 2008 12:30:54 -0700 (PDT) Message-ID: <7d6fde3d0806291230j377fba96s7e014e5d253e6d08@mail.gmail.com> Date: Sun, 29 Jun 2008 12:30:54 -0700 From: "Garrett Cooper" To: "=?ISO-8859-1?Q?S=F8ren_Schmidt?=" In-Reply-To: <5AAEE9BE-4A44-46EE-9913-16BEC21802D2@FreeBSD.ORG> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <7d6fde3d0806260649t6619521bv92b65c472ddb7e1@mail.gmail.com> <7d6fde3d0806280129i31874960ofbc7627598e1426f@mail.gmail.com> <735A937C-89A9-411A-AA3F-377F576E635E@freebsd.org> <7d6fde3d0806280348r65875755pf7dc3917bba2bcb5@mail.gmail.com> <7d6fde3d0806280349j7eace513idb5cd81f9e2e4e0a@mail.gmail.com> <6.0.0.22.2.20080628132240.0255ba38@mail.computinginnovations.com> <7d6fde3d0806281410r781a6a77k98ffe237c10e3eee@mail.gmail.com> <7d6fde3d0806282011x472f8d27s955a8e1ab43a7341@mail.gmail.com> <5AAEE9BE-4A44-46EE-9913-16BEC21802D2@FreeBSD.ORG> Cc: ed@80386.nl, current@freebsd.org, Derek Ragona 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: Sun, 29 Jun 2008 19:30:56 -0000 On Sun, Jun 29, 2008 at 4:22 AM, S=F8ren Schmidt wrote: > > On 29Jun, 2008, at 5:11 , Garrett Cooper wrote: >>> >>> I hate to bring this to you, but you will not have an intact filesystem >>> when >>> the rebuild is done, you have no parity data to rebuild from, just as t= he >>> docs states. >>> >>> -S=F8ren >> >> Just as you predicted, the disk(s) are unreadable still, even after >> the rebuild (and I hope to hell that it didn't destroy/disturb any >> data on the surviving members). >> >> I may just have to get it sent off for recovery (after I dd the >> remaining members because there's still some usable data there -- >> bloody 2.7TB ... grr) -- apart from that I don't think I have a >> choice. > > You wont get anything from that except a huge bill for nothing. Why? If the thing was just treated like a RAID0 config (aka a huge single disk), then why would I end up with a huge bill for nothing (confused)? From what I can tell the drive was just defective (purchased it 4 months ago and it looks like the controller card went out), so fixing or replacing the controller card and setting up the bad blocks properly on the new card (if necessary) should solve my issue. >> Oh, where's this "document" of which you speak all the time? I don't >> see anything about parity support not being available in either the >> geom or iir manpage, or the iir sourcecode. If someone needs a helping >> hand inserting that logic into the kernel, I'll gladly assist so >> others don't follow my footsteps and fsck up their data. >> > > Would you please try to read what I write to you ? > > You still insist in mixing up ATA and IIR, it is two distinct drivers for > different HW and with very different properties. > > For ATA docs just use "man ata" and it will show you the way. > Shortcut to the raid part is "man ataraid". Yeah, I finally see what you mean (after reading the ataraid manpage). The funny thing was that (I thought) iir was in place and functioning a while back so I assumed "Hey, it's SCSI/cam supported -- I'm ok!". Boy was I wrong >:(. >> For once I wish I had been running Linux or Windows (at least) :(... > > Oooohhh, that one is soooo tempting..... 8^) Yeah, yeah, I know. I'm just pissed at myself for not backing up my critical data earlier. -Garrett