Search results

  1. A

    [SOLVED] No space left while recovering

    Okay, finally i solved it. Reason was that the backup made by the Proxmox 3 was really strange. I found that the disk size of my virt was 20G and backup is bigger: /dev/loop6 20G 20G 0G 0% /var/lib/lxc/107/rootfs this is quote from watching df -h at moment when error appeared...
  2. A

    [SOLVED] No space left while recovering

    [ Thu Jan 07, 10:46:09 | root@yls2:~ ] # pct restore 107 vzdump-openvz-107-2016_01_05-14_22_06.tar.gz --storage YLS2D0 Formatting '/mnt/pve/YLS2D0/images/107/vm-107-disk-1.raw', fmt=raw size=21474836480 mke2fs 1.42.12 (29-Aug-2014) Creating filesystem with 5242880 4k blocks and 1310720 inodes...
  3. A

    XenServer 6.2 to Proxmox migration -- windows, black screen

    Just the same problem and options. Only diff in that when i disable KVM support - the machine boots well (but very slowly). I am trying my best magic with google for several hours and still have no decision. I see the problem starts after the SeaBios POST - while trying to access HDD, - i see...

About

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!