Resizing root partition and giving proxmox more space

[bobalo]

Hello proxmox experts. I have a issue with my dedicated server running proxmox. The provider gave us a 128 GB SSD , where only 58GB is assigned as storage in proxmox. How can I assign more storage room since 50% of my SSD is unused atm. This may be helpful :

 

[thheo]

https://pve.proxmox.com/wiki/Debugging_Installation

 

[m.ardito]

pve should be installed on LVM, so you could be able to resize/extend LVM volumes, also.

Marco

 

[bobalo]

https://pve.proxmox.com/wiki/Debugging_Installation

I'd hate to install proxmox all over again I'll see if I can resize LVM volume

 

[m.ardito]

although it'snot directly related to swap, see also this page for lvresize usage

http://pve.proxmox.com/wiki/Extending_Local_Container_Storage#Generic_Notes_on_lvresize

Marco

 

[bobalo]

although it'snot directly related to swap, see also this page for lvresize usage

http://pve.proxmox.com/wiki/Extending_Local_Container_Storage#Generic_Notes_on_lvresize

Marco

Thanks alot Marco! I was able to resize pve-data with 20GB + , however I shrinked the size of pve-root (left it with only 2GB , 1GB was used so it had 1GB free) and now proxmox is not responding.
Trying to reboot the daemon gives I/O error. Is there any way to fix this? Can't seem to resize pve-root anymore. That's what I get when messin 'round

 

[m.ardito]

now proxmox is not responding.Trying to reboot the daemon gives I/O error. Is there any way to fix this?

which daemon, and have you got any text error? If not try to restart the whole machine, or restart services from the command line, it could be more verbose and get some clues...

I don't know, however, if and how this could be related to pve-root free space, or total size... sorry...

Marco

 

[thheo]

Thanks alot Marco! I was able to resize pve-data with 20GB + , however I shrinked the size of pve-root (left it with only 2GB , 1GB was used so it had 1GB free) and now proxmox is not responding.
Trying to reboot the daemon gives I/O error. Is there any way to fix this? Can't seem to resize pve-root anymore. That's what I get when messin 'round

You have to resize the filesystem as well.. you just resized the underlying layer.

 

[iconvergence]

boot with a rescue cd and resize pve-root

i don't find solution without rescue cd maybe there is one

do something like :
sudo lvm vgchange -a y ; sudo e2fsck -f /dev/mapper/pve-root ; sudo resize2fs -f /dev/mapper/pve-root 30G ; sudo lvm lvreduce -L30G /dev/mapper/pve-root

 

[bobalo]

boot with a rescue cd and resize pve-root

i don't find solution without rescue cd maybe there is one

do something like :
sudo lvm vgchange -a y ; sudo e2fsck -f /dev/mapper/pve-root ; sudo resize2fs -f /dev/mapper/pve-root 30G ; sudo lvm lvreduce -L30G /dev/mapper/pve-root

3 logical volume(s) in volume group "pve" now active
-bash: /sbin/e2fsck: Input/output error
resize2fs 1.42.5 (29-Jul-2012)
Filesystem at /dev/mapper/pve-root is mounted on /; on-line resizing required
old_desc_blocks = 2, new_desc_blocks = 2
resize2fs: Read-only file system While checking for on-line resizing support
Positive sign not permitted - use lvextend
Run `lvreduce --help' for more information.

I'll try with the rescue CD

 

[Yehudacorsia]

I was writing an article about it you can read it here

https://docs.google.com/document/d/1_5FFYUGwXQEjNosfBXgn838CdqcUExJrFc5ktqLu52c/edit?usp=drivesdk

 

[moretti]

I was writing an article about it you can read it here

https://docs.google.com/document/d/1zKo0qIw4vSq2eSdDuwUvTvoUb0zSaQKO_tB9QxOWypM/edit?usp=drivesdk

This information did what I need. Thank you.

 

[fiveangle]

I was writing an article about it you can read it here

https://docs.google.com/document/d/1_5FFYUGwXQEjNosfBXgn838CdqcUExJrFc5ktqLu52c/edit?usp=drivesdk

yes, worked like a charm - thanks for the effort !

 

[rsur2000]

I was writing an article about it you can read it here

https://docs.google.com/document/d/1_5FFYUGwXQEjNosfBXgn838CdqcUExJrFc5ktqLu52c/edit?usp=drivesdk

Hi... could you kindly repost the link, because that one is broken. Thank you so much

 

[kyriazis]

I was writing an article about it you can read it here

https://docs.google.com/document/d/1_5FFYUGwXQEjNosfBXgn838CdqcUExJrFc5ktqLu52c/edit?usp=drivesdk

Thanks for writing this.

However, the last lvconvert command gave me an error:

# lvconvert --type thin-pool pve/data
  Command on LV pve/data does not accept LV type thinpool.
  Command not permitted on LV pve/data.
#

Any thoughts?

 

[f313]

Thanks for writing this.

However, the last lvconvert command gave me an error:

# lvconvert --type thin-pool pve/data
  Command on LV pve/data does not accept LV type thinpool.
  Command not permitted on LV pve/data.
#

Any thoughts?

Ran into the same issue.
Did you find a solution?

 

[kyriazis]

Ran into the same issue.
Did you find a solution?

It's been a while since I came across this, but I think I just ignored it. If I remember well, the error was reported because pve/data is already configured as thin-pool, so conversion to the same type is non-sensical (at least that's what lvconvert thinks).

 

[biskero]

I am in the same situation where I ran out of space but I have the problem that Proxmox and a VM are on the same NVMe.
So the LV data contains a VM which is occupying about 45% of the 900Gb while I assigned around 100G to the proxmox installation.
Does this method create problems, like erasing data or it is safe? Maybe just to have a backup just in case?

I run into this issue while I was storing data on TrueNAS (installed on another NVMe) on another HDD. I run out of space in pve/root and I got lock out of proxmox, so I had to delete bunch of software to free up some space. At the moment I am at this point and that's why I want to add more room to pve/root.

/dev/mapper/pve-root 98497780 85636608 7811624 92% /






would this work for me resizing data to 650G and give the rest to pve/root? As I understand the lvremove will not delete my VM but just the metadata underlying. So it safe for me to do this?

# Remove pve-data logical volume.
lvremove /dev/pve/data -y

# Create it again with a new size.
lvcreate -L 650G -n data pve -T

# Give pve-root all the other size.
lvresize -l +100%FREE /dev/pve/root

# Resize pve-root file system
resize2fs /dev/mapper/pve-root

The doc is great btw!
thxs

 

[muner]

I was writing an article about it you can read it here

https://docs.google.com/document/d/1_5FFYUGwXQEjNosfBXgn838CdqcUExJrFc5ktqLu52c/edit?usp=drivesdk

lvremove /dev/pve/data -y

any effect will cause data loss ?

 

[Paddidox]

WARNING: The commands provided in the Google Docs document is going to cause data loss!

Be sure to backup all machines on this host on another storage!