You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was attempting to run growpart when booting off of a RAID device and noticed that growpart never grows the root partition properly.
During boot, I get the message:
GROWROOT: FAILED: /dev/md126p: does not exist
I then modified the "growroot" wrapper that gets put into the initramfs that takes the root partition and finds the name of the root disk from it. It looks like that script simply takes the root partition and strips the last consecutive numbers to find the root disk. For example:
/dev/sda1 -> /dev/sda
/dev/md126p1 -> /dev/md126p
/dev/md126p doesn't exist because the RAID disk name is /dev/md126.
I changed it so that the script always uses /dev/md126 as the disk with 2 variations: one that uses "1" as the partition number, and one that uses "p1" as the partition number. The former fails because "/dev/md1261 does not exist", and the latter fails because the growpart script checks to see that the partition number is actually a numerical value.
This can probably be fixed by modifying growpart to allow the use of numerical values prefixed by "p" for partition numbers and modifying the growroot script that gets put in the initramfs to properly do string formatting with mdraid device names.
Originally reported by: Mario Villaplana on 2015-09-01
Original bug URL: https://bugs.launchpad.net/cloud-utils/+bug/1491148
Last Launchpad Status: Triaged
Last Launchpad Importance: Medium
I was attempting to run growpart when booting off of a RAID device and noticed that growpart never grows the root partition properly.
During boot, I get the message:
I then modified the "growroot" wrapper that gets put into the initramfs that takes the root partition and finds the name of the root disk from it. It looks like that script simply takes the root partition and strips the last consecutive numbers to find the root disk. For example:
I changed it so that the script always uses /dev/md126 as the disk with 2 variations: one that uses "1" as the partition number, and one that uses "p1" as the partition number. The former fails because "/dev/md1261 does not exist", and the latter fails because the growpart script checks to see that the partition number is actually a numerical value.
This can probably be fixed by modifying growpart to allow the use of numerical values prefixed by "p" for partition numbers and modifying the growroot script that gets put in the initramfs to properly do string formatting with mdraid device names.
Thanks for your time.
Related bugs:
bug 1799953: growpart does not work for lvm
The text was updated successfully, but these errors were encountered: