Getting Kernel Panics after upgrade to 1.5.9-RC2

[THEMCV]

(it’s been a while to forgive me for not remembering log locations)

Trying to reimage a Dell Latitude 5411 in UEFI- I am getting the following message:

RAMDISK: incomplete write (-28 != 4096)
X2-compressed data is corrupt
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
Kernel Offset: disabled

I have also tested in a VM and they give the same thing.

[Junkhacker]

@THEMCV You need to update a FOG Configuration->Fog Settings parameter->TFTP Server->KERNEL RAMDISK SIZE set it to 275000 from the original value of 127000

[THEMCV]

@Junkhacker Hey, that did it! Thanks! Although it was set to 250000. Is this a bug with the RC or did I miss something I was supposed to do?

[Junkhacker]

@THEMCV to be honest, i’m not sure. i haven’t been involved much between the new kernel size being experimental to it being in production. i just recognized the problem.

[THEMCV]

@Junkhacker No worries, thank you very much!

[Sebastian Roth]

@THEMCV said in Getting Kernel Panics after upgrade to 1.5.9-RC2:

Hey, that did it! Thanks! Although it was set to 250000. Is this a bug with the RC or did I miss something I was supposed to do?

I don’t think we ever set it to 250000. So it’s really strange you got this value after the upgrade to the latest RC version!

[THEMCV]

@Sebastian-Roth Tom has worked with me on this server before as I did some testing a long while ago- it may have gotten changed around then.

[george1421]

@THEMCV said in Getting Kernel Panics after upgrade to 1.5.9-RC2:

RAMDISK: incomplete write (-28 != 4096)

Yes this is directly indication that the ram disk is smaller than 256M. Tom or Sebastian gave it a little head room and called it 275M as a default. I’m kind of curious if the installer looks specifically for 127000 and will only increase it if it matches. I’m surprised that 250000 remained after the upgrade to the latest release.

[Sebastian Roth]

@george1421 said in Getting Kernel Panics after upgrade to 1.5.9-RC2:

I’m kind of curious if the installer looks specifically for 127000 and will only increase it if it matches. I’m surprised that 250000 remained after the upgrade to the latest release.

I have not had a look at the code for this yet but it might be the case…