Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756695AbZFGWz1 (ORCPT ); Sun, 7 Jun 2009 18:55:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753903AbZFGWzQ (ORCPT ); Sun, 7 Jun 2009 18:55:16 -0400 Received: from cantor.suse.de ([195.135.220.2]:36874 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750998AbZFGWzP (ORCPT ); Sun, 7 Jun 2009 18:55:15 -0400 From: "NeilBrown" To: "Jaswinder Singh Rajput" Date: Mon, 8 Jun 2009 08:55:03 +1000 (EST) Message-ID: <2f9e3044bafcae848f74a1492b0ea471.squirrel@neil.brown.name> In-Reply-To: <1244413881.18742.31.camel@ht.satnam> References: <200906061959.55592.chris2553@googlemail.com> <200906062215.30571.chris2553@googlemail.com> <1244381140.30664.12.camel@ht.satnam> <1244413881.18742.31.camel@ht.satnam> Subject: Re: 2.6.30-rc8 Oops whilst booting Cc: "Chris Clayton" , linux-kernel@vger.kernel.org, "James Bottomley" , "scsi" , "Tejun Heo" User-Agent: SquirrelMail/1.4.15 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-Priority: 3 (Normal) Importance: Normal Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1456 Lines: 36 On Mon, June 8, 2009 8:31 am, Jaswinder Singh Rajput wrote: > On Sun, 2009-06-07 at 19:38 +0100, Chris Clayton wrote: >> 2009/6/7 Jaswinder Singh Ra >> >> > http://img231.imageshack.us/img231/8931/dscn0610.jpg This message says that it found a vfat filesystem on 8:3x (I cannot see what digit should be 'x'). That is probably sdc1 or sdc2. Maybe even sdc6 or sdc7. However the vfat filesystem didn't have /sbin/init. >> http://img99.imageshack.us/my.php?image=dscn0617b.jpg This one says it couldn't find anything at 8,22, which I think should be sdb6. It also shows that you have and sdc6, but sdb only goes up to sdb3. So it seems that your disk drives have changed name - not a wholely unexpected event these days. We now need answers to questions like: - what device do you expect the root filesystem to be on - how is the kernel being told this? Maybe it is hard coded into your initrd. Knowing which distro and what /etc/fstab says might help (though it wouldn't help me, I'm just about out of my depth at this point) Maybe if you changed /etc/fstab to mount by uuid instead of hardcoding e.g. /etc/sdb3, and then run "mkinitramfs" or whatever, it might work. Good luck, NeilBrown -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/