linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: CoolCold <coolthecold@gmail.com>
To: admin@musmo.com
Cc: "Timothy D. Lenz" <tlenz@vorgon.com>, linux-raid@vger.kernel.org
Subject: Re: Converting system to raid
Date: Fri, 10 Apr 2009 13:55:53 +0400	[thread overview]
Message-ID: <f19d625d0904100255j1ee672b8ped4b6b517a7f9dc5@mail.gmail.com> (raw)
In-Reply-To: <49DF0D06.8030705@musmo.com>

Yes, he should provide correct /etc/mdadm/mdadm.conf and
update-initramfs -u on md boot, smth like
chroot /mnt/md0
update-initramfs -u

On Fri, Apr 10, 2009 at 1:10 PM, KwangErn Liew <admin@musmo.com> wrote:
>
> Timothy D. Lenz wrote:
>>
>> Ended with warning: unable to open an initial console. I was able to
>> scroll back and didn't really see any errors. Don't know if I
>> missed a change to some config file or something else that should be built
>> into the kernel. I have gone over a lot of "guides" and
>> don't see what is missing.
>
> FYI, I've never been successful in booting RAID without initrd even though
> all necessary modules are built-in. I guess mdadm.conf requires initrd to
> kick start?
>
>
> KwangErn
> --
> 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
>



-- 
-- 
Best regards,
[COOLCOLD-RIPN]
--
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

  reply	other threads:[~2009-04-10  9:55 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-09 23:44 Converting system to raid Timothy D. Lenz
2009-04-10  9:10 ` KwangErn Liew
2009-04-10  9:55   ` CoolCold [this message]
2009-04-10 19:43     ` Timothy D. Lenz
2009-04-10 19:53   ` Robin Hill
2009-04-10 20:45     ` Timothy D. Lenz
2009-04-10 20:59       ` Robin Hill
2009-04-10 21:26         ` Timothy D. Lenz
2009-04-10 21:51           ` Robin Hill
2009-04-11  5:29             ` Timothy D. Lenz
2009-04-11 14:29               ` CoolCold
2009-04-11 18:47                 ` Timothy D. Lenz
2009-04-12  0:53                   ` Timothy D. Lenz
2009-04-12 11:11                     ` Robin Hill
2009-04-12 19:55                       ` Timothy D. Lenz
2009-04-14  9:30                         ` Robin Hill
2009-04-17  0:47                           ` Timothy D. Lenz
2009-04-17  7:49                             ` Robin Hill
2009-04-11 14:36               ` Robin Hill
2009-04-11 15:04                 ` jim owens
2009-04-11 15:44                   ` Jeff Garzik
2009-04-11 17:40                     ` jim owens
2009-04-12 11:11                       ` Jeff Garzik
2009-04-12 16:43                         ` jim owens
2009-04-12 17:18                           ` Jeff Garzik
2009-04-10 13:22 ` Robin Hill
2009-04-10 19:22   ` Timothy D. Lenz
2009-04-10 19:50     ` Robin Hill
2009-04-11  4:40       ` Jon Lewis
2009-04-11  7:48         ` Jan Ceuleers
2009-04-11  8:50         ` Goswin von Brederlow

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=f19d625d0904100255j1ee672b8ped4b6b517a7f9dc5@mail.gmail.com \
    --to=coolthecold@gmail.com \
    --cc=admin@musmo.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=tlenz@vorgon.com \
    /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).