@george1421 It worked. Thanks !
Posts made by Baessens
-
Ubuntu; Disk size?
Hi
Probably some mistake on my part.
Ubuntu says I only have 3.9GB available, but the virtual disk i made is 200GB, Why am i not seeing this?
(does it have something to do with me enabling VLM when installing the OS?
Does it auto-expand or something?From my Hyper-v:
This is Ubuntu 18.4 LTS, new install.
Thanks in advance.
-
RE: No configuration method found
@sebastian-roth Ah, my bad. I did not see that previous post. I tried snponly.efi, deploying works fine now. Thanks a lot!
-
No configuration method found
FOG version 1.5.9
Hardware: New lenovo thinkcentre m75sWhen deploying an image I am getting the message “No configuration method found” on these new Lenovo desktops we ordered.
Weird thing is I only have this problem with those specific devices, which makes me think it’s an issue regarding the NIC of those pc’s. (I think maybe the NIC’s aren’t getting an IP)
I can deploy without issue on several other devices. I’ve tried UEFI and Legacy.
Boot files I use:
undionly.kpxe
ipxe.efiAny tips on how to fix/troubleshoot this?
Thanks in advance.
Edit: picture
-
RE: Capturing image update database failed
Works fine now. Thanks @Sebastian-Roth !
-
RE: Capturing image update database failed
@Sebastian-Roth Wow… Good spot! I always use a dash, but for some reason it uses
/
in the path.
It doesn’t show it in the images list tho, need to click on the image name to actually see it.
I think there is a regex check but only for the image name, not the path. (which is usually the same)I’ll try it right away.
-
RE: Capturing image update database failed
@Sebastian-Roth
Could it have something to do with the SQL creds?I think it must have happened after an update, either from FOG or Ubuntu.
-
RE: Capturing image update database failed
@Sebastian-Roth I am still getting the same error.
I might just install a whole new server. Can you think of anything else that might be causing the error?Thanks for all your help allready.
-
RE: Capturing image update database failed
It seems to only be the password that is different.
i’ll try that resyncing thing too. -
RE: Capturing image update database failed
@Sebastian-Roth I can also create a directory and upload a random file into that new dir.
-
RE: Capturing image update database failed
@Sebastian-Roth Thanks for your reply.
The password in the/.fogsettings
file is different then the one in the GUI under TFTP server.
Should i change the one in the GUI to match the one in/.fogsettings
?Also i can upload a random file in there.
-
RE: Capturing image update database failed
Also: the /images folder is on a different location(virtual hard drive) then the OS.
EDIT: i’m now on 1.5.9 and deleted all the storage nodes. Still same problem. -
RE: Capturing image update database failed
It’s an Ubuntu server. (16.04)
I just tested it and cannot upload an image anymore at all. I have no problem deploying old images.I also moved the temporary folders before trying to capture.
I capture on one fog-server(FOG1) then let it replicate to 3 other FOG servers which are full nodes. Then i just export and import the images list from FOG1 to the others. Maybe there’s a problem over on some other FOG server with creds, i’ll check some things.
I last uploaded an image on 25th of august, without issues.
Thanks
-
RE: Capturing image update database failed
@Quazz
I do have 3 other fog servers who sync the images from this one. Maybe that plays a role somehow?What about the files in /images/dev
-
Capturing image update database failed
Hi there
FOG version: 1.5.9-RC2
I’m getting the “failed to update database…” error at the very end of capturing an image.
This problem occurs when I am trying to capture a Windows 10 UEFI (V2004) image. (see attach. below)I use Virtualbox and set my DHCP option 67 to undionly.kpxe to capture, as capturing doesn’t work when i put it on ipxe.efi. (I did this before and never had a problem)
Weird thing is I don’t have this problem when i capture an image in “legacy mode” on our hyper-v server.
I keep seeing the username “fogproject” in there, but i don’t have a user by that name tho…
Any help would be appreciated.
-
RE: PXE boot stuck on initialising devices
Works:
Doesn’t work;
The total is different and the rights on default.ipxe (3th row) different user aswell.
Do you spot anything that’s obviously wrong?
Thanks
-
RE: PXE boot stuck on initialising devices
@george1421
Fog that’s working
Fog that’s not working
I do see some differences but i have no idea if they matter. i’ll try and copy the files tomrrow, thanks for the help already!
-
PXE boot stuck on initialising devices
I have one FOG server; when i boot from network(legacy nic) on a Hyper-v server, i can’t seem to get past the “initialising devices…” screen.
I have another FOG server in a different location that works fine on hyper-v, the difference being:
- the version of FOG (fog1: 1.5.7 vs fog2: 1.5.5)
- DHCP server is Unifi USG router(fog1), the other one uses Windows DHCP(fog2)
On both DHCP servers i use undionly.kpxe as the boot file name.
EDIT: when i set the fog1 as boot server in dhcp option on my first location, it works just fine, so it would seem it has something to do with the VM on my other hyperv, so far the only difference is that the configuration version is 9.0, the other one is 8.0 … hm
Any suggestions on how to troubleshoot this?
Thanks in advance