Best posts made by Wolfbane8653

https://help.ubuntu.com/community/Smartmontools
http://www.techrepublic.com/blog/linux-and-open-source/using-smartctl-to-get-smart-status-information-on-your-hard-drives/

• I want to add to the compatibility check and incorporate a smart status check on the drives being imaged.

• Also add the check right before imaging while the inits are doing checks, check the SMART disk status. If “PASSED” then continue. If “FAILED” then error out with message about a bad drive. If “UNSUPPORTED” then continue. (need to check on the message for unsupported but you get the jist)

This also gives you all the details of the HDD check it out!

apt-get install smartmontools 
smartctl -i /dev/sda
smartctl -H /dev/sda  

We could store that HDD info in the database if we wanted also for inventory purposes and such

I believe this will create a better stability of FOG itself

What do all of you think?

“System Cerial” sooo yummy!

Duh.

Re: Using FOG to PXE boot into your favorite installer images

Please Add “Paragon Hard Disk Manager” to your list this should work with any WinPE

Configuration currently works for UEFI only. It appears the wim file is missing bootmgr.exe for the BIOS booting systems

It is highly recommended to use this on a machine that has 4GB+ RAM.

First we’ll create the required directories:

mkdir -p /var/www/fog/Tools/{iso folder name}
chmod -R 777 /var/www/fog/Tools/{iso folder name}

Now we’ll mount the WinPE iso over the loop directory. Then we’ll copy the contents of the DVD to the directory we built above.

mkdir -p /mnt/loop
mount -o loop /{full path where you have the iso stored}/{iso file} /mnt/loop

We are going to copy to /var/www/fog/Tools so we can use the http protocal already setup for fog management.

cp /mnt/loop/bootmgr /var/www/fog/Tools/{iso folder name}
cp /mnt/loop/boot/bcd /var/www/fog/Tools/{iso folder name}
cp /mnt/loop/boot/boot.sdi /var/www/fog/Tools/{iso folder name}
cp /mnt/loop/sources/boot.wim /var/www/fog/Tools/{iso folder name}
cp /mnt/loop/efi /var/www/fog/Tools/{iso folder name}

umount /mnt/loop

Download and install the latest wimboot kernel and extract it from the zip file.

• https://github.com/ipxe/wimboot/blob/master/wimboot
  The issue was discussed in this post: https://forums.fogproject.org/post/144293
  We will use tftp protocal for this file in the fog menu.

cd /tmp
wget http://git.ipxe.org/releases/wimboot/wimboot-latest.zip
unzip wimboot-latest.zip

Copy the wimboot file from the archive directory to root of the os directory (we’ll need this for every windows boot media, so we’ll place it in a common spot).

mkdir -p /tftpboot/os
cp ./wimboot-2.6.0-signed/wimboot /tftpboot/os
chmod -R 777 tftpboot/os

The last bit of magic we need to do is setup a new FOG iPXE boot menu entry for this OS.
In the fog WebGUI go to FOG Configuration->iPXE New Menu Entry
Set the following fields

Menu Item: os.{iso file name}
Description: {iso file you would like to boot from}
Parameters:
set tftp-path tftp://${fog-ip}
set http-path http://${fog-ip}/fog/Tools/HD_Manager
kernel ${tftp-path}/os/wimboot gui
imgfetch --name bootmgr ${http-path}/bootmgr bootmgr
imgfetch --name bootx64.efi ${http-path}/efi/boot/en_us/bootx64.efi bootx64.efi
imgfetch --name BCD ${http-path}/bcd BCD
imgfetch --name boot.sdi ${http-path}/boot.sdi boot.sdi
imgfetch --name boot.wim ${http-path}/boot.wim boot.wim
boot || goto MENU

That’s it, just pxe boot your target system and pick os.{iso file name} from the FOG iPXE boot menu.

You’re going to have to go into mysql database and delete the host with hostID=0.

mysql -u root -p fog

in mysql…

select * from hosts where hostID=0 \G

That will show all your hosts with a bad hostID then you will need to delete them…

delete from hosts where hostID=0;

FINALLY re-register the host you were having trouble with.

x32 bit machines should now be fixed in the latest git.

• x32 Upload times are slow but they will upload all the way. ~84Mib/s with lvl 9 compression (4:20:15)
• x32 Download times are “fast” ~1.8Gib/s lvl 9 compression (00:12:01)
• x64 Up 3.2Gib/s lvl9 (00:20:00) Down 7.3Gib/s lvl9 (00:09:00)

Full Description of problem:
1.)nfs mount issue was due to not getting an ip address during init boot.
2.)Not getting an ip was due to an addition of fixing VLAN issues for networks and sleep command was an “Illegal Instruction” (along with other commands essential to “init fog script”)
3.)sleep was not working due to a compiling issue in the glibc v2.21.

*Solution:
1.) Downgraded init’s to use glibc v2.20 (fixed sleep function).
2.) init’s now get ips from edits in files K40Network and S40Network.
3.)NFS mounts successfully now that init gets an ip address at boot.

These changes have been pushed to both init_32.xz and init.xz.

If you see this issue with your old 32 bit only processors please make sure you update to the latest version and this should be fixed.

P.S. @Tom-Elliott thanks for the remote sessions and time. Took us a while but we nailed down the problem

32-bit and 64-bit both work in the inits.

You just have to boot into debug mode right now and then type in the above commands. I will talk with Tom to see if we can change the compatibility check first as we do not want to mess up the current flow

git 4290

Issue occurred during download at step “restoring partition tables (GPT)…”

Error: “Error trying to restore GPT partition tables”

Checked gdisk /dev/sda but no partitions present due to the FOG script clearing them. Tried a “Quick wipe” and “Full wipe” tasks but still no go.

Went into gdisk again to see if I could create an MBR correctly and it did succeed.

I thought that it maybe the drive so I threw this drive into a confirmed working host. The new host download the image on to the HDD without issue.

Looking into BIOS updates or bad RAM for the issue. Will report back with full solution.

Just thought I would report just incase anyone else had the issue.

https://github.com/FOGProject/fogproject/blob/33fe4988cc738a625308267ae78cdc7879a6e411/src/buildroot/package/fog/scripts/etc/init.d/S99fog

I hope this helps a bit to understand the commands you can use in the new ipxe menu in 1.3.0.

Just did a clean install of Debian 8 (r3707). Still fails on getting packages. The work around was to:

apt-get install apache2 php5 php5-json php5-cli php5-curl mysql-client nfs-kernel-server vsftpd net-tools wget xinetd sysv-rc-conf tar gzip build-essential cpp gcc g++ m4 lftp php-gettext php5-mysqlnd curl libc6 libcurl3 zlib1g php5-fpm

then run the installer.

The compression is done directly on the Host computer and then transferred up to the server.

That said there maybe a way to decompress and recompress an image but complications may occur.

Well obviously the file doesn’t exist. When you uploaded you used Multi partition single disk right? We can see this by your file listing. However you need to reupload using single disk as Wayne was suggesting.

Just changing the option to single disk and trying to download will not create the files needed. Please change the image setting to Single Disk then upload the image. THEN download it another host.

Apache logs consuming fog server hdd (maxes to 100%)
–Have to delete everything in /var/log/apache
–then restart service to clear hdd on server
–finally HDD is back to 22% used

This is a current issue with the SVN

cd /var/log/apache/
rm *
service apache2 restart

Tom has added the program into the init’s but has not implemented this in full as of yet.

Tested x86_64 (aka init) and commands work correctly

Need to test the x86 (aka init_32)

this will be done in the morning

You will need to change the “Image Manager” from partImage to partclone. Then reupload.

<OS>
<path>
Single Disk
Everything
<compression>
PartClone

UPLOAD!

lol just had to

If you update they should be fixed unless you have hostID’s = 0 or iHosts=0…etc.

@Roger-Saffle Are you using an image that was already attached to the domain when you uploaded it?

I can also atest to this. Windows 11 is not having any issue with my Dell Latitude 7440 2-in-1’s. Select “Windows 10” as your OS and you should be just fine…for now

two if’s here…

if you were on the latest svn right before svn went down or used a git during that time
AND
if you uploaded an image on those svn/git builds then your freshly downloaded host may not resize correctly. It was even reported that some would resize correctly while others did not. This was a little glitch in the uploaded images.

SO TO FIX:
upgrade to latest svn/git then re-upload that particular image. Then your downloaded hosts will resize correctly.

Did you create an A Record pointer on your DNS Server to point FOG-SERVER to IP xxx.xxx.xxx.xxx.?