_:n2de6b21fa5b64ed59a1ab132bbf7ab78xb1
<http://schema.org/text>
"Hello, I would like to expand a partitation on an instance, but for some reason the command growpart does not exist on this instance?\nI am proceeding as usual according to https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/recognize-expanded-volume-linux.html, and this has also worked for the other instances in the past, only with the current one I fail at point 2c, as the command \"growpart\" obviously does not exist on my instance?!?\n\nThis is the current situation at this instance:\n-------------\nsudo lsblk\nNAME    MAJ:MIN RM SIZE RO TYPE MOUNTPOINT\nxvda    202:0    0   8G  0 disk \n`-xvda1 202:1    0   5G  0 part /\nxvdb    202:16   0  15G  0 disk \n`-xvdb1 202:17   0  15G  0 part /IOL\n-------------\n\nSo the xvda drive has already been increased from 5 to 8 GB.\n\nBut when I try to enlarge it using growpart, the result looks like this:\n-----------\nsudo growpart /dev/xvda 1\nsudo: growpart: command not found\n-------\n\nAnd indeed, there is obviously none:\n--------\nwhich growpart\n/usr/bin/which: no growpart in (/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/ec2-user/bin)\n----------\n\nMaybe you can imagine the look on my face when I saw this message? 8:o\nWhere did that go?! Are there alternative ways to increase the partitation to the full drive size without growpart?"
<https://repost.aws/zh-Hant/questions/QU3DbeRNp-R3y3_tsCY8LZ_Q/expanding-an-xen-instance-partition-fails-due-to-missing-growpart>