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>,
	linux-raid-owner@vger.kernel.org
Subject: Re: broken raid level 5 array caused by user error
Date: Tue, 10 Nov 2015 18:59:49 -0500	[thread overview]
Message-ID: <564284F5.9080409@turmel.org> (raw)
In-Reply-To: <ceee2de5aba3ca77efc1146e19896b90@pingofdeath.de>

On 11/10/2015 06:47 PM, Mathias Mueller wrote:
> Hi Phil

> sorry, here you go:
> 
> sdb -> sde  Serial Number: JK1170YBHYV6MD
> sdc -> sdf  Serial Number: JK1100YAG64A1T
> sdd -> sdg  Serial Number: JK1121YAG7YDLS
> sde -> sdh  Serial Number: ML0220F30PZUVD
> 
> 
>> We know the possible order combinations:
>>  sdc1 sdb1 sdd1 sde1
>>  sdc1 sdd1 sdb1 sde1
>>  sde1 sdb1 sdd1 sdc1
>>  sde1 sdd1 sdb1 sdc1
> 
> so I used this combinations:
> 
> sdf1 sde1 sdg1 sdh1
> sdf1 sdg1 sde1 sdh1
> sdh1 sde1 sdg1 sdf1
> sdh1 sdg1 sde1 sdf1
> 
> 
>> For now, use data offset 2048 for all of them.
> 
> output of all eight combinations:

Hmmm.  Very strange.  Let's see the dump of the start of the data area of all four partitions:

for x in /dev/sd[efgh]1 ; do echo -e "\n$x\n" ; dd if=$x skip=2048 count=16 2>/dev/null |hexdump -C ; done

Phil


  reply	other threads:[~2015-11-10 23:59 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
2015-11-10 23:47   ` Mathias Mueller
2015-11-10 23:59     ` Phil Turmel [this message]
     [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=564284F5.9080409@turmel.org \
    --to=philip@turmel.org \
    --cc=linux-raid-owner@vger.kernel.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.