linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: John McMonagle <johnm@advocap.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: Can not start md0 after upgrade.
Date: Wed, 25 May 2011 09:54:32 -0500	[thread overview]
Message-ID: <4DDD1828.2020306@hardwarefreak.com> (raw)
In-Reply-To: <201105250819.27372.johnm@advocap.org>

On 5/25/2011 8:19 AM, John McMonagle wrote:
> Just upgraded a poweredge 1850 server from Debian lenny to squeeze and can not 
> boot with the new 2.6.32 kernel.
> 
> From lspci  have this controller:
> SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT 
> Dual Ultra320 SCSI (rev 08)
> 
> 
> Running mdadm raid with root on md0.
> 
> Normally run xen but all  info is for when running without xen.
> 
> I can still boot with the 2.6.26 kernel but not with the new 2.6.32 kernel.
> Under 2.6.32 it fails to start md0.
> in the busy box console 
> Can see all the needed partitions.
> What was sda and sdb are now sdb and sdc that should not matter??
> mdadm.conf is:
> DEVICE partitions
> CREATE owner=root group=disk mode=0660 auto=yes
> HOMEHOST <system>
> MAILADDR xxxxx@advocap.org
> ARRAY /dev/md0 level=raid1 num-devices=2 
> UUID=6f744c89:d2578f95:c150b018:d9f789b1
> ARRAY /dev/md1 level=raid1 num-devices=2 
> UUID=7938d59c:28a69e5e:3facbdc2:12974557

This is probably due to udev changes.  What device is now sda?

Using drive UUIDs instead of /dev/sdx in your arrays should fix this.

-- 
Stan

  reply	other threads:[~2011-05-25 14:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-25 13:19 Can not start md0 after upgrade John McMonagle
2011-05-25 14:54 ` Stan Hoeppner [this message]
2011-05-25 15:06   ` John McMonagle
2011-05-25 15:39     ` Stan Hoeppner
2011-05-25 20:21       ` John McMonagle
2011-05-25 21:57         ` Stan Hoeppner
2011-05-26 18:20           ` Can not start md0 after upgrade. SOLVED John McMonagle
2011-05-26 18:38             ` Stan Hoeppner

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=4DDD1828.2020306@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=johnm@advocap.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 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).