@tom-elliott said in droit:

@julio said in droit:

bonjour voici mon fichier /etc/exports. j’ai ajouter ces deux dernière lignes pour un test mais elle ne fonctionne pas toujours.

I’m not quite sure what you’re looking for.

First things first, the fsid elements must be unique.

Meaning these lines are good.:

/images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0) /images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)

But the following 2 items are not good as they are overwriting the configuration for the first 2 items.

/home/fog/images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0) /home/fog/images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)

Should more likely be:
erreur.PNG

c’est ça mon problème. je cherche comment mon mon image dans mon serveur.

@george1421 Worked Great thank you sir. It was the Storage node password was incorrect.

@sebastian-roth Doh! I feel silly. It was absolutely disk size. I built the test machines smaller than the laptops the images were captured from. Thanks for that, now I can go bug the network engineer 🙂

@nerdstburns There is one important thing I have to add. If you select a single partition in the image definition it won’t touch the partition table on deploy/capture at all!! So I would advice you create two image defintions, one full image where the option Partitions is unselected and another one with Partitions set as suggested by George. Now capture the full image an deploy that to all your hosts once. Then when you want to update C:\ you capture that to the other image definition “Partition 1 only” and deploy that to the hosts again.

If you ever try to deploy the “Partition 1 only” to an empty disk (no or not the correct partition layout deployed before) then it will fail!

@kylian Well the simple answer is yes you can. In the host management page of the target computer there is a filed to identify the disk you want to send the image to.

The bit longer answer is the format of the disk is dependent on how the disk is connected to the computer. If its over a sata cable then disk 1 will be /dev/sda, disk 2 will be /dev/sdb and so on. So if you wanted to deploy to the 3rd disk on the computer you would enter /dev/sdc into that field.

@tom-elliott
Originally I wanted to keep the image without installation as I did at the time … I will experiment with domain integrations. And the multicast (At the time it saturated the network … :))

@sebastian-roth I was able to test on both an M83 and a 7010. I’ll be doing more widespread testing once we get back after the holidays, but everything seems to be fine!

@sebastian-roth said in Permission Denied Capture:

ls -al /images/INFRA-NEW

Ah I ran that and it wasnt listed, so I checked under Images, and all my other images were there- So I just decided to remove that old image from Webui and remake it.

@blema2213 It looks like I need to create an updated post. The intent was for you to follow this process https://forums.fogproject.org/post/103323 until you get to step 18 then jump to the first link I posted to you.

The idea/problem is just as I mentioned, Win10 expects to see local or network based media not in RAM media. Also the issue with the above link is that you can not use the memdisk program with uefi. So what I’m recommending is that you copy the win10 media to a windows server and share it out as read only. Then build a WinPE image that will mount the network share you created and run the winsetup program. Windows will allow you to install over a CIFS share.

So the steps are to

Copy the windows media to a windows based server (or SAMBA) share. Create a WinPE boot media Launch that WinPE image from the fog server over pxe Install Windows from the share created in step 1

@george1421 Thanks so much for your quick reply! I do have 3 DHCP servers that sync with each other but all the settings seem to be correct. I will start a new topic.

This is fixed in the latest dev-branch code. Looking at it again I found this to be a simple typo (ref).

@george1421 You were right! It worked. I didn’t know that I should run it again to complete the installation, my distraction, I lost about 40 hours to solve something that wasn’t even installed! Thank you very much @george1421. You saved my job.

@sebastian-roth Thank you and @george1421 for your assistance it this matter. It worked great!

Thanks again and keep up the great work!

@sebastian-roth Thank you.

It’s the 1.5.9 version. Not tried with a different browser, only Chrome for the time being.

I’ll dig through the logs but if the page is a redirect I guess that’s where the problem lies.

That’s what I need it! Thank you for your post roro, I was trying to fix it during days!

@vemoya We have seen hosts go pending but that seemed to have been cause by the PowerShell module API calls.

We shall try to figure out if you have entries in the DB that are obviously not correct:

shell> mysql -u fogmaster -p Password: ... mysql> use fog; ... mysql> SELECT hostID,hostName,hostPending FROM hosts WHERE hostID NOT IN (SELECT hmHostID FROM hostMAC); ... mysql> SELECT hostID,hostName,hostPending FROM hosts WHERE hostID NOT IN (SELECT hmHostID FROM hostMAC WHERE hmPrimary = '1'); ... mysql> SELECT hostID,hostName,hostPending FROM hosts WHERE hostPending = '1'; ... mysql> SELECT * FROM tasks WHERE taskStateID IN ('1','2','3'); ....

You find the password for the “fogmaster” database user in /var/www/html/fog/lib/fog/config.class.php. Please run the queries and try to copy&paste all the results here in the forums. Use PuTTy or some other SSH tool to connect to your server so you can copy&paste text.

@will Well the issue is on the target computer side. If the ssd was always disk 0 then it would be easy because in the host definition you could say to deploy the image to /dev/sda but the issue comes when there is two hard drives which one is detected first. The first detected (sata) hard drive is /dev/sda and the second detected hard drive is /dev/sdb This most of the time corresponds to which sata cable is connect to the drive. The cable for drive0 is usually detected as /dev/sda and the cable for drive1 is usually detected as /dev/sdb but only when there is a drive connected to the drive0 cable.

So can you have fog image properly, sure. You just need to tell it on a host by host basis when the ssd is connected to any other cable than the one for drive0.

@sebastian-roth I have not, it seems to have just been that one time.

@epsilon52 First let me say that I 100% agree with Sebastian, but I also know a secret for the Dells.

Using the Dell CCTK (Command and configure tool) you can instruct the bios to pxe boot on the next boot up. This is totally outside the scope of FOG and not something that FOG is capable of, but the cctk tool has the ability to update/change bios settings from inside windows. So using that thought one could create a snapin (FOG deployable program) to run the preinstalled cctk command with the proper parameters to pxe boot on the next reboot only then instruct the computer to reboot. You would deploy that task after you have created an imaging task. I have not personally do this on my campus because I have other rules, but it should be totally possible with snapins and the fog client (I don’t use either in my environment).

As I said before I require the Imaging Tech to sit in front of the computer being imaged so they are 100% certain on what computer they are imaging. Because once in the past with the fully automated process we had an Imaging Tech pick the wrong computer and reimaged (i.e. erased) a VIP’s computer.