From: Neil Brown <neilb@suse.de>
To: Pradeep <pradeepjp@yahoo.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm -A erased the superblock ?
Date: Tue, 25 Mar 2008 16:09:24 +1100 [thread overview]
Message-ID: <18408.35076.866095.278205@notabene.brown> (raw)
In-Reply-To: message from Pradeep on Saturday March 22
On Saturday March 22, pradeepjp@yahoo.com wrote:
>
> > Where there any kernel message (view with 'dmesg') at this time?
>
> Mar 21 00:27:45 brahma kernel: md: invalid raid superblock magic on sdd
> Mar 21 00:27:45 brahma kernel: md: sdd does not have a valid v0.90 superblock, not
> importing!
> Mar 21 00:27:45 brahma kernel: md: md_import_device returned -22
>
So mdadm did try to assemble the array out of /dev/sdd. I wonder why.
When it did that, it would have told the kernel to forget about all
the partitions on /dev/sdd so they didn't confuse things. This is why
/dev/sdd1 etc seem to disappear.
>
>
> What is much more interesting, is that I rebooted the machine, and 'mdadm --examine'
> started working again (producing output).
> I then retried the 'mdadm -A' command and that went through as well.
What do you mean exactly. Did it assemble the array correctly?
> I cannot recall if the raid set was originally created on a 32 or a 64 bit O.S.
It shouldn't make any difference.
>
> Is there any other diagnostic I can try ?
Not sure... If the array is working now, I don't think there is a need
to explore further.
If it isn't, maybe
strace -o /tmp/strace mdadm -v -A ......
immediately after a reboot might help (Attach "/tmp/strace").
NeilBrown
prev parent reply other threads:[~2008-03-25 5:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 20:26 mdadm -A erased the superblock ? Pradeep
2008-03-21 19:58 ` NeilBrown
2008-03-22 16:53 ` Pradeep
2008-03-25 5:09 ` Neil Brown [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=18408.35076.866095.278205@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=pradeepjp@yahoo.com \
/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).