linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: John Valarti <mdadmuser@gmail.com>
Cc: John Robinson <john.robinson@anonymous.org.uk>,
	linux-raid@vger.kernel.org
Subject: Re: Server down-fail​ed RAID5-asking for some assistance
Date: Sun, 24 Apr 2011 12:58:48 +1000	[thread overview]
Message-ID: <20110424125848.6730999e@notabene.brown> (raw)
In-Reply-To: <BANLkTi=X8hzx6TNkfJnoantkzOz5Dv4dGQ@mail.gmail.com>

On Sat, 23 Apr 2011 20:28:34 -0600 John Valarti <mdadmuser@gmail.com> wrote:

> On Sat, Apr 23, 2011 at 8:12 PM, John Robinson
> <john.robinson@anonymous.org.uk> wrote:
> ..
> > That was the letter v twice, not the letter w - and I didn't mean you to
> > specify any devices, just `mdadm -Esvv` on its own.
> 
> Oops! sorry.
> Here you go (sdd is my USB thumb drive):
> 
> mdadm: No md superblock detected on /dev/sdd1.
> mdadm: No md superblock detected on /dev/sdd.
> mdadm: No md superblock detected on /dev/sdc.
> mdadm: No md superblock detected on /dev/sdb.
> /dev/sdc2:
>           Magic : a92b4efc
>         Version : 0.90.00
>            UUID : ddf4d448:36afa319:f0917855:03f8bbe8
>   Creation Time : Mon May 15 16:38:05 2006
>      Raid Level : raid5
>   Used Dev Size : 244975104 (233.63 GiB 250.85 GB)
>      Array Size : 734925312 (700.88 GiB 752.56 GB)
>    Raid Devices : 4
>   Total Devices : 3
> Preferred Minor : 1
> 
>     Update Time : Mon Apr 18 07:48:54 2011
>           State : clean
>  Active Devices : 3
> Working Devices : 3
>  Failed Devices : 1
>   Spare Devices : 0
>        Checksum : 5674ce4e - correct
>          Events : 28580020
> 
>          Layout : left-symmetric
>      Chunk Size : 256K
> 
>       Number   Major   Minor   RaidDevice State
> this     0       8        2        0      active sync   /dev/sda2
> 
>    0     0       8        2        0      active sync   /dev/sda2
>    1     1       8       18        1      active sync   /dev/sdb2
>    2     2       8       34        2      active sync   /dev/sdc2
>    3     3       0        0        3      faulty removed
> /dev/sdc1:
>           Magic : a92b4efc
>         Version : 0.90.00
>            UUID : 79435baa:74a2b2c3:68d7e34f:d95ad478
>   Creation Time : Mon May 15 16:38:08 2006
>      Raid Level : raid1
>   Used Dev Size : 136448 (133.27 MiB 139.72 MB)
>      Array Size : 136448 (133.27 MiB 139.72 MB)
>    Raid Devices : 4
>   Total Devices : 4
> Preferred Minor : 0
> 
>     Update Time : Mon Apr 18 07:36:56 2011
>           State : clean
>  Active Devices : 4
> Working Devices : 4
>  Failed Devices : 0
>   Spare Devices : 0
>        Checksum : 6b5ae9fa - correct
>          Events : 4878
> 
> 
>       Number   Major   Minor   RaidDevice State
> this     0       8        1        0      active sync   /dev/sda1
> 
>    0     0       8        1        0      active sync   /dev/sda1
>    1     1       8       17        1      active sync   /dev/sdb1
>    2     2       8       33        2      active sync   /dev/sdc1
>    3     3       8       49        3      active sync   /dev/sdd1
> /dev/sdb2:
>           Magic : a92b4efc
>         Version : 0.90.00
>            UUID : ddf4d448:36afa319:f0917855:03f8bbe8
>   Creation Time : Mon May 15 16:38:05 2006
>      Raid Level : raid5
>   Used Dev Size : 244975104 (233.63 GiB 250.85 GB)
>      Array Size : 734925312 (700.88 GiB 752.56 GB)
>    Raid Devices : 4
>   Total Devices : 3
> Preferred Minor : 1
> 
>     Update Time : Mon Apr 18 07:48:51 2011
>           State : clean
>  Active Devices : 3
> Working Devices : 3
>  Failed Devices : 1
>   Spare Devices : 0
>        Checksum : 5674ce6b - correct
>          Events : 28580018
> 
>          Layout : left-symmetric
>      Chunk Size : 256K
> 
>       Number   Major   Minor   RaidDevice State
> this     2       8       34        2      active sync   /dev/sdc2
> 
>    0     0       8        2        0      active sync   /dev/sda2
>    1     1       8       18        1      active sync   /dev/sdb2
>    2     2       8       34        2      active sync   /dev/sdc2
>    3     3       0        0        3      faulty removed
> /dev/sdb1:
>           Magic : a92b4efc
>         Version : 0.90.00
>            UUID : 79435baa:74a2b2c3:68d7e34f:d95ad478
>   Creation Time : Mon May 15 16:38:08 2006
>      Raid Level : raid1
>   Used Dev Size : 136448 (133.27 MiB 139.72 MB)
>      Array Size : 136448 (133.27 MiB 139.72 MB)
>    Raid Devices : 4
>   Total Devices : 4
> Preferred Minor : 0
> 
>     Update Time : Mon Apr 18 07:36:56 2011
>           State : clean
>  Active Devices : 4
> Working Devices : 4
>  Failed Devices : 0
>   Spare Devices : 0
>        Checksum : 6b5aea1e - correct
>          Events : 4878
> 
> 
>       Number   Major   Minor   RaidDevice State
> this     2       8       33        2      active sync   /dev/sdc1
> 
>    0     0       8        1        0      active sync   /dev/sda1
>    1     1       8       17        1      active sync   /dev/sdb1
>    2     2       8       33        2      active sync   /dev/sdc1
>    3     3       8       49        3      active sync   /dev/sdd1
> /dev/sda2:
>           Magic : a92b4efc
>         Version : 0.90.00
>            UUID : ddf4d448:36afa319:f0917855:03f8bbe8
>   Creation Time : Mon May 15 16:38:05 2006
>      Raid Level : raid5
>   Used Dev Size : 244975104 (233.63 GiB 250.85 GB)
>      Array Size : 73492531mdadm: No md superblock detected on /dev/sda.
> mdadm: No md superblock detected on /dev/loop0.
> 2 (700.88 GiB 752.56 GB)
>    Raid Devices : 4
>   Total Devices : 3
> Preferred Minor : 1
> 
>     Update Time : Mon Apr 18 07:48:54 2011
>           State : clean
>  Active Devices : 3
> Working Devices : 3
>  Failed Devices : 1
>   Spare Devices : 0
>        Checksum : 5674ce60 - correct
>          Events : 28580020
> 
>          Layout : left-symmetric
>      Chunk Size : 256K
> 
>       Number   Major   Minor   RaidDevice State
> this     1       8       18        1      active sync   /dev/sdb2
> 
>    0     0       8        2        0      active sync   /dev/sda2
>    1     1       8       18        1      active sync   /dev/sdb2
>    2     2       8       34        2      active sync   /dev/sdc2
>    3     3       0        0        3      faulty removed
> /dev/sda1:
>           Magic : a92b4efc
>         Version : 0.90.00
>            UUID : 79435baa:74a2b2c3:68d7e34f:d95ad478
>   Creation Time : Mon May 15 16:38:08 2006
>      Raid Level : raid1
>   Used Dev Size : 136448 (133.27 MiB 139.72 MB)
>      Array Size : 136448 (133.27 MiB 139.72 MB)
>    Raid Devices : 4
>   Total Devices : 4
> Preferred Minor : 0
> 
>     Update Time : Mon Apr 18 07:36:56 2011
>           State : clean
>  Active Devices : 4
> Working Devices : 4
>  Failed Devices : 0
>   Spare Devices : 0
>        Checksum : 6b5aea0c - correct
>          Events : 4878
> 
> 
>       Number   Major   Minor   RaidDevice State
> this     1       8       17        1      active sync   /dev/sdb1
> 
>    0     0       8        1        0      active sync   /dev/sda1
>    1     1       8       17        1      active sync   /dev/sdb1
>    2     2       8       33        2      active sync   /dev/sdc1
>    3     3       8       49        3      active sync   /dev/sdd1
> 
> 
> >>> Please also try `mdadm --assemble --scan --verbose` and post the result.
> mdadm: No arrays found in config file
> 

I should have also asked for "mdadm --version".

However given that above, you want to:


   mdadm --assemble --verbose --force /dev/md1 /dev/sda2 /dev/sdb2 /dev/sdc2

NeilBrown


  reply	other threads:[~2011-04-24  2:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-21 18:29 Server down-fail​ed RAID5-asking for some assistance John Valarti
2011-04-21 19:59 ` David Brown
     [not found]   ` <BANLkTim18Sx6JdZO5PiAqnrakDPzy5PNJQ@mail.gmail.com>
2011-04-22  2:32     ` John Valarti
2011-04-22  2:57       ` Server " NeilBrown
2011-04-22  3:31         ` John Valarti
     [not found]         ` <BANLkTin0SoBzRAear8Jt+26MnVJWouXoNA@mail.gmail.com>
     [not found]           ` <20110423074411.78fef94f@notabene.brown>
     [not found]             ` <BANLkTik_ZY4uoV3E=ua1p+tUD9g8xqQDVg@mail.gmail.com>
     [not found]               ` <20110423184824.55ee7893@notabene.brown>
     [not found]                 ` <BANLkTi=sCfFFfmZTzj2g8-aDNhDqVK8e-A@mail.gmail.com>
     [not found]                   ` <20110424075101.6763309f@notabene.brown>
2011-04-24  0:07                     ` John Valarti
2011-04-24  0:37                       ` John Robinson
2011-04-24  1:49                         ` John Valarti
2011-04-24  2:12                           ` John Robinson
2011-04-24  2:28                             ` John Valarti
2011-04-24  2:58                               ` NeilBrown [this message]
2011-04-24  6:30                                 ` John Valarti
2011-04-24  2:54                       ` NeilBrown
2011-04-24  7:06                         ` John Valarti
2011-04-24  8:41                           ` NeilBrown
2011-04-24 11:57                             ` John Robinson
2011-04-24 12:29                               ` NeilBrown
2011-04-24 16:04                                 ` John Valarti
2011-04-24 16:15                                   ` John Valarti
2011-04-24 16:31                                     ` Mathias Burén
2011-04-24 18:41                                       ` John Valarti
2011-04-22 11:19       ` David Brown

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=20110424125848.6730999e@notabene.brown \
    --to=neilb@suse.de \
    --cc=john.robinson@anonymous.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=mdadmuser@gmail.com \
    /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).