Uploaded image for project: 'Mender'
  1. Mender
  2. MEN-3366

mender-grow-data.service fails on GPT images



    • Type: Bug
    • Status: Done
    • Priority: (None)
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: yocto-2.7-warrior
    • Labels:
    • Days in progress:


      [[0;1;31m●[[0m mender-grow-data.service - Mender service to grow data partition size
         Loaded: loaded (/lib/systemd/system/mender-grow-data.service; disabled; vendor preset: enabled)
         Active: [[0;1;31mfailed[[0m (Result: exit-code) since Sat 2020-03-28 15:35:39 UTC; 25s left
        Process: 131 ExecStart=/usr/sbin/parted -s /dev/mmcblk0 resizepart 4 100% [[0;1;31m(code=exited, status=1/FAILURE)[[
       Main PID: 131 (code=exited, status=1/FAILURE)
      Mar 28 15:35:39 nvgw-gen1 parted[131]: Warning: Not all of the space available to /dev/mmcblk0 appears to be used, you
       can fix the GPT to use all of the space (an extra 52682752 blocks) or continue with the current setting?
      Mar 28 15:35:39 nvgw-gen1 parted[131]: Error: Unable to satisfy all constraints on the partition.
      Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

      The failure is strange, because we are running "parted -s" which means do not prompt user for input but it does this anyway and fails. Running the commands manually works just fine without the "-s" option.

      The version of parted used on "warrior" is 3.2, which is from 2014. I have tested using parted 3.3 (from 2019) and it does work and this error is not shown so I suspect it is a parted bug in the way it handles GPT images. As this have shown to work without any issues on MBR images.

      Actually was not related to parted version, and the problem was missing backup GPT partition table at end of disk. This needs to be in place for "parted resizepart" to work.




            • Assignee:
              mirzak Mirza Krak
              mirzak Mirza Krak
            • Votes:
              0 Vote for this issue
              1 Start watching this issue


              • Created:

                Zendesk Support