Posts made by lukebarone

@Sebastian-Roth I didn’t know about the 100% option - I like that!

@RogerBrownTDL Try this instead:

lvextend -L +398g ubuntu-vg/ubuntu-lv --resizefs

@RogerBrownTDL Yes.

lvextend - Increase the volume size
-L - Specify the size to increase it by
ubuntu-lv - The name of your logical volume (as reported)
--resizefs - Resize the EXT{2|3|4} file system

@RogerBrownTDL

lvextend -L +398g ubuntu-lv --resizefs

You may need to reboot for it to take effect. This will use all the remaining LVM volume space for your logical volume. You can’t go smaller after the fact, so be sure you want to use it all first.

@Scootframer Hmmm… I’m not sure off the top of my head. I know I’ve seen this issue before, but I do not recall what the fix was.

@Scootframer ls -la /images?

@Scootframer To verify what it is first, run ps aux | grep 2643. Then run kill -9 2643 to forcefully kill it.

@Scootframer Oh good!

Anyways, I would try the latest dev-branch and see if the issue persists. If not, then we would start looking at the logs on the server.

@Scootframer On your server, navigate to the folder you downloaded fog to, and run git checkout dev-branch. Then, re-run the ./bin/installfog.sh script to install the latest version.

If you only have 3.9 GB of free space, I’m going to guess that it’s running out of space before it can set the permissions (but someone else would have to verify that for me). The partitions are supposed to be saved into that dev folder until captured, then it gets moved over and renamed.

@Scootframer Can you confirm you’re using the latest FOG version in the dev-branch branch?

How full is your /images partition/drive? Is it a local drive on your server or an NFS mount? Does /images/a4bb6d84ebf4 exist on your server?

@kalafina I use Samba on a file server. Since you’re running Windows clients, it should work with minimal setup. You need to ensure that wherever the file is stored that the computer account can access it, not necessarily just the user.

But you are right - FOG is defaulting to adding the uploaded snapin file to the end of the command line. There is a walkthrough for adding a Wi-Fi key as a snapin that includes how to upload a ZIP file and run a command from inside - I’d recommend trying that if the above isn’t working.

https://www.youtube.com/watch?v=M-HXtqeukks

@Tom-Elliott You are crazy, but not for that reason… I keep forgetting to check the non-master code -.- That’s a me issue, lol

@danieln Looks like it’s failing at the password part:

$password = htmlspecialchars_decode($password, ENT_QUOTES | ENT_HTML401);

https://github.com/FOGProject/fogproject/blob/master/packages/web/lib/fog/fogftp.class.php#L464

Not sure who is maintaining the PHP code, but it’s failing at that line and breaking out.

@kalafina So that’s showing that the DISM command doesn’t like spaces, even when surrounded by quotation marks.

I’d suggest creating a simple .CMD file and running that. For example (untested):

@echo off
copy /y \\server\share\appassoc.xml C:\
dism.exe /online /import-defaultappassociations:C:\appassoc.xml

Obviously, replace \\server\share with a path that is network-reachable from your client.

…

On the other hand, looking at your “Snapin Command read-only”, it looks like you have a syntax error anyways - the appassoc.xml part should NOT have a space before it when including the path.

Another thing to try is instead of running the cmd.exe, run dism.exe for the Snapin Run With, Argument set to /online /import-defaultappassociations:, and see what that produces?

@Tom-Elliott Try with the path starting with %~dp0. For example:

/c dism.exe /online /import-defaultappassociations:%~dp0\appassoc.xml

That variable will map to the current drive and path. If the appassoc.xml file is in the same folder as where FOG is running the command, it should auto-expand and auto-escape the characters (i.e. spaces).

@Romain-0 I cannot read the Francais, but I have seen this message before.

Have you disabled Secure Boot? Can you boot with a built-in network card as opposed to a USB one?

@kalafina To confirm, you have the feature installed in your image, correct? Even though it’s not turned on until you push the snapin?

@jmcnamee Random question, why do you need to switch to BIOS mode instead of staying in UEFI? The DHCP server should give out a filename based on the architecture during the FOG OS boot. See this link for more details. You will need to disable Secure Boot in your VM though, if enabled.

In my VMs (using Hyper-V or Virtualbox), I would add the drive controllers as SATA as opposed to IDE - have you been able to capture a GPT disk with an IDE controller? I always though that was mutually exclusive.

@Kureebow USB Booting instructions:

https://wiki.fogproject.org/wiki/index.php?title=USB_Bootable_Media