linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wiliam Colls <william.colls@rogers.com>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Can't Boot from /dev/md0 - Solved
Date: Mon, 12 Mar 2012 12:44:12 -0400	[thread overview]
Message-ID: <4F5E27DC.4010306@rogers.com> (raw)
In-Reply-To: <4F5D38FD.4080803@rogers.com>

On 03/11/2012 07:45 PM, Wiliam Colls wrote:
>
> Ubuntu 10.04 server, patched to date.
>
> This machine is configured to boot from a Raid1 array. The partitions
> are located on /dev/sdb1 and /dev/sdc1, the boot partition is located on
> /dev/sda1. This configuation has worked well for some time, but after a
> recent shutdown for maintenance, which did not involve any of the
> partitions, the machine refuses to boot. The sequence hangs very shortly
> after startup, and eventually errors out with the message /dev/md0 not
> available. and drops into the Busybox shell.
>
> After booting from a live rescue CD, and examining the partitions, they
> are all intact, and clean. They rescue CD was able to assemble the array.
>
> Not sure where to go from here. Any Suggestions will be greatfully
> received.
>
> William.
>
> PS. I am sure that I read some recent discussion on a very similar
> problem, but I can't find that material now. If anyone has a link, it
> also be greatfully received.
>

At least for now. After further investigation, I realised that the mdadm 
module was availalbe in the kernal, and I was able to assemble the array 
from the busybox prompt, and the boot will then continue normally. Still 
trying to determine what caused the problem and find a permanent fix.


-- 
I know that you believe that you understand what you think I said, but I 
am not sure that you realise that what you heard was not what I meant.

      reply	other threads:[~2012-03-12 16:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-11 23:45 Can't Boot from /dev/md0 Wiliam Colls
2012-03-12 16:44 ` Wiliam Colls [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=4F5E27DC.4010306@rogers.com \
    --to=william.colls@rogers.com \
    --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).