On 2009-08-24, Emanoil Kotsev <delop...@yahoo.com> wrote: >> >> Thanks for confirming the md5sum and the suggestion. It also fails boot >> to level 1. I used rescue to turn on /etc/default/bootlogd but nothing >> gets logged to /var/log so I guess it doesn't get that far. I would >> have liked to know where it fails, since it does boot rescue CDs. I am >> giving up assuming it is the motherboard. > > hehe, why are you making this assumption?! > > try passing init=/bin/sh to the kernel at boot time ( I wrote a basic 5step > howto get to the limited shell have a look in the list) you can start your > system and recreate the initramfs. This will solve your problem (I'm pretty > sure as I have seen this many times.) > > The problem is I think when you install you have something like 2.6.26-1. > Then if you do an upgrade it will suggest something like 2.6.26-...i686 and > after installing you can not boot - I think this was notorious in etch) > > If you are not using raid/lvm/encryption or other exotics you can skip the > initrd option on boot thus booting directly the kernel > > hope it helps regards > > regards >
Thank you for your suggestion. I just tried booting with init=/bin/sh and unfortunately it got Kernel panic in the same way. The box was not upgraded from the Lenny install of half a year ago. It was just shut down for two weeks. How would I skip initrd? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org