From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Knight Subject: Re: assembling array after disk failure Date: Sat, 26 Oct 2013 18:31:19 -0400 Message-ID: <526C42B7.1020202@woh.rr.com> References: <526C2E5F.1060507@woh.rr.com> <526C3C3E.6040406@turmel.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <526C3C3E.6040406@turmel.org> Sender: linux-raid-owner@vger.kernel.org To: Phil Turmel Cc: linux-raid@vger.kernel.org List-Id: linux-raid.ids Thank you. --force is exactly what I needed to do. It is working properly now. On 10/26/2013 06:03 PM, Phil Turmel wrote: > On 10/26/2013 05:04 PM, Dan Knight wrote: >> Hello after some trouble with disks, I am trying to reassemble an >> array. When I start the array, I am told I don't have enough disks to >> start. What is really strange to me is that when I examine the disks in >> the array, mdadm gives me different overall information for different >> disks. What do I need to do to assemble the array? >> >> **[root@server etc]# mdadm -As >> **mdadm: /dev/md127 assembled from 3 drives - not enough to start the >> array.** >> *[root@server etc]# cat /proc/mdstat* >> Personalities : >> md127 : inactive sdf[2](S) sde[4](S) sdb[3](S) sdc[1](S) sdd[0](S) >> 9767572480 blocks super 0.91 > "--force" is your friend in such situations. > > mdadm --stop /dev/md127 > mdadm -Af /dev/md127 /dev/sd[bcdef] > > You haven't given enough information for any advice on avoiding future > trouble... > > Phil >