Fog Download FAILS

[SteveB689]

Thsi is just a thought, I have installed a second hdd for the images… and all good when it comes to upload to the new image store.
Again Fog scripts seem to want to default to /dev/sda when the path should be sdb.
Does anyone else have issues with this?
I task downloading, the script runs… NO ERRORS… just doesnt do it.

[Quazz]

@SteveB689 Fairly certain you’re seeing the target HDD, not the source.

What do you see when you try to image?

[Wayne Workman]

@SteveB689 said in Fog Download FAILS:

Thsi is just a thought, I have installed a second hdd for the images… and all good when it comes to upload to the new image store.
Again Fog scripts seem to want to default to /dev/sda when the path should be sdb.

Can you elaborate? What did you put a second hdd in? When I first read that line, I thought you were meaning you added it to the fog server, but the second line to me suggests you’ve added it to the target host.

[Wayne Workman]

If you’ve added a second HDD to the FOG server and have re-configured your storage node to point to it, and have it mounted and all that jazz,

You still need to update the /etc/exports file. This file is how to configure the NFS sharing for FOG. If a second HDD in the fog server is the case, it should be pretty simple for you to edit the exports file to reflect where the new images directory is.

[SteveB689]

@Wayne-Workman said in Fog Download FAILS:

If you’ve added a second HDD to the FOG server and have re-configured your storage node to point to it, and have it mounted and all that jazz,

You still need to update the /etc/exports file. This file is how to configure the NFS sharing for FOG. If a second HDD in the fog server is the case, it should be pretty simple for you to edit the exports file to reflect where the new images directory is.

Hi

I will check that file and edit appropriately if need be…
Unfortunately, I am in a position just to be able to get this deployment scenario up and running whilst having to attend to my other IT duties… not conducive to sensible troubleshooting.
Plan B now, is to create this whole FOG setup on VM box on 1 machine so that I can at least carry the entire concept on 1 laptop… and work out what works and does not work.

I havent even got to the point of overcoming the fact that the HP 280 desktop machines having UEFI boot as default.

[SteveB689]

@SteveB689

This editting the exports file

1. Edit /var/www/fog/commons/config.php. (on centos 6 see /var/www/html/fog/commons/config.php)
   Change the values of STORAGE_DATADIR and STORAGE_DATADIR_UPLOAD to

“/home/fog/images/”

and

“/home/fog/images/dev/”

for example.

If you already have created images with FOG, don’t forget to move the complete directory /images to the new place. Be sure that the correct access rights are granted.

2. Edit your exports file (in /etc/exports) to export the new location via NFS:
   /home/fog/images *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)

/home/fog/images/dev *(rw,sync,no_wdelay,no_root_squash,insecure)

After that tell the running NFS-server to read the new config:

exportfs -a

3. Edit your storage-node definition:
   Go to Storage -> All storage nodes and edit the entry of the “Image Location:” to your new target for your Storage Node “DefaultMember”.

After that your “Disk Information” (Free / Used / Total) at the dashboard may not be correct anymore. Edit the file freespace.php in your web-root (/var/www/fog/status/) (on centos 6 see /var/www/html/fog/status):

define( “SPACE_DEFAULT_STORAGE”, “/home/fog/images/” );

You may also need to modify the permissions for the /home/fog directory. It is suggested that you use:

chmod 701 /home/fog

4. Create .mntcheck file in your new “images” and “dev” folders :
   touch .mntcheck

Nothing here mentions /dev/sdb* where my images now reside… it’s all about a share name … so this where I am getting confused… how does FOG know about a second hdd?

[Quazz]

@SteveB689 This all depends on how the second HDD is set up. Can you give us some more information about that?

LVM would be easiest and would require almost no action besides setting up the LVM itself.

But I’m guessing you’re not using LVM?

What’s the actual path to the image location you created on /dev/sdb?

[Wayne Workman]

@SteveB689 Where did you find those steps? They are very outdated.

I would never advise anyone manually edit commons/config.php, All you’d need to do is modify the image path setting in /opt/fog/.fogsettings and re-run the installer. Without doing that, the changes to that config.php file will simply be overwritten the very next time you re-run the installer or update. Then you’ll blame the update, when in fact it was just using the settings set inside the .fogsettings file.

To mount the 2nd HDD, you would modify /etc/fstab to mount it correctly and to the directory you want. I would suggest mounting it to /images

If you’re using Ext4 as the file system, mounting there would mean adding this line to /etc/fstab
/dev/sdb /images ext4 defaults 0 0

lvm:
/dev/sdb /images ext2 defaults 0 1

for NTFS:
/dev/sdb /images ntfs-3g rw,auto,user,fmask=0111,dmask=0000,noatime,nodiratime 0 0

for Fat32
/dev/sdb /images vfat rw,auto,user,fmask=0111,dmask=0000,noatime,nodiratime 0 0

And FOG Trunk supports UEFI if you’re not already using it.

[SteveB689]

@Wayne-Workman

That makes perfect sense… I will have to check how I amended the fstab file… which I know I did according to some other instructions.

Those ‘steps’ by the way are on the FOG wiki pages as regards NFS… there are noted as ‘old’ but there doesnt seem to be any ref to what you have suggested.

[Wayne Workman]

@SteveB689 search the wiki for .fogsettings it explains each item.