You are not logged in.
I upgrade every weekend and have not had a problem for ages. But this time I cannot boot arch. My default set-up is to use lilo from my Slackware install and use a boot floppy. I have a script that updates the files in the Slackware boot folder. I then boot into Slackware and run lilo to update the boot sector on the floppy. I also have a GRUB boot floppy. I have used that also and tried the arch-fallback with exactly the same result:
kinit:Cannot opon root device sda7(8,7)
kinit: init not found!
kernel panic - not syncing.
The update ran through without any errors and I was expecting a painless update. What do I need to do to get my system back?
Thanks.
Offline
I have just read the wiki section on kernel panic. It suggests that I should roll back to the previously installed kernel. Should I do this, and does this mean that there is a problem with the new kernel on my system?
Thanks.
Offline
OK, I've managed to reinstall the old kernel and nvidia package and now have a working system. Clearly my system has an issue with the new kernel. Is there a way of determining what this issue is and whether I need to do something or whether it will right itself with the next kernel update?
Offline
You should tell us which kernel are you updating from and to, otherwise it is difficult to guess the source of your troubles.
Mortuus in anima, curam gero cutis
Offline
Another default kernel upgrade just hit the repo, so that might fix your problem if that's the one you use.
oz
Offline
You should tell us which kernel are you updating from and to, otherwise it is difficult to guess the source of your troubles.
The upgrade was from 2.6.20.7-2 to 2.6.21.1-7.
Offline
I see the same kernel panic on VMWare Server (v1.0.2.39867) with kernel 2.6.21.1.-7. With 2.6.20-ARCH kernel from install CD I dont see this problem.
Offline
I run arch in a vm and I did an update (pacman -Syu) 2-3 days ago and got a kernel panic on the reboot - but it went away after upgrading to VMWare Workstation 6.0 (from 5.5). So if you're running it under VMWare and you have problems it may help to upgrade.
I have to say that arch is pretty remarkable when it comes to upgrading packages and not breaking all sorts of crap. Can't think of anything that handles it better.
Offline
I upgrade every weekend and have not had a problem for ages. But this time I cannot boot arch. My default set-up is to use lilo from my Slackware install and use a boot floppy. I have a script that updates the files in the Slackware boot folder. I then boot into Slackware and run lilo to update the boot sector on the floppy. I also have a GRUB boot floppy. I have used that also and tried the arch-fallback with exactly the same result:
kinit:Cannot opon root device sda7(8,7) kinit: init not found! kernel panic - not syncing.
The update ran through without any errors and I was expecting a painless update. What do I need to do to get my system back?
Thanks.
I had the same issue. My hard drive (SATA) root partition changed from sda1 to sdc1 because my IDE drives changed from hda and hdb to sda and sdb respectively. It pushed all of my drive letters. You will have to update your /etc/fstab for your root, swap, and home (If different from root) partitions with the new names. If fdisk will work, you can try a "fdisk -l" to see what your drive setup is.
HP Chromebook 14
Offline
TripleE thanks for this. I have been a little busy recently and decided to let things settle down for a bit. Only spotted your post today From what you say it looks like it is a game of chicken and egg if the partitions move with the kernel. I also have a combination of SATA and IDE. If I create a template fstab by incrementing everything in there by a letter and swapping it with the old fstab after the upgrade by using a rescue disk I guess that will do it?
So why has this renaming happened? Does it affect everybody as only a few individuals appear to have reported problems?
Thanks.
Offline
Thanks to the excellent wiki item "Persistent naming of block devices" I have sorted this one. I set-up disk labels and edited /etc/fstab and boot manager then did a kernel update. Everything worked perfectly.
That's what I love about linux (and arch), when presented with a challenge there is always an answer and one comes out the other side with more knowledge and experience.
Alan
Offline