Posts made by Jarli

@ITSolutions said in Adding larger partition:

Edit: Sorry but I am not a linux “expert” and not great with fedora in general, usually on debian/ubuntu distros. But I think I see what the issues seem to be.

So I am assuming you have /run/media/root/fedora-expanded/images and /run/media/root/fedora-expanded/images/dev?

Have you tried this article https://wiki.fogproject.org/wiki/index.php?title=Adding_Storage_to_a_FOG_Server?

If you want all of your images moved to this new spot and not have the original location it maybe best to set it up like this and make sure the mount points are /images and /images/dev otherwise you need to make many more changes to make everything work. It sounds like just changing your mount point would be easiest and best now that everything is moved to your new drive.

That did the trick.

Thanks.

@ITSolutions I’ll give this a try and let you know thanks.

Fedora, fog version 3748,

Yep everything worked before but I couldn’t update my image as the original partition is full.

The partition is under /dev/xvdb and its mounted at /run/media/root/fedora-expanded

Hi All,

So I’ve just added a second virtual disk to my fog system and I’m having some issues getting my systems to actually begin the imaging process.

DHCHP starts and runs fine, I’ve copies .mntcheck to /images and /images/dev.

I’ve copied the existing images over into this new partition of this VM under /images.

The error message I am getting is

Fatal Error: Failed to mount NFS Volume. 

Following this obviously doesn’t work otherwise I wouldn’t be posting.

Any help is much appreciated.

Thank you @Tom-Elliott

So I have my fog server on a private LAN for imaging, and while the active computers in the Fog system was useful before hand, and the scanning / pinging, it is now a hindrance and only slows the performance of the web console.

Is there an easy way to disable this function, or is it required?

Got it fixed.

The Storage Management password was goof’d.

Corrected it to match, and it completed the TFTP upload.

@Tom-Elliott Perfect thanks, so I’ll sysprep this and test the upload.

@Tom-Elliott Sorry last question,

in the TFTP_FTP_Password field in the configuration website, does the password have to be the encrypted form or will plain text work?

Well the drive has enough space, but after the upload completes is where I’m getting this issue.

So after a fresh cup of coffee, and thinking about it “normally” I just put the LiveCD into the Xen VM, booted from the LiveCD and extended the partition…

Now to test the upload and confirm if I have any other issues.

I do now have 30GB free space.

Thanks for the help guys

Well i temporarily configured internet access onto this VM, and downloaded gparted.

the full 80GB partition is visible within, but it’s not usable…

hrm…

@Wayne-Workman Any guidance on how I can expand the partition?

This is a VM running within Xen.

@Wayne-Workman said:

@Jarli is the server out of space? df -h

Doh… that seems like it.

@george1421 said:

Can you give us a better idea of your environment?

1. What version of fog are you using? (i.e. 1.2.0 stable, or a trunk version, if trunk then what is the number in the cloud on the login page.
2. What host OS are you using.

Are you seeing the ipxe FOG menu at all? I’m a bit confused since you mentioned invalid password and tftp together. Tftp doesn’t use passwords, thats why its trivial. If you are not getting the ipxe boot menu then what is the PXE error message?

We are able to get to the PXEi boot menu, and can deploy an image, but aren’t able to upload an image into fog.

Not sure what changed, as my colleague nor I have made any changes to the system in a very long time.

Our fog server (fedora) is on a closed network, and handling DHCP for this network.

Fog Version 3748

Kernal Versionz

bzImage Version: 4.1.0 and bzImage32 4.1.0

So as the topic describes, we’re having an issue when attempting to upload an image into fog.

The connection is failing at TFTP.

I’ve confirmed that I can TFTP from my windows desktop to Fog without issue, and download a file.

Any help would be appreciated.

Thanks guys.

This can’t be a 100MB vNIC issue, he receives 4-5GB write speeds from the Ubuntu (fog) server to his laptops. With the current setup.

Update,

Appears to be the cable, yet we’ve been using this same cable to image all of our other machines. And the device is still capable of pulling DHCP using this ethernet cord. . .

Nothing like a bad cable

We’ve been receiving this error several times while attempting to image a few machines. The client machine will pull DHCP fine, and begin the iPXE boot process, but fails with the error below and never makes it to the boot menu. Other times, a machine will boot to the fog menu and image without issue.

[url]http://ipxe.org/err/040ee1[/url]

Has anyone else experienced this, and know what the issue might be.

I’m leaning towards either a bad port on the switch, or the entire switch its self is having issues.