Posts made by JimmyJ0516

@george1421 Alrighty Thank you so much for helping. Everything is now working fine with no issues at all. Last question lol how do I make this issue solved or does someone take care of that lol?

@george1421 Actually this did fix the issue. It has now captured the d1.mbr file. I am now going to deploy the image to make sure it works 100%. Thank you

@george1421 I have successfully updated and I am now on 1.5.9-RC2.9. I will try and capture a image now and see where this takes me.

@george1421 Understood so I am moving into my /opt directory where all of the versions of Fog are stored and then I proceed to run the command you gave me correct?

@george1421 I have been using the TAR/GZ archive way of downloading the updates and all of the updates are stored in /opt is that a problem?

@Sebastian-Roth Do you think and again I’m just throwing it out there. What if I downgrade to 1.5.7. All of the images I created were on 1.5.7. Now that I am capturing images for the first time on 1.5.8 I am having these issues. If I do downgrade do I just re-run the installer for 1.5.7? As well as you mentioned all of the images before the news created the owner is fogproject and the new ones have root as the owner.

@george1421 I posted the results below. Also, this is not the first time using the computer I have captured the image before and never had issues. I also took another computer model and capture the image of that and also had the same issue the d1.mbr file is missing. I have also post the results of the differences.

[Thu Jun 18 root@fogclient ~]# lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 465.8G  0 disk 
|-sda1   8:1    0   579M  0 part 
`-sda2   8:2    0 465.2G  0 part 
[Thu Jun 18 root@fogclient ~]# fdisk -l /dev/sda
Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Disk model: ST500DM002-1SB10
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x0105e8f5

Device     Boot   Start       End   Sectors   Size Id Type
/dev/sda1  *       2048   1187839   1185792   579M  7 HPFS/NTFS/exFAT
/dev/sda2       1187840 976771071 975583232 465.2G  7 HPFS/NTFS/exFAT
[Thu Jun 18 root@fogclient ~]# 

This is from the server itself

/images/OPT7040-2019:
total 18393216
drwxrwxrwx  2 fogproject root        4096 Nov 18  2019 .
drwxrwxrwx 26 fogproject root        4096 Jun 18 09:38 ..
-rwxrwxrwx  1 fogproject root     1048576 Jul  1  2019 d1.mbr
-rwxrwxrwx  1 fogproject root   392718467 Jul  1  2019 d1p1.img
-rwxrwxrwx  1 fogproject root 18440862240 Jul  1  2019 d1p2.img
-rwxrwxrwx  1 fogproject root         190 Jul  1  2019 d1.partitions
-rwxrwxrwx  1 fogproject root          15 Jul  1  2019 d1.size

/images/OPT7040-2020:
total 19968056
drwxrwxrwx  2 root       root        4096 Jun 17 12:20 .
drwxrwxrwx 26 fogproject root        4096 Jun 18 09:38 ..
-rwxrwxrwx  1 root       root   424917799 Jun 17 12:14 d1p1.img
-rwxrwxrwx  1 root       root 20022329625 Jun 17 12:20 d1p2.img
-rwxrwxrwx  1 root       root         190 Jun 17 12:13 d1.partitions
-rwxrwxrwx  1 root       root          15 Jun 17 12:13 d1.size

/images/OPT3040-2019:
total 16517136
drwxrwxrwx  2 fogproject root        4096 Jun 28  2019 .
drwxrwxrwx 26 fogproject root        4096 Jun 18 09:38 ..
-rwxrwxrwx  1 fogproject root     1048576 Jun 28  2019 d1.mbr
-rwxrwxrwx  1 fogproject root   382515569 Jun 28  2019 d1p1.img
-rwxrwxrwx  1 fogproject root    13559174 Jun 28  2019 d1p2.img
-rwxrwxrwx  1 fogproject root    11096900 Jun 28  2019 d1p3.img
-rwxrwxrwx  1 fogproject root 16505295550 Jun 28  2019 d1p4.img
-rwxrwxrwx  1 fogproject root         861 Jun 28  2019 d1.partitions
-rwxrwxrwx  1 fogproject root          15 Jun 28  2019 d1.size

/images/OPT-3040-IMG:
total 11964976
drwxrwxrwx  2 root       root        4096 Jun 18 09:38 .
drwxrwxrwx 26 fogproject root        4096 Jun 18 09:38 ..
-rwxrwxrwx  1 root       root   424782473 Jun 18 09:33 d1p1.img
-rwxrwxrwx  1 root       root 11827327909 Jun 18 09:38 d1p2.img
-rwxrwxrwx  1 root       root         190 Jun 18 09:32 d1.partitions
-rwxrwxrwx  1 root       root          15 Jun 18 09:32 d1.size

@george1421 Sorry, I did not see that. I am running 1.5.8. I am going to run those commands now

@george1421 thanks for the steps. So I did as you said and I indeed got an error https://imgur.com/A6QGyJk I took a picture of it.

@george1421 I have tried capturing the image 2-3 times yesterday and it keeps failing to capture the d1.mbr file

@Sebastian-Roth it was a fresh OS install from one of my lab machines. I captured the image yesterday on June 16th. Also yes I saw that the image does not have the d1.mbr file I just do not know why.

@george1421 this is the error I got. when trying to image a machine that is all that came up. https://imgur.com/7Bd51th

Hello Everyone I am having issues with capturing and deploying the image. I am able to pull the image with no issues and no errors but when I try to deploy it to a unit I get the following message “Image Store Corrupt Unable to locate MBR no file found” I am adding as well some pictures to possibly show some troubleshooting steps I may be asked of. https://imgur.com/nXU283k. https://imgur.com/8guERyQ. https://imgur.com/7Bd51th Thank you again for the help.

@astrugatch Ok so I found the issue. I recently changed the IP address of my FOG Server so I reinstalled the FOG Client software on a PC and during setup put my new IP and it now works. I just need new images with the correct IP on the fog client software.

@astrugatch yes this is what I currently have on the active directory config.

OU=Imaged,DC=hawthorne,DC=k12,DC=nj,DC=us

I am running the FOG server version 1.5.4 I am not sure what version of Client I am using I installed it on the image like 3 months ago. I also went to C:\Program Files (x86)\ FOG but all that is in that folder are .tmp files

Hello, everyone, I am having an issue with my computers joining active directory after being done with the image. It does not join at all. I have checked my AD settings on FOG everything looks to be right I also used FOGCrypt for the password. I also have FOG Client installed on the images.

AD DEFAULT DOMAINNAME - domain name
AD DEFAULT OU - OU=Imaged,DC=haw,DC=k,12DC=nj,DC=us
AD DEFAULT USER- ADuser
AD DEFAULT PASSWORD ••••••••••••••••••••••••••••••••
AD DEFAULT PASSWORD LEGACY
ENFORCE HOST CHANGES CHECKED OFF

@Sebastian-Roth @Wayne-Workman First of all Thank you very much for assisting me through all of this. I am currently running FOG on a Hyper V VM. Each of them are on different VLANs they connect through fiber on a Meraki Switch.

@Wayne-Workman Hi Wayne I finally got around to try the link you sent me but I had no luck.

@Wayne-Workman thank you I will try this sorry for the late response. I am busy doing a last minute Rack install with switch upgrades so that is currently taking up most of my time before the school year starts. I will get back to you once i test thank you very much again i really appreciate it