See this post for more instructions/documentation:
https://forums.fogproject.org/topic/9001/partimage-for-old-images

Where is the MSI located in your setup?

Worked with @theWizard yesterday via remote session.

Found that the snapins were being uploaded to another storage node. That storage node /opt/fog/snapins folder had incorrect permissions on it.

Fixed the permissions and confirmed the working on working-RC-24. I’m solving this thread.

@Quazz
thanks

Worked with @noelpd via chat.

Apache had an issue with ssl that prevented it from restarting, and git had an issue with ssl preventing it from doing a git pull.

I directed him to use svn instead, and that worked. But there was still the issue with Apache, and @noelpd says that uninstalling and reinstalling apache fixed the issue.

I think there is something else going on related to ssl that caused these two issues to begin with.

I agree with you that it works wonderfully well with postdownloadscripts,
Thanks to the scripts provided by the forum community. Thanks to them.

But we must look for a bit before we find the existence of this functionality.

Many people will turn to OPSI because it is better indicated in the documentation and it is native in the application.

http://www.opsi.org/en

I always love Fog because it’s very light.

Thanks to the Fog team

Anybody familiar with code, and/or feel like testing:

Please take a look here:

https://github.com/FOGProject/fogproject/commit/5ead9f7a9dfd822aae06bb99de41769b87988ddb

Criticize and/or test the code that I’ve added to see if it help address the issue please?

@x23piracy said in Problem on HP ProBook 650g2:
Then have you got problem with computer with Realtek RTL8168D/8111D NIC (if you have some)
Thanks for your answer

Just a heads up. I tested upload with working-RC-24 and 1.3.0-RC-13 and am not seeing an issue.

I can only think, possibly, the disk is setup in ‘raid’ through the bios and it’s presenter still display’s /dev/sda to the system. Another potential, I suppose, could be the disk is completely empty? I’m only guessing of course.

The change I put in for maintaining ntfsresize is still working properly from what I can see. So it’s failing, from what I can tell, appropriately. Again, I’ll need more info to more suitably help I think. I mean, this could potentially happen because it’s fragmented and can’t move data around (testing) to find the size that can shrink to.

This post is solved

@mohamedadel No. Fog is an imaging solution. Nearly every imaging solution works the same way. It starts by wiping the disk (or disks), lays the drive out based on the image’s original partition layout, and lays the image on the partitions as laid out.

You can select specific partitions to use, though I haven’t ever done it the support has been added. Though I suspect you’ll have better luck doing them based on using the current Rc’s.

You can also change the image type to single disk - resizable, and then re-capture your image.

@EspenU As I posted before, if you have issues with the 64 bit kernel for some reason, just use the 32 bit kernel for all imaging needs. You can use this kernel universally for both 32 bit and 64 bit systems. There is no technical advantage of the 64 bit over the 32 bit kernel. Just renaming the global 64 bit kernel and inits values to point to the 32 bits stuff should be sufficient for all of your imaging needs.

@Dalton-Childers So this was a problem with the image.

@george1421
Would love to have that script. I am not giving up on this one. Will be at this first thing in the morning. Gotta go home and feed the kids.

Let me know how I can get that script you mentioned. I did check the default.ipxe and it was good to go.

V/R

@Tom-Elliott, @Wayne-Workman

Thanks for your help guys, great stuff. I was able to increase my disk size the way I want it too.

0_1479159136765_upload-ea588445-3e1c-4913-842a-09aebff13f1a

0_1479159145646_upload-2fd09ea2-6d4f-4ca7-b1ab-64e515b86943

@utopia There is some variants in what’s going on for SQL backup. While the version that “automatically” creates a new backup is slightly larger, this is mostly just comments.

I’ve seen some strange things in regards to Ubuntu in the past. The unfortunate part is that not all systems are the same. What you experienced does not mean everybody experiences. The only other thing I can think is ondrej changed how the repo is used relatively recently. Of note, php5-fpm is no longer proper, it’s supposed to be php5.6-fpm as described earlier in the posting. I’ve added this change for the working branch now so hopefully this will no longer be an issue.

I don’t know what php5 items are still lingering, but I’d imagine you could remove them with aptitude just as well?

@x23piracy it isn’t a can I it’s a you should. Php and Apache is always installed regardless of node or server install.

@Scott-Adams It’s a DB-only setting, it’s not anywhere else. So no worries.

@abos_systemax said in FOG - boot to FOS - rcu_sched self-detected stall on CPU:

I assumed that it used bzImage for UEFI because UEFI doesn’t really support x32?

It does. There aren’t a lot of UEFI systems that are 32 bit, but they are out there.

Are you using the boot files that come with fog and are you serving them from the FOG Server? Could these files be obsolete or are you shuffling things around? I only ask because the filename you give in your dhcpd.conf file is not where that file actually is located on a 1.3.0 RC fog server by default.

At any rate, if you’re serving these boot files from a FOG server on 1.3.0 RC, the PXEClient:Arch:00006 filename should instead be: filename "i386-efi/ipxe.efi";

Also, if you wanted, you could simply replace all of your classes in your dhcpd.conf file with these (standard FOG isc-dhcp classes):

class "UEFI-32-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006"; filename "i386-efi/ipxe.efi"; } class "UEFI-32-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002"; filename "i386-efi/ipxe.efi"; } class "UEFI-64-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007"; filename "ipxe.efi"; } class "UEFI-64-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00008"; filename "ipxe.efi"; } class "UEFI-64-3" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00009"; filename "ipxe.efi"; } class "Legacy" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000"; filename "undionly.kkpxe"; } class "SURFACE-Pro-4" { match if substring(option vendor-class-identifier, 0, 32) = "PXEClient:Arch:00007:UNDI:003016"; filename "ipxe7156.efi"; } class "Apple-Intel-Netboot" { match if substring (option vendor-class-identifier, 0, 14) = "AAPLBSDPC/i386"; option dhcp-parameter-request-list 1,3,17,43,60; if (option dhcp-message-type = 8) { option vendor-class-identifier "AAPLBSDPC"; if (substring(option vendor-encapsulated-options, 0, 3) = 01:01:01) { # BSDP List option vendor-encapsulated-options 01:01:01:04:02:80:00:07:04:81:00:05:2a:09:0D:81:00:05:2a:08:69:50:58:45:2d:46:4f:47; } elsif (substring(option vendor-encapsulated-options, 0, 3) = 01:01:02) { # BSDP Select option vendor-encapsulated-options 01:01:02:08:04:81:00:05:2a:82:0a:4e:65:74:42:6f:6f:74:30:30:31; filename "ipxe.efi"; next-server x.x.x.x; } }