@Quazz Okay, it’s in there. No change. Still acting like there’s no space left on the device which isn’t true at all. The image is only ~15GB.
Posts made by THEMCV
-
RE: fog.drivers script will not run correctly in postdownloadscripts
-
RE: fog.drivers script will not run correctly in postdownloadscripts
@george1421 I feel like an idiot. I got them jumbled up in my early stages. Bleh. Okay, so should I take the script that is from your link and use it or do as @Quazz suggested and just include a call to it?
@Wayne-Workman: The message from removing the >/dev/null 2>&1
This rsync lacks old-style --compress due to its external zlib. Try --zz. Continuing without compression. rsync:` write failed on "/ntfs/Windows/DRV/OptiPlex 980/x64/chipset/PP0H5-A00-00.WUB7/JasperFo.uno": No space left on device (20) rsync error: error in file IO (code 11) at receiver.c(393) [reciever=3.1.2]
Which doesn’t make much sense as the device does have space.
-
RE: fog.drivers script will not run correctly in postdownloadscripts
@Quazz I did not, no. I think I found the /fog reference though and might be our problem.
I think it might be my postdownload script itself.
#!/bin/sh ## This file serves as a starting point to call your custom postimaging scripts. ## <SCRIPTNAME> should be changed to the script you're planning to use. ## Syntax of post download scripts are #. ${postdownpath}<SCRIPTNAME> if [ $osid == "5" -o $osid == "6" -o $osid == "7" ]; then #only handling Win7/8/8.1 clearScreen; mkdir /ntfs &>/dev/null ntfs-3g -o force,rw $part /ntfs #mount image (remember this is mounting partition [U][B]after[/B][/U] new image is deployed) mkdir /fog &>/dev/null mount -o nolock,proto=tcp $storageip:/fog/ /fog #this is a share created on server under /fog which contains drivers, software etc.. (just add /fog to exports but you could use existing location i.e. /images and if you do, do not ne$ dots "Mounting Device"; if [ "$?" = "0" ]; then echo "Done"; . ${postdownpath}fog.drivers # run fog.drivers script umount /ntfs; # unmount when all is done :-) else echo "Failed To Mount Device"; sleep 30; fi fi
@Wayne-Workman I removed it and am testing it now.
-
RE: fog.drivers script will not run correctly in postdownloadscripts
the /fog mount error has disappeared from the process now @Quazz , but the same “Failed to download driver information”
-
RE: fog.drivers script will not run correctly in postdownloadscripts
@george1421 I really am not sure. I don’t see anything in the script that refers to /fog except in the notation. I added the folder and copied the drivers into there from /images/drivers and am testing it now.
-
RE: fog.drivers script will not run correctly in postdownloadscripts
@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.
-
RE: fog.drivers script will not run correctly in postdownloadscripts
@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?
-
RE: fog.drivers script will not run correctly in postdownloadscripts
@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
-
RE: fog.drivers script will not run correctly in postdownloadscripts
@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.
-
RE: fog.drivers script will not run correctly in postdownloadscripts
@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
-
RE: fog.drivers script will not run correctly in postdownloadscripts
@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.
-
RE: 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.
-
RE: fog.drivers script will not run correctly in postdownloadscripts
@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
-
RE: fog.drivers script will not run correctly in postdownloadscripts
@george1421 I installed dos2unix and converted the fog.driver. Testing now.
We have all Dells thankfully.
-
RE: fog.drivers script will not run correctly in postdownloadscripts
@george1421 Nail on the head. Copied it into Notepad++ to review it and then copied it back.
I’ll try that. Thank you so much.
-
fog.drivers script will not run correctly in postdownloadscripts
Server
- FOG Version: 1.3.0-RC-16
- OS: Debian 8 ‘jessie’
Client
- Service Version: v0.11.5
- OS: Windows 7
Description
We’re trying to get a master image made and using lots of sources on the forum, we found a script here:
#!/bin/bash ceol=`tput el`; manu=`dmidecode -s system-manufacturer`; case $manu in [Ll][Ee][Nn][Oo][Vv][Oo]) machine=$(dmidecode -s system-version) ;; *[Dd][Ee][Ll][Ll]*) machine=$(dmidecode -s system-product-name) #pruduct is typo, just realized sorry :( ;; *) machine=$(dmidecode -s system-product-name) # Technically, we can remove the dell one as it's the "default" ;; esac [[-z $machine]] && return #assuming you want it to break if it is not lenovo or dell? machine="${machine%"${machine##*[![:space:]]}"}" #Removes Trailing Spaces system64="/ntfs/Windows/SysWOW64/regedit.exe" # sloppy detect if 64bit or not [[! -f $system64]] && setarch="x86" || setarch="x64" ############################################# #this is not section necessary needed, it's just to make the path "human readable" #rather than using osid for filepath case $osid in 5) osn="Win7" ;; 6) osn="Win8" ;; 7) osn="Win8.1" ;; 9) osn="Win10" ;; esac ############################################# dots "Preparing Drivers" # below creates local folder on imaged pc # this can be anywhere you want just remember # to make sure it matches throughout! clientdriverpath="/ntfs/Windows/DRV" remotedriverpath="/images/drivers/$osn/$machine" [[! -d $clientdriverpath]] && mkdir -p "$clientdriverpath" >/dev/null 2>&1 echo -n "In Progress" #there's 3 ways you could handle this, #driver cab file, extracted driver files or both #so on the server put extracted driver files to match below folder tree #i.e. Model Latitude E5410, Windows 7 x86 image would be: #/fog/Drivers/Win7/Latitude E5410/x86 rsync -aqz "$remotedriverpath" "$clientdriverpath" >/dev/null 2>&1 [[! $? -eq 0]] && handleError "Failed to download driver information" #if you wanted to use driver.cab use this line below. #i.e. /fog/Drivers/Win7/Latitude E5410/E5410-Win7-A07-KTT4G.CAB #cabextract -d "$clientdriverpath" "$remotedriverpath/*.CAB" >/dev/null 2>&1 #if you wanted to mix both cab and extracted use these: #rsync -aqz --exclude='*.CAB' "$remotedriverpath" "$clientdriverpath" >/dev/null 2>&1 #[[! $? -eq 0]] && handleError "Failed to sync cab and non-cab drivers" #cabextract -d "$clientdriverpath" "$remotedriverpath/*.CAB" >/dev/null 2>&1 #[[! $? -eq 0]] && handleError "Failed to extract cab files" #this next bit adds driver location on pc to devicepath in registry (so sysprep uses it to reference) # remember to make devicepath= match the path you've used locally #also do not remove %SystemRoot%\inf #and to add more locations just use ; in between each location regfile="/ntfs/Windows/System32/config/SOFTWARE" key="\Microsoft\Windows\CurrentVersion\DevicePath" devpath="%SystemRoot%\inf;%SystemRoot%\DRV"; reged -e "$regfile" &>/dev/null <<EOFREG ed $key $devpath q y EOFREG echo -e "\b\b\b\b\b\b\b\b\b\b\b${ceol}Done"; # this just removes "In Progress and replaces it with done :-)"
Looking it over and it seems good to go, I tried it and received the following error:
mount: mounting <ip address>:/fog/ on /fog failed: Permission denied /images/postdownloadscripts/fog.drivers: line 2: $'\r': command not found /images/postdownloadscripts/fog.drivers: line 3: $'\r': command not found /images/postdownloadscripts/fog.drivers: line 4: $'\r':syntax error near unexpected token '$'in\r'' 'images/postdownloadscripts/fog.drivers: line 4: 'case $manu in umount: can't unmount /ntfs: Invalid Argument
Then it finishes out and boots into Windows without its drivers it needs.
the drivers are in /images/drivers/Win7/Optiplex 790/x64 for this lone machine at the moment.
I’ve been working on this for a while and the drivers are my downfall. I can’t seem to parse these scripts myself.
Anything and anything would be amazing and helpful.
Thank you
-
RE: Basic FOG competency test
Oh yeah, FOG is my favorite piece of software. Deployed at the last 3 places that I’ve worked.
That’d be pretty sweet to have a test on it.
-
RE: Using a SSD Drive in a FOG server
Yep, was using a 1TB Samsung 850 Pro and it worked great in an Optiplex GX620.
-
RE: Cannot upload Neverware Cloudready (ChromeOS) to FOG. "e2fsck failed to check /dev/sda20 (shrinkPartition)
@Wayne-Workman I will give that a shot. Thank you!