From: Tim Small <tim@seoss.co.uk>
To: Doug <doug.duboulay@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: debian dist-upgrade etch -> squeeze broke my mdadm RAID1
Date: Wed, 11 Aug 2010 09:16:20 +0100 [thread overview]
Message-ID: <4C625C54.5060000@seoss.co.uk> (raw)
In-Reply-To: <201008111527.37009.Doug.duBoulay@gmail.com>
On 11/08/10 06:27, Doug wrote:
> After the upgrade and installation of a new 2.6.32 kernel, the kernel
>
I believe Debian only supports upgrading between major versions, so you
should have gone 4.0.x (etch) -> 5.0.x (lenny) -> 6.0-pre (squeeze). If
you didn't then that'll explain the problem you're seeing which is
really Debian-specific, and relates (I believe) to the change in device
naming with the switch to udev which occured between etch and lenny (and
is presumably taken into account when upgrading between those two).
HTH,
Tim.
--
South East Open Source Solutions Limited
Registered in England and Wales with company number 06134732.
Registered Office: 2 Powell Gardens, Redhill, Surrey, RH1 1TQ
VAT number: 900 6633 53 http://seoss.co.uk/ +44-(0)1273-808309
prev parent reply other threads:[~2010-08-11 8:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 5:27 debian dist-upgrade etch -> squeeze broke my mdadm RAID1 Doug
2010-08-11 8:16 ` Tim Small [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=4C625C54.5060000@seoss.co.uk \
--to=tim@seoss.co.uk \
--cc=doug.duboulay@gmail.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).