From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sarah Newman Subject: Re: raid 5 crashed Date: Fri, 3 Jun 2016 09:31:37 -0700 Message-ID: <5751B0E9.8040008@prgmr.com> References: <20160511131524.GA11811@cthulhu.home.robinhill.me.uk> <574C8EB9.3070706@youngman.org.uk> <574D958F.8060209@turmel.org> <574DDCBD.40801@youngman.org.uk> <95079572-f319-ca57-a3e9-e8d00ef40248@fnarfbargle.com> <20b1858b-0cd7-a7de-82af-9167dbcfb09e@fnarfbargle.com> <574F00F5.80801@youngman.org.uk> <2f3e2fe6-1810-e7bd-7dc0-483ed4f0d46b@fnarfbargle.com> <57503C3F.6020005@youngman.org.uk> <40b1ed1e-b0bd-a496-b5c8-6ad1f370b3ee@fnarfbargle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-raid-owner@vger.kernel.org To: bobzer Cc: linux-raid List-Id: linux-raid.ids On 06/03/2016 08:27 AM, bobzer wrote: > i use losetup to make my dd image a dev/loop device and took the risk > of start the raid but it doesn't work: > i did : > mdadm --assemble --force --name=/dev/md0 /dev/sdb1 /dev/sdd1 > /dev/loop2 /dev/sdc1 > it answer : > mdadm: device /dev/sdb1 exist but is not an md array > > except that is not true, sdb1 and sdd1 are the correct drive. sdc1 is > the one saw as a spare The --name is for if you want to call the device something other than just md0. If you use /dev/md0 instead of --name=/dev/md0 it might work.