Asus EEE PC Imaging Errors

[EAHarvey]

Hi guys and gals. I am new to the group and very glad to be here. I am enjoying FOG and what it has to offer. We use it here at work exclusively for imaging.

The issue that I am having is whether I do a manual client add for either Full host add through the menu, the image will not seem to push down. So basically it goes through it’s DHCP and PXE boot, but when it gets to the actual image part it starts normally but before it actually gets to PARTCLONE it gives an database updated message, reboots and the TASK is gone. I can reassign the Task and it still does the same thing. Any ideas? Thanks so much in advance for all your help. I have updated to the latest Kernel.

[Tom Elliott]

First thing, the image that you’re trying to push down to this system’s disk information is the same size (exactly) or larger than the system that was used to create the image?

[Wayne Workman]

@Tom-Elliott said:

First thing, the image that you’re trying to push down to this system’s disk information is the same size (exactly) or larger than the system that was used to create the image?

In other words, is the HDD you’re deploying to at least as big as the HDD the image came from?

This issue pops up a lot in the forums. If the destination HDD is smaller than the source, use the “resizable” image type and it should work.

[EAHarvey]

Tom, thanks so much for fast reply. I think i may have the issue resolved. I think the Drive doen not have a valid partition table on it. I am about to fix that and go from there.

That brings up a good question thoughj. I have Hardrives that have multiple partitions on a single disk. I have been choosing this type of upload. Would the single disk (re sizable) work for this. That way i can have the flexibility of different drive sizes?

Again Thanks so much for all you do,

[Wayne Workman]

@EAHarvey Yes, multiple partitions can be handled by the “Single disk - resizeable” type.

The only reason there is to NOT use resizeable image types is if you are taking an image from a file system type that isn’t supported by fog’s resize feature.

This means file-systems other than EXTFS or NTFS.

I used to not use resizeable - then that one computer came along that had the drive replaced previously and I was racking my brain about why it wasn’t working… it was a smaller drive. Now I use resizeable for every single image I have.

[EAHarvey]

Ok awesome sounds good. I am testing that theory now. I am trying to upload the same image i just downloaded. The image works fine. I am getting an error when it goes through it’s checks. It just reboots and removes the task. Testing now.

Is there a way to put a pause in it so that i can see the errors before it reboots?

[Junkhacker]

@EAHarvey said:

Is there a way to put a pause in it so that i can see the errors before it reboots?

before i can answer that, i need to know what version of fog are you running

[EAHarvey]

Version \1.2.0

[Wayne Workman]

@EAHarvey said:

Version \1.2.0

When you choose to upload, on the confirmation page - choose “Debug” instead of instant.

This will prompt you to hit enter at every step of the upload process to continue.

[EAHarvey]

Sweet. I’m testing now to see what’s up. You guys are all Amazing BTW!! Thank you so much.

[EAHarvey]

@Wayne-Workman

These are my options.

[EAHarvey]

I see something about setting up a debug task. I’m going to try this to test also.

[Wayne Workman]

@EAHarvey I didn’t know that 1.2.0 didn’t have debug tasks… I apologize.

Can you consider upgrading to FOG Trunk, please? You might even find that your problem goes away.

[EAHarvey]

@Wayne-Workman

I guess I’m not familiar with trunk. Different version than 1.2.0/? Where do i download it?

Forgive me for not knowing this, i was unaware of another version.

[Wayne Workman]

@EAHarvey https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk

I recommend the SVN method. You should fully update your system before doing this, and backup your data beforehand also. There are steps in the article at the bottom for backing up your data.

[EAHarvey]

Ahh ok, so this is like the currently developing version of FOG. More like a beta.

[Wayne Workman]

@EAHarvey Yup. But, it’s referred to in historical threads and sites abroad as “FOG Trunk”, so I call it that in order to keep those historical references accurate. But yeah, it’s beta. It’s all I use at work and at home. It’s MOST safely used with virtualization, but three of my organization’s fog servers are not virtualized and they are doing fine - we just don’t update those as often.

[Junkhacker]

@Wayne-Workman beta implies that it has reached a point where it is being tested to be considered a release candidate, trunk is simply the development trunk. the central repo of all changes that have been brought into the mainline. while we try to keep the development trunk stable, it is not a finalized form and hasn’t necessarily been tested much at all, depending on how much has been committed to it on a given day.
I prefer to recommend upgrades to specific versions of the trunk if I can. an upgrade from 1.2.0 to svn revision 3652 should be pretty painless and has most of the new features that most users would notice.

[EAHarvey]

Ok awesome. I have it installed and running. Going to start some testing. I’ll let you guys know. Thanks so much for the great help.

[EAHarvey]

lol now that i have updated my tftp sever is timing out,… Oh my.