From mboxrd@z Thu Jan 1 00:00:00 1970 From: "John Stoffel" Subject: Re: corrupt raid 5 Date: Wed, 4 Jan 2006 15:45:03 -0500 Message-ID: <17340.13263.40580.460585@smtp.charter.net> References: <5981e8c80601031907l6d612bfcsf4a81826efc97f@mail.gmail.com> <17339.20993.529499.281141@smtp.charter.net> <5981e8c80601032135p312a37e0kf8c4e3d6edd05e53@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5981e8c80601032135p312a37e0kf8c4e3d6edd05e53@mail.gmail.com> Sender: linux-raid-owner@vger.kernel.org To: Lorac Thelmwood Cc: linux-raid@vger.kernel.org List-Id: linux-raid.ids >>>>> "Lorac" == Lorac Thelmwood writes: >> Lorac> First I can't start the array because it complains about a bad Lorac> superblock. Have you tried forcing the start of the array with the --force flag? Something like this: mdadm -A --run /dev/md1 Please give the output of the command. Lorac> What's the output of 'cat /proc/mdstat' and 'mdadm >> --detail /dev/md?' where ? is the number of your raid 5 array? Lorac> debian:~# cat /proc/mdstat Lorac> Personalities : [raid1] [raid5] Lorac> md1 : inactive hdh1[4] hdc1[0] hdg1[3] hdf1[2] hde1[1] Lorac> 976791680 blocks This is the key info, the array is assembled, but it hasn't been started properly, probably because of the missing disk. Try the --run args as above and see what it does for you. See how it says 'inactive', this means you need to get it running first. Good luck, John