Kernel for Ubuntu 64 bit
-
@Tom I guess we’ll need to capture a video of this. The kernel panic is the end results of something that happened earlier in the boot process. If you have a mobile phone we will need to see a video of the booting process from the kernel mode. If you can make sure the mobile is held solid (book, stuck with bubble gum on wall) and if you have an iphone 5 or newer please record in slow motion (it gives old eyes a better chance at seeing the actual error). I will refresh my dev box in the AM and boot one of our e7440s to see if I can duplicate your issue.
-
I think I have a way to test a theory on what/why the kernel panics.
This is because the init’s only have a limited to “link” data on the disk (known as an inode).
An inode is the exact point on a disk that a file is located. The buildroot system defaults to 0 for auto calculate inodes to give, but this is only relevant at the point the init’s is generated.
My normal configs give 4096 inodes, i just updated the value to 8192 in hopes to see if we get much further.
-
@george1421 Captured the boot process here
I tried to record it in slow motion both with Galaxy S5 and iPhone 6 - That’s the best results.
Thanks,
Tom
-
Did you update to the very latest version? Tom Elliott has found something which might fix this issue. Please upgrade and let us know.
-
@Sebastian-Roth Completed svn up successfully - Running 6196.
Tested on the OptiPlex 990 and the Latitude E7240 - the issue is not resolved.
I get the same error.
Thanks,
Tom
-
@Tom-Elliott Not sure if it’s relevant, but I thought I throw it out there:
My Fog is VM lives on ESXI 6. The disk type is Thick provision Lazy Zeroed.
Tom
-
@Tom said:
Completed svn up successfully - Running 6196.
Did you also run the installer script after
svn up? If yes, please post the output of this command againls -al /var/www/fog/service/ipxe/init* ; ls -al /var/www/fog/service/ipxe/bzImage* -
@Sebastian-Roth
Ran the following command:
sudo ls -al /var/www/html/fog/service/ipxe/init* ; ls -al /var/www/html/fog/service/ipxe/bzImage*Results:
-rw-r–r-- 1 fog www-data 17659820 Feb 4 13:37 /var/www/html/fog/service/ipxe/init_32.xz
-rw-r–r-- 1 fog www-data 18750104 Feb 4 13:36 /var/www/html/fog/service/ipxe/init.xz
-rw-r–r-- 1 fog www-data 6883968 Feb 4 13:37 /var/www/html/fog/service/ipxe/bzImage
-rw-r–r-- 1 fog www-data 6783136 Feb 4 13:37 /var/www/html/fog/service/ipxe/bzImage32 -
@Tom Can you try updating again?
I found some things out over the weekend. I doubt you’ll see any success, but at least I’ll know if things are working a bit better or not.
-
@Tom-Elliott
Trying to run installfog.sh and I get command not found.At this point, would it make any difference is I’ll scrap the VM and start from scratch?
Thanks,
Tom
-
@Tom How are you calling installfog.sh?
-
@Tom-Elliott
Navigating to svn/trunk/bin
sudo installfog.sh -
@Tom you need to use:
sudo ./installfog.sh -
@Tom-Elliott Thank you, successfully updated to 6237. The issue is not resolved.
Should I start over from scratch? will it make any difference?
Thanks,
Tom -
Also, ran this again:
sudo ls -al /var/www/html/fog/service/ipxe/init* ; ls -al /var/www/html/fog/service/ipxe/bzImage*Results:
-rw-r–r-- 1 fog www-data 17611576 Feb 8 13:08 /var/www/html/fog/service/ipxe/init_32.xz
-rw-r–r-- 1 fog www-data 18786192 Feb 4 13:08 /var/www/html/fog/service/ipxe/initxz
-rw-r–r-- 1 fog www-data 6957536 Feb 4 13:08 /var/www/html/fog/service/ipxe/bzImage
-rw-r–r-- 1 fog www-data 6856848 Feb 4 13:09 /var/www/html/fog/service/ipxe/bzImage32 -
@Tom I see different dates in that output. One says “Feb 8” and the others “Feb 4”?? I guess this is just a copy/paste typo? File sizes look good to me. Do you try booting different client models? Always getting the same error?
-
@Sebastian-Roth Yes, the dates are copy/paste typo. My client’s are the OptiPlex 990 and Latitude E7240.
They both shows the same error.Thanks,
Tom
-
@Tom Other machines that you could test?
-
@Sebastian-Roth Yes, just tested Latitude E6330 - Same results.
-
I have a 7240 on my workbench. Let me see if I can pxe boot it. I just rebuilt our production server last friday with the latest build at that time. I need to do this for image qualification anyway. Give me a few minutes to get things setup.
[edit] Looking back through this thread, I don’t see what mode we are booting into BIOS or EFI? I’ll test both for the qualification just in case [/edit]
