VM forced into emergency mode after increasing disk size


New Member
Aug 24, 2023
First of all, I apologize for not following the official documents to increase size.
I very need your help.

My Proxmox system is set up on a single physical machine running 4 LXCs and a virtual machine (endeavouros OS with KDE), Proxmox is installed on a separate 256GB SSD and everything else is on a 12TB mechanical hard disk.
I'm new to both proxmox and linux (Linux 6month、Proxmox 1month)

Originally I had given the endeavouros VM 1000G of space to use, and today I wanted to expand the capacity of this VM in order to back up my main computer's files first.

1. I didn't close the VM at first, and in the WEB GUI of Proxmox, I selected the hard disk in the Hardware tab of the VM and chose "Resize",then adjusted it to 5TB.
Then restarted the VM and found the available partitions increased, I thought I should also extend the file system to the unused partitions in the VM, so far so good.

2. So I went inside the VM, but I didn't use the command, I installed "KDE's partition manager tool" and used manager's GUI, entered the size I wanted to expand and chose execute, then it show the execution is failed, but I still tried to use different number to scale it up to test if the change was successful.

3. I tried several times with different sizes and succeeded to see the increase in capacity in the file manager (999GB>1.9TB), then I continued to try to see if it could be scaled up to 5TB, but it didn't work, I ran the command by partition manager tool to scale up the partition at least 5 times, but it failed, and that was the beginning of the disaster...

4. After Step3, I restarted the VM and it failed to start.
here is the error msg shot
proxmox_虛擬機自救 2023-08-24 224046.png
When I follow the prompts to execute the following command
It returns the following result
fsck /dev/disk/by-uuid/cb52f685-4320-40c9-9a7c-4bb84f73e800 fsck from util-linux 2.39.1 e2fsck 1.47.0 (5-Feb-2023) The filesystem size (according to the superblock) is 524288000 blocks The physical size of the device is 511705088 blocks Either the superblock or the partition table is likely to be corrupt! Abort?

After collecting some data, I tried the solution with the highest score
in this article
executed command
e2fsck -f /dev/disk/by-uuid/cb52f685-4320-40c9-9a7c-4bb84f73e800
But when I want resize2fs, system say command not found
By the way, lsblk also return command not found to me

So for now, I don't know how to do, although I have a backup, I still hope that the system can restore whitout lose data.
I just want to increase disk size.....

If you need other information plz tell me, I can provide it immediately as fast as I can.
Last edited:
Increasing is normally not a problem and the normal way is partion increase, filesystem increase and everything can be done online. I have no idea what went wrong, yet I have never used any GUI partitioning tool. Maybe the culprit lies there.
Thanks for your reply, I also think that increasing the capacity of the hard disk will not cause any problem.
But here's the problem.
I'm looking for any guidelines I can follow to get my system back.
I feel that I have a special situation where some commands don't work? (ex: resize2fs).


The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!