Tag Info

Hot answers tagged

2

Firstly, you have your /dev/sdX numbers mixed up between your screenshot and your summary. Hence, the four partitions from df are /dev/sda4 mounted on / /dev/sda2 mounted on /boot /dev/sda1 mounted on /boot/efi /dev/sda3 mounted on /home /dev/sda1 is not empty; df shows it contains 191M. Type: Microsoft basic in the partition table ...


1

In your case I do not believe resize2fs will work without serious games, as it assumes that the start does not move. there may be other tools that do not have this restriction, but they will definitely have to be done with the target unmounted (live cd or the like). A traditional solution would be to add another partition in the gap, format it and move stuff ...


1

resize2fs is a tool used to resize the filesystem, not the underlying block device. Before you can use resize2fs, you need to ensure that the underlying device (/dev/sda7 in this case) has more space available to use. In normal usage, the filesystem is sized correctly for its underlying device; thus, usually, you need to grow the block device before you can ...


1

You can observe in /sys the block device for a given partition name. Eg for /dev/sda1: $ ls -l /sys/class/block/sda1 lrwxrwxrwx 1 root root /sys/class/block/sda1 -> \ ../../devices/pci0000:00/.../ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1 A script to take arg /dev/sda1 and print /dev/sda is: part=$1 part=${part#/dev/} disk=$(readlink ...



Only top voted, non community-wiki answers of a minimum length are eligible