From: Wols Lists <antlists@youngman.org.uk>
To: Axel Spallek <axel@spallek.org>, linux-raid@vger.kernel.org
Subject: Re: RAID5 grow interrupted.
Date: Thu, 22 Sep 2016 16:18:06 +0100 [thread overview]
Message-ID: <57E3F62E.10706@youngman.org.uk> (raw)
In-Reply-To: <36947ef9-64e2-f084-4949-476107e2771e@spallek.org>
On 22/09/16 15:11, Axel Spallek wrote:
> The server came up again, but without /dev/md1.
>
> I had made a Backup, which is 2 days old. Not so bad, because I have the
> seafile data on several computers. But to get the RAID back to work
> would be better.
>
> How do I restart the rebuild process with the backup-file?
>
> This is what I get in the console:
>
> root@s10:~# cat /proc/mdstat
> Personalities :
> md1 : inactive sdh1[0](S) sda1[5](S) sdb1[6](S) sdc1[7](S) sdd1[8](S)
> sdf1[4](S) sde1[2](S) sdg1[1](S)
> 31255059140 blocks super 1.2
>
> unused devices: <none>
Okay, quick response here. Won't do any damage, might work.
Stop and reassemble the array ...
mdadm --stop /dev/md1
mdadm --assemble --scan
What you describe sounds like something tried to start the array while
it was half-assembled. There's a bunch of interactions between udev,
systemd, and mdadm, which seem to get badly off-kilter if something
hiccups anywhere.
My suggestion won't do any harm - it might fix the problem, and it'll
give the experts the chance to chime in.
Cheers,
Wol
next prev parent reply other threads:[~2016-09-22 15:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 14:11 RAID5 grow interrupted Axel Spallek
2016-09-22 15:18 ` Wols Lists [this message]
2016-09-22 18:44 ` Axel Spallek
2016-09-22 17:19 ` Andreas Klauer
2016-09-22 18:59 ` Axel Spallek
[not found] ` <9c618b69-1e84-60a8-d25c-55171058c855@websitemanagers.com.au>
2016-09-22 18:41 ` Axel Spallek
2016-09-22 19:45 ` Andreas Klauer
2016-09-23 5:23 ` Axel Spallek
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=57E3F62E.10706@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=axel@spallek.org \
--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.