From: Greg KH <gregkh@linuxfoundation.org>
To: Alexander Sommer <alex@sommer-info.net>
Cc: stable@vger.kernel.org
Subject: Re: Betreff: crashed linux mdadm raid
Date: Wed, 12 Jun 2019 19:09:33 +0200 [thread overview]
Message-ID: <20190612170933.GA6986@kroah.com> (raw)
In-Reply-To: <7ebdd1c4e0f955fa2b5bebc85547c975@sommer-info.net>
On Wed, Jun 12, 2019 at 06:50:09PM +0200, Alexander Sommer wrote:
> Hello,
>
> after a problem with my external disk enclosure my md-raid is broken.
>
> if I do an assemble I got this:
> root@server:~ # mdadm --assemble /dev/md2 /dev/sd[lmnop]1
> mdadm: /dev/md2 assembled from 2 drives - not enough to start the array.
>
> I assume the broblem is that the disks events counter has different
> states:
>
> root@server:~ # mdadm --examine /dev/sd[lmpno]1 | egrep -e "/dev/sd" -e
> "Raid Level" -e Events -e "Device Role" -e "Array State"
> /dev/sdl1:
> Raid Level : raid5
> Events : 253626
> Device Role : Active device 0
> Array State : AA.AA ('A' == active, '.' == missing, 'R' == replacing)
> /dev/sdm1:
> Raid Level : raid5
> Events : 253626
> Device Role : Active device 1
> Array State : AA.AA ('A' == active, '.' == missing, 'R' == replacing)
> /dev/sdn1:
> Raid Level : raid5
> Events : 253618
> Device Role : Active device 2
> Array State : AAAAA ('A' == active, '.' == missing, 'R' == replacing)
> /dev/sdo1:
> Raid Level : raid5
> Events : 253618
> Device Role : Active device 3
> Array State : AAAAA ('A' == active, '.' == missing, 'R' == replacing)
> /dev/sdp1:
> Raid Level : raid5
> Events : 253618
> Device Role : Active device 4
> Array State : AAAAA ('A' == active, '.' == missing, 'R' == replacing)
>
> This raid is used for backup, I do rsync to this device and have for
> every day on directory and I need some of the old data, so I need only a
> way, to read some old files, and than it is no problem to clean the
> disks and create it new. So I do not need the realy last state. If I got
> the files which are some days old it will be ok, on this device normaly
> I do not delete something, there come only new files and hardlinks to
> the old ones.
>
> So, do I have a chance to start it?
No idea, try contacting your distribution for support.
good luck!
greg k-h
prev parent reply other threads:[~2019-06-12 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 16:50 Betreff: crashed linux mdadm raid Alexander Sommer
2019-06-12 17:09 ` Greg KH [this message]
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=20190612170933.GA6986@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alex@sommer-info.net \
--cc=stable@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.