Hello everone!
I have a dedicated server in a Datacenter in Germany.
It has 256GB of RAM and 4 disks of 16TB (64TB)
I'm wanting to use this server only with a VM, an email server.
How do I make this single VM use all disk space?
That is, all 64TB?
Hi,
Yes, I checked and the MBR is destroyed.
And worse, the backups made by PBS end up making backups with the MBR destroyed.
That is, the backups are also being affected.
I'm trying to install the new virtual machine and I'll have to reconfigure the whole VM.
What astonishes me, due to the...
So you can have an idea of the size of my problem.
The server that gave the problem is a file server, and I only have 3 backups of this VM, a 2.4TB VM.
In addition to the delay in restoring this vm from PBS, I still run the risk of the 3 backups being damaged with this error in the partition...
Hi,
Masi a VM, from another server just gave the same problem.
Now a Windows Server VM.
It doesn't boot anymore.
I put the disk in another working VM, and there is no more partition on the virtual disk.
That is, the problem is happening caused by PROXMOX BACKUP, for some reason it damages...
Hello my colleagues.
I have an ASUSTOR NAS with 1 16TB disk.
I wanted to use it to receive the backups made by PBS.
But I don't know how to add this folder on my NAS to PBS.
Can you help me ?
I think you did not understand me.
Look in the video, I recorded an old VM (before the update) and a new VM (after the update.
This MACHINE option is different.
https://www.youtube.com/watch?v=iFtQ27ubz7s
One thing I'm fixing right now.
In a newly created VM, in HARDWARE in the MACHINE config it is like MACHINE= q35
And on VMs that are older than PROXMOX 7.3.3 the MACHINE field is pc-q35-7.0
But I can't switch to LATEST (this LATEST option only appears for the new VMs I installed after I...
Look here, I recorded the screen for you to see the error.
I thought it was only happening with Linux VMs, but now I see that with Windows VMs too.
And I don't know where to read the logs to see what this error is.
https://www.youtube.com/watch?v=gk2prYCH2gE
hello guys, another VM stopped working.
it dawned stuck, so I had to run the kill -9 command on the VM service to force it to stop.
and now when I start it, the boot says that there is no disk to boot.
wow, I'm getting discouraged from this PROXMOX, for so many years it ran very well, now...
hello guys, another VM stopped working.
it dawned stuck, so I had to run the kill -9 command on the VM service to force it to stop.
and now when I start it, the boot says that there is no disk to boot.
wow, I'm getting discouraged from this PROXMOX, for so many years it ran very well, now...
don't remember exactly which version it was, otherwise I'm mistaken it was the penultimate version.
I already did that, I compared a VM that is OK, with the one that doesn't boot anymore, but the two are identical.
Look, if I install a new Ubuntu Linux VM, then yes, it can boot normally.
That is, I lost my other VM, it does not boot at all after I updated to PROXMOX 7.3.3
All my Linux VMs won't boot anymore.
But if I install a new VM, it boots normally.
I've never really seen this happen on PROXMOX.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.