Topics created by geardog

Any luck clearing up this error? Running into the same thing now setting up a separate storage node location(still local). I get this when trying to deploy an image.

@Tom-Elliott Thank you

Took me a while to circle back to this, but it’s nice to have it working as expected.

@geardog I think I understand what you did. Let me say this with my words. You built a FOG server but did not have the space on the small VM, so you connected via NFS to an external NAS. You mapped the /images over to the remote NFS server wanting to borrow space from that external NAS.

If that is the case, then you can’t do that with NFS. Basically you are trying to reshare a network connected drive. This is akin to taking server A and mounting a directory from server B as the W drive, then trying to share the mapped W: drive to a third computer.

The only way to make the above scenerio to work is via mouting the remote disk as an iscsi LUN on the fog server. map that external iscsi lun over the /images directory. Then install FOG. That will work because the iscsi lun is a block device, and nfs is a file level device.

@sebastian-roth
Wow, so is my only known option for external storage making the NAS behave as a storage node? It has a flaky proprietary OS/GUI that has warning everywhere. “You will brick me if…”

@sebastian-roth So I’m not sure what has changed, as I’ve had to focus on other things, but now it works. I didn’t follow the most recent direction, but I’m booting various boxes via pxe successfully. No idea. …

@geardog Two things from the tutorial I just want to point out:

Make sure its at least version 2.76 by issuing this command at the fog server’s linux command prompt sudo dnsmasq -v. The version needs to be 2.76 or later.

and as George already mentioned here:

Be sure to replace <fog_server_ip> exactly with the IP address of your fog server. Be aware that <fog_server_ip> appears multiple times in the config file.

@geardog said in Resize failure?:

A cold boot with fast-start disabled allowed a good capture.

Just for another option:

Let sysprep power off the computer after its run Run the following command from a command prompt shutdown -s -t 0

Both of those commands will ensure that the system is properly powered off and ready for image capture.

@Sebastian-Roth
Gparted fixed it with the “check” command, running what appeared to be the same commands I entered at terminal.

I’ll try to capture it again after I’m more confident the box is ok.

thanks guys

@Sebastian-Roth
No no, you’ve made clear that it is a lost cause trying to sort this out. If I had a clean capture and deploy on this version showing the system partition shrinking it would be different. Your comments made that clear. Thanks for the help.

@george1421

I consider it resolved. Thanks for chiming in.

@geardog said in No configuration methods succeeded (I210 NIC):

It turned out to be a bios/UEFI setting “option rom launch policies.” New to me. In my defense, this box’s bios is pretty massive and clumsy to navigate through, but works now!

Well that is a new one for me too. You might want to post the model of HP computer this is just in case someone else has the same issue in the future. This issue does sound a bit unique to this hardware.

@geardog Sorry for the long delay. Will be ready fairly soon. Are you still interested, I hope?!

I added it yesterday but also had to put in some major work to fix issues in our kernel build environment… https://github.com/FOGProject/fos/pull/12

@sebastian-roth

I just happen to be harvesting 1TB drives from workstations for server use. The 250GB drives I picked up for $10 each are adequate for the floor computers.

Thank you for the firm point at cause.

@Sebastian-Roth

lspci -nn showed the drive to be in raid mode

using a tutorial on bcdedit via cmd for safemode boot I was able to change the setting without reinstalling windows

now the machine is imaged

resolved and thankyou

coming back to this with a fresh mind and some new info helped

@geardog I thought you might just want to start from scratch, install a fresh clean windows 7 in UEFI mode. But seems like you could even convert form legacy BIOS to UEFI if you are keen: https://social.technet.microsoft.com/wiki/contents/articles/14286.converting-windows-bios-installation-to-uefi.aspx