Solved

Kernel update, system (Debian) doesn't boot anymore

Posted on 2008-10-25
2
676 Views
Last Modified: 2013-12-06
Kernel was 2.4.18-bf2.4, excecuted

apt-get install grub
grub-install

apt-get install linux-image-2.6.18-6-686

So far so good. When I boot however, I get stuck in a grub command prompt. What i did there was

root (hd0,0)       result from "find /boot/grub/stage1"
setup hd0
kernel /vmlinuz-2.6.18-6-686 root=/dev/hda1         (i had 2 partitions / and /home they're on an IDE disk)

initrd /initrd.img-2.6.18-6-686

So far so good, no error messages, just confirmation messages.

Now when i boot, i get a message "waiting for root file system"...and after a few minutes i fall into the busybox shell. Nothing i do there seems to have any effect.

Booting into the old kernel also doesn't work because i've no initrd of it. Can i create this in the shell ? i suppose not? Why is the root file system not working, but the vmlinuz file in /boot can be found? /boot is not a seperate partition.

How can i boot into the old kernel?
what mistakes did i make in upgrading from 2.4 to 2.6?

Does anybody have any ideas?
0
Comment
Question by:Xyptilon2
2 Comments
 
LVL 4

Accepted Solution

by:
ben-gur earned 500 total points
Comment Utility
Boot from the first installation CD, but instead of starting the installation type "linux rescue" to start the command prompt rescue mode.
Run chroot to set the / directory:
chroot /mnt/sysimage
See if you can install grub again:
/sbin/grub-install /dev/hda
This should have fixed the problem.

If not, boot again to "rescue mode". Execute "grub". Then install grub using this commands:
grub> device (hd0) /dev/hda1
grub> root (hd0,0)
grub> setup (hd0)
Should also work...

Here is a comprehensive guide for solving problems with grub:
http://www.linuxforums.org/forum/linux-tutorials-howtos-reference-material/6527-howto-solve-boot-problems-grub.html

Good luck,
Adam.
0
 
LVL 13

Author Closing Comment

by:Xyptilon2
Comment Utility
Didn't solve the problem, but i think it was unsolvable, thankfully it was a test machine that was being phased out so no harm done. Just installed a new system from scratch, thanks for the link though :)
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Setting up Secure Ubuntu server on VMware 1.      Insert the Ubuntu Server distribution CD or attach the ISO of the CD which is in the “Datastore”. Note that it is important to install the x64 edition on servers, not the X86 editions. 2.      Power on th…
It’s 2016. Password authentication should be dead — or at least close to dying. But, unfortunately, it has not traversed Quagga stage yet. Using password authentication is like laundering hotel guest linens with a washboard — it’s Passé.
Learn how to get help with Linux/Unix bash shell commands. Use help to read help documents for built in bash shell commands.: Use man to interface with the online reference manuals for shell commands.: Use man to search man pages for unknown command…
Connecting to an Amazon Linux EC2 Instance from Windows Using PuTTY.

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

8 Experts available now in Live!

Get 1:1 Help Now