From: Lapohos Tibor <tibor.lapohos@rogers.com>
To: linux-raid@vger.kernel.org
Subject: Re: embedding area is unusually small... (GRUB2 on software RAID1)
Date: Wed, 6 Jan 2010 08:18:43 -0800 (PST) [thread overview]
Message-ID: <195985.49531.qm@web88208.mail.re2.yahoo.com> (raw)
In-Reply-To: <4589525.I9CuDL8pqf@rnqqfki.eternal-september.org>
Thanks for your reply, Antonio.
--- On Wed, 1/6/10, Antonio Perez <ap23563m@gmx.com> wrote:
> What's the output of:
> fdisk -lu /dev/sda
I will look at it tonight. Thanks.
> However, the way you are making partitions is quite complex
> and the needed space could be somewhere else.
Does this mean that this partitioning is not the right way to proceed? should I create all the partitions first and build them into so many /dev/md[01234] devices separately maybe?
> Please, stop repeating your question everywhere.
I am very sorry if I upset the community. I did not think that linux-raid, grub-devel and help-grub lists would represent the same experts. In fact, based on what I see on the GRUB sites is, that grub-devel experts are different from more like "legacy" supporting help-grub ones. Maybe a bit of clarification would help keeping the developers/maintainers email intake a bit lower. So I must ask: which one is the most appropriate for my question?
Thanks again,
Tibor
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-01-06 16:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 14:23 embedding area is unusually small... (GRUB2 on software RAID1) Lapohos Tibor
2010-01-06 16:02 ` Antonio Perez
2010-01-06 16:18 ` Lapohos Tibor [this message]
2010-01-06 20:41 ` Antonio Perez
2010-01-06 21:40 ` Lapohos Tibor
2010-01-06 22:23 ` Antonio Perez
2010-01-07 14:59 ` Lapohos Tibor
2010-01-07 16:14 ` Antonio Perez
2010-01-07 16:26 ` Lapohos Tibor
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=195985.49531.qm@web88208.mail.re2.yahoo.com \
--to=tibor.lapohos@rogers.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