From mboxrd@z Thu Jan 1 00:00:00 1970 From: Drew Subject: Re: Maximizing failed disk replacement on a RAID5 array Date: Mon, 6 Jun 2011 08:37:03 -0700 Message-ID: References: <4DECF025.9040006@fnarfbargle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: <4DECF025.9040006@fnarfbargle.com> Sender: linux-raid-owner@vger.kernel.org To: Brad Campbell Cc: Durval Menezes , linux-raid@vger.kernel.org List-Id: linux-raid.ids > Now, if I'm off the wall and missing something blindingly obvious feel free > to thump me with a clue bat (it would not be the first time). > > I've lost 2 arrays recently. 8TB to a dodgy controller (thanks SIL), and 2TB > to complete idiocy on my part, so I know the sting of lost or corrupted > data. I think you've covered the process in more detail, including pitfalls, then I have. :-) Only catch is where would you find a cheap 2-3TB drive right now? I also know the sting of mixing stupidity and dd. ;-) A friend was helping me do some complex rework with dd on one of my disks. Being the n00b I followed his instructions exactly, and him being the expert (and assuming I wasn't the n00b I was back then) didn't double check my work. Net result was I backed the MBR/Partition Table up using dd, but did so to a partition on the drive we were working on. There may have been some alcohol involved (I was in University), the revised data we inserted failed, and next thing you know I'm running Partition Magic (the gnu tools circa 2005 failed to detect anything) to try and recover the partition table. No backups obviously. ;-) -- Drew "Nothing in life is to be feared. It is only to be understood." --Marie Curie