Posts made by Dark000

@Tom-Elliott Thank you for the workaround. It works now, so that will give me the time to look into network issue. Thanks again, you always come through.

Then it is definitely network issue. If it is not too much of a trouble is it possible to get fog 1.2 wol functionality back (where its 1 host at a time). I know the new way is more efficient but just until i can figure out the network issue.

Yes that is correct (the topic title could be better formed). If i put those hosts that didn’t power on into new group (or individual host wol) the wol works but again only until there are less than 6 members. I am guessing that Multicast filtering is enabled because the thing is that wol worked for the whole group (more than 6) in 1.2 version of fog. Can i somehow troubleshoot the issue inside the fog or do you think this could be network issue.

Server

• FOG Version: 1.4.4
• OS: Cent0S 7.3

Client

• Service Version:
• OS: Win10

Description

I upgraded from 1.2 to 1.4.4. Now wol for single host works normally. Wol for groups doesn’t. What i found out is that if the group has low number of hosts of no more than 6 then it works even for the groups. But if there is more it doesn’t. Then some computers wake up and some don’t.

Can i just ask what exactly do i need to change to fix this. I upgraded from 1.2 to 1.4.4. Now i have the same problem. Wol for single host works. Wol for groups doesn’t. What i found out is that if the group has low number of hosts of no more than 6 then it works even for the groups. But if there is more it doesn’t. Then some compuers wake up and some don’t.

Server: CentOS

This is wierd. All i did was

service FOGScheduler restart

and now it works. Not to say that i restarted the whole server before and that didn’t help and also the status of this service was “running”.

@Tom-Elliott , thank you for the indirect tip.

Server

• FOG Version: 1.2.0
• OS: Centos 7

Description

After moving fog server from Centos 6 to Centos 7 (installing new os and fog and moving images). Everything seems ok other than now I have a problem with WOL when it is scheduled. Manually it works fine. Cronjobs also work under root crontab.

What else am i missing?

@george1421 Thank you for the tip. I copied values from .../ipxe/boot.php?mac=<mac_address_you_just_deployed_to> and now it works.

@Quazz Yes, quite a few things are altered.

I get this error:

If i send the same image over web interface it works.

No this is from FOG Configuration>PXE Boot Menu>Advanced Configuration Options:

:MENU
menu
item --gap -- --Images---
item master10 Windows 10 Image
:master10
kernel bzImage root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns="dnsiphere" web=${fog-ip}/fog/ consoleblank=0 loglevel=4 type=down img=win10master ftp=${fog-ip} imgType=mps osid=7 storage=${fog-ip}:/images capone=1 imgFormat=2
imgfetch init.xz
boot || goto MENU

This setting was in 1.2.0 and it’s also now in 1.3.0 its just that now it doesn’t work.

Server

• FOG Version: 1.3.0 rc13
• OS: centos 6.6

Description

After fog upgrade from 1.2.0 this advanced menu option seems to not be working. How do i adjust:

kernel bzImage root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns="dnsiphere" web=${fog-ip}/fog/ consoleblank=0 loglevel=4 type=down img=win10master ftp=${fog-ip} imgType=mps osid=7 storage=${fog-ip}:/images imgFormat=2
imgfetch init.xz

@george1421 Yes the grub menu that is specified as exit. As with goes into bios i meant that even if i don’t boot to network (no cable), computer wont boot from deployed (Win10 image) hard drive and since it can’t find operating system it goes into bios settings. But that is problem with my image or with bios settings. Maybe the problem is only one partition i tend to merge recovery 500mb partition with the rest. But that is fixable i guess, i am just glad that now after fog upgrade the deployment to NVMe disks works. Also thank you for the tip about KBs updates for Win7.

Thank you for all the information it worked! I upgraded to latest version via “Upgrade to trunk” instructions.

Now when i try to deploy the disk gets recognized, and deployment finishes normally. So that is solved than.

I have two somehow related questions if i can ask them here. After deployment and reboot the system doesn’t boot up. It goes into GRUB menu or if i pull out the network cable it goes into bios. I figured it is because NVMe creates all sorts of partitions compared to just one that i have from syspreped image which is created in virtualbox. Do you have any advice how to recreate new one (virtualbox (how) or should i just do it from physical machine).

Second question is related to quick menu item, i had this line which was working, now after upgrade how do i adjust:

kernel bzImage root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns="dnsiphere" web=${fog-ip}/fog/ consoleblank=0 loglevel=4 type=down img=win10master ftp=${fog-ip} imgType=mps osid=7 storage=${fog-ip}:/images imgFormat=2
imgfetch init.xz

Server

• FOG Version: 1.2
• OS: Centos 6.6

Client

• Service Version:
• OS: Either Win7 or Win10

Description

How do i deploy fog image to ssd disk that is not recognized by fog. The ssd is onboard and it is not listed in bios under storage it is however visible in bios list order as “N1-Samsung SSD 950 PRO 256G”. Also if i try to do classic install with windows dvd it is recognized.

That is it. Thank you so much guys. Such great community makes using fog even more satisfying.

How do i do that?

I thoght i have the latest, you mean fog right. Isn’t there some way to clear deployed snapins from database.

I can’t be the only one with this error can i:
[IMG]http://oi59.tinypic.com/11l1ksh.jpg[/IMG]

Sorry, Fog 1.20. Centos 6.5

I deleted snapin file from /opt/fog/snapins. I deleted this snapin that i was trying to send as well. There is nothing udner active task and under active snapins tasks. But when i try to send different snapins to this machine i get error that snapins are already deployed. There are none to be seen. I can deploy this snapin to other machines that were not in this affected group.

Hello i was about to deploy snapins to group of computers but before i did i deleted snapin file from server. So when i choose deployment ofcorse nothing happend. I manually deleted all snapin deployment from Active Snapin Tasks and Active Tasks.

The problem now is that i cant deploy any more snapins to this machines. I get this red error:
All Snapins task failed to create for [U]R0[/U] with image [U].U[/U]
Snapins Are already deployed to this host.

I am guessing that there are still records somewhere in the mysql, can anybody help me delete those failed snapins so i can send new one.