Wrong Image Size indicated in the image manager.

[george1421]

@processor said in Wrong Image Size indicated in the image manager.:

I can tell you there is no sda2, only sda1

There is only one partition on that disk? This is a windows computer right? If there is no sda2 then just run the other commands, that will give us a better picture of your disk layout.

[processor]

@george1421

I did what you asked these are the screenshots :

So as you see one partition, and it content is visible.

I did further tests :

-HD Base mode, with 1 reserved partition and an OS partition : Resizing OK
-HD Base mode, with 1 Partition only for the OS : Resizing KO, partition detected as reserver even if it’s not
-HD Dynamic mode, with 1 partition or more : Resizing OK, but with this message : ldm_parse_tocblock() cannot find tocblock, I don’t yet know if deploy work with the created image did not had time to test yet and it seems the capture is longer.

Any idea why FOG detected a solo win10 partition on a base disk as reserved?

[george1421]

@processor While I see it, I don’t believe it. I’ve never seen a windows install with just a single partition (after Windows NT). Is there another disk in the system because the boot partition is missing or this is a strange MBR disk.
The fact that there is only one partition may be confusing FOG’s logic because the first partition of a windows disk is always fixed in size. How did you create this disk layout?

[processor]

@george1421
I don’t know, it’s been done by a colleague of mine. But as far as I know users here install base OS with genuine Microsoft sources, clicking next, next . But I think we have the same behavior with our 2K16 base capture.

Is there any possibility to avoid the detection as reserved partition by command line in debug mode for instance? Or do we have to rebuild the bases and the full images we’ve done with this unconventional disk organization?

Bad news for us converting base disk to dynamic make the capture resizable , but can’t deploy it on another machine.

[Junkhacker]

@george1421 said in Wrong Image Size indicated in the image manager.:

I’ve never seen a windows install with just a single partition (after Windows NT)

…but that was the standard for xp and 2000 pro. it was also easy to configure with windows 7, even though it wasn’t the default.

[george1421]

@Junkhacker Right, but windows 10 should never do that. I’m not even sure I can make it create just one big partition. I know bitlocker as well as uefi system’s can’t boot from that disk structure.

My intuition is telling me to start over and do it right because this structure will bite you in the backside in the future like with a feature upgrade.

[processor]

@george1421
May be because we use Legacy boot and not UEFI?

[Junkhacker]

@george1421 uefi systems definitely couldn’t use it, but i don’t see any reason it wouldn’t be possible with windows 10. sure wouldn’t recommend it though. it just really threw me off when you said you hadn’t seen single partition setups since NT

[Junkhacker]

@processor even with legacy boot, this is far from the default setup

[george1421]

@Junkhacker said in Wrong Image Size indicated in the image manager.:

single partition setups since NT

FWIW: I believe NT and Win2000 use the same kernel. But I could be wrong there too, that was almost 20 years ago you know.

[processor]

OK, you are certainly both right. But this not help. As I did not made the bases I don’t know what happened.
Now :

• is there any way for this image to be compliant with FOG? (any way to recreate the system partition without breaking everything)

• list item there any way make FOG not detect them as reserved?

• list item Or the only option is to rebuild the source images?

By the way many thanks for the interest you put in this subject

[george1421]

@processor said in Wrong Image Size indicated in the image manager.:

list item there any way make FOG not detect them as reserved?

Lets start by removing this one from the list. The word “reserved” is a special word. If you look at the drive with windows running in the computer management applet. Does that partition say “Reserved”. If it label say OS or something else then we can remove the “reserved” line from your issue. Then its down to FOG treating the first partition as unsizable.

is there any way for this image to be compliant with FOG?

Its just not the matter of making it compliant with FOG, it’s not Microsoft best practices compliant. We probably can make fog do what we want, but you will have issues in the future with Microsoft upgrades. So the question is do you make it right now or latter. It really isn’t a fog question.

@Developers if its the first partition thing, can we just mark the image as resizable in the image config files?

[Junkhacker]

@george1421 said in Wrong Image Size indicated in the image manager.:

@Developers if its the first partition thing, can we just mark the image as resizable in the image config files?

yeah, that should work.

[processor]

Great, how to do it? Is it something that I can do or is it something that can only be done by the devs?

[george1421]

@processor Its something you can do, but I don’t remember the exact file to change. Its a simple change, but if you make the wrong one its not good. That is why I sent a note to the devs.

[processor]

@george1421 ok looking forward the info.

[Junkhacker]

ok, in the directory for that image, there should be a file named “d1.fixed_size_partitions”. the contents of that file would be “:1” telling it that partition one should not be resized. delete that line.

[Sebastian Roth]

@george1421 We skip some of the checks for single partition setups. See here for example: https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/bin/fog.upload#L108

@processor Beside what I posted about the mentioned d1.fixed_size_partitions will still be created on upload/capture and seems like we don’t skip the tests for single partition setups on deploy. Therefore it won’t do the resizing on deploy for you. Quick fix as suggested by @Junkhacker, delete that file from your /images/… directory and it should expand.

Many thanks for George who kept asking the right questions to nail this down. I’ll see if it makes sense to add the check skipping for single partition setups on deployment as well.

[processor]

@Sebastian-Roth

Hi, unfortunatelly, it did not worked, still saying a 500GB hd is too small whereas there is only 80GB of data. I try to remove :1 or to delete d1.fixed_size_partitions and result is the same. May be there is some info info stored in d1.mbr or img that can’t be changed.

When I get the error message regarding the size, there is an info inside telling that I can use -C parameter to avoid size checkin. I guess this is a partclone message. Do you know if it’s possible to apply this parameter?

[edit]

In debug mode I ran

partclone.ntfs -r -C -s /images/testimage/d1p1.img -o /dev/sda1

and it keeps telling me I have not enough space

[Sebastian Roth]

@processor said in Wrong Image Size indicated in the image manager.:

still saying a 500GB hd is too small whereas there is only 80GB of data

Maybe I have missed that in the earlier discussion. Has it always been this exact error?? Can you please post a picture of that error on screen??