@JJ-Fullmer @Jurgen-Goedbloed Would one of you take care of adding this new feature to the documentation?
Best posts made by Sebastian Roth
-
RE: NVMe madness
-
RE: Display Host Name Throughout Host Management
Though Tom is right about the info item I still vote for adding the name so you can see it without clicking. Just makes it more comfortable when editing cause you always know/see which host you are working on. It’s actually the same for most other items I find: images, users, groups, storage node, snapins, printers, … you name it. In the current stable version one could always see the item name while editing and I feel more people will miss that.
-
RE: Unable to Fog Image pulled from Large Size HDD to Small Size HDD
What Tom means by adding 1 to that file is essentially this:
echo "1" > d1.fixed_size_partitions
(or use your favorite editor and write “1” into that file - without the quotes!). Then try deploying to the target machine again. Not need to re-upload for this test.As well, please run this deploy task in debug mode (just before creating the task check “Schedule task as a debug task”). To start the deploy use the command
fog
. The step through and you should get back to a shell after the error. Then runsfdisk -d /dev/sda
and post a picture here. -
RE: API Help
@chris-whiteley said in API Help:
The only thing I can’t figure out is how to make that host be associated with a SnapinID. For instance, I want it to be associated with a SnapinID of 1. How can I do that?
While I haven’t tested lately I would think you should be able to create a snapin association like this:
curl -X PUT -d '{"snapins":[1]}' http://x.x.x.x/fog/host/33/edit
Assuming the host you want to associate the snapin (ID 1) to has host ID 33. Don’t forget the API tokens in the call.
-
RE: Remove computers from domain.
@Phaturia Either do it the snapin way or just change names directly in the DB. If you are a bit familiar with MySQL commands this is a real easy oneliner. Create a group and put in all the clients you want to remove from the domain. Note down the ID of this newly created group - when editing the group you see the ID in the URL bar. Then open a terminal/shell and go ahead:
shell> mysql -u root -p ... mysql> use fog; mysql> UPDATE hosts,groupMembers SET hosts.hostName = CONCAT(hosts.hostName, '_'), hosts.hostADDomain = CONCAT(hosts.hostADDomain, '_') WHERE hosts.hostID = groupMembers.gmHostID AND groupMembers.gmGroupID = <GROUPID>;
The only thing you need to adjust is the
<GROUPID>
at the end of the command. Put in the groups id as simple number, no quotes or anything. Leave that command prompt open for changing things back to normal after all the clients of this group have shut down. Then do:mysql> UPDATE hosts,groupMembers SET hosts.hostName = SUBSTRING(hosts.hostName, 1, CHAR_LENGTH(hosts.hostName)-1), hosts.hostADDomain = SUBSTRING(hosts.hostADDomain, 1, CHAR_LENGTH(hosts.hostADDomain)-1) WHERE hosts.hostID = groupMembers.gmHostID AND groupMembers.gmGroupID = <GROUPID>;
The only issue with this I can think of is the timing. Some clients will reboot way faster than others. To workaround this you just need to set the “Menu Timeout” value in FOG Configuration -> iPXE Boot Menu to zero (no timeout). They’ll all wait on the FOG menu screen then.
Note: In case you have client names as long as the maximum allowed size (15 characters) those clients will disappear from the web UI but will still be fine because the DB allows for 16 characters. Possibly the unjoin from the domain won’t work for those clients. But when you run the second mysql command names will be changed to normal for all the clients.
Sure we could add an unjoin function to FOG but this would take a lot more than what I just described as we’d have to alter client and server code for that.
-
RE: Could not boot: Input/Output error(http://ipxe.org/1d0c6539)
@ManofValor said:
Am I supposed to register through the client every time?
Well, new/unknown clients need to register (themselves) or be registered (via web gui) once! New client/MAC address new registration. But you don’t need to re-register clients once per task or once a day or whatever!
-
RE: Move partitions on GPT layouts - need people to test
@JJ-Fullmer Thanks for posting the other details as well. Looking all fine so far. We definitely want to do further tests.
Could you do one with Windows 7? Be sure to install in UEFI mode to get a GPT partition layout.
I can look into testing a Linux distro.
-
RE: Change keyboard layout in FOG Boot Menues
@Tom-Elliott Probably another reason why we should build iPXE at install time instead of providing the binaries! Will look into this at some point…
Edit: Ok, just created a new topic on this and moved posts so we don’t take over this one. Follow this: https://forums.fogproject.org/topic/10858/compile-ipxe-on-install
-
RE: Fogftp login failed
This is really strange! Can we get a tcpdump/wireshark packet dump of the FTP connection when the errors show up after upload?? Just to make sure FOG is sending the correct user/password to the FTP daemon.
@kortnor The easiest to get a good packet dump of this is probably using tcpdump on the FOG server. Install tcpdump package (yum, dnf, apt-get, aptitude, …) and let your client do the upload. Prepare everything and as soon as you get the first ftp_login message on screen fire uptcpdump -i eth0 -w ftp_issue.pcap host 10.10.0.x
(where 10.10.0.x must be your client’s IP address!). After you have seen the error messages for five times you can stop tcpdump (Ctrl+c). Please upload the PCAP file here in the forum! -
Move partitions on GPT layouts - need people to test
UPDATE: This is now part the official inits!!
After several people noticed that Windows 10 2004 comes with a different partition layout that FOG is not able to shrink and deploy to a smaller size disk I started working on that code and adding the functionality to actually move the start sector of partitions. Up to now FOG never moved partitions because it would surely cause trouble as manipulating boot loader code in the MBR would also be needed and is way too error prone to do. With GPT partition layout on UEFI based systems partition start positions should not be “hardcoded” in bootloader code anymore.
Though this seems to work I would really like more people to test this before we actually add this to the official release!
Here are the steps I recommend when testing:
- Make sure you have a working backup copy of your host used to capture the image from! Just in case something goes wrong when capturing with the new init.
- Download the init file and put that in
/var/www/html/fog/service/ipxe/
on your FOG server. - Create a new image definition for this test.
- Decide which hosts you use for testing capture and deploy (the later having a smaller size disk to see if it works) with this new init, edit their hosts settings in the FOG web UI and set Host Init to
init-201114.xz
as well as the image definition you just created. - Schedule a capture task and pay attention to the boot process where it says
bzImage..ok
andinit-201114.xz..ok
to make sure it actually uses the new init file. - Schedule a deploy task for a machine with a smaller size disk and deploy to it. Again make sure it says
init-201114.xz..ok
when booting. - Please post here if you see issues as well as having success. Let us know what OS you have installed (Win 10 2004? Linux?) and the partition layout (contents of
/images/NEWIMAGENAME/d1.partitions
)!
References:
https://forums.fogproject.org/topic/14691/error-trying-to-restore-gpt-partition-when-deploying-image-to-smaller-drive-error-return-code-4
https://forums.fogproject.org/topic/13220/error-trying-to-restore-gpt-partition-deploying-an-image-to-smaller-disk
https://forums.fogproject.org/topic/14684/windows-8-1-corrupted-bcd
https://forums.fogproject.org/topic/15158/fog-failed-partition-issue
https://forums.fogproject.org/topic/15163/partitions-is-too-big-for-the-diskIssue fixed later on:
https://forums.fogproject.org/topic/15363/issue-with-single-disk-resizable -
RE: USB ethernet adapter mac(s) for imaging multiple hosts. (Universal Imaging Nics) (Wired Nic for All Wireless Devices)
I have quite a few non-ethernet devices, and it’s a growing number.
Yes, we have more and more users with devices not having an onboard NIC and therefore we want to handle this properly.
A more dynamic and or integrated solution would be great, but I get that having the service use uuid and eventually phasing out the MAC addresses as a registration entity is that solution and that it will take some time. If there’s anything I can do to help with that, I would love to contribute.
Absolutely, this is what we are aiming for. I will get back to you on this I am sure!
PS: About the API cmdlet. You should talk to @Wayne-Workman who’s working on a native Linux API cmd thing.
-
RE: Apache Error on Trunk 4991
Bump… would be good for CentOS fresh install as well.
-
RE: Which Linux distro(s) have been tested with FOG - What is recommended?
@JYost I’d definitely suggest using server.
While we do try to make upgrades with the FOG installer possible even across distro versions there have been so many changes in repos and packages between 16.04 and 20.04 - I would rather recommend to take a full database dump, install FOG fresh and clean and import the database and sync over the
/images
directory. I am sure it will take way less time than trying to dis-upgrade from 16.04 to 20.04 and as well update FOG. -
RE: Generate barcode for host from inventory
@msi Don’t worry, I didn’t see that as offense! Not at all. I really like people bringing in new ideas. Just couldn’t see that we’d find the time to add this special request.
I just thought, since we already have a database for list of host, why not add another column for asset tag.
Yeah, see Wayne’s answer on that…
-
RE: No lease after trying to perform host inventory
@middendorf As I said before: Does your switch have energy saving capabilities (called EEE or 802.3az)? Another possible cause could be auto-negotiation again. You can try disabling this on the client port on your managed switch. But I really hope that this is not the case again.
-
RE: USB Boot and point to custom FOG server IP
@brakcounty While a split DNS config will help you to get a few steps ahead it’s as George said, FOG wasn’t made to be used with more than one interface. Not exactly sure if single cast deploy ( over NFS share) will work but I imagine it does. But multicast will definitely not work in both networks without major code changes I am sure.
-
RE: Location Plugin - enhancement of behavior
@Wayne-Workman Yeah, interesting one! Thanks. I’d vote for that. Shouldn’t be too hard to add.
-
RE: tsc : Fast TSC Calibration failed
Well then I think you need to go with FOG trunk! Why wouldn’t you anyway? The problem is that the network startup script was not very robust in FOG 1.2.0. A newer kernel is needed for some NICs but that’s not the only thing. Some NICs are kind of picky when it gets to starting it up and getting an IP. We won’t fix FOG 1.2.0 but if FOG trunk is working for you why bother using FOG 1.2.0??
-
RE: Changing host registration database interaction
@c4c What you are looking for should be mostly in /var/www/html/fog/service/inventory.php on your FOG server. Also the Inventory class is probably important for what you want to achieve.
FOG can be extended using plugins. Take a look at the exisiting plugins in the code. Though I have to say that I am not exactly sure plugins are powerful enough to let you do what you want.
If more people would like to have this feature in FOG we might discuss adding it to the FOG core code. Though in this case you’d have to look into working towards the new FOG 1.6.x version as we won’t add new features to 1.5.x anymore. Can’t give you a definite date but we plan on releasing a last 1.5.10 version and then move on to 1.6.x from there.
-
RE: MBR to GPT Conversion Task
@netbootdisk Doing this in general could cause us a lot of trouble. I wouldn’t wanna go there.
But that’s not saying it’s nothing we should look into and give it a try. Maybe start by using a postdownloadscript. Check out George’s post on this: https://forums.fogproject.org/topic/7740/the-magical-mystical-fog-post-download-script
Using
gdisk
in a script you can use this method (sure there are others as well):gdisk /dev/sda <<EOF w Y EOF
Give it a go and let us know what happens. By the way: why do you want to convert from MBR to GPT? If it’s to move on to UEFI there is more to it than just that!!!