@oleg-knysh You may also be interested in trying out an experimental init.xz that uses a newer version of partclone. Though the github issue does not indicate this resolves the issue for them, perhaps it will in this case. It’s worth a shot anyway.
https://drive.google.com/file/d/1u_HuN5NSpzb7YmQBAsrzDELteNmlWUWU/view
@Sebastian-Roth I don’t know if it’s changed, but you needed an account created for you before you could edit the FOG wiki, I don’t think even I have one at the moment.
Had a kernel error of rootfs can’t mount blablabla on a device today, normal init works fine. Ramdisk size is at 275000 currently.
Unsure why this happened.
edit: Might just be a machine issue as it seems to be acting up in other ways too (namely freezing)
@oleg-knysh Here is the issue on the partclone github: https://github.com/Thomas-Tsai/partclone/issues/112
Currently still unresolved unfortunately.
I can only recommend trying to update BIOS and update firmware of the disks.
@astrugatch Looks like there would be an edge case if you answered ‘no’ to php/apache reinstall during update where it would just carry on with the ‘packages’ line from .fogsettings and thus cause no problems.
@astrugatch https://github.com/FOGProject/fogproject/commit/29af4df767775e08fc102ea1cf61b4da789b61d5
Fixed on dev as far as I’m aware, but essentially the issue was that moving from Mysql to Mariadb caused the database to not be moved properly and thus it would appear as if the database is gone to the end user.
If you’re already on the dev branch or if you already had Mariadb installed then you’re likely fine.
@sudburr Make solid backups of database and such. I don’t know for sure if you can just roll back without setting back the old db.
Go to the host (or group if it’s all of them) settings and reset encryption data.
In most cases that’s what solves this error as far as I’m aware.
@bigjim Your dnsmasq config is outdated if you’re using the a newer version. (and UEFI + BIOS proxydhcp didn’t work at all on older versions)
dhcp-boot=tag:UEFI32,i386-efi/ipxe.efi,10.5.0.240
dhcp-boot=tag:UEFI,ipxe.efi,10.5.0.240
dhcp-boot=tag:UEFI64,ipxe.efi,10.5.0.240
The syntax tag: is no longer valid and needs to be replaced with net:
https://wiki.fogproject.org/wiki/index.php?title=ProxyDHCP_with_dnsmasq#Install_dnsmasq_on_CentOS_7 for reference
It’s confusing because there’s info on both older versions of dnsmasq and the newer ones, but likely this is the cause.
@oleg-knysh I do recall a specific SSD model (or multiple) having absurdly low speeds in partclone.
Do you know what models they are?
Of course, FOG has versioned releases
Eg command
git checkout tags/1.5.3
This particular model seems to be bad news in Linux environments in general.
People having trouble installing Linux on it, getting it to boot, etc
Also here’s a FOG thread of 2017: https://forums.fogproject.org/topic/10795/hp-x360-11-g1-ee/5
It’s unrelated otherwise, but it’s to illustrate that this particular piece of hardware has a legacy of being a pain in the ass.
@george1421 I believe Microsoft has been trying to create a cross platform powershell (https://devblogs.microsoft.com/dotnet/powershell-is-now-open-source-and-cross-platform/), though I don’t see us integrating that into FOS.
@george1421 If you actually install Linux, it will generally mount it using the UUID, which should always be the same.
As for the BIOS, the PCI path doesn’t change for NVME drives, just which one initalizes first can be volatile (and thus the block naming scheme in Linux gets messed up). BIOS looks for the boot file on the PCI path afaik.
However, I’d be interested in seeing if this issue occurs on successive Ubuntu/Centos LiveCD boots
You’re trying to pull something from the images folder over https, but https isn’t configured to serve that location.
Think more along the lines of /var/www/fog
@Sebastian-Roth That’s true, though we could always just backup the current inits on the client side and add a “restore original inits” button.
@aephk You may have to recapture the image (I assume image type is single disk - resizable) to get the data correct.
I’m guessing your target is slightly smaller which makes the partition table not fit, but once the resizable aspect works correctly this should work fine.
It’s also possible you have an odd partition layout (eg a recovery partition after your windows partition) that’s ballooning your image size.
Similar to the kernel update one, perhaps it would be interesting to have a way to update the init files as opposed to having to do it manually or updating FOG as a whole.
I don’t know if there are backwards incompatible changes we need to be mindful of, however.
Thoughts?
Try updating just the init.xz files then
https://fogproject.org/inits/init.xz
and
https://fogproject.org/inits/init_32.xz
They go in /var/www/fog/service/ipxe
@spidajon That looks like an NFS mount. You can’t export something that’s mounted onto your system. (you can’t daisy-chain)
So in other words, you need to try and do it directly, by for example creating a storage node in the web UI and adding the address there directly.