Posts made by imagingmaster21

@george1421 No I did not find it with the MAC Adress

Yes I do get errors when capturing it goes through up to 100% on the capture job and then gives a error about the image store and that the computer will reboot in 1 minute. In the ‘List all Images’ it shows my image with the size of it, but is no were to be found in the /images directory. @Sebastian-Roth

When I go to deploy an image I get this error.

I went through and verified all the FOG passwords are correct, also when a Image is captured it is not showing in the images directory and I do not see it in the dev directory as the MAC name.

Any ideas?

@joe-gill
Looks like a issue on the serviceconfigurationpage.page.php file with lin 1475…

@Joe-Gill Try looking into your apache settings and look at logs. Here is a an article on how to do that, might vary depending on the web service you are using for web server.
https://blog.codeasite.com/how-do-i-find-apache-http-server-log-files/

@johnny-T
Let me answer one question at a time.

#1:The only limit you would have for image size would be based off whatever space is available in storage.

#2: Are you asking if you can transfer images from one server to another? Is so then yes. You just need to make sure everything in the web GUI fo the image settings as on the original server as it is for the server you are transferring it to (image name, operating system compression, etc.)

@boyan-biandov
Did you try putting something like this in your answer file:

<cpi:offlineImage cpi:source="wim:c:/users/administrator/desktop/10%20pro/sw_dvd5_win_pro_ent_edu_n_10_1709_64bit_english_mlf_x21-50143/sources/install.wim#Windows 10 Pro" xmlns:cpi="urn:schemas-microsoft-com:cpi" />

@sebastian-roth I fixed the problem, the FOG TFTP and Storage Node passwords needed corrected.

@Sebastian-Roth I just was thinking of this last evening. I had that problem before when I first started using FOG. It just ended up being the wrong passwords. You don’t think of that after you have one server up and running for a year.

I just built a test server to test out FOG 1.5.4. I go to capture my first image on it and on the host machine itself it goes through just fine and when finished reboots to the hard drive. But if you look in FOG task it still shows it as capturing. It does not give a percentage under FOG task for the capture job, but just a spinning circle, and does not go away even if you give it a day.

If you go into the images directory it does not even show the folder for the image I captured.

My production FOG server is still running 1.5.2, I used the same settings for this image as I always do on my production FOG Server 1.5.2. I also compared the permissions for the /images directory between the production 1.5.2 server and the test 1.5.4 server and nothing appears to be different.

Any ideas on what I am missing here? I think its just a setting within FOG is m guess.

@george1421 @JJ-Fullmer
Following this linked worked! Thanks to @george1421
https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image/3?page=1

@JJ-Fullmer @george1421
I tried updating both of the Kernals and it produced the same result. So I then tried switching the ipxe.efi and the realtek.efi and gave the same results. ipxe.efi boots to the FOG PXE menu and gives the same result when imaging. But when using realtek.efi you are not even able to PXE boot. So trying different efi files after updating the Kernels did not work. Is there anything else worth trying other than updating to the new version of FOG?

@jj-fullmer
@george1421

I just tried switching from snponly.efi to ipxe.efi and it gave the same result as before. I then tried realtek.efi and it would not boot to the PXE menu, it gave a timeout error for DHCP. So I switched back to using snponly.efi.

@JJ-Fullmer You mentioned about updating the the bzimage and init kernel files. I am going to try this first with backing up the current ones first.

@george1421 @JJ-Fullmer
I just tried flashing the firmware BIOS to the latest version and it did not resolve the issue, so that should eliminate the firmware.

Here is another systail log, I think it is pretty much the same:
https://dl2.pushbulletusercontent.com/UsKM9oEU0cs3F00ycSBUAqtbFdwznlGh/image.png

@george1421
This is the computer from Lenovo:
https://www3.lenovo.com/us/en/laptops/thinkpad/thinkpad-13-series/ThinkPad-13-Windows-2nd-Gen/p/22TP2TX133E

It is a Lenovo 13e, model number 20j10006us.

@george1421

• I am booting a Lenovo 13 laptop wit a USB to Ethernet Adapter: Here is the link to the Adapter
  https://www.amazon.com/Network-CableCreation-Ethernet-Supporting-Required/dp/B013G4C8RE/ref=sr_1_4?ie=UTF8&qid=1528291661&sr=8-4&keywords=usb+3.0+to+ethernet

• 1.5.2 actually, I’d like to try avoiding upgrading to 1.5.4, I did not realize 1.5.4 came out. But if upgrading will fix this then thats fine.

• This is booting in UEFI mode, I did try Legacy and no luck (turned off secure boot and security chip). Also tried UEFI with CSM on and off and same result.

• Here is some screenshots of the DHCP for option 67:
  https://dl2.pushbulletusercontent.com/4OjA3BFqkVxs7T8IAehdDoF6p8vZf8Es/20180606_101945.jpg

  https://dl2.pushbulletusercontent.com/6C5Ewggp7yEbQMcBz1Piaaq2dBCJ8BAR/20180606_102033.jpg

I am trying to deploy an image to a machine that requires a USB to Ethernet adapter. I have the adapter registered as a host in FOG and I have the kernal arguments set. I have been able to do this before on version 1.4.4, I am now on the latest version and not able to do so. This is the first time I’ve had to do this on the latest version. When I did this with version 1.4.4 I used this link as a reference:
https://wiki.fogproject.org/wiki/index.php?title=USB_NIC_(usb_network_adapter)

So now when I go to deploy the image to the machine it will PXE boot to the FOG menu and I can select the image, it will go through bzImage…ok and init.xz… just fine, but after that its just a black screen. I’ve tested other known good images on this ethernet adapter with the same result.

Also here is a Ethernet Adpater I am trying this on with how I have it set in FOG.
https://dl2.pushbulletusercontent.com/1b30zBDYwcKOLiCxiiTymzEvJM9HdgRQ/image.png

Also I ran a syslog tail here is the results below the machine in question is getting a .106 IP Address:
https://dl2.pushbulletusercontent.com/2rQONvoHXxarn3byt1j8K6G4aRfpaKWI/image.png

This is the type of adapter I am using:
https://www.amazon.com/Network-CableCreation-Ethernet-Supporting-Required/dp/B013G4C8RE/ref=sr_1_4?ie=UTF8&qid=1528291661&sr=8-4&keywords=usb+3.0+to+ethernet

I am guessing there is something different in the new version with the settings that I am just not aware of.

@quazz
That worked!

@Sebastian-Roth
I am not sure what you mean by getting the contents of d1.partitions, d1.minimum.partitions, and d1.fixed_size_partitions. I am not sure how I would get that. But below is the screenshots of what shows up in disk manager:

• Host Machine (VM):
  https://dl2.pushbulletusercontent.com/g4a51qXNrNK5LjJ5zyRwvVmarfkBjz4V/20180530_083028.jpg

• Machine with the image from the Host Machine deployed to:
  https://dl2.pushbulletusercontent.com/HO6LPMms77NSKfceOfpSTdMmV8kDfclH/20180530_084145.jpg
  So on this machine its showing the C:\ with 49.37GB which is exactly the same from the Host machine, then you have a 69.24GB unallocated which should be all merged with the storage of C and in this case giving C a total capacity of 118.61 GB of storage.

As I mentioned before I am able to fix this issue after the image is deployed per machine using AOMEI, but this process takes fix minutes to do and when you do this to every machine adding an extra 5 mintues on does add up. Here is the link to the software I am using:
https://www.disk-partition.com/free-partition-manager.html

I am using FOG Version 1.5.2, I also tried this on a test version of FOG 1.5.0 to see if that made any difference and it did not. (I kept all the same exact settings with the image). Below is a screenshot of the image settings within FOG:
https://dl2.pushbulletusercontent.com/JCcHjoWJtYCwfm9GRK28PDV8UMKndIdD/image.png

Let me know how I go about getting the d1.partitions information, I never did that before and I would like to know how I am still trying to find a article on how to do that in the meantime.