@LittleTux After changing /etc/exports you have to run exportfs -ra so that they actually get ‘exported’

@Tom-Elliott Was just wondering, since I came across someone who needed to specifiy 4k sector size to get full speed out of their drive; though admittedly their speeds were far greater than users who are having the issue of this thread it seems! So unrelated indeed. Thanks for the info.

@Tom-Elliott As far as I understand, this problem is occurring specifically on NVME SSDs

@DeRo93 Unfortunately there are some issues on that model with certain SSDs (though not all) that are currently resolved.

I’m unsure where to even point the finger at this point, but extensive attempts from our side have been done with no success.

Another user was using older models to deploy their images to the drive and then put those drives into the G6 model.

@DeRo93 Have you tried 0.3.12? The differences between those two versions are minor.

@DeRo93 Technically, yes, but it is considered unstable and unfinished.

@DeRo93 If available, install firmware updates, BIOS updates and such.

@Developers Looking over FOS, it seems that sector size is always assumed to be 512. Could this be involved in the slow speeds? (as it would cause missalignment, potentially)

Additionally, it seems sector size isn’t always correctly reported by tools such as fdisk (possibly hardware manufacturers fault; dont know). So even if software is generally clever enough to handle it on its own, if it assumes the wrong value, we can assume worse performance (even after deployment)

You’ll have to disable secure boot in BIOS.

@zaboxmaster /usr/share/fog/lib/funcs.sh

@rocksteve69 Unfortunately I’m unsure what else to try at the moment.

@zaboxmaster Alright. I do think $osid should be in lowercase to start off with.

Does the checkin file work or does that one also not work?

All that said, I’m not entirely sure if this will work, though I admit my knowledge in this area isn’t great.

I don’t know if the osid is ever even passed into this area of FOS.

The imageid might be a better bet.

@rocksteve69 You may have to increase the ramdisk size in the settings on the WebUI

It’s at TFTP settings (set it to something like 275000)

@zaboxmaster So what doesn’t work?

Does it not wait? Does it get stuck on waiting? It’s unclear which part “doesn’t work”

@rocksteve69 https://drive.google.com/open?id=1WLjXQYKDoZCAxF5Gfjeva2O-MLrfQ40N

Copy to /var/www/fog/service/ipxe

Change kernel in WebUI to bzImage529

@rocksteve69 Thanks!

Looks like that version is running on Linux Kernel 5.2.9-2, potentially including some NVME fixes for certain devices.

I am compiling that kernel, hopefully that’s the only thing needed, because otherwise I am unsure where to start looking.

Will post a link here when it’s done.

@rocksteve69 Which Clonezilla version was this?

@Developers Could this be partition alignment related or was that already fixed ages ago? I can’t remember.

@Sebastian-Roth I just tried to replicate this, but this behavior doesn’t seem to occur on my end. I am on the latest dev version, though.

Resizable is not an option since there are no open source tools to resize HFS+ or APFS partitions, unfortunately.

For preliminary APFS support (untested) you will need a newer init.xz file as well.

You can grab that here: https://dev.fogproject.org/blue/organizations/jenkins/fos/detail/master/101/artifacts

Rename it to something like init_apfs.xz then copy it over to /var/www/fog/service/ipxe

Set the init file to init_apfs.xz in the WebUI

@zaboxmaster said in Need to create a While loop on deployment for when an image has not been assigned:

while the $OSID = null then sleep 200

That’s because you’re setting the $OSID to null in your while loop, so it will never end.

A single = means set value to

Double = (==) means compare strings

In bash, if you want to check if a variable is ‘null’, you want to do something like (not sure if syntax is 100% correct) (-z checks if the variable is null)

while [[ -z "$OSID" ]] 
do 
        sleep 200
done

@Sebastian-Roth Agreed.

You have a bigger problem on your hands if people are trying to brute force from inside your network, imo.

And even more so if you publically expose FOG.

Though logging failed auth attempts could potentially be interesting.

@astrugatch Can you explain why you would like this?