All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard B. Pyne" <rpyne@kinfolk.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: system startup hangs
Date: Wed, 07 Dec 2011 16:24:52 -0700	[thread overview]
Message-ID: <4EDFF5C4.10602@kinfolk.org> (raw)
In-Reply-To: <20111208100033.69c42b6c@notabene.brown>



On 12/7/2011 4:00 PM, NeilBrown wrote:
> On Wed, 07 Dec 2011 15:38:05 -0700 "Richard B. Pyne"<rpyne@kinfolk.org>
> wrote:
>
>> Please forgive me if I ask stupid questions, I am fairly new to linux
>> raid and most of the documentation I can find is severely outdated
>> and/or written for someone who already understands linux raid.
>>
>> I have successfully built a set raid 6 array with 4 drives and have
>> copied my system partitions onto the raid drives. I then reboot with
>> root=/dev/md0.
>>
>> Everything looks like it is working right up through:
>>
>> md/raid:md0 raid level 6 active with 4 out of 4 devices, algorithm 2
>> md0: detected capacity change from 0 to 1000131788
>> md: autorun DONE.
>> md0: unknown partition table
>> EXT3-fs (md0): error: couldn't mount because of unsupported optional
>> features
>> EXT2-fs (md0): error: couldn't mount because of unsupported optional
>> features
>> EXT4-fs (md0): mounted filesystem with ordered data mode.  Opts: (null)
>> VFS: Mounted root (ext4 filesystem) readonly on device 9:0.
>> freeing unused kernel memory: 472k freed
> It looks like the array got setup fine, the filesystem on it was mounted, and
> then .... nothing.
>
> I think at this point it should be running /sbin/init.
>
> It doesn't seem like a RAID problem exactly.  Maybe something when wrong when
> you copying the system partition into the RAID, but that is just a guess.
>
> At this point we probably need to know at least what distro you are using.
> There is probably some way to turn on tracing in the initrd and the boot
> sequence, but it is different for different distros.
>
> NeilBrown
>
I am using lunar linux. ( http://lunar-linux.org ). The kernel is 3.1.4 
x86_64 confiugred with raid autodetect and the raid sets were built with 
-e 0.90.

--Richard

  reply	other threads:[~2011-12-07 23:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-07 22:38 system startup hangs Richard B. Pyne
2011-12-07 23:00 ` NeilBrown
2011-12-07 23:24   ` Richard B. Pyne [this message]
2011-12-07 23:01 ` Mathias Burén
2011-12-07 23:19   ` Richard B. Pyne
2011-12-08 12:21 ` Robin Hill
2011-12-08 16:16   ` Richard B. Pyne

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=4EDFF5C4.10602@kinfolk.org \
    --to=rpyne@kinfolk.org \
    --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.