All of lore.kernel.org
 help / color / mirror / Atom feed
From: Drew Reusser <dreusser@gmail.com>
To: Phil Turmel <philip@turmel.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: Issue with Raid 10 super block failing
Date: Sun, 18 Nov 2012 16:49:56 +0000	[thread overview]
Message-ID: <CAPAnFc9_AqQCHnzpNukVJNuaAZ0k9+i0wEZn6SAX=ucF_X_k2g@mail.gmail.com> (raw)
In-Reply-To: <50A8F247.8060002@turmel.org>

On Sun, Nov 18, 2012 at 2:35 PM, Phil Turmel <philip@turmel.org> wrote:
> Good morning Drew,
>
>
> On 11/17/2012 10:07 PM, Drew Reusser wrote:
>
> [top-posting repaired.  Please don't do that on kernel.org lists.]
>
>> On Sat, Nov 17, 2012 at 11:48 PM, Phil Turmel <philip@turmel.org> wrote:
>
> [trim /]
>
>>> This isn't a complete report for four devices.  Please show the output
>>> of "blkid" and "cat /proc/partitions" so we can help you report the
>>> details needed.
>
>> C is the pen-drive I am booting from currently and F is the 2TB disk I
>> was using to backup to.
>>
>> mint dev # cat /proc/partitions
>> major minor  #blocks  name
>>
>>    7        0     939820 loop0
>>    8        0  976762584 sda
>>    8        1  976760832 sda1
>>    8       16  976762584 sdb
>>    8       17  976237568 sdb1
>>    8       32    1985024 sdc
>>    8       33    1984960 sdc1
>>    8       48  976762584 sdd
>>    8       49  976760832 sdd1
>>    8       64  976762584 sde
>>    8       65  976237568 sde1
>>   11        0    1048575 sr0
>>    8       80 1953514584 sdf
>>    8       81 1953512448 sdf1
>
> Ok.  This suggests that the array was originally built from partition #1
> on each drive, not the drive itself.
>
>> mint dev # blkid
>> /dev/loop0: TYPE="squashfs"
>> /dev/sda1: UUID="db9e3115-556a-49db-27c4-2d3002657472"
>> UUID_SUB="933ec5c0-d681-9e33-adb0-e6c890e337bd" LABEL="mint:0"
>> TYPE="linux_raid_member"
>> /dev/sdb1: UUID="db9e3115-556a-49db-27c4-2d3002657472"
>> UUID_SUB="9d6df7c7-ce40-1405-4ea1-8763a528ecc5" LABEL="mint:0"
>> TYPE="linux_raid_member"
>> /dev/sdc1: UUID="5860-2FA0" TYPE="vfat"
>> /dev/sdd1: UUID="db9e3115-556a-49db-27c4-2d3002657472"
>> UUID_SUB="fa1a1b82-989e-933a-95e4-d2495cee901d" LABEL="mint:0"
>> TYPE="linux_raid_member"
>> /dev/sde1: UUID="db9e3115-556a-49db-27c4-2d3002657472"
>> UUID_SUB="594ed481-471e-f11a-027f-1c246f9d057d" LABEL="mint:0"
>> TYPE="linux_raid_member"
>> /dev/sdf1: UUID="1C3C2B104A8445ED" TYPE="ntfs"
>
> As does this.  Somehow you ended up with a v1.2 superblock on /dev/sda.
>
> Please repeat the examines with "mdadm -E /dev/sd[abde]1"
>
> Phil
>
>

I originally started the disks at (block?) 2048 so there was a 2mb
partition to load the bootloader (grub) and mdadm.  Everything else
was on one partition as you observed.  I figured the simpler the
better for this configuration.

Here you go.


mint dev # mdadm -E /dev/sd[abde]1
/dev/sda1:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : db9e3115:556a49db:27c42d30:02657472
           Name : mint:0  (local to host mint)
  Creation Time : Thu Nov 15 16:08:02 2012
     Raid Level : raid10
   Raid Devices : 4

 Avail Dev Size : 1953259520 (931.39 GiB 1000.07 GB)
     Array Size : 1952211968 (1861.77 GiB 1999.07 GB)
  Used Dev Size : 1952211968 (930.89 GiB 999.53 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : 933ec5c0:d6819e33:adb0e6c8:90e337bd

    Update Time : Thu Nov 15 20:08:55 2012
       Checksum : b516984f - correct
         Events : 17

         Layout : near=2
     Chunk Size : 512K

   Device Role : Active device 0
   Array State : AAAA ('A' == active, '.' == missing)
/dev/sdb1:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : db9e3115:556a49db:27c42d30:02657472
           Name : mint:0  (local to host mint)
  Creation Time : Thu Nov 15 16:08:02 2012
     Raid Level : raid10
   Raid Devices : 4

 Avail Dev Size : 1952212992 (930.89 GiB 999.53 GB)
     Array Size : 1952211968 (1861.77 GiB 1999.07 GB)
  Used Dev Size : 1952211968 (930.89 GiB 999.53 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : 9d6df7c7:ce401405:4ea18763:a528ecc5

    Update Time : Thu Nov 15 20:08:55 2012
       Checksum : 3103c408 - correct
         Events : 17

         Layout : near=2
     Chunk Size : 512K

   Device Role : Active device 1
   Array State : AAAA ('A' == active, '.' == missing)
/dev/sdd1:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : db9e3115:556a49db:27c42d30:02657472
           Name : mint:0  (local to host mint)
  Creation Time : Thu Nov 15 16:08:02 2012
     Raid Level : raid10
   Raid Devices : 4

 Avail Dev Size : 1953259520 (931.39 GiB 1000.07 GB)
     Array Size : 1952211968 (1861.77 GiB 1999.07 GB)
  Used Dev Size : 1952211968 (930.89 GiB 999.53 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : fa1a1b82:989e933a:95e4d249:5cee901d

    Update Time : Thu Nov 15 20:08:55 2012
       Checksum : 5ea6d02d - correct
         Events : 17

         Layout : near=2
     Chunk Size : 512K

   Device Role : Active device 2
   Array State : AAAA ('A' == active, '.' == missing)
/dev/sde1:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : db9e3115:556a49db:27c42d30:02657472
           Name : mint:0  (local to host mint)
  Creation Time : Thu Nov 15 16:08:02 2012
     Raid Level : raid10
   Raid Devices : 4

 Avail Dev Size : 1952212992 (930.89 GiB 999.53 GB)
     Array Size : 1952211968 (1861.77 GiB 1999.07 GB)
  Used Dev Size : 1952211968 (930.89 GiB 999.53 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : 594ed481:471ef11a:027f1c24:6f9d057d

    Update Time : Thu Nov 15 20:08:55 2012
       Checksum : 786bd4bc - correct
         Events : 17

         Layout : near=2
     Chunk Size : 512K

   Device Role : Active device 3
   Array State : AAAA ('A' == active, '.' == missing)

  reply	other threads:[~2012-11-18 16:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-17 18:06 Issue with Raid 10 super block failing Drew Reusser
2012-11-17 23:48 ` Phil Turmel
2012-11-18  3:07   ` Drew Reusser
2012-11-18 14:35     ` Phil Turmel
2012-11-18 16:49       ` Drew Reusser [this message]
2012-11-18 17:01         ` Phil Turmel
2012-11-18 17:39           ` Drew Reusser
2012-11-18 18:56             ` Phil Turmel
2012-11-18 19:10               ` Drew Reusser
2012-11-19 13:39                 ` Phil Turmel
2012-11-19 16:44                   ` Drew Reusser
2012-11-19 17:12                     ` Phil Turmel
2012-11-19 20:41                   ` Drew Reusser
2012-11-19 20:47                     ` 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='CAPAnFc9_AqQCHnzpNukVJNuaAZ0k9+i0wEZn6SAX=ucF_X_k2g@mail.gmail.com' \
    --to=dreusser@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=philip@turmel.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.