From: Michael Evans <mjevans1983@gmail.com>
To: Joachim Otahal <Jou@gmx.net>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Swap on /dev/md1 always lost after reboot
Date: Sun, 28 Mar 2010 23:33:53 -0700 [thread overview]
Message-ID: <4877c76c1003282333j7250a117y4dcff2aa12f75e9b@mail.gmail.com> (raw)
In-Reply-To: <4BB01158.6050109@gmx.net>
On Sun, Mar 28, 2010 at 7:32 PM, Joachim Otahal <Jou@gmx.net> wrote:
> Joachim Otahal schrieb:
>>
>> free says: swap active, mdstat says:
>> md2 : active (auto-read-only) raid1 sda2[1] sdb2[0]
>> 979840 blocks [2/2] [UU]
>
> minor correction: the output right after creating the raid + issuing a
> mkswap is
> md2 : active raid1 sda2[1] sdb2[0]
> 979840 blocks [2/2] [UU]
> [=======>.............] resync = 37.9% (372480/979840) finish=0.1min
> speed=93120K/sec
>
> and a few second later:
> md2 : active raid1 sda2[1] sdb2[0]
> 979840 blocks [2/2] [UU]
>
> mdadm.conf updated, but md2 still not there after reboot.
>
> Joachim
>
> --
> 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
>
Trigger the regeneration of your initrd/initramfs image. It's
probably got an mdadm.conf that lacks your second device.
--
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
next prev parent reply other threads:[~2010-03-29 6:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 2:21 Swap on /dev/md1 always lost after reboot Joachim Otahal
2010-03-29 2:32 ` Joachim Otahal
2010-03-29 6:33 ` Michael Evans [this message]
2010-03-29 17:32 ` Joachim Otahal
2010-04-14 20:13 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2010-03-29 2:21 Joachim Otahal
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=4877c76c1003282333j7250a117y4dcff2aa12f75e9b@mail.gmail.com \
--to=mjevans1983@gmail.com \
--cc=Jou@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.