linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: Drew Reusser <dreusser@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Issue with Raid 10 super block failing
Date: Sun, 18 Nov 2012 13:56:19 -0500	[thread overview]
Message-ID: <50A92F53.5080100@turmel.org> (raw)
In-Reply-To: <CAPAnFc9KLBDhCDt1WYiOye5wvRv=zvBDfL1=8OEYg04VBCLHBQ@mail.gmail.com>

Hi Drew,

Please don't top-post.  Repaired again.

On 11/18/2012 12:39 PM, Drew Reusser wrote:
> On Sun, Nov 18, 2012 at 5:01 PM, Phil Turmel <philip@turmel.org> wrote:

[trim /]

>> This all looks like it should work.
>>
>> Please try "mdadm -v --assemble /dev/md0 /dev/sd[abde]1" and show the
>> output.  If it doesn't work, also show "cat /proc/mdstat" and "dmesg".

> The issue is not that I cannot get the raid to create, it is that I
> cannot access any of the files on the system when I mount it.  It was
> setup as an ext4 filesystem and it all was working and I rebooted and
> it was not after that point.
>
>
> mint mnt # mount -t ext4 /dev/md0 /mnt/raid
> mount: wrong fs type, bad option, bad superblock on /dev/md0,
>        missing codepage or helper program, or other error
>        In some cases useful info is found in syslog - try
>        dmesg | tail  or so
>
> mint dev # mdadm -v --assemble /dev/md0 /dev/sd[abde]1
> mdadm: looking for devices for /dev/md0
> mdadm: /dev/sda1 is identified as a member of /dev/md0, slot 0.
> mdadm: /dev/sdb1 is identified as a member of /dev/md0, slot 1.
> mdadm: /dev/sdd1 is identified as a member of /dev/md0, slot 2.
> mdadm: /dev/sde1 is identified as a member of /dev/md0, slot 3.
> mdadm: added /dev/sdb1 to /dev/md0 as 1
> mdadm: added /dev/sdd1 to /dev/md0 as 2
> mdadm: added /dev/sde1 to /dev/md0 as 3
> mdadm: added /dev/sda1 to /dev/md0 as 0
> mdadm: /dev/md0 has been started with 4 drives.
> mint dev # cat /proc/mdstat
> Personalities : [raid10]
> md0 : active raid10 sda1[0] sde1[3] sdd1[2] sdb1[1]
>       1952211968 blocks super 1.2 512K chunks 2 near-copies [4/4] [UUUU]
>
> unused devices: <none>

Ok.  So it's not a raid problem.  You didn't show your dmesg.

Phil

  reply	other threads:[~2012-11-18 18:56 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
2012-11-18 17:01         ` Phil Turmel
2012-11-18 17:39           ` Drew Reusser
2012-11-18 18:56             ` Phil Turmel [this message]
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=50A92F53.5080100@turmel.org \
    --to=philip@turmel.org \
    --cc=dreusser@gmail.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).