I think it is possible.

Try to follow my logic:
You make an image of a hard drive and it creates files for each partition. (That’s easy)
Once done, you have a directory and files like this.
/images/IMAGENAME/HOSTNAME/d1.mbr – Master boot record
/images/IMAGENAME/HOSTNAME/d1p1.img – C:\ Drive
/images/IMAGENAME/HOSTNAME/d1p2.img – D:\ Drive

As the above file structure shows you [B]Disk 1 Partition 1[/B] and [B]Disk 1 Partition 2.[/B]

So, if you only wish to restore the C:\ drive and not the d:\ drive, simply remove or rename the file for that partition, in this case it would be [B]d1p2.img[/B].

Now, this does not solve your issue 100% (because it will still upload/backup all partitions) ; BUT will
allow you some flexibility when downloading/restoring images.

[B]This is only theory and has not been tested/ proven by me.[/B] (but I think others have.)

I can test this theory when I find time… it could prove useful.

When you type in the username credentials in FOG type domainname\username instead of just username. This only applies to windows 7 images though.

Dear Friend,
If you have problem related reasons just like server crashing, system software malfunction, hardware failure and virus infection can easily cause corruption in SQL Server database. When SQL database corrupts, vital data get lost and important business work stops. To handle such situation, database needs to be recovered by some special methods as manual recovery is not possible in severe database corruption issues. There are several third party SQL recovery tools available that can easily repair SQL database and retrieve the data.
one tool may be [B]Kernel SQL Sever Recovery Software[/B]
for more you can visit here…[SIZE=2][FONT=Arial][url]http://www.restoresqldatabase.org/[/url][/FONT][/SIZE]

You can use MySQL Workbench and cancel the task under “scheduledTasks.”

I submitted a bug sometime at the end of last year. It will be fixed in version 0.33.

I think I need help with the permissions issue with regards to fog trying to mount my Windows NFS share, can anyone assist?

Also, the upload goes to /images/dev/[mac addr] until the image is completely uploaded and moved to it’s final home at the end of the imaging processes. The chances of the upload process leaving you imageless is small, but the chance your new image is worthless due to some configuration issue, is medium.

If you have a large number of devices, you can create a new image definition and upload it just to make sure it works, then run a simple SQL statement to point all devices that used the old image ID to the new image ID.

[quote=“chad-bisd, post: 3409, member: 18”]I’m not sure what partitions are present in your setup, but you might try changing the image type to Multiple Partitions - Single Disk.[/quote]

Not sure what happened, but it blew out the partition on the terminal. Rebuild time. Oh well. Thanks for the tip and I will try that next time it’s ready to be pushed up.

I prefer 10.04 LTS so I’ll have updates to the system for a while. A lot of stuff has been done with Fog on Ubuntu 10.04 LTS, so the knowledge base is larger than the new versions. If you wave to be a pioneer, go with the newer ones, but if you need it to work and have lots of resources for problems, stick with 10.04 LTS.

[quote=“Matthias, post: 3326, member: 815”]Hi,

I need some help inserting drivers into the kernel in order to be able to image some of our computer models.

For example, we have Acer S461 models with a ATI Radeon video card. When I remove the card everything works. but with the card I get the snow screen.

I tried compiling a kernel according to the instructions on [url]http://fogproject.org/forum/threads/compiling-a-custom-kernel-for-acer-iconia-tab-copied-from-old-forums.216/[/url]

In xconfig I selected the ATI Radeon drivers. The resulting bzImage then does have a proper video display, but now I don’t have network and the hard drive is not recognized either.

Also I noticed that my custom bzImage is only 5 MB in size while the original one is 12 MB.

So my questions are:

why is my custom kernel so much smaller?

how can I create a kernel that is exactly the same as the original plus the additional drivers?

Thank you in advance,

Matthias[/quote]

I did some research, here are the answers:

my custom custom kernel was smaller because I used the kitchensink config file (fog_0.32/kernel/kitchensink.config)

with the fog_0.32/kernel/core.config file the resulting bzImage was 12 MB.

In xconfig I did the following changes:
-deselect “Device Drivers - Graphics Support - AGPGART (AGP Support)”
-select “Device Drivers - Graphics Support - Direct Rendering Manage - ATI Radeon”.
-deselect the option under ATI Radeon for: “Enable modesetting on radeon by default - New Driver”.

That kernel now works with our Radeon cards.

Regards,

Matthias

Gotcha, will try all this out once I get some data gathered 🙂 Thanks a bunch.