Hi, everyone!
I know that whenever FOG Web Interface shows this message when I try to access it:
it’s to time to reinstall it.
The problem is: this situation occurs every 2 months the average.
Is there another way to solve this unless reinstalling it?
@Sebastian-Roth it’s funny but… I decided change the client IP (added 172.24.12.49 into DHCP Exclusion Zone now client received 172.24.12.65), so it worked!
Maybe some lockout from FW or Core rules… but it’s working, as I figured out on other computer with some specification. Could you check PCAP of 172.24.12.65? It’s here: new PCAP, just to understand it, because I know, FW and Core rules are not the target of this forum 
@Sebastian-Roth these are the answers, as followed:
userutil@moringa:~$ sudo iptables -L
[sudo] password for userutil:
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT udp -- anywhere anywhere multiport dports mdns
ACCEPT tcp -- anywhere anywhere multiport dports 4000
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
@Sebastian-Roth , I did a capture directly from FOG server (172.24.3.144) by Wireshark, the troubled client is 172.24.12.49. Here you have it: https://drive.google.com/open?id=1oolDaPqrF4gFIzN8gRfIXrnyKC18ahHj
Hi,
I still have the ipxe.efi chainloading tantalizing me… I already posted another issue about it (11240) and it worked when I followed instructions to “connect” to a unmanaged switch over building switch “as a workaround”…
…we have here several types of computer with UEFI boot. Some of them is working properly. That’s its behavior:
on the other side, I have some computers will no work, they gave me this kind of error:
Any ideas? As I see, it’s not properly IPXE issue, because some UEFI are booting from IPXE… Is the second type of BIOS “lazy” to process IPXE Boot request??
I have this problem in FOG every 3 months aproximately. All I just do is to reinstall it and everything turns well, wihout any lose of data or settings.
@Sebastian-Roth, it’s funny. Fog deployed successfully all partitions, simply pressing ENTER after each breakpoint.
@Sebastian-Roth That’s what I did.
Follows Settings you suggested:
After usual messages, these are what I get. Here are the images:
@Sebastian-Roth Follows here:
Below is a variable dump from FOG
osid=9
osname=Windows 10
mbrfile=
type=down
storage=172.24.3.144:/images/
img=PositivoD535Win10A8
imgType=mpa
imgFormat=0
imgPartitionType=All
disks=/dev/sda /dev/sdb
hd=/dev/sda
* Press [Enter] key to continue
[Tue Sep 11 root@fogclient /]#
Typing fdisk -l, we have:
Disk /dev/sda:119.2 GiB, 128035676160 bytes, 250069680 sectors
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/physical): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/sda1 1 500118191 500118191 238.5 ee GPT
Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
@Sebastian-Roth said in Deploying FOG in a raw SSD disk:
ismajordebug=1
@Sebastian-Roth, where will I add these Host Kernel Args?
Hi, guys!
I have several computers that had SSD issues, forcing assistance to change them by newer, raw disks.
Each computer has two-disks (sda-SSD 100Gb, sdb-SATA 500Gb). Only SSD was changed.
So I cannot deploy image on them due to it.
That’s the classical error message:
Image store corrupted, unable to locate MBR, no file found (MBRFileName)
Other message I got (in other moment):
Error trying to restore GPT partition tables (restorePartitionTablesAndBootLoaders)
I saw some ancient issues opened here, but nothing of them conclusive.
As workaround, I make a clear-Windows 10 formatting; after that, I can deploy successfully on them.
Do we have any updated news about it?
Hi,
We have 1.4.4 installed, and it’s running very well. UEFI boot runs fine. Just an issue to solve: After white-backgrounded FOG menu, we have a black screen with just a blinking cursor for almost 2 minutes, so we have this message:
r8169 0000:01:00.0 (unnamed net_device) (uninitialized): rtl_ocp_tx_cond == 1 (loop: 2000, delay: 50).
Starting logging: OK
Populating /dev/ using udev: udevd[2675]: error creating epoll fd: Function not implemented
done
Initailizating random number generator... done.
After that, everything works fine. FOG finishes its task normally.
Is there anything I can do reduce this lag?
@george1421, it worked! I put it under an unmanaged switch, and the computer got boot. At the first try, it got chainloading error, but at second try, it worked! Thanks!
I will consider about enabling dnsmasq for ProxyDHCP.
@quazz and @george1421, I did a workaround to it. As my DHCP works with subnets, I took apart one of them to offer ipxe.efi instead of undiolny.kpxe. Now I have other issue… I have two UEFI devices, to older got a iPXE boot as I did my workaround, but the other, newer, did not! It’s telling this:
Could not boot: Connection reset (http://ipxe.org/0f0a6095)
Chainloading failed, his 's' for the iPXE shell; reboot in 10 secondsHi,
Did somebody got a PXE boot from a Windows 2003 DHCP by UEFI? According to Wiki nobody got it yet. I would be the first, but I’ll be happier if somebody got it before! 
No regarding which Vendor Classes to register (because I think W2k3 will not follow this directive) they always try to read undionly.kpxe. If I force them to read any other, link as ipxe.efi, they return a “NBP filesize is 0 Bytes” condition.
Any ideas?
@sebastian-roth and @Wayne-Workman, solved! I just had to update storage management password for DefaultMember. After that, I got successfully uploaded captured image. Thanks!
Hi!
I’m trying to capture an image as a new version, over an already existing image. The problem is FOG is not ending this process. Task management talks about 95% to complete.
after capturing process, it shows this message:
Is it user permissions? Must I give all to root user?
userutil@moringa:~$ ls /images -l
total 72
drwxrwxrwx 7 fog fog 4096 Dec 5 15:44 dev
drwxrwxrwx 2 fog fog 4096 Mar 22 2017 DieboldTAAWXP
drwxrwxrwx 2 fog fog 4096 Aug 8 14:39 HPCompaqW10au
drwxrwxrwx 2 fog fog 4096 May 25 2017 HPCompaqWau
drwxrwxrwx 2 fog fog 4096 Aug 8 14:40 ItautecSM3330Win10au
drwxrwxrwx 2 fog fog 4096 May 4 2017 Lenovo6073XP
drwxrwxrwx 2 fog fog 4096 Oct 17 08:08 LenovoA706099Win10au
drwxrwxrwx 2 fog fog 4096 Mar 22 2017 LenovoA7099W10
drwxrwxrwx 2 fog fog 4096 Mar 22 2017 LenovoA70zPainelW10au
drwxrwxrwx 2 fog fog 4096 Mar 22 2017 LenovoThinkPadWin10AU
drwxrwxrwx 2 fog fog 4096 May 25 2017 PositivoATDPFXP
drwxrwxrwx 2 fog fog 4096 Mar 22 2017 PositivoD535W10
drwxrwxrwx 2 fog fog 4096 Aug 8 14:55 PositivoD535W10au
drwxrwxrwx 2 fog fog 4096 Oct 25 14:55 PositivoD570W10au
drwxrwxrwx 2 fog fog 4096 Aug 9 20:11 PositivoD610W10au
drwxrwxrwx 2 fog fog 4096 Jun 19 07:38 PositivoDVistaXP
drwxrwxrwx 2 fog fog 4096 Aug 8 14:37 PositivoP4PEW10au
drwxrwxrwx 2 fog fog 4096 Mar 23 2017 postdownloadscripts
userutil@moringa:~$ cd /images/dev
userutil@moringa:/images/dev$ ls
0040a71e1b0b 1cc1de2a94a3 7054d2c6dfe1 e06995fdb3c5 postinitscripts
userutil@moringa:/images/dev$ ls -l
total 20
drwxrwxrwx 2 fog fog 4096 Aug 8 14:40 0040a71e1b0b
drwxrwxrwx 2 fog fog 4096 Aug 8 14:39 1cc1de2a94a3
drwxrwxrwx 2 root root 4096 Dec 5 17:25 7054d2c6dfe1
drwxrwxrwx 2 fog fog 4096 Aug 8 14:37 e06995fdb3c5
drwxrwxrwx 2 root root 4096 Aug 5 00:50 postinitscripts
@wayne-workman and @sebastian-roth, this issue is solved. I thought I posted an answer days ago, but where is it? The important is FOG is running fine about this issue. When I reinstalled FOG, I unmounted images partition, so post init sripts were copied to original /images folder on server sda disk. So I unmounted /images againd e copied this folder to correct place.
As the original question, it’s fine. I got successful to deploy this image to another host.
Thanks!
@wayne-workman , I think it’s another issue. I cannot deploy any other image, because I got this error below. The deployer stuck in this screen, no regarding what user I choose to execute the task:
