All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseba Ibarra <wajalotnet@gmail.com>
To: list linux-raid <linux-raid@vger.kernel.org>
Subject: Can't mount /dev/md0 Raid5
Date: Wed, 11 Oct 2017 12:25:14 +0200	[thread overview]
Message-ID: <59DDF18A.9060800@gmail.com> (raw)

The md0 is ext4 formated. But now, I can even start the SO when all the 
disk are pluged. One of them is corrupt. It makes an odd sound at the 
starting. However if I unplug that disk the system start fine, however 
no RAID is detected and after assemble it says:


root@grafico:/home/jose# mdadm --detail /dev/md0
/dev/md0:
                  Version : 1.2
       Creation Time : Sat Aug 5 23:10:50 2017
             Raid Level : raid5
      Used Dev Size : 976629760 (931.39 GiB 1000.07 GB)
         Raid Devices : 4
         Total Devices : 3
           Persistence : Superblock is persistent

          Update Time : Thu Sep 21 13:34:35 2017
                      State : active, degraded, Not Started
       Active Devices : 3
    Working Devices : 3
       Failed Devices : 0
       Spare Devices : 0

                   Layout : left-symmetric
           Chunk Size : 512K

                    Name : servidor:0
                     UUID : 0b44a3b8:83eafabc:644afc87:bdb5b1f3
                   Events : 3109

     Number   Major   Minor   RaidDevice State
-       0        0        0      removed
1       8       17        1      active sync   /dev/sdb1
2       8       33        2      active sync   /dev/sdc1
3       8       49        3      active sync   /dev/sdd1


I'm not sure how to continue, since i don't see the RAID. GParted see 
the disks, however doesn't see the md0 and I'm bit scared if I lost the 
data content.


Joseba Ibarra

             reply	other threads:[~2017-10-11 10:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-11 10:25 Joseba Ibarra [this message]
2017-10-11 10:42 ` Can't mount /dev/md0 Raid5 Rudy Zijlstra
2017-10-11 11:14   ` Joseba Ibarra
2017-10-11 11:29     ` Adam Goryachev
2017-10-11 11:56       ` Joseba Ibarra
2017-10-11 13:23         ` Adam Goryachev
2017-10-11 13:35           ` Joseba Ibarra
2017-10-11 19:13             ` Adam Goryachev
2017-10-11 19:46               ` Joseba Ibarra
2017-10-11 14:01         ` Mikael Abrahamsson
2017-10-11 17:27           ` Joseba Ibarra
2017-10-11 20:46             ` NeilBrown
     [not found]               ` <59DE891F.1@gmail.com>
     [not found]                 ` <878tghwf6j.fsf@notabene.neil.brown.name>
     [not found]                   ` <59DE9313.50509@gmail.com>
2017-10-11 21:55                     ` Joseba Ibarra
2017-10-11 19:49           ` John Stoffel
2017-10-11 20:57             ` Joseba Ibarra
  -- strict thread matches above, loose matches on Subject: below --
2017-09-22  9:13 Joseba Ibarra
2017-09-27 22:38 ` NeilBrown

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=59DDF18A.9060800@gmail.com \
    --to=wajalotnet@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 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.