Resized partition not expanding in DietPi on hyper-V

General Discussion
1

having an issue with my Dev environment where I am showing as out of space on both nodes:

  jaja@fauxPi108:~$ df -h
  Filesystem      Size  Used Avail Use% Mounted on
  udev             10M     0   10M   0% /dev
  /dev/sda1       7.9G  7.2G  329M  96% /
  tmpfs           954M     0  954M   0% /dev/shm
  tmpfs           382M   11M  372M   3% /run
  tmpfs           5.0M     0  5.0M   0% /run/lock
  tmpfs           1.0G     0  1.0G   0% /tmp
  tmpfs            50M  8.0K   50M   1% /var/log
  tmpfs           191M     0  191M   0% /run/user/1001

  jaja@fauxPi111:~$ df -h
  Filesystem      Size  Used Avail Use% Mounted on
  udev             10M     0   10M   0% /dev
  /dev/sda1       7.9G  7.7G     0 100% /
  tmpfs           954M     0  954M   0% /dev/shm
  tmpfs           382M   11M  372M   3% /run
  tmpfs           5.0M     0  5.0M   0% /run/lock
  tmpfs           1.0G     0  1.0G   0% /tmp
  tmpfs            50M  8.0K   50M   1% /var/log

I have grown the underlying virtual disk but attempting to extend the OSs use of that space has proven difficult. using the dietpi-drivemanager

Review of log shows the following:

  Removed /etc/systemd/system/local-fs.target.wants/dietpi-fs_partition_resize.service.
  Disk /dev/sda: 8 GiB, 8589934592 bytes, 16777216 sectors
  Disk model: Virtual Disk
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x3038ce32

  Old situation:

  Device     Boot Start      End  Sectors Size Id Type
  /dev/sda1  *     2048 16777215 16775168   8G 83 Linux

  /dev/sda1:
  New situation:
  Disklabel type: dos
  Disk identifier: 0x3038ce32

  Device     Boot Start      End  Sectors Size Id Type
  /dev/sda1  *     2048 16777215 16775168   8G 83 Linux

  The partition table has been altered.
  resize2fs 1.46.2 (28-Feb-2021)
  The filesystem is already 2096896 (4k) blocks long.  Nothing to do!

It appears the utility sees the original size of the disk and not the expanded disk shown in hyper-v

Can anyone help? I am SOL until I fix this and wondering if rebuilding it is not my best option.

2

can you share some information on your disk layout

lsblk -o name,fstype,label,size,ro,type,mountpoint,partuuid,uuid
3

Thanks for the comment and sure:

lsblk -o name,fstype,label,size,ro,type,mountpoint,partuuid,uuid                                
NAME FSTYPE LABEL  SIZE RO TYPE MOUNTPOINT PARTUUID                             UUID
fd0                  4K  0 disk                                                 
sda                  8G  0 disk                                                 
└─sda1
     ext4            8G  0 part /          3038ce32-01                          690e62d6-86dd-4b74-bddd-04f392fddbc6
sr0               1024M  0 rom
4

disk/partition available for the system has still a size of 8GB.

5

Yes, this is explicitly my issue. As you can see, the Virtual disk is actually more than double that size:

image
image707×533 9.83 KB

6

Sorry for the late reply, does the problem still exist?

7

I messed it up super bad and blew it away and rebuilt. Thanks for the concerns.