Recent content by twentytwo

I am not sure if I follow, what I have so far is remove bak and backUP from Storage. Next step is to rm mnt/bak and mnt/backupz?. I could not use umount becuase these are not mount which I assume I unmounted previously via Storage? Do you mean unmount /dev/sdd1 and mount it again and what...

Okay but I realise double forward dash and too many backup folder names due to my mistake. How can I remove BackUP from Storage and modify bak to Backup and change the path target from /mnt/bak to /mnt/backup/dump ? Will these delete my backups files? Sorry for asking dumb questions

I try to restore first backup file and stop. Not sure what the exit code 133 mean? estore vma archive: lzop -d -c /mnt/bak/backup/backup//dump/vzdump-qemu-100-2020_02_28-08_59_12.vma.lzo | vma extract -v -r /var/tmp/vzdumptmp15486.fifo - /var/tmp/vzdumptmp15486 CFG: size: 684 name...

I found the backups files which is located in bak - backup - dump, whats the next step?

I cannot provide the log as I have start fresh installation and the vzdump backups saved in /dev/sdd. I tried to mount it and when I view the content which is empty.. How to I find out if I have any data on that drive?

After I typed this lsblk -o +FSTYPE,UUID /dev/sdd* The result are here sdd 8:48 0 3.7T 0 disk └─sdd1 8:49 0 3.7T 0 part ext4 d8871cd7-11b1-4f75-8cb6-254a6120 72f6 sdd1 8:49 0 3.7T 0 part ext4...

Hi, My Proxmox played up and decided to do fresh clean installation, I have VM backups on dev/sdd (Spinning Disk) and want to know how can I mount the existing disk that has backups on it to Storage so that I can hopefully perform the restore method to get my VMs back. Can anyone assist me to...

This error appears after I restart the server and Windows 10 VM are not responsive, couple of programs that I use for work does not work. Could anyone help me diagonse this problem. I have plenty of space on my hard disk so it has be something else that I am not aware of.

Output Scenario 1. Spinning drive working on USB2 port -------------------------------------------------------------------- /usr/bin/kvm \ -id 102 \ -name Production \ -chardev 'socket,id=qmp,path=/var/run/qemu-server/102.qmp,server,nowait' \ -mon 'chardev=qmp,mode=control' \...

I plugged external drive to USB1 which is USB 2 port which picked up the drive. I plugged USB 3 16GB into different USB 3 port after shutdown the VM and edit USB3. Tried that with the drive without success. Shutdown the VM again and plug the 16GB into 3.1 USB which is the supported by the...

Here is the config of the VM agent: 1 balloon: 0 bios: ovmf bootdisk: scsi0 cores: 4 cpu: host efidisk0: local-zfs:vm-102-disk-1,size=128K hostpci0: 02:00,pcie=1,x-vga=1 ide2: none,media=cdrom machine: q35 memory: 15000 name: Production net0: e1000=62:3D:19:4F:7F:0C,bridge=vmbr0,firewall=1...

Do you think it is relate to lack of wider USB 3 device support or possible solution via file modification like 100.conf to enable those USB device that I mentioned?

I tried the methods that you suggested and Vertatim USB 3 16GB I plugged, got recognise but Lexar USB 3 and Unitek Y-3035 Hard Disk Enclosure USB3.1...

I am currently running version 6.1-3 and yes I did checked the "use USB3" checkbox

Thank you SG90, your solution works!