From mboxrd@z Thu Jan 1 00:00:00 1970 From: Phil Turmel Subject: Re: recovering failed and unrecognizable RAID5 during mdadm --grow without backup Date: Fri, 13 May 2016 10:11:11 -0400 Message-ID: <5735E07F.2030802@turmel.org> References: <1b26650f-0b2c-2485-f781-e3fd26340741@misalpina.net> <5734D23D.6030400@turmel.org> <5734E637.6030307@turmel.org> <7cf56631-7909-6a92-f0b2-05dd02722ee8@misalpina.net> <5735DF05.8080706@turmel.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5735DF05.8080706@turmel.org> Sender: linux-raid-owner@vger.kernel.org To: Claudiu Rad , linux-raid@vger.kernel.org List-Id: linux-raid.ids On 05/13/2016 10:04 AM, Phil Turmel wrote: > On 05/12/2016 05:37 PM, Claudiu Rad wrote: > >> how can i safely stop this reshape and assuming my / partition inside >> the array is sane enough restart the actual server normally after >> fsck-ing all volumes? > > Well, your root is inside the array. So you won't be able to boot > without the array assembling in the initramfs, which needs manual > intervention to supply the backup file. Actually, if it still isn't too far into the reshape, you could use --revert-reshape. Then it'll reshape back to the original chunk size what it has done so far. That might be quicker than finishing the reshape. Then you could reboot into your normal OS. Whether you finish reshaping, or unreshaping, you need to not be reshaping at all when you boot into your normal OS, if you can't do the initramfs console. Phil