[SOLVED] Partition resizing problem

[arnaudrigole]

Hi Fog Community,

First, i wanna wish you an happy new year and say THANK YOU! I’ve been using FOG since 2 years right now, it’s very efficient and fast to deploy, adapted for professional usages!

I’m posting this because i encounter a little issue when trying to upload my last DELL 7285 master image;
The process is failing at the resizing step, here is what i get:

Updating $BadClust file …
Updating $Bitmap file …
ERROR(34): Could not map attribute 0x80 in inode (miss the number): Numerical result out of range

I tried to do a chkdsk /r /f on the disk before imaging;
and change the compression level from 6 to 0, and type from Partclone Gzip to Partimage but the issue stills the same.

I found this https://forums.fogproject.org/assets/uploads/files/1468447170744-gparted_details_bad.htm?v=b3tf0ilfkio which seems to be the same problem, but it’s like an attached document to a thread that i can’t find

The FOG version is 1.4.4, the kernel is updated.
The machine concerned is a DELL Latitude 7285 running Windows 10.

Thank you in advance for your precious help
Arnaud

EDIT : it looks like to be an issue related to the disk type “nvme”, i’ll try to update my fog server in 1.5.5
EDIT2: i’ve just updated our FOG instance in 1.5.5 with the kernel 4.5.0 x64, the problem stills present

printscreen related:

[arnaudrigole]

Hi @george1421, @Sebastian-Roth, @Tom-Elliott

For information, the root cause of the problem seems to be the original partitioning from DELL.
I’ve based my master image on the pre-installed “out of box” Windows 10. Not a good idea…

So i have done a clean install of Windows 10 from a Microsoft ISO, partitioned the disk in two volumes (plus the recovery partition and EFI boot partition automatically created) so we have a and D:, and done again the image process and it worked like a charm!

Thanks team!

[george1421]

Well my first recommendation would be to upgrade to 1.5.5, but now that you are there, lets look into that disk. Do you have another computer of the same model you can test to see if you get the same results.

For data collection, what version of Win10 is on that target computer you are trying to capture?

[arnaudrigole]

@george1421

Hi George,
Thank you for your reply.
Unfortunately, i got no computers with the same configuration
The Windows 10 version is 1803

[Tom Elliott]

@arnaudrigole did you ensure to shutdown without fastboot switched on?

[arnaudrigole]

EDIT: Same problem without fastboot
I really don’t understand, i had the same computer model, a Latitude 7285 few weeks ago, i’ve did the same partitioning and didn’t get that issue when imaging. The only difference is that the hardware on my current 7285 seems to have been upgraded, with a NVMe PCIe SSD and AMD Chipset controller, versus the previous version which has a SATA SSD and Intel Chipset.

EDIT2: I just received 10 laptops more, the exact same model & configuration.
I tried to image the pre-installed DELL Windows from one of them directly with FOG , and it worked well! There is only one partition for system & datas, which has 230gb. Do you have an idea of what is causing the problem in my partitioning?

@Tom-Elliott
Hey Tom,
Fastboot is turned on, i didn’t know that it could be a problem!
I’ll try this morning to reimage without it
For info, here is the partitioning of the concerned machine

[Sebastian Roth]

@arnaudrigole Please try defragmenting the partitions (nvme0n1p3 in your case so I guess this would be drive - but better defrag and as well). Then try again.

I am fairly sure the issue has nothing to do with the new model using a NVMe disk!

[arnaudrigole]

Hi @Sebastian-Roth !
I think the concerned partition is more the drive, because the first partition is the one contains the EFI bootfiles, and the second one the recover (or maybe the opposite)

I’ll try it! But since we works with full flash disks, the concept of defragmentation doesn’t exist anymore, they call it “optimization”. Anyway, i don’t know what’s the difference ^^

I’ll feedback you as soon as possible, i’m away from the company this week.

Arnaud

[arnaudrigole]

Hi @george1421, @Sebastian-Roth, @Tom-Elliott

For information, the root cause of the problem seems to be the original partitioning from DELL.
I’ve based my master image on the pre-installed “out of box” Windows 10. Not a good idea…

So i have done a clean install of Windows 10 from a Microsoft ISO, partitioned the disk in two volumes (plus the recovery partition and EFI boot partition automatically created) so we have a and D:, and done again the image process and it worked like a charm!

Thanks team!

[Quazz]

@arnaudrigole I am glad you found a solution that worked for you, though I’m still interested in trying to at least guess at why the other partition scheme gave problems.

Was there a difference in disk size in the SATA vs nVME SSDs?

Perhaps the nVME SSD is smaller and the OEM partitition at the end of the disk was out of range, though we’d expect a different error for that.