All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: Mathias Mueller <raidfail@gmx.de>
Cc: Linux raid <linux-raid@vger.kernel.org>
Subject: Re: broken raid level 5 array caused by user error
Date: Tue, 10 Nov 2015 16:41:45 -0500	[thread overview]
Message-ID: <56426499.8000205@turmel.org> (raw)
In-Reply-To: <3c05d813e42324cdf95989784f6d7b17@pingofdeath.de>

On 11/10/2015 04:33 PM, Mathias Mueller wrote:
> Hi Phil,
> 
>>> This both combinations
>>
>> Well, I gave you *four* combinations for order, and two suggestions for
>> chunk size.  Eight combinations to try.
> 
> Sorry, this two words were just the beginning of a sentence, which I
> didn't finish an forgot to remove :)
> 
> I tried 16 combinations at all (eight with --data-offset=1024 and eight
> with --data-offset=2048), the following four combinations gave the
> "/dev/md0 has unsupported feature(s)" message occurs:
> 
> --data-offset=1024 --chunk 64: sde sdd sdb sdc
> --data-offset=1024 --chunk 512: sde sdd sdb sdc
> --data-offset=1024 --chunk 64: sde sdb sdd sdc
> --data-offset=1024 --chunk 512: sde sdb sdd sdc
> 
> the other four combinations with --data-offset=1024 and all eight
> combinations with --data-offset=2048 gave
> 
> fsck.ext2: Superblock invalid, trying backup superblocks...
> fsck.ext2: Bad magic number in super-block while trying to open /dev/md0

You're not providing enough information.  Show the new vs. old
name/serial combinations, then show the --create and fsck
command/output, one by one.

For now, use data offset 2048 for all of them.

Phil

  reply	other threads:[~2015-11-10 21:41 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-10 21:33 broken raid level 5 array caused by user error Mathias Mueller
2015-11-10 21:41 ` Phil Turmel [this message]
2015-11-10 23:47   ` Mathias Mueller
2015-11-10 23:59     ` Phil Turmel
     [not found]       ` <b0cdddd4394bbc1356980bb61ac199c3@pingofdeath.de>
2015-11-11  1:00         ` Phil Turmel
2015-11-11 17:53           ` Mathias Mueller
2016-01-18 15:33             ` Mathias Mueller
2016-01-18 19:09               ` Phil Turmel
2016-01-19 14:35                 ` Mathias Mueller
2016-01-19 17:51                   ` Phil Turmel
2016-01-19 19:37                     ` Phil Turmel
2016-01-20  9:04                       ` Mathias Mueller
2016-01-22  9:30                         ` Mathias Mueller
2016-01-22 17:16                           ` Phil Turmel
2016-01-22 17:39                             ` Mathias Mueller
2016-01-22 19:13                               ` Phil Turmel
2016-01-25 10:02                                 ` Mathias Mueller
2015-11-11  1:03       ` Phil Turmel
2015-11-11  1:29         ` Mathias Mueller
  -- strict thread matches above, loose matches on Subject: below --
2015-11-09 11:27 Mathias Mueller
2015-11-09 11:56 ` Mikael Abrahamsson
2015-11-09 13:50   ` Phil Turmel
     [not found]     ` <07de4cd96f39ecb6154794d072ca12e7@pingofdeath.de>
     [not found]       ` <5640B8AD.3030800@turmel.org>
2015-11-09 15:41         ` Mathias Mueller
     [not found]           ` <d764bf541381927fa4183c9266fb3f5a@pingofdeath.de>
     [not found]             ` <5640C38B.4060503@turmel.org>
     [not found]               ` <a3a91665c4b7cdd70dacc7d8815cc365@pingofdeath.de>
2015-11-09 21:13                 ` Phil Turmel
2015-11-10  8:37                   ` Mathias Mueller
2015-11-10 13:55                     ` Phil Turmel
2015-11-10 14:55                       ` Mathias Mueller
2015-11-10 15:20                       ` Mathias Mueller
2015-11-10 15:28                         ` Phil Turmel
2015-11-10 21:02                           ` Mathias Mueller
2015-11-10 21:11                             ` Phil Turmel

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=56426499.8000205@turmel.org \
    --to=philip@turmel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=raidfail@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.