From: Sharif Islam <mislam@uiuc.edu>
To: linux-raid@vger.kernel.org
Subject: Worked!! Re: recreate superblock? (was Re: mdadm: failed to RUN_ARRAY)
Date: Mon, 11 Oct 2004 15:00:02 -0500 [thread overview]
Message-ID: <416AE642.9040504@uiuc.edu> (raw)
In-Reply-To: <416ADA7A.5060802@uiuc.edu>
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
prev parent reply other threads:[~2004-10-11 20:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-09 15:39 mdadm: failed to RUN_ARRAY Sharif Islam
2004-10-09 16:38 ` Sharif Islam
2004-10-11 16:16 ` recreate superblock? (was Re: mdadm: failed to RUN_ARRAY) Sharif Islam
2004-10-11 13:42 ` Mike Tran
2004-10-11 19:09 ` Sharif Islam
2004-10-11 20:00 ` Sharif Islam [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=416AE642.9040504@uiuc.edu \
--to=mislam@uiuc.edu \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).