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

I don’t know what you mean.

1.2.0 should have the partition selection items. If you know how the partitions show up in linux, you should be able to specify which one to image.

If that’s not the case, I know for a fact it’s in SVN.

It’s possible it’s a network issue. Meaning it could be the kernel doesn’t have the driver for your nic. (Can you provide NIC informatoin of the trouble system?)

The error as I zoom in, says the network is unreachable, which would explain not mounting the file as well.

Okay,

So there is no issue with Capone, or the menu generation.

Rather, it’s the method at which you’re creating the DMI/Shutdown fields with the image association fields.

These are two separate forms.

What this means:

When you are setting up capone, it gives one page full of all the information you need.

The DMI and shutdown fields are their own form because these are global values.

The Image association field is it’s own form to separate between the two.

Please, set your DMI/Shutdown fields and use it’s corresponding button to update.

Then set your image associations (or leave them if you set them already.)

Then boot a host, if the menu isn’t set, it will create the menu item.

After the item is created, you can specify it as default.

That will be this then! :

[COLOR=#007700][FONT=monospace]if ([/FONT][/COLOR][COLOR=#0000bb][FONT=monospace]substr[/FONT][/COLOR][COLOR=#007700]FONT=monospace==[/FONT][/COLOR][COLOR=#dd0000][FONT=monospace]“00:15:5d”[/FONT][/COLOR][COLOR=#007700][FONT=monospace]){
print [/FONT][/COLOR][COLOR=#dd0000][FONT=monospace]“# Hyper-V MAC address detected - no console background\n”[/FONT][/COLOR][COLOR=#007700][FONT=monospace];
} else {
print [/FONT][/COLOR][COLOR=#dd0000][FONT=monospace]“console --picture [/FONT][/COLOR][COLOR=#0000bb][FONT=monospace]$this[/FONT][/COLOR][COLOR=#007700][FONT=monospace]->[/FONT][/COLOR][COLOR=#0000bb][FONT=monospace]booturl[/FONT][/COLOR][COLOR=#dd0000][FONT=monospace]/ipxe/bg.png --left 100 --right 80\n”[/FONT][/COLOR][COLOR=#007700][FONT=monospace];
}[/FONT][/COLOR]

[COLOR=#007700][FONT=monospace]Will give that shot! :)[/FONT][/COLOR]

sanboot isn’t used for loading iso’s typically. i’ve always had the best luck with [CODE]chain memdisk iso raw[/CODE]
sorry if this isn’t addressing your question, i’m having a hard time understanding what you meant

Can you post the install log?

/var/log/foginstall.log

it never stops blinking, I have to power it down.

what are the details of the computer you’re having problems with? brand/model
the first step i would take would be to update the undionly.kpxe file to the latest version from here
[url]http://sourceforge.net/p/freeghost/code/HEAD/tree/trunk/packages/tftp/[/url]
if that doesn’t work, try using undionly.kkpxe instead
there are plenty of threads about troubleshooting ipxe error 0x040ee119

you could edit the “imageID” field of the “images” table in the “fog” database, but if it’s purely for aesthetics i recommend against it.
that ID is used for internal record keeping and task management in fog