Posts made by G0dzilla

Few possible ideas;

Was the image uploaded from a VM or a physical computer ?
Maybe try changing SATA mode to IDE/Compatibility from AHCI if that is available, or - not already set in BIOS.

chkdsk /f [or /R]
sfc /scannow

The drives should have the same partition table etc after imaging…

Perhaps try a fdisk -l under debug mode or in a linux distro to check.

Verify you have the same partitions on the correct drives.

Might be worth running a chkdsk on both drives before imaging. [this may rule out filesystem corruption/drive problems]

Can you boot the 2nd machine into safe mode? [this may help pinpoint driver/software issue]

Also, so we understand correctly. If you put this image on another computer of the same model/hardware, it works correctly?
Different model/different hardware does not work ?

There was a patch written for this in previous versions.
I think it would be useful to have in current/future versions as well.

Tom has set the status to closed on 2014-05-26;
Is there any plans or thoughts for updating this patch for use?
[url]http://sourceforge.net/p/freeghost/patches/53/[/url]

I think it would be useful if the disk surface test task could log the results to the host that is registered to.

I think it would be nifty if FOG included DDrescue as an imaging option, or use DDRescue instead of DD for raw images.

Whilst this wouldn’t really benefit deployment scenarios at all which FOG is targeted for, it could still be quite useful and convenient [IMO] if you need to image a failing drive for what ever reason.

[quote=“buckITall, post: 25106, member: 101”]I am very much interested in this,
Is there a way to create subfolders in the pxe menu?
Such as:

System100-
W7x86
W7x64
W8x86
System 101-
Vista86x
Vista64x
W8.1x86[/quote]

[url]http://www.fogproject.org/wiki/index.php/Edit_PXE_menu_to_create_sub_menus[/url]

Do any other machines PXE boot OK?
Or have you just setup FOG for the first time and this is the first attempt at network booting from it?

[QUOTE]I performed an image upload of the single disk, the first attempt I tried single resizable and fog failed to image the drive[/QUOTE]

Any more information?
What version of FOG?
Did it attempt to upload as raw filesystem/fat32/ntfs etc?
How many partitions did the drive have and what filesystems did they have?

[QUOTE]Did a console recovery chkdis /p and it found all kinds of unhappy stuff and still not booting so I am going to try a recovery install.[/QUOTE]

The drive could be faulty.
Otherwise “/fixboot C:” & “/fixmbr C:” from the recovery console might make it boot again.

[QUOTE]When I attempt to deploy fog gets to a line stating it could not mount sr0 and was mounting it read only[/QUOTE]
I believe this could be your CD drive.

What is your intended use for FOG? are you using it to try and backup, or trying to create images for deployment?
It is much more convenient to create images in VMware/Virtualbox and use the snapshot feature in case things go wrong. Will save a lot of time.

[url]https://www.coolacid.net/articles/39-latest/134-restore-a-partimage-backup-to-loopback[/url]

At my workplace we have a similar setup.

I have been using FOG instead and it has been much nicer.

It only takes an extra minute to register a host - and the imaging through fog has been at least twice the speed of ghost in my testing. The time saved through the imaging process easily justifies the need to register a computer once in the FOG database.

This is just from my experience.
I don’t plan on using ghost again.