I'm not sure why but would like others to confirm/deny that it happens for them with the image from the first f27 release.
[root@cloudhost ~]# rpm-ostree status State: idle Deployments: ● fedora-atomic:fedora/27/aarch64/atomic-host Version: 27.1 (2017-11-10 12:02:44) Commit: da1bd08012699a0aacaa11481d3ed617477858aab0f2ea7300168ce106202255 GPGSignature: Valid signature by 860E19B0AFA800A1751881A6F55E7430F5282EE4 [root@cloudhost ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 40G 0 disk ├─sda1 8:1 0 200M 0 part /boot/efi ├─sda2 8:2 0 1G 0 part /boot └─sda3 8:3 0 4.8G 0 part └─atomicos-root 253:0 0 4.8G 0 lvm /sysroot sdb 8:16 0 368K 0 disk sdc 8:32 0 10G 0 disk [root@cloudhost ~]# growpart /dev/sda 3 GPT PMBR size mismatch (12582911 != 83886079) will be corrected by w(rite). attempt to resize /dev/sda failed. sfdisk output below: | GPT PMBR size mismatch (12582911 != 83886079) will be corrected by w(rite). | Backup files: | PMBR (offset 0, size 512): /tmp/growpart.gpxB0y/backup-sda-0x00000000.bak | GPT Header (offset 512, size 512): /tmp/growpart.gpxB0y/backup-sda-0x00000200.bak | GPT Entries (offset 1024, size 16384): /tmp/growpart.gpxB0y/backup-sda-0x00000400.bak | | Disk /dev/sda: 40 GiB, 42949672960 bytes, 83886080 sectors | Units: sectors of 1 * 512 = 512 bytes | Sector size (logical/physical): 512 bytes / 512 bytes | I/O size (minimum/optimal): 512 bytes / 512 bytes | Disklabel type: gpt | Disk identifier: 5B1DEB7C-8134-464C-8767-0883E53D8B64 | | Old situation: | | Device Start End Sectors Size Type | /dev/sda1 2048 411647 409600 200M EFI System | /dev/sda2 411648 2508799 2097152 1G Linux filesystem | /dev/sda3 2508800 12580863 10072064 4.8G Linux LVM | | >>> Script header accepted. | >>> Script header accepted. | >>> Script header accepted. | >>> Script header accepted. | >>> Script header accepted. | >>> Script header accepted. | >>> Created a new GPT disklabel (GUID: 5B1DEB7C-8134-464C-8767-0883E53D8B64). | /dev/sda1: Created a new partition 1 of type 'EFI System' and of size 200 MiB. | Partition #1 contains a vfat signature. | /dev/sda2: Created a new partition 2 of type 'Linux filesystem' and of size 1 GiB. | Partition #2 contains a ext4 signature. | /dev/sda3: The last usable GPT sector is 12582878, but 83886079 is requested. | Failed to add #3 partition: Invalid argument | Leaving. | FAILED: failed to resize ***** WARNING: Resize failed, attempting to revert ****** 512+0 records in 512+0 records out 512 bytes copied, 0.0930597 s, 5.5 kB/s ***** Appears to have gone OK ****
Metadata Update from @dustymabe: - Issue tagged with: F27, host, multi-arch
I too see same issue with growpart on aarch64. Good thing to note is that growpart works as expected on ppc64le. I will investigate further why this is happening on aarch64.
It took me a while to figure out whether problem exist in latest upstream cloud-utils or is specific to Fedora. So far, I can confirm that issue exist with cloud-utils-0.27 version (we use this version in Fedora 27 and rawhide). With upstream cloud-utils-0.28 or later version, growpart runs successfully on aarch64.
I have opened bug for same - https://bugzilla.redhat.com/show_bug.cgi?id=1515835
thanks @sinnykumari!
Able to contact cloud-utils package maintainer and he also agrees that updating to upstream latest version 0.30 will be a good idea.
Have sent PR to update cloud-utils in Fedora to 0.30 - https://src.fedoraproject.org/rpms/cloud-utils/pull-request/1
PR has been merged to cloud-utils dist-git master branch and 0.30 is now available for Fedora rawhide. Thanks to @juergh and @dustymabe for all the help on getting this done! We should soon have 0.30 package update available in F27.
Fedora 27 build of cloud-utils-0.30 package is available in bodhi for testing. Please test it to ensure that it works as expected and give karma. Link - https://bodhi.fedoraproject.org/updates/FEDORA-2017-6ad062c8ff
This is fixed now and should go out in today's release: https://pagure.io/releng/issue/7290
Metadata Update from @dustymabe: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.