From: Tim Small <tim@seoss.co.uk>
To: Janek Kozicki <janek_listy@wp.pl>
Cc: linux-raid@vger.kernel.org
Subject: Re: booting into /dev/md0 after an upgrade to squeeze
Date: Mon, 18 Oct 2010 20:49:02 +0100 [thread overview]
Message-ID: <4CBCA4AE.5020504@seoss.co.uk> (raw)
In-Reply-To: <20101018201448.62a76ba6@atak.bl.pg.gda.pl>
On 18/10/10 19:14, Janek Kozicki wrote:
> But, maybe do you have some experience with booting into raid1 /dev/md0
> after upgrading to squeeze?
>
You can stop grub doing the root=uuid= thing by changing /etc/default/grub
If you can get someone to the keyboard, then you can probably get them
to edit what grub is using as a one-off - i.e. change the root=uuid=xxx
entry to root=/dev/md0 (or even just one half of the mirror if you need
to get it working, then you can fix it later)...
It's also worth checking the contents of /etc/mdadm/mdadm.conf is
sensible - maybe if you duplicated the partition (with dd maybe, if you
said you duplicated the UUID), then it contains an incorrect uuid= line?
If it's incorrect, you may need to regenerate the initramfs having
corrected it (a copy is placed in the initramfs files) with
"update-initramfs -k all -u"
In a similar situations, where I have no remote console (IPMI SoL, Intel
AMT etc.), I like to use "qemu -snapshot ..." to verify that a system
will boot up correctly by pointing it at the real hard disks (see recent
post to this list).
HTH,
Tim.
next prev parent reply other threads:[~2010-10-18 19:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 18:14 booting into /dev/md0 after an upgrade to squeeze Janek Kozicki
2010-10-18 19:49 ` Tim Small [this message]
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=4CBCA4AE.5020504@seoss.co.uk \
--to=tim@seoss.co.uk \
--cc=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