Search results

root@ORACULO:~# qm config 103 agent: 1 boot: order=sata0 cores: 4 cpu: host ide2: none,media=cdrom memory: 4096 meta: creation-qemu=6.2.0,ctime=1660485287 name: VIDEO net0: virtio=9E:2D:00:BA:03:92,bridge=vmbr2,firewall=1 numa: 0 ostype: l26 sata0: HD-VMs-1:103/vm-103-disk-0.qcow2,size=1T...

Message: No bootable disk found.

Hi, same problem in my server. After update for version 7.3.3, my VMs dont start anymore.. Helpme...

After I shutdown a VM it won't boot again if I don't restart the server. No idea where or how to look for a solution. Before update version 7.3.3

Guys, I got it here. Very simple, after installing PBS, don't restart the server, just install ifupdown again and that's it, then restart and everything will be working in Azure. I want to use Azure to do my backups and I'm going to schedule it to stay on only at dawn, so I spend less. Enjoy.

Hello friend, I'm trying to do the same thing, but it's with the PROXMOX BACKUP SERVER. I can install on Debian on Azure, access the panel and everything, but when I restart the server, I lose access to the panel and SSH, I believe it is something related to ifupdown Can you help me?

Hello colleagues. I'm putting a Proxmox server into production, at the moment it doesn't have any VMs installed, it's not being used yet. It's located in a Datacenter in Germany and there's a problem that I can't solve. I've already reinstalled Poxmox more than 5x and it didn't help. It is...

same problem, but my server is localhost, fisicaly... please helpme!

OK, very thanks...

I see, I already requested the purchase of a new SSD. But I leave here my huge thanks, your help was really of great value. Thank you so much for the goodwill! You were phenomenal.

root@oraculo:~# smartctl -t long /dev/sdb smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.13.19-4-pve] (local build) Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org === START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION === Self-test functions not supported Sending...

Any command I use to format the partition always gives an error like this, see: root@oraculo:~# fdisk /dev/sdb Welcome to fdisk (util-linux 2.36.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Command (m for help): d Selected...

Okay, but this disk is just the storage of the VMs, but when doing that, it gives this error in the GUI: error wiping '/dev/sdb': 209715200 bytes (210 MB, 200 MiB) copied, 2.21614 s, 94.6 MB/s

This disc: sdb 8:16 0 447.1G 0 disk └─sdb1 8:17 0 447.1G 0 part

Now how do I format my other SSD HD and prepare it so I can restore my VMs?

UAU MAN!!!! Perfect!!!!!!

Dont work: root@oraculo:/mnt/HDD/BACKUP_1/dump# pvesm add dir HDD --path /mnt/HDD/BACKUP_1 --is_mountpoint yes --content backup create storage failed: unable to activate storage 'HDD' - directory is expected to be a mount point but is not mounted: '/mnt/HDD/BACKUP_1'...

Ok, I understand, how do I format my 500GB SSD disk and mount it again in PROXMOX? Then I will restore my backups on these disks.

root@oraculo:~# cd /mnt/HDD/BACKUP_1 root@oraculo:/mnt/HDD/BACKUP_1# ls dump images root@oraculo:/mnt/HDD/BACKUP_1# cd dump root@oraculo:/mnt/HDD/BACKUP_1/dump# ls vzdump-qemu-100-2022_02_16-22_00_02.log vzdump-qemu-101-2022_02_18-23_00_02.vma.zst vzdump-qemu-102-2022_02_21-21_00_02.log...

root@oraculo:~# find /mnt/HDD/ -name "dump" /mnt/HDD/BACKUP_1/dump root@oraculo:~# I didn't quite understand what I did, but I followed your step by step. But HD BACKUP_1 still doesn't appear in proxmox console.