Search results

I was not considering SD card installation, but rather referencing to this bit of info # remove the entry from PVE storage config first (this is not destructive) pvesm remove local-lvm # remove Thin LVM itself - this is destructive, but should be OK as long as you # did not created any VM's...

hello i would like to steal some space from pve-data and allocate it to pve-root. Is booting from gparted live and doing it via the gui a possible solution? Thanks edit: found this thread https://forum.proxmox.com/threads/pve-root-directory-runs-out-of-space-why-and-what-should-i-do.102988/

Thanks, I've done #3 but I will def do #1 and #2 this time round.

hi all, trying to recover from a catastrophic power failure and running into dead ends... hoping someone can help. My PVE node was booting to a grub - unknown filesystem error. I was able to run fsck on /pve/root and bring it back to bootable but running into this problem: # lvconvert --repair...

Well i feel silly. The answer was obviously to assign the mounts by UUID as described here

Hi Ver.6.3-3 I have 3 mounted drives scsi1/scsi2/scsi3 setup as sdb/sdc/sdd respectively take snapshot then rollback to snapshot and blk devices are scrambled ex. scsi1 - becomes sdd (was sdb) scsi2 stays sdc scsi3 - becomes sdb (was sdd) This screws up my mounts in fstab. Question...

Hello, Ver 6.3-3 I am curious about snapshots of my ubuntu vm: When I create snapshots with RAM enabled, there is automatically an entry for a ZFS dataset of 21.1 GB added - regardless of filesystem changess. hmir/data/vm 194G 953G 96K /hmir/data/vm...

➜ /root pveversion -v proxmox-ve: 6.3-1 (running kernel: 5.4.78-2-pve) pve-manager: 6.3-3 (running version: 6.3-3/eee5f901) pve-kernel-5.4: 6.3-3 pve-kernel-helper: 6.3-3 pve-kernel-5.4.78-2-pve: 5.4.78-2 pve-kernel-5.4.73-1-pve: 5.4.73-1 ceph-fuse: 12.2.11+dfsg1-2.1+b1 corosync: 3.0.4-pve1...

agent: 1 balloon: 2048 boot: order=scsi0;ide2;net0 cores: 1 ide2: local:iso/ubuntu-20.04.1-live-server-amd64.iso,media=cdrom memory: 4096 name: test-u net0: virtio=6E:CF:5C:08:F8:AA,bridge=vmbr0,firewall=1 numa: 0 ostype: l26 scsi0: htank:vm-101-disk-0,size=32G scsihw: virtio-scsi-pci smbios1...

Not sure this is proxmox related but here goes: PVE 6.3-3 ubuntu-20.04.1-live-server-amd64.iso on 32 GB ZFS all settings vanilla

You sir are the best in the world. I had no idea there was a difference between quota and refquota. From this link: For anyone else wondering where this is accomplished its in the container or vm menu under /rescources ---> resize disk.

You are correct sir: zfs get refquota zvol/henry/torrent/subvol-100-disk-0 zvol/henry/torrent/subvol-100-disk-0 refquota 250G local Might I ask how to increase this? The following is having no effect: zfs set quota=400G zvol/henry/torrent/subvol-100-disk-0

I am stuck with this one and I know it should be a simple answer, so sorry in advance... zvol/henry/CQFsync 3.10G 4.90G 96K /zvol/henry/CQFsync zvol/henry/CQFsync/subvol-100-disk-0 3.10G 1.90G 3.10G /zvol/henry/CQFsync/subvol-100-disk-0 This...

Hi all, I discovered the SSD that my node was running on was failing. I reinstalled PVE on a new disk, and was able (with help) to recover my container and all seems well. Cheers guys

Solved! Somehow the mountpoint size parameter was erased in the config file buried in the tar.lzop container backup: /etc/vzdump/pct.conf I then added the line that oguz suggested to the config and then used tar --lzop -cvf /containername.tar.lzop <container root> Then I just restored in...

Ok I have found what I believe is the conf file in my tar.lzo backup, and I made the correction you suggested... /etc/vzdump/pct.conf But now I am having a hard time re-creating the archive, I have tried tar -cfvz /tmp/vzdump-lxc-123-2018_12_31-13_30_08.tar.lzo ./* and tar -cfv ./* |...

I only have the dumpfile so I wont be able to restore in order to backup again. But thanks for the heads up, I have no idea how that parameter got lost... I'll watch that doesn't happen in my next backups. Thanks

*edit - for whatever reason this message just stopped on its own, after adding GPG keys for another unrelated source.

I modified /etc/apt/sources.list as outlined here. Still, I end up with this nuisance message: Reading package lists... Done E: The repository 'https://enterprise.proxmox.com/debian/pve stretch Release' does not have a Release file. N: Updating from such a repository can't be done securely...

Doesn't matter where I attempt to restore it. Gives me this error every time. TASK ERROR: unable to detect disk size - please specify mp2 (size) Config: arch: amd64 cores: 8 hostname: uni-plx-sync memory: 4096 mp0: torrent:subvol-123-disk-1,mp=/media/torrent,size=400G mp1...