From: Janek Kozicki <janek_listy@wp.pl>
To: linux-raid@vger.kernel.org
Subject: booting into /dev/md0 after an upgrade to squeeze
Date: Mon, 18 Oct 2010 20:14:48 +0200 [thread overview]
Message-ID: <20101018201448.62a76ba6@atak.bl.pg.gda.pl> (raw)
Hello,
I just upgraded my backup server to debian squeeze. It was
etch->lenny->squeeze upgrade.
And now I'm unable to boot into /dev/md0. It seems that grub is
identifying root by uuid of an ext3 filesystem which was on /dev/md0.
Before upgrading (etch to squeeze) I made a backup copy of /dev/md0
into another partition, which resulted in duplicating its uuid.
I had reboots in meantime after I finished lenny upgrade, and those
reboots worked.
But after finishing squeeze upgrade I could not boot into /dev/md0,
but instead I kept landing on the backup copy of /dev/md0 (which was
done before upgrade, and was containing etch). I verified with dmesg,
by looking at kernel command line that root=uuid=(uuid of ext3 filesystem).
And so, I changed uuid of that backup copy partition, so that the
original one /dev/md0 would be only one with such uuid. In the end -
I am unable to boot into it.
This server is remote, so it simply stopped starting up. I'll go
there and see myself, maybe selecting with keyboard another entry in
grub2 will be just enough.
But, maybe do you have some experience with booting into raid1 /dev/md0
after upgrading to squeeze?
best regards
--
Janek Kozicki http://janek.kozicki.pl/ |
next reply other threads:[~2010-10-18 18:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 18:14 Janek Kozicki [this message]
2010-10-18 19:49 ` booting into /dev/md0 after an upgrade to squeeze Tim Small
2010-10-18 21:18 ` Janek Kozicki
2010-10-19 6:53 ` booting into /dev/md0 after an upgrade to squeeze - SOLVED Janek Kozicki
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=20101018201448.62a76ba6@atak.bl.pg.gda.pl \
--to=janek_listy@wp.pl \
--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