From: Lapohos Tibor <tibor.lapohos@rogers.com>
To: dev raid <linux-raid@vger.kernel.org>
Subject: Re: embedding area is unusually small... (GRUB2 on software RAID1)
Date: Thu, 7 Jan 2010 08:26:11 -0800 (PST) [thread overview]
Message-ID: <272147.77280.qm@web88202.mail.re2.yahoo.com> (raw)
In-Reply-To: <21410882.iaPbMVeJ7U@rnqqfki.eternal-september.org>
> > ....How, I don't know.
>
> Did you check the "fdisk -lu /dev/sda" output?
>
Yes. 63, so I still went on and repartitioned as described in Trial #[123].
I'm thinking that it could have been something left behind by the Intel Matrix RAID volume management... Maybe Neil Brown could give an explanation to this. I also noticed that if one re-partitions the exact same way, the RAID superblock information becomes available again, that is, partitioning or disassembling a RAID device does not threcken those records off the disks. Therefore, even if one does not create a partitioned md array, it will be, on its own! Actually it makes sense, since partitioning does not involve alteration of records throughout the disks... I just thought it would be interesting to share all this.
In the near future I will describe my story in a single post, maybe it will inspire some developers to address certain points in their documentation work.
Thanks again to All,
Tibor
prev parent reply other threads:[~2010-01-07 16:26 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
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 [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=272147.77280.qm@web88202.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