@Tom-Elliott Can you confirm this being an issue in 1.6??

@rzuchowski Try connecting a dumb (unmanaged) mini switch between the client and your building switch and try again. It’s very likely a spanning tree issue.

If it still doesn’t work tell us your FOG server IP and post a picture of the error on screen.

@george1421 said in The future of partclone and therefore FOG as it is:

RAMDISK: incomplete write (-28 != 4096)
XZ-compressed data is corrupt

Yes, ran into that yesterday already. See here. We moved back to 101 MB (just a little larger so that hopefully we don’t run into a space issue again) for 1.5.6 binaries. But we’ll move to 256 MB for 1.5.7 in the near future I suppose.

@Junkhacker Might be related? https://forums.fogproject.org/topic/12911/chainloading-failed-advanced-menu

@kratkale You are welcome. It’s good to have people around who rapidly test things that we push out. Thanks to you!

@kratkale You can give it a try but I am fairly sure there won’t be an issue with that. Marking as solved.

@Tom-Elliott Sure we’ll fix that in 1.5.7 but I’d like to see 1.5.6 not going on ground just a few days after we released it. Therefor I am trying to get to a solution where people can just use 1.5.6 without having to fix anything manually. Just tested and seems we are fine with the currently uploaded files. All good I hope.

@kratkale said in Failed to set disk guid ...:

Do you think upload will also be now faster? There I’ve a rate of about 2.8GB/min …

There is no general answer to this. It all depends on the hardware you have. Bit CPU and lots of RAM will make compression faster. The more you can compress, the less data needs to be transfered to the FOG server and written to the disk there…

@Junkhacker Please go to the FOG web UI -> FOG Configuration -> FOG Settings -> FTP Server and increase KERNEL RAMDISK SIZE from 127000 to 275000.

Sorry for all the rumor.

@Tom-Elliott Not a good situation where we would need to either revert the inits to 100 MB size or quickly push out a new release just to fix the KERNEL RAMDISK SIZE. I will build 101 MB inits (yes, just a little larger to hopefully get around the space issue mentioned below) over night just so we have those handy.

Edit: Good news, we still had the tool chain from the latest jenkins build on the server and so I am able to generate new inits fairly quickly. Will update the latest ones on the web server as well as binaries.1.5.6.zip for now.

Edit2: inits and binaries1.5.6.zip are updated. New checksums are:

e69e0763cfda1e02159553ea1cdbdc55  init.xz
00d811eef21cdfab4bab5160ad888bec  init_32.xz

@kratkale Yeah, just saw that as well. Please go to the FOG web UI -> FOG Configuration -> FOG Settings -> FTP Server and increase KERNEL RAMDISK SIZE from 127000 to 275000.

@Junkhacker said in Failed to Set Disk GUID (sgdisk -U) (restoreUUIDinformation):

edit3: ok, that was giving me kernel panics. not sure what was going on there

Did you get this fixed??!?!

@Junkhacker Can you please post the MD5 sums here.

da11c7a619efc4a737f9a715810f01a3  init.xz
7de47b8634d6c95ba869369dfefd9c82  init_32.xz

I just downloaded and tested those myself. They are the new ones from my point of view. Maybe you have some proxy cache or it’s just that we still have not properly fixed this for your case. Can you please post the contents of your /images/<IMAGENAME>/d1.partitions here.

@austinjt01 @Junkhacker New init files are available that should address both issues you saw. Manually download those (32 bit and 64 bit) and put in /var/www/html/fog/service/ipxe/ on your FOG server or simply re-run the FOG installer.

Please let us know if the issues are gone.

@george1421 Any news on this topic? I was hoping to engage more in this but as you see things keep popping up that need quick fixing…

@kratkale New init files are available. Manually download those (32 bit and 64 bit) and put in /var/www/html/fog/service/ipxe/ on your FOG server.

Please let us know if the warning is gone with those inits.

@Junkhacker The inits are still building bit I will make those the official 1.5.6 inits so we won’t have that bug in 1.5.6! Will let you know when they are ready.

@astrugatch said in FOG 1.5.6 Officially Released:

Does this only happen on first install? I did an upgrade from 1.5.5 and didn’t see this question.

You are absolutely right. Seems like I have missed this important case altogether, arggghhhh!

The easiest route for you is editing /opt/fog/.fogsettings now. After running the 1.5.6 installer once you should have an “empty” hostname setting in there: hostname='' -> Just change the hostname to whatever you want it to be and re-run the installer.

Pushed a fix to dev-branch. Hope this is appropriate for the next releases.

Edit: More fixes pushed after testing this.

@Junkhacker Don’t worry about running the commands. I have pushed a fix already. The inits should be available soon.

@Tom-Elliott No we don’t from my point of view. Just pushed a fix for that. The inits should be build by tomorrow (or later this day your time).

@kratkale As well please post the contents of the text file /images/M910_201901131240/d1.partitions here.