From: Info@quantum-sci.net
To: linux-raid@vger.kernel.org
Subject: Re: Help
Date: Fri, 21 Aug 2009 23:14:31 -0700 [thread overview]
Message-ID: <200908212314.31887.Info@quantum-sci.net> (raw)
In-Reply-To: <200908211220.28701.Info@quantum-sci.net>
Not able to boot to my RAID devices. md0 is / and ext3 RAID1, but md1 and md2 are swap and JFS respectively, RAID10 created like this:
mdadm --create /dev/md1 --level=raid10 --layout=o2 --metadata=1.2 --chunk=256 --raid-disks=2 missing /dev/sdb2
It gives the initial kernel boot message but then says
invalid raid superblock magic on sdb2
invalid raid superblock magic on sdb3
... and halts progress. I have to hard-reset to continue. Why isn't the error more specific?
I've tried setting the metadata to 1.1, and tried adjusting mdadm.conf from /dev/md/1 to /dev/md1, but neither helped. The parts are set to raid autodetect and the kernel parameter is set to md_autodetect. What could be wrong?
On Friday 21 August 2009 12:20:28 Info@quantum-sci.net wrote:
>
> My God, the command is not working. I need to remove sdb1 from md0 so I can change it from a RAID10 to RAID1, and it simply ignores my command:
> # mdadm /dev/md0 --fail /dev/sdb1 --remove /dev/sdb1
> # cat /proc/mdstat
> Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath]
> md2 : active raid10 sdb3[1]
> 1868560128 blocks super 1.2 64K chunks 2 offset-copies [2/1] [_U]
> bitmap: 94/446 pages [376KB], 2048KB chunk
>
> md1 : active raid10 sdb2[1]
> 6297344 blocks super 1.2 64K chunks 2 offset-copies [2/1] [_U]
> bitmap: 0/25 pages [0KB], 128KB chunk
>
> md0 : active raid10 sdb1[1]
> 78654080 blocks super 1.2 64K chunks 2 offset-copies [2/1] [_U]
> bitmap: 76/151 pages [304KB], 256KB chunk
>
> unused devices: <none>
> #
>
>
> My system is half-converted and is now unbootable. What am I going to do?
>
>
next prev parent reply other threads:[~2009-08-22 6:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 13:27 RAID10 Layouts Info
2009-08-21 16:43 ` Goswin von Brederlow
2009-08-21 18:02 ` Info
2009-08-21 19:20 ` Help Info
2009-08-21 19:38 ` Help John Robinson
2009-08-21 20:51 ` Help Info
2009-08-22 6:14 ` Info [this message]
2009-08-22 9:34 ` Help NeilBrown
2009-08-22 12:56 ` Help Info
2009-08-22 16:47 ` Help John Robinson
2009-08-22 18:12 ` Help Info
2009-08-22 20:45 ` Help Info
2009-08-22 20:59 ` Help Guy Watkins
[not found] ` <200908230631.46865.Info@quantum-sci.net>
2009-08-24 23:08 ` Help Info
2009-08-24 23:38 ` Help NeilBrown
2009-08-25 13:18 ` Help Info
2009-08-27 12:47 ` Help Info
2009-08-23 20:28 ` Help John Robinson
2009-08-22 6:31 ` RAID10 Layouts Goswin von Brederlow
2009-08-21 20:42 ` Keld Jørn Simonsen
2009-08-21 21:04 ` Info
2009-08-21 21:57 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2006-08-23 19:21 help Archie Cotton
2006-02-04 2:21 Help Oren Ben-Menachem
2004-10-20 5:05 help Srinivasa S
2004-10-20 5:50 ` help Guy
2004-10-21 1:47 ` help Jon Lewis
2004-04-01 16:56 Help Jason C. Leach
2004-04-01 17:00 ` Help Måns Rullgård
2004-02-01 13:13 help Rami Addady
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=200908212314.31887.Info@quantum-sci.net \
--to=info@quantum-sci.net \
--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).