All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Goryachev <mailinglists@websitemanagers.com.au>
To: o1bigtenor <o1bigtenor@gmail.com>,
	Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Request for assistance
Date: Wed, 6 Jul 2016 11:55:06 +1000	[thread overview]
Message-ID: <577C64FA.6050504@websitemanagers.com.au> (raw)
In-Reply-To: <CAPpdf58z4JagWmP=xiUj9qOU-bdyN7W=EvcM9evjCT4ZWp+VxQ@mail.gmail.com>

On 06/07/16 10:13, o1bigtenor wrote:
> Greetings
>
> Running a Raid 10 array with 4 - 3 TB drives. Have a UPS but this area
> gets significant lightning and also brownout (rural power) events.
>
> Found the array was read only this morning. Thought that rebooting the
> system might correct things - - - it did not as the array did not
> load.
>
> commands used followed by system response
>
> mdadm --detail /dev/md0
>     mdadm:  md device /dev/md0 does not appear to be active.
>
> cat /proc/mdstat
>     md0  : inactive sdc1[5](S) sdf1[8](S) sde1[7](S) sdb1[4](S)
>
> mdadm -E /dev/sdb1
>                         sdc1
>                         sde1
>                         sdf1
>
> everything is the same except for 2 items
>
> sde and sdf have uptime listed from July 04 05:50:46
>                            events 64841
>                            array state of AAAA
>
> sdb and sdc have uptime listed from July 05 01:57:38
>                             events 64844
>                             array state of AAA.
>
>
>
> Do I just re-create the array?
>
No, not if you value your data. Only re-create the array if you are told 
to by someone (knowledgeable) on the list.

In your case, I think you should stop the array.
mdadm --stop /dev/md0
Make sure there is nothing listed in /proc/mdstat
Then try to assemble the array, but force the events to match:
mdadm --assemble /dev/md0 --force /dev/sd[bcef]1

If that doesn't work, then include the output from dmesg as well as 
/proc/mdstat and any commandline output generated.

You might also want to examine why two drives dropped, referring to logs 
or similar might assist.

Regards,
Adam

-- 
Adam Goryachev Website Managers www.websitemanagers.com.au

  reply	other threads:[~2016-07-06  1:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-06  0:13 Request for assistance o1bigtenor
2016-07-06  1:55 ` Adam Goryachev [this message]
2016-07-06 12:14   ` o1bigtenor
2016-07-06 12:51     ` Wols Lists
2016-07-06 18:28       ` o1bigtenor
2016-07-06 21:31         ` Wols Lists
2016-07-07  2:05         ` Brad Campbell
2016-07-07  3:28           ` o1bigtenor
2016-07-06  7:39 ` keld
2016-07-06 12:15   ` o1bigtenor
  -- strict thread matches above, loose matches on Subject: below --
2022-10-22  8:11 request " Tanju Brunostar
2022-10-22  8:13 ` Julia Lawall
2022-10-22  8:20   ` Tanju Brunostar
2022-10-20 11:00 Request " Ubuntu
2022-10-20 11:10 ` Greg KH
2022-10-20 11:14   ` Tanju Brunostar
2022-10-20 11:59     ` Julia Lawall
     [not found] ` <CAOkYk0iU0B98JsH77avky--AS19V=GhQox2f_b4PAG3ZBB+SVQ@mail.gmail.com>
2022-10-20 11:34   ` Tanju Brunostar
2022-10-20 12:10     ` Greg KH
2022-10-20 14:39       ` Theodore Ts'o
     [not found]         ` <Y1Hby38PE/QVlRhF@Slackware>
2022-10-21  6:11           ` Tanju Brunostar
2021-04-12  1:17 o1bigtenor
2010-03-12 14:04 Aditya Pendyala

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=577C64FA.6050504@websitemanagers.com.au \
    --to=mailinglists@websitemanagers.com.au \
    --cc=linux-raid@vger.kernel.org \
    --cc=o1bigtenor@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 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.