From: Iordan Iordanov <iordan@cdf.toronto.edu>
To: NeilBrown <neilb@suse.de>
Cc: "Joe Landman" <joe.landman@gmail.com>,
"Mathias Burén" <mathias.buren@gmail.com>, b2 <b2@playtime.bg>,
linux-raid@vger.kernel.org
Subject: Re: debian software raid1
Date: Wed, 20 Apr 2011 10:59:18 -0400 [thread overview]
Message-ID: <4DAEF4C6.8010902@cdf.toronto.edu> (raw)
In-Reply-To: <20110420111239.734ae4c1@notabene.brown>
Hi Neil,
On 04/19/11 21:12, NeilBrown wrote:
> I seem to remember that I had to do something special to grub to get it to
> boot initially, but I also vaguely remember that after some series of updates
> (this is Debian) it seemed to get a lot easier. My "grub.cfg" contains:
>
> menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-686' --class debian --class gnu-linux --class gnu --class os {
> insmod raid
> insmod mdraid
> insmod part_msdos
> insmod ext2
> set root='(md0,1)'
> search --no-floppy --fs-uuid --set 03e9951f-d174-4d88-9b4c-dd7a31c0de61
> echo 'Loading Linux 2.6.32-5-686 ...'
> linux /vmlinuz-2.6.32-5-686 root=UUID=6e8a3564-5588-476e-bbe5-a68c967c6c8e ro quiet
> echo 'Loading initial ramdisk ...'
> initrd /initrd.img-2.6.32-5-686
> }
>
> which was all automatically created, and it seems to "just work".
Yes, I am also reminded now that grub and md was a bit strange, mostly
because I was converting a single drive system to a RAID1 system, and I
had dd-d /dev/sda onto /dev/sdb. Grub seemed to struggle with the fact
that the UUID was the same on /dev/sda1, /dev/sdb1, and naturally
/dev/md0p1, which was initially created on top of /dev/sda. It refused
to boot a couple of times complaining about the UUID, which was easily
resolved by editing the grub entry on the fly in the grub prompt, and
changing root=UUID=6e8a3564-5588-476e-bbe5-a68c967c6c8e to
root=/dev/md0p1 (note that the UUID is just an example UUID), and
booting that way. Afterward, doing:
grub-install --modules="raid" /dev/md0
seemed to eventually placate grub. Also, I did not really see any change
in grub.cfg, but then again, I didn't actually do a "diff" of grub.cfg
before and after. The point is that it still uses UUID, the UUID is
still the same among all these devices (naturally, since this is RAID1),
and it *no longer complains*. It's a bit disconcerting, but I will learn
to live with it :D.
I hope this helps!
Iordan
next prev parent reply other threads:[~2011-04-20 14:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 12:12 debian software raid1 b2
2011-04-19 12:25 ` Mathias Burén
2011-04-19 16:03 ` Iordan Iordanov
2011-04-19 21:10 ` Gordon Henderson
2011-04-19 21:33 ` Steven Haigh
2011-04-19 22:01 ` Roberto Spadim
2011-04-19 22:05 ` Mathias Burén
2011-04-19 22:51 ` NeilBrown
2011-04-20 0:33 ` Joe Landman
2011-04-20 1:12 ` NeilBrown
2011-04-20 14:59 ` Iordan Iordanov [this message]
2011-04-20 14:51 ` Iordan Iordanov
2011-04-21 6:15 ` Luca Berra
2011-04-21 14:50 ` Iordan Iordanov
2011-04-22 5:59 ` Luca Berra
2011-04-22 19:19 ` Iordan Iordanov
2011-04-22 19:28 ` Mikael Abrahamsson
2011-04-23 0:07 ` Iordan Iordanov
2011-04-20 10:28 ` Asdo
2011-04-20 12:40 ` NeilBrown
2011-04-23 8:33 ` Jan Ceuleers
2011-04-22 19:21 ` Iordan Iordanov
2011-04-22 22:12 ` NeilBrown
2011-04-23 0:05 ` Iordan Iordanov
2011-04-23 12:54 ` David Brown
2011-04-23 14:23 ` Keld Jørn Simonsen
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=4DAEF4C6.8010902@cdf.toronto.edu \
--to=iordan@cdf.toronto.edu \
--cc=b2@playtime.bg \
--cc=joe.landman@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=mathias.buren@gmail.com \
--cc=neilb@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.