From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sharif Islam Subject: Worked!! Re: recreate superblock? (was Re: mdadm: failed to RUN_ARRAY) Date: Mon, 11 Oct 2004 15:00:02 -0500 Sender: linux-raid-owner@vger.kernel.org Message-ID: <416AE642.9040504@uiuc.edu> References: <4168064D.3050903@uiuc.edu> <4168140A.6070300@uiuc.edu> <416AB1E1.1070605@uiuc.edu> <1097502158.5815.62.camel@langvan2.homenetwork> <416ADA7A.5060802@uiuc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <416ADA7A.5060802@uiuc.edu> To: linux-raid@vger.kernel.org List-Id: linux-raid.ids Thanks. This worked. I am back with degraded mode. mdadm --create --verbose /dev/md5 --level=5 --chunk=128 --raid-devices=6 /dev/hde1 /dev/hdf1 /dev/hdg1 /dev/hdh1 /dev/hdi1 missing Sharif Islam wrote: > Mike Tran wrote: > >> Hi Sharif, >> >>> From the kernel log, I believe that the raid5 array now has 4 working >> >> disks out of 6 raid disks. My suggestion is to recreate the array. >> >> Before recreating the MD array, I would suggest that you run mdadm >> --examine /dev/hdxx (i.e. hde1, hdf1 or hdg1) and write down the >> information of the original array setup. >> Some of the important Raid5 info are : Raid Devices, Total Devices, >> Preferred Minor (/dev/mdx), Spare Devices, Layout, Chunk Size, order of >> devices. >> When you **decide** to use mdadm -C to recreate array, mdadm will ask >> you to confirm on overwriting existing md superblock. >> >> > Thanks for your response. Will it delete the existing the data on the > RAID? > > -Sharif > > - > To unsubscribe from this list: send the line "unsubscribe linux-raid" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html