From: Andread Mayrhoff <repro@spoilbase.eu>
To: linux-raid@vger.kernel.org
Subject: Re: Help needed: array inactive after grow attempt
Date: Thu, 28 Apr 2016 21:50:24 +0200 [thread overview]
Message-ID: <7cfbdd22b8c20acdb95fababfa1a04a6@spoilbase.eu> (raw)
In-Reply-To: <1d5a8c36a6802a9e7e32eb056165f200@spoilbase.eu>
I might add
~/tmp # mdadm --stop /dev/md127
mdadm: stopped /dev/md127
~/tmp # mdadm --assemble --scan
mdadm: Failed to restore critical section for reshape, sorry.
Possibly you needed to specify the --backup-file
Thanks for helping me out of this...
Am 2016-04-28 21:27, schrieb Andread Mayrhoff:
> Hello,
>
> I believe I need some help from an mdadm expert.
>
> I tried to add a disk to an existing RAID5-array (/dev/md127) that
> consisted of 5 disks: /dev/sd[bcdef]1
> The system is a 4.5.2-2-kernel, x86_64-architecture, mdadm 3.3.1.
> I attempted to add partition /dev/sdg1 to that array, in an attempt to
> create a 6-disk-RAID5-array.
> To achieve that goal, I typed "mdadm --add /dev/md127 /dev/sdg1".
> As I found that working, I attempted to grow the array by typing
> "mdadm --grow /dev/md127 --raid-devices=6".
>
> I left my machine, and when I returned, I found it had been switched
> off by my... ahem, anyway, it had been switched off.
>
> I powered it on again, "cat /proc/mdstat" returned
>
>>>
> Personalities : [raid6] [raid5] [raid4]
> md127 : inactive sdg1[9](S) sdf1[8](S) sdc1[5](S) sdb1[6](S)
> sde1[4](S) sdd1[7](S)
> 17578345656 blocks super 1.0
>
> unused devices: <none>
> <<
>
> mdadm --detail /dev/md127 returns
>
>>>
> /dev/md127:
> Version : 1.0
> Raid Level : raid0
> Total Devices : 6
> Persistence : Superblock is persistent
>
> State : inactive
>
> Delta Devices : 1, (-1->0)
> New Level : raid5
> New Layout : left-symmetric
> New Chunksize : 128K
>
> Name : n54l:raid5.11111111.eu
> UUID : b120f4d9:d1ba5648:e1359c5d:7a36372e
> Events : 60868
>
> Number Major Minor RaidDevice
>
> - 8 17 - /dev/sdb1
> - 8 33 - /dev/sdc1
> - 8 49 - /dev/sdd1
> - 8 65 - /dev/sde1
> - 8 81 - /dev/sdf1
> - 8 97 - /dev/sdg1
> <<
>
> Now, before I do anything extreme like unplugging that disk again or
> forcing a recreate, could an expert suggest the next logical step I
> should do. I know this sounds pretty defensive, but rather than
> playing "Raid-hero with an erased set of disks" I'd go along with
> "Raid-idiot that needed experts' advice which is why he still's got
> all his data".
>
> Thanks for your advice!
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-04-28 19:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 19:27 Help needed: array inactive after grow attempt Andread Mayrhoff
2016-04-28 19:50 ` Andread Mayrhoff [this message]
2016-04-28 20:02 ` Andread Mayrhoff
2016-05-03 18:47 ` Phil Turmel
2016-04-28 22:12 ` Wols Lists
2016-04-28 22:43 ` Adam Goryachev
[not found] ` <c98c947ff2759669bcb5ccf87c3dd245@spoilbase.eu>
2016-04-28 23:30 ` Wols Lists
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=7cfbdd22b8c20acdb95fababfa1a04a6@spoilbase.eu \
--to=repro@spoilbase.eu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox