From: "Andrew Hodgetts" <andrew.hodgetts@btinternet.com>
To: linux-raid@vger.kernel.org
Subject: Help fixing broken array after power loss
Date: Sun, 1 Jun 2014 19:37:07 +0100	[thread overview]
Message-ID: <002001cf7dc8$7e4c3b10$7ae4b130$@btinternet.com> (raw)
Hi
I have a challenge!!
I've been upgrading my array with larger disks, then needed to remove one of
the disk from the array (long story) so I shrunk the array and was in the
process of reducing the number of disks when I lost power and have now lost
the ability to mount the array.
So I'm now in a state where I don't know if 9 or 10 disks are in the array,
all I know is it will not start.  Because I've been swapping disks out I
don't know what order the disks are supposed to be in to re-start the array.
Running Mdadm 3.2.5 on debian kernel 3.2.0-4-amd64
I can 'start' the array with 9/10 disks (using devices a-j alphabetically)
but it is not mountable, the filesystem type is 'jbd' when it should be ext4
What can I do to get this working/what info can I provide so you can help?
Cheers
Andy
                 reply	other threads:[~2014-06-01 18:37 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='002001cf7dc8$7e4c3b10$7ae4b130$@btinternet.com' \
    --to=andrew.hodgetts@btinternet.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).