I am astounded that I had this exact problem, and found this answer six months later.

I successfully imaged the previous XP image tho. On the same test PC.

p.s. I did notice via gui of the fog server that the XP image in question in the image folder is now 98gb instead of 35 that it should be.

Based on the results, my guess is somebody already had this same type of issue but disabled it with:[code]setenforce 0[/code] on the server, which is why it was working. On the next reboot, because it wasn’t disabled before, it just reset to enforcing.

i have hp system with Win7 and three partitions i can do upload the image and it does with all partition but one parttition d1p3.img has size of 340 Kb actually its is 30gb partition with data of 26GB. i can restore the image but while restoring the parttition d1p3 it does not locate image file and ask for full path.

[url]http://fogproject.org/wiki/index.php?title=Adding_Storage_to_a_FOG_Server[/url]

[media=youtube]69gJvHjTKNQ[/media]

Yeah that works too lol 🙂

I didn’t have access to my WDS server, and I am the only one adopting FOG in my corporation, the rest wants to spend all their time dicking with that WDS server, FOG is easier for me to use. So long story short, I wasn’t allowed to just disable the service 🙂

thanks guv

A couple of ideas found on Cisco forums, [url]https://supportforums.cisco.com/thread/2033218[/url]:

[SIZE=12px][FONT=Arial][COLOR=#333333]Do you have a Layer 3 interface (interface vlan 73) on the 3750? Please try[/COLOR][/FONT][/SIZE]
[FONT=Arial][COLOR=#333333][SIZE=12px]the following on the leaf switch:[/SIZE][/COLOR][/FONT]
[FONT=Arial][COLOR=#333333][SIZE=12px] [/SIZE][/COLOR][/FONT]
[FONT=Arial][COLOR=#333333][SIZE=12px]ip routing[/SIZE][/COLOR][/FONT]
[FONT=Arial][COLOR=#333333][SIZE=12px] [/SIZE][/COLOR][/FONT]
[FONT=Arial][COLOR=#333333][SIZE=12px]interface vlan 73[/SIZE][/COLOR][/FONT]
[FONT=Arial][COLOR=#333333][SIZE=12px]ip helper-address[/SIZE][/COLOR][/FONT]
[FONT=Arial][COLOR=#333333][SIZE=12px]exit[/SIZE][/COLOR][/FONT]
[FONT=Arial][COLOR=#333333][SIZE=12px] [/SIZE][/COLOR][/FONT]
[FONT=Arial][COLOR=#333333][SIZE=12px]service dhcp[/SIZE][/COLOR][/FONT]
[FONT=Arial][COLOR=#333333][SIZE=12px] [/SIZE][/COLOR][/FONT]
[FONT=Arial][COLOR=#333333][SIZE=12px]2. try to use encapsulation on both ports[/SIZE][/COLOR][/FONT]
[FONT=Arial][COLOR=#333333][SIZE=12px] [/SIZE][/COLOR][/FONT]
[FONT=Arial][COLOR=#333333][SIZE=12px]switchport trunk encapsulation dot1q[/SIZE][/COLOR][/FONT]

i guess it won’t work well

[url]http://www.facebook.com/m2tsconverter[/url]

[media=youtube]Fdoo7yfvKK4[/media]

That’s some of the fun with linux. Getting to fix things on your own.

Learning the command line can be troublesome at first, but once you start to understand, it’s so much fun.

I’m a huge fan of all the linux’s, but debian based forms are not as easy for me to use. Maybe it’s because when I started with them, it was all the early forms of RH before they went enterprise.

I’m with Tom on this one, sounds like Apache server isn’t configured for the bond0 interface.

Sorry I wasn’t much help as I really don’t use ubuntu.

Awesome, thanks!

There is no means of doing that that I’m aware of. Active Directory doesn’t have the capabilities to just rename a system.

[quote=“Axel, post: 12528, member: 686”]So I spent 10+ hours today trying to get this to work. I’ve followed multiple tutorials on using an external NFS share and my results are not good. After I configure the NFS share in FOG the web GUI says unable to connect on the front page where usually the space free/used is displayed. I’ve created the NFS share, remade /images mounted my NFS share in FOG on /images, created the .mntcheck and then the /dev folder with .mntcheck inside it. I’ve made sure to chmod -R fog:root /images. When uploading an image once the process gets to send method-nfs I get an error of mount: 192.168.62.125:mnt/nfsdata/dev/ failed, reason given by server : Permission denied
mount: mounting 192.168.62.125:/mnt/nfsdata/dev/ on /images failed bad file descriptor. I’ve even tried following posts on here where people had similar issues and i’ve had no luck. The fog server is a vm running in Proxmox with bridged networking. Any ideas?[/quote]

hey Axel

not sure if you resolved your issue, post is too long… didn’t read all of it…

however, I have noticed two things that may be causing your issue…

the first… you used chmod -R fog:root /images… when it should be chown -R fog:root /images (perhaps you meant to type that…)
the second, in your screen shots for the storage node section, the password field should resemble the password in plain text, not the encrypted type… try changing to your normal password, save and try that…

I always issue (right or wrong) the following commands on the /images folder…
chmod -R 777 /images
chown -R fog:root /images

but that’s just me…

Good, glad to be of help. I’ve implemented this as a feature into FOG 0.33b as well.

In FOG 0.32 it’s call is MYSQL_DATABASE where in FOG 0.33 it’s called DATABASE_NAME.

That’s normal.