I cant capture Big image 300GB

[Quazz]

@BASURILLABAS2 I’m guessing you’ve already tried capturing it again?

It could be the hard drive running into issues as well.

I recommend updating FOG to the latest and trying again (latest is RC11)

[BASURILLABAS2]

I have tried to capture several times and its fail.

With Clonezilla works well.

I’ll try updating FOG.

[Tom Elliott]

@BASURILLABAS2 Clonezilla doesn’t use resizable, maybe if you change the partition type so it’s of the “non-resizable” type?

[Tom Elliott]

I also have to ask,

Why such a large image? Does this same setup work with fog on say a 20GB Image? Or 30GB?

I highly doubt it’s got anything to do with the size of the image directly, but 300GB seems a bit large for an image.

[BASURILLABAS2]

@Tom-Elliott

I have a lot of teaching with many programs and large size and every year grows the image

[Quazz]

@BASURILLABAS2 If possible deploying the programs using snapins might be more desirable for your situation, just something you might want to consider for the future.

[Wayne Workman]

How much free space is left on the disk, before trying to capture?

[BASURILLABAS2]

@Tom-Elliott

I defrag the image with ‘Auslogics Disk Defrag’ with the option ‘Defrag & Optimize’ to leave the image no blank spaces and so work with and without resizable option.

[sudburr]

I can relate to working with heavy images. I’ve captured some as large as 482GiB

Looking at your picture, it appears that you created your image on a physical machine. Did you zero the HDD and verify it error free before you installed your OS?

[Quazz]

@BASURILLABAS2 https://wiki.fogproject.org/wiki/index.php?title=Error:_extended_record_needed

It’s not the same, but potentially related error.

Make sure the Hard Drive is actually in good working order though. Just because Windows is working properly, doesn’t mean the HDD is.

[BASURILLABAS2]

@BASURILLABAS2
Currently it works well with the option 'Defrag & Optimize’

[Quazz]

@BASURILLABAS2 So it’s working now then?

[BASURILLABAS2]

@Quazz
yes now it´s working

[george1421]

@BASURILLABAS2 So do we have a root cause yet of this issue? Disk (organization, failure, structure), attempting to resize a really big image?? I’m finding this a unique issue that will probably come up again.

[Tom Elliott]

@george1421 The disk defrag was not fully proper. It couldn’t move portions to the proper areas. Once done a few times (just guessing) I think it started to work for him because the bits of “freespace” were then “properly cleared”