You are not logged in.
Pages: 1
I did a base install from an Arch 0.7.2 CD. The system came up fine afterwards. I proceeded to do a pacman -Syu system upgrade. After rebooting, I get the following error:
kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
I'm doing this on a ThinkPad T60p (SATA hard disk).
What is the problem and what can I do to solve it?
On a side note: when a command is actively being run, such as a pacman upgrade, I'm able to move the caret/cursor around the terminal, including up onto previous lines. I've not got gdm running or anything, and I've not seen this happening on any of the other distributions that I've used. Is this normal, and what's causing this?
Offline
Be sure you answered "yes" to the upgrade questions asked when doing the ....Syu.... In addition, if using lilo, you must modify lilo.conf for the mkinitcpio changes. If using grub, changes are also necessary there AFAIK.
If possible, read the wiki for the details.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Thanks for that; I'd not adjusted my grub configuration.
For anyone else with the same problem: http://wiki.archlinux.org/index.php/Mkinitcpio
Offline
check our grub menu.lst and make sure the line
initrd /boot/something.img reads initrd /boot/kernel26.img
I had to do that when I upgraded and I had the exact same error you did,
Offline
miito;
Open up the initial post and you will find an EDIT icon in upper right hand corner to enable you to modify the subject to indicate it as solved.
Have a good day!
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
check our grub menu.lst and make sure the line
initrd /boot/something.img reads initrd /boot/kernel26.img
I had to do that when I upgraded and I had the exact same error you did,
that fixed my exact same problem, thanks!
Offline
Pages: 1