Unable to expand rootfs Filesystem /dev/sda1 under Hyper-V VHDX

Troubleshooting
1

Dear Community!

Today I installed the Hyper-V VHDX Image as Bullseye (Debian 11) Version, wich is needed for Loxberry.
After the first start the partition has round about 900MB.

I tryed to expand the fs with dietpi-drive_manager but it wont work.
During the startup it runs so fast, that you cant read anything, reboot is in under 5 seconds. There is no hold on for expanding anything.

Than I tryed to expant it to 8GB with parted. It says that the sector was out of range. This is impossible because in Hyper-V Manager the VHDX is expanded to 10GB.

After it I installed hyperv-daemons.

Now I can expand partition 1 (/dev/sda) with parted to 8GB.

It says:
Disk /dev/sda: 9664MB
Sector size 512B/512B
Partition Table: msdos
Disk Flags:
1 Start:1049kB End:8192MB Size:8191MB Type:primary File_System:ext4 Flags:boot

So for me it shows now the right size. After a reboot df-h says again /dev/sda 897M - 100%

Again I started dietpi-drive_manager but it wont work, same same, nothing happen.

How can I expant it, is this a typial bug with using Windows Hyper-V?

Thx for your competent answeres!

Required Information

  • DietPi version | G_DIETPI_VERSION_CORE=9 G_DIETPI_VERSION_SUB=0 G_DIETPI_VERSION_RC=2 G_GITBRANCH='master' G_GITOWNER='MichaIng'

  • Distro version | bullseye

  • Kernel version | Linux DietPi 5.10.0-27-amd64 #1 SMP Debian 5.10.205-2 (2023-12-31) x86_64 GNU/Linux

  • Architecture | amd64

  • SBC model | Virtual Machine (x86_64)

  • Power supply used | 230V | 1000W

  • SD card used | Samsung 960 Pro SSD

2

hmm I just did a fresh install using DietPi Hyper-V disk image and I get whole 8GB disk ootb

NAME   FSTYPE LABEL  SIZE RO TYPE MOUNTPOINT PARTUUID                             UUID
fd0                    4K  0 disk
sda                    8G  0 disk
└─sda1 ext4            8G  0 part /          df11abb7-01                          a8361e6d-a239-41e5-b3f0-310c1d4820f0
sr0                 1024M  0 rom
root@DietPi:~#

root@DietPi:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
udev             10M     0   10M   0% /dev
/dev/sda1       7.9G  888M  6.7G  12% /
tmpfs           951M     0  951M   0% /dev/shm
tmpfs           381M  5.3M  376M   2% /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
root@DietPi:~#

Did you already checked /var/tmp/dietpi/logs/fs_partition_resize.log ?

3

Hey Joulinar,

thanks for your answere. Did you also install the older Bullseye Debian 11 version?
I am not goog in Linux, so I’m at my wits’ end :slight_smile:

root@DietPi:~# lsblk
NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
fd0      2:0    1    4K  0 disk
sda      8:0    0    9G  0 disk
└─sda1   8:1    0  7.6G  0 part /

root@DietPi:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
udev             10M     0   10M   0% /dev
/dev/sda1       897M  830M  4.9M 100% /
tmpfs           433M     0  433M   0% /dev/shm
tmpfs           173M  4.8M  169M   3% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           432M     0  432M   0% /tmp
tmpfs            50M  8.0K   50M   1% /var/log

root@DietPi:~# cat /var/tmp/dietpi/logs/fs_partition_resize.log
Removed /etc/systemd/system/local-fs.target.wants/dietpi-fs_partition_resize.service.
[ INFO ] Detected root drive /dev/sda with root partition 1
[ INFO ] No DietPi setup partition found, last partition is: " "
lsblk: unknown column: MOUNTPOINTS
Removed /etc/systemd/system/local-fs.target.wants/dietpi-fs_partition_resize.service.
[ INFO ] Detected root drive /dev/sda with root partition 1
[ INFO ] No DietPi setup partition found, last partition is: " "
lsblk: unknown column: MOUNTPOINTS
Removed /etc/systemd/system/local-fs.target.wants/dietpi-fs_partition_resize.service.
[ INFO ] Detected root drive /dev/sda with root partition 1
[ INFO ] No DietPi setup partition found, last partition is: " "
lsblk: unknown column: MOUNTPOINTS
Removed /etc/systemd/system/local-fs.target.wants/dietpi-fs_partition_resize.service.
[ INFO ] Detected root drive /dev/sda with root partition 1
[ INFO ] No DietPi setup partition found, last partition is: " "
lsblk: unknown column: MOUNTPOINTS
Removed /etc/systemd/system/local-fs.target.wants/dietpi-fs_partition_resize.service.
[ INFO ] Detected root drive /dev/sda with root partition 1
[ INFO ] No DietPi setup partition found, last partition is: " "
lsblk: unknown column: MOUNTPOINTS
Removed /etc/systemd/system/local-fs.target.wants/dietpi-fs_partition_resize.service.
[ INFO ] Detected root drive /dev/sda with root partition 1
[ INFO ] No DietPi setup partition found, last partition is: " "
lsblk: unknown column: MOUNTPOINTS
Removed /etc/systemd/system/local-fs.target.wants/dietpi-fs_partition_resize.service.
[ INFO ] Detected root drive /dev/sda with root partition 1
[ INFO ] No DietPi setup partition found, last partition is: " "
lsblk: unknown column: MOUNTPOINTS
Removed /etc/systemd/system/local-fs.target.wants/dietpi-fs_partition_resize.service.
[ INFO ] Detected root drive /dev/sda with root partition 1
[ INFO ] No DietPi setup partition found, last partition is: " "
lsblk: unknown column: MOUNTPOINTS
Removed /etc/systemd/system/local-fs.target.wants/dietpi-fs_partition_resize.service.
[ INFO ] Detected root drive /dev/sda with root partition 1
[ INFO ] No DietPi setup partition found, last partition is: " "
lsblk: unknown column: MOUNTPOINTS
4

This is a known issue for old Bullseye systems actually. We are already going to create new images.

5

btw: LoxBerry has provided a Beta image supporting Bookworm. Maybe you like to join and support LoxBerry guys on their journey to move to Bookworm Betatest: LoxBerry 3.x auf Debian 12 (Bookworm) - loxforum.com

6

Perfect idea and thanks for the Link!