Could not resize (expandPartition)

[OmegaXis]

@sebastian-roth it does look similar. But unfortunately there doesn’t seem to be a solution. I will try running chkdsk on the gold and issuing a capture to see if that helps. Unfortunately my entire project is on hold till I can get this resolved

[OmegaXis]

Update, running chckdsk scans did not solve anything.

im now at a point where i can get like one in 10 to image correctly, but its a different laptop every time. Worst part, nothing has changed.

There doesnt seem to be any reason that the ones that work do and the ones that don’t don’t. But this is not a good solution.

[OmegaXis]

So, A funny thing (not really funny as much as annoying) has started happening. I have thrown the same laptop (Thinkpad L450) now at the fog server 5 times. All 5 times resulted in failure at the resizing sda2 partition.

For the purposes of sheer insanity, I threw it at the fog server one more time expecting the exact same results. Unfortunately (or fortunately, still not sure) With that one laptop, it worked.

This whole thing seems to be hit or miss all of the sudden. When I had this setup in my home lab (minus the lenovo laptops, I was using vm’s and desktops instead)

[Sebastian Roth]

@OmegaXis Thanks for the update, it’s very unfortunate you get different results when deploying to the exact same machine. This should not happen!!

I’ll have a look at it over the weekend and see what I can find out.

[OmegaXis]

@sebastian-roth thanks

So after that one went through, everything seemed to start working fine again. Unfortunately, as its the weekend, its in a state at my office desk where I don’t trust it. I’m working this weekend on some other projects with my home lab. Let me know if you think of anything.

[Sebastian Roth]

@OmegaXis Looking at resize2fs’s source code I see that the issue you face can be caused by four different conditions:

1. Filesystem is marked with an error (e.g. not clean unmounted) - I am sure we can ignore this condition because you proofed it’s not unclean by running e2fsck in debug mode and before capture!
2. Filesystem is not in a valid state - Again I think we can dismiss this condition as e2fsck would let us know about this!
3. Timestamp of the last filesystem check is older than timestamp of last mount - I think this is the most likely cause. If the BIOS battery is old and the system clock is way off (back in the past) the timestamp set on the last filesystem check (done by our FOS scripts just before running resize2fs) could be set to a really old date.
4. Free blocks counter is larger than total blocks counter - Again fairly sure this is not the trouble in your case because this would cause e2fsck to fail as well I am sure.

To work around the issue I would suggest you add a little post init script to force resize2fs to do it’s work and skip the checks. I don’t see why this could cause major trouble as the FOS scripts do a filesystem check beforehand and would error out in case something is really wrong with the filesystem.

Edit /images/dev/postinitscripts/fog.postinit on your FOG server and add a sed call to the end of the file. If you don’t have any post init scripts in there yet the file would like this with the added sed call:

#!/bin/bash
## This file serves as a starting point to call your custom pre-imaging/post init loading scripts.
## <SCRIPTNAME> should be changed to the script you're planning to use.
## Syntax of post init scripts are
#. ${postinitpath}<SCRIPTNAME>

# modify resize2fs call
sed -i -e 's/resize2fs \$part$/resize2fs -f \$part/g' /usr/share/fog/lib/funcs.sh

If you have other things in there, just add my last two lines it to the end of your file. Make sure you copy and paste the line to not risk a typo! I tested this and it works.

Now schedule another deploy task and see if you can reproduce the issue again.

[OmegaXis]

Hay Sebastian.

I think your theory on the bios clock is probably correct. Most of the laptops have been in storage for over a year. Once they started working, they had been plugged into network and power for a bit. I’ll take a look Monday at the other recommendations.

[Wayne Workman]

@omegaxis Because the root cause seems to be identified, I won’t pursue recreating the issue. Ping me directly if you find this to not be true. I’d need to know your Linux system layout & sizes, as well as source HDD size and destination HDD size. I can replicate all this stuff using VMs.

[OmegaXis]

@wayne-workman
im willing to call this resolved given that it seems to have been a time sync issue.

[Patrix]

Hi,

We had the same exact problem, we used a laptop with a 256GB NVMe SSD to create the image and then deployed on a 240GB Sata SSD and we got that error.

We then tried pretty much every possible hack available on the internet to change the partition size without success.

We then tried to capture the image on the 240GB SSD to deploy it on the 256 and it worked.

We ran into that issue a few more times. Everytime the source disk only has arround 30GB of data but if the total size of the disk is more than the target disk, it will fail, no matter what.

[Sebastian Roth]

@Patrix While you might have the same issue it could be a totally different problem as well. We just don’t know enough of you specs to tell yet.

So if you want help I ask you to open your very own topic and post all the information of you setup:

• FOG version
• Init version
• Linux OS and version of your FOG server
• OS installed on the host you want to capture/deploy
• contents of d1.minimum.partitions of the particular image you want to deploy to a smaller size disk