Как изменить размер Amazon EBS (подключенного с правами root) за пределы 2 ТБ?
Я пробовал разные варианты изменения размера корневого диска EBS, конвертируя его из MBR в GPT, но пока безуспешно.
OS: Ubuntu 18.04.5 LTS (GNU/Linux 5.4.0-1094-aws x86_64)
Root device: dev/sda1
Volume size: 3000GiB
Вот что я пробовал до сих пор:
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 55.6M 1 loop /snap/core18/2679
loop1 7:1 0 116.7M 1 loop /snap/core/14447
loop2 7:2 0 25.1M 1 loop /snap/amazon-ssm-agent/5656
loop3 7:3 0 116.7M 1 loop /snap/core/14399
loop4 7:4 0 55.6M 1 loop /snap/core18/2667
loop5 7:5 0 24.4M 1 loop /snap/amazon-ssm-agent/6312
nvme0n1 259:0 0 3T 0 disk
└─nvme0n1p1 259:1 0 2T 0 part /
$ df -hT
Filesystem Type Size Used Avail Use% Mounted on
udev devtmpfs 7.7G 0 7.7G 0% /dev
tmpfs tmpfs 1.6G 780K 1.6G 1% /run
/dev/nvme0n1p1 ext4 2.0T 1.9T 43G 98% /
tmpfs tmpfs 7.7G 64K 7.7G 1% /dev/shm
tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs tmpfs 7.7G 0 7.7G 0% /sys/fs/cgroup
/dev/loop0 squashfs 56M 56M 0 100% /snap/core18/2679
/dev/loop1 squashfs 117M 117M 0 100% /snap/core/14447
/dev/loop2 squashfs 26M 26M 0 100% /snap/amazon-ssm-agent/5656
/dev/loop3 squashfs 117M 117M 0 100% /snap/core/14399
/dev/loop5 squashfs 25M 25M 0 100% /snap/amazon-ssm-agent/6312
/dev/loop4 squashfs 56M 56M 0 100% /snap/core18/2667
tmpfs tmpfs 1.6G 0 1.6G 0% /run/user/1000
$ sudo gdisk /dev/nvme0n1
GPT fdisk (gdisk) version 1.0.3
Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory. THIS OPERATION IS POTENTIALLY DESTRUCTIVE! Exit by
typing 'q' if you don't want to convert your MBR partitions
to GPT format!
***************************************************************
Command (? for help): w
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to /dev/nvme0n1.
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
$ sudo gdisk /dev/nvme0n1
GPT fdisk (gdisk) version 1.0.3
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Command (? for help): q
$ sudo parted /dev/nvme0n1
GNU Parted 3.2
Using /dev/nvme0n1
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
Model: Amazon Elastic Block Store (nvme)
Disk /dev/nvme0n1: 3221GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 2199GB 2199GB ext4 Linux filesystem
(parted) resizepart
Partition number? 1
Warning: Partition /dev/nvme0n1p1 is being used. Are you sure you want to continue?
Yes/No? yes
End? [2199GB]? 3000GB
(parted) print
Model: Amazon Elastic Block Store (nvme)
Disk /dev/nvme0n1: 3221GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 3000GB 3000GB ext4 Linux filesystem
(parted) q
Information: You may need to update /etc/fstab.
$ blkid
/dev/nvme0n1p1: LABEL="cloudimg-rootfs" UUID="90e1dfca-b055-4f93-b62e-6347bcb451a7" TYPE="ext4" PARTUUID="f7355124-01"
$ cat /etc/fstab
LABEL=cloudimg-rootfs / ext4 defaults,discard 0 0
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 55.6M 1 loop /snap/core18/2679
loop1 7:1 0 116.7M 1 loop /snap/core/14447
loop2 7:2 0 25.1M 1 loop /snap/amazon-ssm-agent/5656
loop3 7:3 0 116.7M 1 loop /snap/core/14399
loop4 7:4 0 55.6M 1 loop /snap/core18/2667
loop5 7:5 0 24.4M 1 loop /snap/amazon-ssm-agent/6312
nvme0n1 259:0 0 3T 0 disk
└─nvme0n1p1 259:1 0 2.7T 0 part /
$ df -hT
Filesystem Type Size Used Avail Use% Mounted on
udev devtmpfs 7.7G 0 7.7G 0% /dev
tmpfs tmpfs 1.6G 780K 1.6G 1% /run
/dev/nvme0n1p1 ext4 2.0T 1.9T 43G 98% /
tmpfs tmpfs 7.7G 64K 7.7G 1% /dev/shm
tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs tmpfs 7.7G 0 7.7G 0% /sys/fs/cgroup
/dev/loop0 squashfs 56M 56M 0 100% /snap/core18/2679
/dev/loop1 squashfs 117M 117M 0 100% /snap/core/14447
/dev/loop2 squashfs 26M 26M 0 100% /snap/amazon-ssm-agent/5656
/dev/loop3 squashfs 117M 117M 0 100% /snap/core/14399
/dev/loop5 squashfs 25M 25M 0 100% /snap/amazon-ssm-agent/6312
/dev/loop4 squashfs 56M 56M 0 100% /snap/core18/2667
tmpfs tmpfs 1.6G 0 1.6G 0% /run/user/1000
$ sudo resize2fs /dev/nvme0n1p1
resize2fs 1.44.1 (24-Mar-2018)
Filesystem at /dev/nvme0n1p1 is mounted on /; on-line resizing required
old_desc_blocks = 256, new_desc_blocks = 350
The filesystem on /dev/nvme0n1p1 is now 732421619 (4k) blocks long.
$ df -hT
Filesystem Type Size Used Avail Use% Mounted on
udev devtmpfs 7.7G 0 7.7G 0% /dev
tmpfs tmpfs 1.6G 780K 1.6G 1% /run
/dev/nvme0n1p1 ext4 2.0T 1.9T 43G 98% /
tmpfs tmpfs 7.7G 64K 7.7G 1% /dev/shm
tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs tmpfs 7.7G 0 7.7G 0% /sys/fs/cgroup
/dev/loop0 squashfs 56M 56M 0 100% /snap/core18/2679
/dev/loop1 squashfs 117M 117M 0 100% /snap/core/14447
/dev/loop2 squashfs 26M 26M 0 100% /snap/amazon-ssm-agent/5656
/dev/loop3 squashfs 117M 117M 0 100% /snap/core/14399
/dev/loop5 squashfs 25M 25M 0 100% /snap/amazon-ssm-agent/6312
/dev/loop4 squashfs 56M 56M 0 100% /snap/core18/2667
tmpfs tmpfs 1.6G 0 1.6G 0% /run/user/1000
$ sudo resize2fs /dev/nvme0n1p1
resize2fs 1.44.1 (24-Mar-2018)
Filesystem at /dev/nvme0n1p1 is mounted on /; on-line resizing required
old_desc_blocks = 256, new_desc_blocks = 350
The filesystem on /dev/nvme0n1p1 is now 732421619 (4k) blocks long.
$ df -hT
Filesystem Type Size Used Avail Use% Mounted on
udev devtmpfs 7.7G 0 7.7G 0% /dev
tmpfs tmpfs 1.6G 780K 1.6G 1% /run
/dev/nvme0n1p1 ext4 2.7T 1.9T 767G 72% /
tmpfs tmpfs 7.7G 64K 7.7G 1% /dev/shm
tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs tmpfs 7.7G 0 7.7G 0% /sys/fs/cgroup
/dev/loop0 squashfs 56M 56M 0 100% /snap/core18/2679
/dev/loop1 squashfs 117M 117M 0 100% /snap/core/14447
/dev/loop2 squashfs 26M 26M 0 100% /snap/amazon-ssm-agent/5656
/dev/loop3 squashfs 117M 117M 0 100% /snap/core/14399
/dev/loop5 squashfs 25M 25M 0 100% /snap/amazon-ssm-agent/6312
/dev/loop4 squashfs 56M 56M 0 100% /snap/core18/2667
tmpfs tmpfs 1.6G 0 1.6G 0% /run/user/1000
Как видите, обаdf -hTиlsblkкоманды показывают увеличенный размер раздела и размер файловой системы. Однако после этого, когда я перезапускаю экземпляр, он не загружается и не проходит проверку доступности:
Instance reachability check failed
Что мне здесь не хватает?