@fog_newb “FTP IMAGE SIZE” on the settings page
Best posts made by Junkhacker
-
RE: Request dev branch Web UI show how much space an image takes up on the server.
-
RE: Hosts not imaging - HELP
@prestop did you replace the drive with a larger one, as previously suggested? your non-resizable image will need to be deployed and recaptured to become resizable. you’ll want to check the “Schedule Shutdown after task completion” checkbox when you deploy, and then schedule a capture after it finishes. if you don’t boot up the computer after imaging, it doesn’t even have to be a computer compatible with the image you’re deploying.
-
RE: Fog Trunk Git 7645 update fails at SQL
That’s kind of odd from my point of view as the tools used to do the actual up- and download (
udp-sender
for multicast download and NFS for upload and unicast download) haven’t changed much in a while!we’ve made changes to how compression/decompression is handled to better utilize the processing power available
-
RE: FOG .32 upgrade to 1.2 issue
@Darrell-Lanson /var/www/fog/lib/fog/config.class.php
-
RE: One FOG server with multiple storage nodes?
@george1421 esxi vm, not physical. compression level 6. target is an Optiplex 3020 i5 with SSD. if only a single target is being imaged at a time, i get similar speeds almost all the time. Ethernet is near saturation, the rest is the magic of multi-threaded compression/decompression.
-
RE: One FOG server with multiple storage nodes?
@theterminator93 instead of trying to set up multiple storage nodes on the same server, have you tried nic teaming on the esxi box and using the VMXNET adapters? also, how is the speed improvement after upgrading to trunk?
-
RE: Fog client confusion
@Quazz my point is that to image a drive by default means to put an existing image on the drive. any other use of the term requires qualifiers like “create an image”
-
RE: A hostname with that name already exists.
try updating to the latest build.
-
RE: A hostname with that name already exists.
@svalding in that case, i would manually add that address to a host (one you’ll keep track of) and check the checkboxes that say to ignore it. i do something similar with usb network adapters.
-
RE: Fog 1.2.0 Scheduled Tasks Not Initiating
before diving in too deep troubleshooting this, is upgrading to the latest stable release not an option? (operating system and fog versions, if possible)
-
RE: Dedupe storage - how to best bypass pigz packaging?
sorry i didn’t see this thread earlier, but i have experimented with dedup of uncompressed fog images on a zfs filesystem to see if it was worth it. i saw far less gains than when using compression. but i really can’t say i’m highly experienced in dedup, so maybe i did something wrong. let us know how your experiments go
-
RE: Upgrade version
@george1421 well, unfortunately, the file naming conventions and formatting hasn’t always been the clearest. it’s gotten a lot better, even if i don’t think what we use now is perfect
-
RE: Fog failed to update from 1.2.0 to 1.3.4
@SOL images are compatible. instructions for migrating to a new server is covered in the wiki https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG
-
RE: Additional disk space is not showing up on Fog server
@sjensen your virtual machine doesn’t know it’s a virtual machine, so what hypervisor you’re using is irrelevant. everything in the steps past gparted (which you say you’ve already done) is relevant
-
RE: Custom client boot menus for each client
@guthriesound here’s one way you can do it
add to the fog.local for each different boot iso you need to boot to something like this to the “Parameters” section
iseq ${serial} DellSerial && initrd http://${fog-ip}/${fog-webroot}/special.iso && chain memdisk iso raw ||or you could add those new menus with names like fog.iso1, fog.iso2… and have the lines be like
iseq ${serial} DellSerial && goto fog.iso1 ||
-
RE: Custom client boot menus for each client
@george1421 the first example i listed could do that, if you named the iso files after the serial of the target computer, but i think it’s more practical to just add another line for each one, since you may want to use the same iso for more than one target computer.
ipxe knows many things you can use for your conditional test, for a handy list i have this entry in my advanced menu:hostinfo echo This computer : || echo MAC address....${net0/mac} || echo IP address.....${ip} || echo Netmask........${netmask} || echo Serial.........${serial} || echo Asset number...${asset} || echo Manufacturer...${manufacturer} || echo Product........${product} || echo BIOS platform..${platform} || echo || echo press any key to return to Menu || prompt goto MENU
i try not to use mac address because a computer may have more than one, and you can get the wrong one by referencing net0/mac, making you rest against multiple potential network adapters to get the one with the mac address you want
-
RE: Power controls do not work
@dws88 shutdown and restart options are for interaction with the fog client running on client computers and for wake on lan, not IPMI or any other hardware interface level of management.
-
RE: Image Capture from a Yoga 11E
@John-L-Clark this doesn’t look like a checkdisk issue. the reason the disk isn’t clean is because the computer is shutdown in hybrid mode instead of being cleanly shutdown. try using from an elevated command prompt “shutdown /s”
-
RE: New to Fog
@george1421 said in New to Fog:
If you have someone that knows linux, they can create new fog server in under an hour from bare metal to a working fog server.
and if you don’t have anyone that knows linux, you can probably still fumble your way through getting a new fog server up and running in a day