All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: Dave Gomboc <dave_gomboc@acm.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid10 recovery assistance requested
Date: Sun, 22 Sep 2013 22:54:57 -0400	[thread overview]
Message-ID: <523FAD81.9070005@turmel.org> (raw)
In-Reply-To: <CA+dwz-0eskPSQ44v0vgwfjwRpTbQaokQ3Q258Em1W2eRi1SO4w@mail.gmail.com>

On 09/22/2013 08:29 PM, Dave Gomboc wrote:
> I now have the 4TB Hitachis in again.  I'll leave them in unless you
> ask me to switch back to the 2TB Seagates.

Ok.

>> dd if=/dev/sdX1 bs=4096 skip=1 count=1 2>/dev/null |hexdump -C
>> dd if=/dev/sdX1 bs=4096 skip=2048 count=16 2>/dev/null |hexdump -C
>>
>> And reverify which drive name in linux corresponds to which serial number.
> 
> ls -l /dev/disk/by-id output includes:
> 
> lrwxrwxrwx 1 root root  9 Sep 22 17:20
> ata-Hitachi_HDS724040ALE640_PK1310PAG5ZY0J -> ../../sdb
> lrwxrwxrwx 1 root root 10 Sep 22 17:20
> ata-Hitachi_HDS724040ALE640_PK1310PAG5ZY0J-part1 -> ../../sdb1
> lrwxrwxrwx 1 root root  9 Sep 22 17:20
> ata-Hitachi_HDS724040ALE640_PK1310PAG62REJ -> ../../sdc
> lrwxrwxrwx 1 root root 10 Sep 22 17:20
> ata-Hitachi_HDS724040ALE640_PK1310PAG62REJ-part1 -> ../../sdc1
> lrwxrwxrwx 1 root root  9 Sep 22 17:20
> ata-Hitachi_HDS724040ALE640_PK1310PAG62T2J -> ../../sdd
> lrwxrwxrwx 1 root root 10 Sep 22 17:20
> ata-Hitachi_HDS724040ALE640_PK1310PAG62T2J-part1 -> ../../sdd1
> lrwxrwxrwx 1 root root  9 Sep 22 17:20
> ata-Hitachi_HDS724040ALE640_PK1311PAG4W5TS -> ../../sda
> lrwxrwxrwx 1 root root 10 Sep 22 17:20
> ata-Hitachi_HDS724040ALE640_PK1311PAG4W5TS-part1 -> ../../sda1

Ok.

> root@sysresccd /root % dd if=/dev/sda1 bs=4096 skip=1 count=1
> 2>/dev/null |hexdump -C
> 00000000  fc 4e 2b a9 01 00 00 00  00 00 00 00 00 00 00 00  |.N+.............|
> 00000010  3c 76 af 95 fa 16 ca 54  33 0b 75 47 b9 04 0b 8a  |<v.....T3.uG....|
> 00000020  63 68 65 61 70 3a 74 65  72 61 6d 6f 6f 63 68 00  |cheap:teramooch.|
> 00000030  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
> 00000040  df 62 21 4d 00 00 00 00  0a 00 00 00 02 01 00 00  |.b!M............|
> 00000050  00 68 e0 e8 00 00 00 00  00 04 00 00 04 00 00 00  |.h..............|
> 00000060  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
> *
> 00000080  00 08 00 00 00 00 00 00  82 6c e0 e8 00 00 00 00  |.........l......|
> 00000090  08 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
> 000000a0  00 00 00 00 00 00 00 00  66 80 69 13 40 2f 8c fb  |........f.i.@/..|
> 000000b0  a7 4e 11 fd 5c a1 7f ee  00 00 00 00 00 00 00 00  |.N..\...........|
> 000000c0  b5 fe 33 52 00 00 00 00  08 02 00 00 00 00 00 00  |..3R............|
> 000000d0  ff ff ff ff ff ff ff ff  7f 39 b7 06 80 01 00 00  |.........9......|
> 000000e0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
> *
> 00000100  00 00 01 00 02 00 03 00  fe ff fe ff fe ff fe ff  |................|
> 00000110  fe ff fe ff fe ff fe ff  fe ff fe ff fe ff fe ff  |................|
> *
> 00000400  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
> *
> 00001000



> root@sysresccd /root % dd if=/dev/sda1 bs=4096 skip=2048 count=16
> 2>/dev/null |hexdump -C
> 00000000  73 65 74 0d 0a 20 20 20  62 20 20 20 20 20 20 20  |set..   b       |

Oops.  Should have dropped the "bs=4096" on that one.  The default
"bs=512" is what I was trying for there.

However, based on the data you've reported, sda1 and sdc1 are identical,
down to the superblock bytes.  And sdb1 and sdd1 are also identical,
down to the superblock bytes.

Are you sure there were no misdirected "dd" operations?

Phil

  parent reply	other threads:[~2013-09-23  2:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-16  3:30 raid10 recovery assistance requested Dave Gomboc
2013-09-19  3:20 ` Dave Gomboc
2013-09-19  4:29   ` Stan Hoeppner
2013-09-20  5:29     ` Dave Gomboc
2013-09-22 17:15       ` Dave Gomboc
2013-09-22 21:52         ` Phil Turmel
2013-09-22 22:45           ` Dave Gomboc
2013-09-22 23:04             ` Dave Gomboc
2013-09-22 23:25             ` Phil Turmel
     [not found]               ` <CA+dwz-0eskPSQ44v0vgwfjwRpTbQaokQ3Q258Em1W2eRi1SO4w@mail.gmail.com>
2013-09-23  2:54                 ` Phil Turmel [this message]
2013-09-23  3:19                   ` Dave Gomboc
2013-09-23  3:27                     ` Phil Turmel
2013-09-23  3:34                       ` Dave Gomboc
2013-09-23  3:51                         ` Phil Turmel
2013-09-23  4:04                           ` Dave Gomboc
2013-09-23  4:12                             ` Phil Turmel
2013-09-23  4:55                               ` Dave Gomboc
2013-09-23  5:07                                 ` Dave Gomboc
2013-09-23  5:19                                 ` Adam Goryachev
2013-09-23 12:32                                 ` Phil Turmel
2013-09-23 12:57                                   ` Dave Gomboc
2013-09-24  0:29                                     ` Adam Goryachev
2013-09-24  5:55                                       ` Dave Gomboc
2013-09-28 15:47                                     ` Dave Gomboc
2013-09-28 16:01                                       ` 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=523FAD81.9070005@turmel.org \
    --to=philip@turmel.org \
    --cc=dave_gomboc@acm.org \
    --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 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.