Page 1 of 1

Upgrade .38 to .40 -- Kernel panic

Posted: Tue Mar 04, 2008 5:45 pm
by Kirse
Hi,

I had a running minimyth netbooting frontend running the .38 version. I tried to upgrade to the .40 version of minimyth by replacing the old rootfs and kernel files by the new ones. At this point I didn't change any configurations. When I try to boot the new kernel it loads kernel and rootfs and then stops with: Kernel panic - not syncing ...

Do I have to change any bootparameters? Any suggestions?

Thanks,

Kirse

Posted: Tue Mar 04, 2008 9:34 pm
by Pablo
What are your current boot parameters?

The boot parameters listed here should work.

Kernel Panic

Posted: Sun Mar 09, 2008 1:34 am
by tech-rat
I am having the same problem with Version 40

The message says:
Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)

My boot parameters are:
LABEL minimyth-ram-v40
KERNEL ram-minimyth-0.20-40/kernel
APPEND ro root=/dev/ram0 initrd=ram-minimyth-0.20-40/rootfs ramdisk=96000


This is happening on both my ASUS frontend and my VIA frontend.

However the NFS root fs works great on both of them.

Todd

P.S. Thanks for adding perl into the rootfs

Re: Kernel Panic

Posted: Sun Mar 09, 2008 2:52 am
by Pablo
tech-rat wrote:I am having the same problem with Version 40

The message says:
Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)

My boot parameters are:
LABEL minimyth-ram-v40
KERNEL ram-minimyth-0.20-40/kernel
APPEND ro root=/dev/ram0 initrd=ram-minimyth-0.20-40/rootfs ramdisk=96000


This is happening on both my ASUS frontend and my VIA frontend.

However the NFS root fs works great on both of them.

Todd

P.S. Thanks for adding perl into the rootfs
ramdisk=96000 should be ramdisk_size=96000

Fixed

Posted: Sun Mar 09, 2008 3:13 am
by tech-rat
Thanks. Works fine now.

I looked at the doc webpage a couple of times and still missed that
spelling. I have had it wrong this whole time.

Todd

Re: Fixed

Posted: Sun Mar 09, 2008 3:21 am
by Pablo
tech-rat wrote:Thanks. Works fine now.

I looked at the doc webpage a couple of times and still missed that
spelling. I have had it wrong this whole time.

Todd
Actually, it was not wrong until recently. Originally, the kernel used ramdisk={size}. However, they deprecated and then obsoleted that in favor of ramdisk_size={size}. Since it was not obsoleted until either 2.6.23 or 2.6.24, ramdisk={size} worked until very recently.

Posted: Mon Mar 10, 2008 1:43 am
by Kirse
Solved it for mee too. Thanx