From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Robinson Subject: Re: Server =?UTF-8?B?ZG93bi1mYWls4oCLZWQgUkFJRDUtYXNraW5nIGZvciBz?= =?UTF-8?B?b21lIGFzc2lzdGFuY2U=?= Date: Sun, 24 Apr 2011 03:12:54 +0100 Message-ID: <4DB38726.2090805@anonymous.org.uk> References: <20110422125734.1a68a736@notabene.brown> <20110423074411.78fef94f@notabene.brown> <20110423184824.55ee7893@notabene.brown> <20110424075101.6763309f@notabene.brown> <4DB370E1.5030602@anonymous.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-raid-owner@vger.kernel.org To: John Valarti Cc: NeilBrown , linux-raid@vger.kernel.org List-Id: linux-raid.ids On 24/04/2011 02:49, John Valarti wrote: [...] > This is looking gloomy now. No it isn't! > There definitely is NO mdadm.conf > I checked. > I used "find" OK, that's fine - I didn't really expect there to be, unless you were using an emergency shell half-way through booting, in which case if there was one it might have been wrong since you've had to remove drives. [...] > mdadm -Esvv /dev/sd[abc]2: > mdadm: --examine/-E cannot be given with -w That was the letter v twice, not the letter w - and I didn't mean you to specify any devices, just `mdadm -Esvv` on its own. >> Please also try `mdadm --assemble --scan --verbose` and post the result. > HERE: > mdadm: /dev/sda2 not identified in config file. > mdadm: /dev/sdb2 not identified in config file. > mdadm: /dev/sdc2 not identified in config file. Again, I didn't mean you to specify any devices, just exactly `mdadm --assemble --scan --verbose` on its own. I'm not quite sure where you are but your timezone is -0600 while mine is +0100, it's gone 3 in the morning, so I'm going to bed now. Neil Brown is +1000 so it's Easter Sunday for him, which makes me think it's unlikely you'll see a reply from him today/tomorrow. Just stay calm and don't panic, we'll get there. Cheers, John.