From: "David M. Strang" <dstrang@shellpower.net>
To: linux-raid@vger.kernel.org, Neil Brown <neilb@suse.de>
Subject: Re: Booting from raid1 -- md: invalid raid superblock magic on sdb1
Date: Sun, 27 Nov 2005 14:14:10 -0500 [thread overview]
Message-ID: <058201c5f386$bf23d150$200a11ac@NCNF5131FTH> (raw)
In-Reply-To: 055901c5f30c$282ad520$200a11ac@NCNF5131FTH
On Saturday 26 November 2005 23:32:51, David M. Strang wrote
> Please forgive me for pinging you direct on this Neil; but I fear you are
> the only one who can answer it.
>
> I am a bit considered by this in the startup log:
>
> Nov 26 21:47:35 xenogenesis kernel: md: raid1 personality registered as nr
> 3
> Nov 26 21:47:35 xenogenesis kernel: md: md driver 0.90.2 MAX_MD_DEVS=256,
> MD_SB_DISKS=27
> Nov 26 21:47:35 xenogenesis kernel: md: bitmap version 3.39
>
> While mdadm lets me start a v1.0 superblock; I fear that I missing some
> level of kernel patch.
>
> Nov 26 21:47:35 xenogenesis kernel: md: Loading md_d0: /dev/sdb1
> Nov 26 21:47:35 xenogenesis kernel: md: invalid raid superblock magic on
> sdb1
> Nov 26 21:47:35 xenogenesis kernel: md: sdb1 has invalid sb, not
> importing!
> Nov 26 21:47:35 xenogenesis kernel: md: md_import_device returned -22
Just a quick update; I've been putting forth some due diligence on this --
and it appears basically, that do_mounts_md.c is an antique. I've added a
small debug line to md.c under md_import_device; and then also traced thru
the do_mounts_md.c code; and basically the crux of the situation is
do_mounts_md.c doesn't evaluate the superblock of the device and set
SET_ARRAY_INFO for persistent superblocks. So, everything defaults to the
legacy superblock type. (Superblock v0.90.x)
-- David M. Strang
next prev parent reply other threads:[~2005-11-27 19:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-26 16:18 Booting from raid1 -- md: invalid raid superblock magic on sdb1 David M. Strang
[not found] ` <559c115f0605930c434a98c6cfd8fd66@logidac.com>
2005-11-26 17:36 ` David M. Strang
2005-11-26 19:05 ` David M. Strang
2005-11-27 4:36 ` David M. Strang
2005-11-27 19:14 ` David M. Strang [this message]
2005-11-27 22:00 ` Neil Brown
2005-11-28 2:11 ` David M. Strang
2005-11-28 2:24 ` Ross Vandegrift
2005-11-28 2:33 ` David M. Strang
2005-11-28 3:11 ` Ross Vandegrift
2005-11-28 3:19 ` David M. Strang
2006-02-14 4:12 ` Lilo append= , A suggestion Mr. James W. Laferriere
2006-02-14 7:15 ` Neil Brown
2006-02-14 7:17 ` Luca Berra
2005-12-03 14:02 ` Booting from raid1 -- md: invalid raid superblock magic on sdb1 Bill Davidsen
2005-12-03 19:49 ` David M. Strang
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='058201c5f386$bf23d150$200a11ac@NCNF5131FTH' \
--to=dstrang@shellpower.net \
--cc=linux-raid@vger.kernel.org \
--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 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).