No idea ?

[quote=“Julianh, post: 39299, member: 24986”]I had this, drove me nuts. Believe it or not the solution was to do a “fast wipe” of the disk before imaging down.

Hope it helps[/quote]
I’ll be avoiding Black Friday crazies and tossing together a test fog server at home instead. I’ll give this a shot and post my results. DarkEnergy, i can’t even image the same system I did an upload from

We found the Problem, see here:

[url]http://fogproject.org/forum/threads/clone-upload-fails-with-invalid-partition-data-error.11594/[/url]

Delayed start tried, but no joy there either I’m afraid.
I’m going to go through the guide and start fresh with a new, simple image, despite it working fine for the last few years. Just to make sure nothing on the machine could be interferring with anything.
Failing that I might have to try a completely fresh install on a new server hard drive. Something somewhere is stopping the machines from talking to each other since updating.

Thanks

James

I’d actually tried Yumi but must have only used the Syslinux ISO access. It worked with the GRUB access. Thanks.

Probably not worth it to use PXE if I can’t use the router’s DHCP.

Thanks.

facepalm

Didn’t read any further than “browser” before realizing I have been a fool 🙂

Many thanks for the reply, been mad busy and missed the obvious, you know what its like when a fresh pair of eyes saves you from throwing a mouse across the room at an innocent, you have potentially saved someone a trip to the emergency room 😄

I reinstall the SVN version and now fog server work properly.
Thank you Tom, great job¡¡
Bye.

ok, the problem is solved. My partner previously had modified the boot partion so after your advise, I have reinstalled the operating system of the laptop from the begining in order to rebuild a new image and finally it has worked properly.
Otherwise, I’m really greatfull for your support. Thanks so much. GOOD JOB !

New job, new OS, new imaging server = big headache. This rookie went around and around with this error today. Tried resetting the passwords repeatedly. Sounds like I need to delete the FOG user I set up on the Ubuntu box and start learning about this 777 stuff … in a hurry.

I ran into this issues for a couple of hours. I actually found that SELinux turned back on since it wasn’t disabled in the start up config. For anyone that has more issues with the error above try the command sestatus if enforcing follow this page [url]http://www.crypt.gen.nz/selinux/disable_selinux.html[/url]

You’d have to build a new kernel for this support.

The reasoning:

I removed all USB HDD potentials, as what was happening more often than not was FOG was imaging the external drives when that was NOT the intended drive. Because of this, I removed USB HDD’s from the kernel.

No luck with fixparts. Sounds like you’re leaning towards this being a problem with the partition not matching what is in the image. Would it be worthwhile to create a new image with a smaller partition, and leave part of the hd unallocated?

How do I check that the storage node can properly access the database server? As I stated in the OP that I can create images that are stored on the Node and deploy those images without a problem. The Web GUI can also read the Hardware info from the Node. [ATTACH=full]1516[/ATTACH]

[url=“/_imported_xf_attachments/1/1516_Untitled.jpg?:”]Untitled.jpg[/url]

I don’t know.

There’s lots of documentation on the internet on how to do it, but I’ve never tried any of the steps.

Maybe start there? Specifically: dhcp user class ipxe?

Glad to help you find it.

Hi Tom,

Thanks for the update I’d forgotten that init_32 would also need to be amended.

One thing though, on my box (Ubuntu 12.04 LTS alternate + added desktop + Webmin) there is no /var/www/fog/html folder, hence i’d gone to /var/www/fog/service/ipxe

My original posting worked, at least for init.xz anyway. The test laptop was happily sitting there waiting for a keypress when I woke up this morning. Perhaps the filepath has changed between the latest and stable releases of Fog ? Anyway I’m a happy bunny.

Would it be possible to add this change to the next version please ? It doesn’t make any sense for badblocks to write test results to the screen and then allow a reboot before you’ve had a chance to see them does it ?

Kind Regards,
Robin

Now its working!! Thanks a lot!
:):)

other thing to consider you may need IP-helpers configured if it’s layer 3