fog.drivers script will not run correctly in postdownloadscripts

[THEMCV]

@george1421 I installed dos2unix and converted the fog.driver. Testing now.

We have all Dells thankfully.

[george1421]

@THEMCV THEN, if you have ONLY Dells, I might suggest you change the order of the driver library to match the format of the dell cabs.

This I can tell came from Lee’s script. (understand this is only a personal opinion of the setup)
remotedriverpath="/images/drivers/$osn/$machine"

This structure is different than what comes in the dell cab of machine then OS. In my scripts I would use this format
remotedriverpath="/images/drivers/$machine/$osn/$arch'

There is no right or wrong way here, I just pick easy over neat.

[THEMCV]

@george1421 Here’s what I got back this time:

mount: mounting <ip address>:/fog/ on /fog failed: Permission denied
* Mounting device.................................................Done
/images/postdownloadscripts/fog.drivers: line 15: [[-z: command not found
/images/postdownloadscripts/fog.drivers: line 18: [[!: command not found
* Preparing Drivers....................................................../images/postdownloadscripts/fog.drivers: line 35: [[!: command not found
In Progress/images/postdownloadscripts/fog.drivers: line 43: [[!: command not found
Done
umount: can't unmount /ntfs: Invalid Argument

[THEMCV]

@george1421 I extracted the driver from the .CAB file, but I will try switching them out tomorrow when I get in.

[george1421]

@THEMCV said in fog.drivers script will not run correctly in postdownloadscripts:

@george1421 I extracted the driver from the .CAB file, but I will try switching them out tomorrow when I get in.

It makes it easier when you have new models to just extract the cabs and throw it in a directory on a windows computer to build the structure. Then use 7-zip to create an archive to copy to the fog server, then use unzip to extract.

[george1421]

@THEMCV But your error is having a problem in line 15 with the test of $machine is zero. Just wondering if the word if needs to precede the conditional test. I’m not an expert bash programmer so I can’t about all of the shortcuts you can do in bash.

[Tom Elliott]

@george1421 It’s got nothing to do with the if or not. It’s because (and I’m just guessing) he literally copied and pasted the code.

Right now the code braces are stripping spaces.

So he is literally having his file with: [[-z $machine]] rather than [[_-z $machine_]] (replacing the _ with actual spaces.

[Tom Elliott]

@THEMCV Please try this:

wget -O /images/postdownloadscripts/fog.drivers http://mastacontrola.com/fog.drivers

–Fixed.
Wayne

[THEMCV]

@Tom-Elliott I downloaded that and we’re definitely farther! No more parsing errors, so that’s amazing. Thank you!

Now it’s telling me

mount: mounting 10.4.200.150:/fog/ on /fog failed: permission denied
   * Mounting Device...................................................................Done
   * Preparing Drivers..................................................................In progress

Then it tells me an error has been detected

Failed to download driver information

So I double checked my directory which is: /images/Drivers/Win7/OptiPlex 980/x64

I’m using extracted CAB drivers for now, but might switch/try just CAB files. They seem to be in place where they should be.

Thank you Tom.

[Wayne Workman]

@THEMCV It’s failing on this line:

rsync -aqz "$remotedriverpath" "$clientdriverpath" >/dev/null 2>&1

SO, just before that, for troubleshooting purposes, echo out the command it’s running like:

echo
echo "rsync -aqz \"$remotedriverpath\" \"$clientdriverpath\""
echo

Put those three lines one line above the problem line, exactly as I typed it. It will echo out the actual command being run. Then, run the script. The command will get echoed out and look proper. Examine it, copy it, and try to run the command by itself and see what happens.

[THEMCV]

@Wayne-Workman Okay, got it.

mount: mounting 10.4.200.150:/fog/ on /fog failed: permission denied
   * Mounting Device...................................................................Done
   * Preparing Drivers..................................................................In progress
rsync -aqz "/images/drivers/Win7/OptiPlex 980" "/ntfs/Windows/DRV"

Then

Failed to download driver information

It definitely sat on Preparing Drivers much longer than before, but the same outcome.

I confirmed the directory is /images/drivers/Win7/OptiPlex 980/x64

[Tom Elliott]

@THEMCV Is it /images/drivers/Win7/OptiPlex 980/x64 or is it /images/Drivers/Win7/OptiPlex 980/x64

(Notice the D in drivers is capitalized).

[THEMCV]

@Tom-Elliott It was /Drivers/ and not /drivers/ but I changed to /drivers/. Same issue.

When I was looking over the code I misread and thought I saw a reference to /Drivers, so that’s on me.

[Quazz]

Am I going crazy or is this a simple issue with the fog server not mounting on the client?

mount: mounting 10.4.200.150:/fog/ on /fog failed: permission denied

Is the IP correct? Does the /fog folder exist?

[george1421]

@Quazz That is what I was just trying to reverse engineer. Where did the /fog directory come from? The only nfs share is /images.

The info that is missing here is that I the mount isn’t happening in this script but in the fog postdownload script from here: https://forums.fogproject.org/topic/4278/utilizing-postscripts-rename-joindomain-drivers-snapins/29

[edit] Side note, I found that my post install scripts fail when deploying to NVMe disks since the disk structure is different. I was looking at merging some of the code magic Tom created into my scripts too.

[THEMCV]

@Quazz The IP is correct. I must have gotten things turned around looking at the Auto install script on the FOG wiki.

So I need to make a fog directory in root like this, correct?

/fog/Drivers/Win7/OptiPlex 980/x64

[THEMCV]

@george1421 Just so I’m understanding, so the /fog directory should or should not exist? And if it does it is because of the script?

[Quazz]

@THEMCV The fog directory does not exist by default, it must be manually created, given correct permissions and an entry in /etc/exports needs to be made to export it as a nfs share so it can be mounted on clients.

mkdir /fog
chmod 777 /fog
chown fog:fog /fog
nano /etc/exports

add this line add the bottom:

/fog *(ro,sync,no_wdelay,subtree_check,insecure_locks,no_root_squash,insecure,fsid=2

then finally do the following command to export the directory:

exportfs -a

Check if it it is being exported with:

showmount --exports

Use sudo if necesary

Do note that you still need to create diretories and add drivers yourself.

[george1421]

@THEMCV OK, I understand you may be getting conflicting information here because we are coming at the same problem from different perspectives.

In my scripts I have the drivers (on the fog server) in /images/drivers …
That is what the scripts should be trying to mount. You can use /fog/drivers but you will need to setup an export in NFS to do that. Me being lazy I just used the /images share that was already there.

Looking at the script from Lee’s page this is the line in question

remotedriverpath="/images/drivers/$osn/$machine"

In this case its saying the drivers are in /images/drivers/… on the fog server. Where is /fog/drivers coming from?

[THEMCV]

@Quazz Okay, I completed this and it’s finished. showmount --exports does show /fog is working. And I added in the drivers that I had in the other location.