From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: "Jeffrey B. Layton" <laytonjb@charter.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm array not found on reboot
Date: Mon, 7 May 2007 13:11:11 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0705071310150.968@p34.internal.lan> (raw)
In-Reply-To: <463F5EB6.2090605@charter.net>
On Mon, 7 May 2007, Jeffrey B. Layton wrote:
> Justin Piszcz wrote:
>>
>>
>> On Mon, 7 May 2007, Jeffrey B. Layton wrote:
>>
>>> Justin Piszcz wrote:
>>>>
>>>>
>>>> On Mon, 7 May 2007, Jeffrey B. Layton wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> I apologize if this is a FAQ question or a typical newbie question,
>>>>> but by google efforts have yielded anything yet.
>>>>>
>>>>> I built a RAID-1 using mdadm (Centos 4.2 with 2.6.16.19 kernel
>>>>> and mdadm 1.6.0-2). It's just two SATA drives that I created using:
>>>>>
>>>>> mdadm --create --verbose /dev/md1 --level=raid1 --raid-devices=2
>>>>> /dev/sda1 /dev/sdb1
>>>>>
>>>>> The md built correctly and I built an ext3 on it. I created
>>>>> /etc/mdadm.conf
>>>>> and modified /etc/fstab to mount the device. But when I reboot, the
>>>>> kernel
>>>>> drops into RAID repair mode because it can't seem to find /dev/md1 and
>>>>> yells about not finding any valid superblock (I can get the exact
>>>>> message
>>>>> if needed). However I can mount /dev/sda1 with no problems.
>>>>>
>>>>> The only way I can get md1 back is to issue the command:
>>>>>
>>>>> mdadm -A /dev/md1 /dev/sda1 /dev/sdb1
>>>>>
>>>>> and everything works. I want to have /dev/md1 mounted automatically
>>>>> on boot. I'm missing something simple here - how do I do this?
>>>>
>>>> Sounds like a udev issue and/or you did not create the mdadm.conf
>>>> properly. Show us your mdadm.conf.
>>> ARRAY /dev/md1 level=raid1 num-devices=2
>>> UUID=e235ee6c:415f1494:23c28b59:afd20140
>>> devices=/dev/sda1,/dev/sdb1
>>> ARRAY /dev/md0 level=raid1 num-devices=2
>>> UUID=7121b438:7d36f9f6:8aa9c8b3:b5b0d211
>>> devices=/dev/hdc1,/dev/hdd1
>>
>> What distro?
> CentOS 4.2. I've been reading something about raidautorun. Would help in this
> case?
>
> Thanks!
>
> Jeff
>
>
That is probably what you want-- also technically you don't 'need' to have
the partitions set to 0xfd [Linux Raid Auto Detect], but that may help as
well.
fdisk -l /dev/sda
Disk /dev/sda: 74.3 GB, 74355769344 bytes
255 heads, 63 sectors/track, 9039 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 2090 16787893+ fd Linux raid autodetect
/dev/sda2 * 2091 2107 136552+ fd Linux raid autodetect
/dev/sda3 2108 9039 55681290 fd Linux raid autodetect
Justin.
next prev parent reply other threads:[~2007-05-07 17:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-07 16:45 mdadm array not found on reboot Jeffrey B. Layton
2007-05-07 16:58 ` Justin Piszcz
2007-05-07 17:06 ` Jeffrey B. Layton
2007-05-07 17:02 ` Justin Piszcz
2007-05-07 17:15 ` Jeffrey B. Layton
2007-05-07 17:11 ` Justin Piszcz [this message]
2007-05-07 19:53 ` Richard Scobie
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=Pine.LNX.4.64.0705071310150.968@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=laytonjb@charter.net \
--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