Hi,
I have fedora core 1 on my computer, recently I updated the kernel from 2.4.22-1.2115.nptlsmp to 2.4.22-1.2149.nptlsmp through yum from redhat update site.
After the update I am not able to boot the new kernel. The older kernel boots without any problem. The machine gives a kernel panic, with the last few lines of the display as follows:
Mounting /proc filesystem Creating block devices Creating root device mkrootdev: label / not found Mounting root filesystem mount: error 2 mounting ext3 pivotroot: pivot_root (/sysroot, /sysroot/initrd) failed: 2 umount /initrd/proc failed: 2 freeing unused kernel memory: 164k freed kernel panic: No init found. Try passing init= option to kernel.
I have a Intel 865GBF Motherboard with Pentium 4 2.6HT processor 2Gb DDR SD RAM and a 120 MB SATA drive ST3120026AS and PATA ST380011A hard disks.
I boot from the sata drive /dev/sda
Please give me some pointers to look into to rectify the problem. Please also indicate if more information is required to diagnose the problem.
Thanks for your help
sadhu
Hiyee Nachiketa,
Hi,
I have fedora core 1 on my computer, recently I updated the kernel freeing unused kernel memory: 164k freed kernel panic: No init found. Try passing init= option to kernel.
[snip]
Boot through the old kernel nachiketa and have the /etc/fstab edited such that in the column that has the partitions defined make sure you remove the "LABEL=xxx" and push in the actual partition names. Use "df -h" towards figuring out which partition mounts on what device.
Its a very generic issue and make sure you have a bootable red hat cd at hand to boot through if things are messed up any time.
Trevor
Thanks for your help
sadhu
Philip..;)
On 2004.01.28 10:02 Philip S Tellis wrote:
On Tue, I think his problem is more to do with lilo.conf or grub.conf than with /etc/fstab <hint>
[snip]
Wanna lay a bet on this one and the winner treats all at the next ilug-bom meeting to samosas-chai and biskuts..:)??. What say???.
Trevor
Trevor Warren wrote:
Boot through the old kernel nachiketa and have the /etc/fstab edited such that in the column that has the partitions defined make sure you remove the "LABEL=xxx" and push in the actual partition names. Use "df -h" towards figuring out which partition mounts on what device.
Its a very generic issue and make sure you have a bootable red hat cd at hand to boot through if things are messed up any time.
Thanks. I tried it out just now, but it messed up the system, as you anticipated. Now I can not mount /dev/sda1 after a rescue boot.
As I do not have the time to experiment just now, I will have to keep it for later. Will let you know the results.
Thanks for the tip, I was searching the net for more than a week without getting any pointers.
sadhu
Trevor
-
Nachiketa Sadhu -
Philip S Tellis -
Trevor Warren