linux-kernel - Re: 2.6.30-rc8 Oops whilst booting

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2f9e3044bafcae848f74a1492b0ea471.squirrel@neil.brown.name>
Date:	Mon, 8 Jun 2009 08:55:03 +1000 (EST)
From:	"NeilBrown" <neilb@...e.de>
To:	"Jaswinder Singh Rajput" <jaswinder@...nel.org>
Cc:	"Chris Clayton" <chris2553@...glemail.com>,
	linux-kernel@...r.kernel.org,
	"James Bottomley" <james.bottomley@...senpartnership.com>,
	"scsi" <linux-scsi@...r.kernel.org>, "Tejun Heo" <tj@...nel.org>
Subject: Re: 2.6.30-rc8 Oops whilst booting

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/