When you create a Rocky Linux VM on Azure the OS disk defaults to 8GB and you can’t change it during the creation. I am able to expand the volume to 30GB after creating the VM from the portal, but I’m having a hard time expanding it within Rocky terminal. (obviously I’m a linux noob)
Here is what I see with lsblk command:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 30G 0 disk
├─sda1 8:1 0 100M 0 part /boot/efi
├─sda2 8:2 0 1000M 0 part /boot
├─sda3 8:3 0 7.8G 0 part /
├─sda4 8:4 0 4M 0 part
└─sda5 8:5 0 1M 0 part
sdb 8:16 0 8G 0 disk
└─sdb1 8:17 0 8G 0 part /mnt
Heya - thanks for pointing this out… there is a bit of an issue with this partition layout that I need to address. I’ll get a new image pushed out this week.
The current disk layout has two partitions after the / partition, which makes it difficult/impossible to grow the disk. We’ve had this happen with our LVM images, but not with these until now. We ‘fix’ this by manually creating the partitions rather than let Anaconda create them via Kickstart, because the ordering of the partitions by Anaconda is not guaranteed. See: add %pre to base images · 46fabf40b7 - kickstarts - Rocky Enterprise Software Foundation Git Service
Hello cwhitmore
I’m sorry to break it to you, but you stepped on the hoe!
I appreciate your behavior, that you modestly and sincerely say that you do not have the knowledge and experience.
No one is born learned and everyone learns while living! This forum and the Linux community prove it.
You are not happy about that, but the fact that “neil” intervene is indicative that the scribbles on the forum are read by “Infrastructure Team Lead” and it was you who helped to fix a malfunction!
Take an example of me. If “neil” hadn’t intervened (thanks for that!) you don’t think I would have paid attention to the partition numbering and looked right there after you even showed it!?
For me, / is the last partition and the expand is correct and works. But that doesn’t mean I missed that detail. I missed her! My mistake. And I didn’t know that partition concatenation creates a problem when expand a filesystem. My situation is this:
Xino - Thank you for your patience. I’m finally able to make time to learn what I can about Linux and especially Rocky Linux. I like doing things on my own and hate asking for help so thank you for providing the steps and links to online docs.
Has this issue been fixed? We are experiencing the same issue, we can not easily expand the root partition which is most likely due to the extra 2 partition created after root partition #3…
Device Start End Sectors Size Type
/dev/sda1 2048 206847 204800 100M EFI System
/dev/sda2 206848 2254847 2048000 1000M Linux filesystem
/dev/sda3 2254848 18638847 16384000 7.8G Linux filesystem
/dev/sda4 18638848 18647039 8192 4M PowerPC PReP boot
/dev/sda5 18647040 18649087 2048 1M BIOS boot
The version that is published to our Azure region (EastUS2) is not fixed. We have to redeploy quite a number of VMs now because we just recently discovered the issue when we went to expand a partition.
I think we now have to download what is in their community gallery and upload those images to our region…I believe those images do not have the issue so you might check there. I hope they do decide to publish working images to our Azure region in the future.
Small precision: We’re using the following Azure marketplace image:
center-for-internet-security-inc:cis-rocky-linux-9-l1:cis-rocky-linux-9-l1-gen2:1.0.2
It looks like rocky 8 does NOT have the same issue:
center-for-internet-security-inc:cis-rocky-linux-8-l1:cis-rocky-linux-8-l1:1.0.2
I will make sure the marketplace is updated. Thank you for your patience. The marketplace processes are kinda… annoying, and it would be great for us to have more people with the ability to help move things along. I am actively working on how we can facilitate that.
