[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#337293: linux-image-2.6.14-1-k7: kernel doesn't boot...



On Mon, Nov 07, 2005 at 09:49:53PM +0100, Erik van Konijnenburg wrote:
> On Mon, Nov 07, 2005 at 10:54:37AM +0100, Bruno Boettcher wrote:
> > On Thu, Nov 03, 2005 at 09:09:34PM +0100, Erik van Konijnenburg wrote:
> > Hello!
> > 
> > > Underneath the tmpfs mounted on /dev is the /dev/ that is part of your
> > > root device.  You can do 'mount -o bind / /mnt; ls /mnt/dev' to see
> > > what's there.  /dev/.static/dev/ may contain an alias of this.
> > didn't knew this one :D
> > alas:
> >  ls  -l /dev/.static/dev/console /dev/console
> >  crw-------  1 root root 5, 1 2005-11-03 19:02 /dev/console
> >  crw-------  1 root tty  5, 1 2005-10-27 23:54 /dev/.static/dev/console
> > 
> > > For yaird, that /dev on your root device needs to contain at
> > > least /dev/console, there's some other stuff too that you want there.
> > > On an etch install I tested this week, those special files are available
> > > without special user action necessary.
> > seems as if the file is there....
> 
> Pity, it was a nice theory.
> 
> > i have put up the stuff related to what asked me the ramfs guy and the
> > menu.lst onto http://bboett.free.fr/kernel/
> > could it be possible that theres some problem with rdeving the installed
> > kernel?
> > strange this is that all kernels have a boot device hda1.... and i don't
> > have any device called by that name... does grub automaticly do a rdev?
> 
> Rdev as in http://www.netadmintools.com/html/8rdev.man.html ?
> That's been obsolete a few years now.
> 
> Some notes on your dump:
> * the root=/dev/sdb1 should be redundant but harmless.
>   you may want to try without.
> * you seem to have a aic7xxx type scsi controller with a straightforward ext3 fs on it
>   as root device.  Correct?

And there are recent bug reports for that driver:
see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=338089
This may cause your boot problems.

> * boot with 'ydebug' on the kernel command line and you'll be dumped in a shell
>   before switching to the real root.
>   You'll also see the init script commands being executed.
>   Any odd error messages?
> 
> * At this point you don't have ls, but you can do 'cd /mnt; echo *'.
>   /mnt should at this point have your root device, with /mnt/dev/console on it.
> 
> Have a look around /mnt; does it look like your root?
> 
> Have a look at /sys/block/sdb; does it look as a /sys entry for a working disk?
> 
> Regards,
> Erik



Reply to: