From: sfunk1x <sfunk1x@gmail.com>
To: NeilBrown <neilb@suse.com>, Wols Lists <antlists@youngman.org.uk>,
linux-raid@vger.kernel.org
Subject: Re: MDADM RAID 6 Bad Superblock after reboot
Date: Thu, 19 Oct 2017 17:43:03 -0700 [thread overview]
Message-ID: <e257fcc8-9773-a8a2-42bd-6030aef6329e@gmail.com> (raw)
In-Reply-To: <87zi8mg7mi.fsf@notabene.neil.brown.name>
On 10/19/2017 02:17 PM, NeilBrown wrote:
> Anything is better than nothing.. Can we get a photo of "mdadm
> --examine" output on one of the devices (e.g. /dev/sda1) ??
>
> Also, what mdadm version (mdadm -V) and kernel version (uname -r)?
https://imgur.com/x2rZEl5
I included an --examine of sda1 and sdf.
> mdadm never tries to edit mdadm.conf.
> It does modify files in /run/mdadm (or maybe /var/run/mdadm).
> Can we get a photo of that audit log?
I was mistaken, I think. It looks like mdadm tried to read (??) the file
and the context for the file was not set properly:
https://imgur.com/5UvFExp
In order to "fix" the issue, I ran sealert against the audit.log and
followed it's instructions, producing a rules file.
>
> I'm very suspicious of these new drives appearing to have not metadata.
> Can you
> od -x /dev/sdf | head
> od -x /dev/sdf | grep a92b
> and provide a photo of the output?
grep'ing a92b scrolled off the screen, so I grabbed a portion of it,
ctrl-c' and included head:
https://imgur.com/WDcAYBc
Thanks for the help so far.
next prev parent reply other threads:[~2017-10-20 0:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6a0f0e0b-6b03-8ec1-b02f-b17b0447aff8@gmail.com>
2017-10-18 18:14 ` MDADM RAID 6 Bad Superblock after reboot Sean R. Funk
2017-10-18 19:40 ` Wols Lists
2017-10-19 1:52 ` sfunk1x
2017-10-19 10:58 ` Wols Lists
2017-10-19 14:11 ` Sean R. Funk
2017-10-19 14:28 ` Wols Lists
2017-10-19 21:17 ` NeilBrown
2017-10-20 0:43 ` sfunk1x [this message]
2017-10-20 1:50 ` NeilBrown
2017-10-22 21:00 ` sfunk1x
2017-10-22 22:40 ` NeilBrown
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=e257fcc8-9773-a8a2-42bd-6030aef6329e@gmail.com \
--to=sfunk1x@gmail.com \
--cc=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.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).