@tedlaur You can provide your error log from the install, but sometimes more fruitful is the actual php-fpm error (or on debian it may just be in the http error logs)

I don’t recall, and it has been a while since I did direct troubleshooting with fog. I can still read of course and probabaly help in that way, but my systems are limited as of late and as such harder for me to troubleshoot issues to try to replicate.

Forgot to say that I turned SPECULATION_MITIGATIONS on in the current default kernels some days after my last post because there wasn’t any feedback from people testing those kernels.

@Fog_Newb Awesome! Thanks for testing 1.5.9.138. This was meant to fix another issue reported on github but looks like the same problem in the code was causing the issue you saw.

Please keep an eye open and try as many things as you can (capture/deploy, fog-client, maybe plugins).

@Tom-Elliott said in FOG kernels and inits moving to github:

Majority of the time the Inits are built one off for some specific need. No where near the frequency of the kernels needing to be updated.

I don’t think that’s true. We do bug fixes and add features to the inits way more often than once a year (when at least the buildroot update is to be done). Take a look at the last dozen or so fos repo commits.

@dreN Great! Are you currently using the dev-branch version? Testing/using the latest dev-branch and reporting issues if you can. As well you are more than welcome to help on the documentation. Please send me a private message to discuss further steps.

@sebastian-roth it’s working thank you !!

https://github.com/FOGProject/fogproject/pull/409/files
https://github.com/FOGProject/fogproject/pull/410/files

@UWPVIOLATOR

Yes here -> https://github.com/FOGProject/fogproject/compare/1.5.8...1.5.9

@Sebastian-Roth Ok, thank you.

Finally merged all the work into dev-branch. Done.

@Sebastian-Roth i understand the reasoning for not updating it. i’m hoping to have a chance to help with testing by the end of the week.

Sorry for the late answer …

We’ve just upgraded to 1.5.9 and update Bitrate and Remit Hello Interval on «Storage Node» settings page.

The generated command was conform and everythings works great !

Thanks a lot

Did some more testing and will merge this into dev-branch now before the new release. Have tested on CentOS (existing installation and fresh) as well as Debian (fresh installation). Should be good to go.

@bloodwar I have looked through the code up and down, forth and back… Just don’t know all about UEFI and have no idea why this goes wrong. I am pretty close to sending a message to the kernel mailinglist. But before that I’d like you to try other kernels first. Please use some older kernels just to see if those can boot on that device. I think the easiest way is to download old kernel binaries here and here, plugin the USB key you made and put the kernel binary on it as EFI/BOOT/BOOTX64.EFI (rename that file - GRUB EFI binary).

Now boot the Lenovo N24 off that USB key and see how far you get. If you see Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)) than you are past the issue. If it just sits there for 3 minutes then I’d expect it to be locked. Please try at least 10 kernel binaries of various versions from the links above.

@george1421 said in Detect Windows Boot/Recovery/Reserved/System partitions reliably:

These files would need to be named uniquely global (i.e. not having natural language variants).

Good point George! Though I am fairly sure this is the case for some files that are used for booting the OS like bootmgr and such files.

@george1421 webif should be a known short for web interface 😄