From: rrk <rrk@prairie.lakes.com>
To: linux-raid@vger.kernel.org
Subject: md0 larger than physical block size with mdadm
Date: Mon, 17 May 2004 20:13:08 -0500 [thread overview]
Message-ID: <40A96324.7040407@prairie.lakes.com> (raw)
i have been trying to build a raid 1 array -- everything looks prefect
until i try to boot then i get an error msg to effect that md0 is larger
than the physical block size (md0 2560351 vs pb 2560320) this is consistent
across md0 thru md3 not the exact block count but close. kernel is 24.26
mdadm is 1.5 quick summary built debian system tested it used sfdisk
to partion hdc verified both disks matched used mkfs.ext3 to format partions
copied dta over set fd auto detect partion type both drives created it
let it mirror verified
superblocks (mdadm -E /dev/hda1 ) all looked fine. Any idea's ?
md's where build from mepis -- used as a bootable CD ? something goofy
with mepis?
can someone reccommed a different 'bootable' ? or is that not an issue?
reply other threads:[~2004-05-18 1:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=40A96324.7040407@prairie.lakes.com \
--to=rrk@prairie.lakes.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;
as well as URLs for NNTP newsgroup(s).