Kernel panic after upgrading to trunk

[AsciiReign]

I tryed updating one of our fog server which was still running 0.32 to trunk (5786) and everything worked fine.
OS is still Ubuntu 12.04.5

until i tried to register a client. then i get the ‘famous’

kernel panic-not syncing: VFS: unable to mount root fs on 
unknown block(0,0)

error.

i searched the forum and checked that i did not save bzImage as bzImage32 or vice versa

i tryedlooking into the grub settings and also tryed dropping the database after i backed it up.

didnt help. i got the error on two different clients so i guess they are not broken.

i downloaded the kernels and inits using wget:

• wget https://fogproject.org/kernels/bzImage
  wget https://fogproject.org/kernels/bzImage32
  wget https://fogproject.org/inits/init.xz
  wget https://fogproject.org/inits/init_32.xz

[Tom Elliott]

This almost always happens with the downloaded files not being properly downloaded.

Rerunning the installer usually fixes this. THe fact that the files are dated December 10th is an indicator that there was indeed an issue in downloading the files.

[AsciiReign]

i redownload them and did an md5sum check.

af352fa8f5dbbe61816e79237aa482ae  bzImage
307ab9fbbb94ca7c92c7af968c0c5009  bzImage32
5e9736c8a79aaeb0816e183c83bae782  init_32.xz
603850d41de476102156ca19164b31f3  init.xz

Could you verify that those are correct?

[Tom Elliott]

@AsciiReign

af352fa8f5dbbe61816e79237aa482ae  bzImage
307ab9fbbb94ca7c92c7af968c0c5009  bzImage32
5e9736c8a79aaeb0816e183c83bae782  init_32.xz
603850d41de476102156ca19164b31f3  init.xz

[AsciiReign]

Thank you.
So it seems the download is correct.
I will try to register the host tomorrow.
Anything else i should check or info we could use if it still does not work?

[Tom Elliott]

@AsciiReign another thing you may want to check is the tftp setting specifically what/where it’s looking at the inits and kernel. From the sounds of it it may be trying to use a 64 bit kernel on a 32 bit init.gz. Notice the extension is gz not xz.

[AsciiReign]

It seems that the problem was the networkcard in our server.
Replaced it and it works.
But thank you for your support.
And merry christmas.
How do i mark the thread as solved?

[ch3i]

@AsciiReign said:

How do i mark the thread as solved?

It’s done