Search results

I've created a privileged container, just to test if I can do nfs with it, but now I need to delete it, but unfortunately I cant' I am getting this error: is there a different way or command that I can use to delete a privileged container? I'm running: Linux px3 5.4.44-2-pve #1 SMP PVE 5.4.44-2

Sorry for the late reply. No restoring also show the same problem. we are able to fix the partition of the VM.

@Alwin - is it possible to just clone the existing SSD drive with another SSD drive, then replace it with that clone ssd?

My I ask how to do backup of the partition table? this will be a big help.

Yes

One of my SSD is at 24% wearout this one if my Ceph(DB) and pretty much soon when it reach 75% wearout I want to replace it. my I ask on how to replace this properly? without causing damage to my system.

any solution on this? I am experiencing this same issue right now and couldn't find a solution to this.

I experience the same problem today, several VM’s that I have is keep on rebooting and says no bootable drive.. The last thing that I did was to create a backup. I have tried to restore from back up and also end up with the same result. my backup is from a nas server that I mount to my proxmox...

I have a domain within my proxmox network, but when I tried to ping it within the proxmox network, I can't ping this domain. but pinging that domain from outside proxmox is not a problem all works well. I don't have firewall installed on this centos container. other domain inside can be ping...

Thank you that solve it.

We upgraded our proxmox from 5.4 to 6.1.5, so far some of the issue we encounter has been solved but one that we can't solve. And from Luminous to Nautilus We got a Health_warn that says the time frame is still the same even if we restart the monitor Also in our logs when we are restarting...

is it possible to back-up VMs to a NAS server? If yes, is there a way where the back up goes directly to the NAS server? We are using ceph rbd, not cephfs, so we can't see individual files.

@tom - so this means I need to put up a scheduling for scrubbing, right?

is it possible to update corosync only without any problem? I am not planning to upgrade to 6 yet until I got my back up server up for this.

bumping on this

anyone? any idea?

is it possible for proxmox to keep on scrubbing? I mean after one cycle of scrubbing then it start scrubbing again. from regular scrubbing then to deep-scrubbing. we have osd.0 to osd.14 then after a while then after a while another one and a lot of this in between this has been going...

any suggestion?

whenever I have a VM/CT on HA and something came up, we always have this problem starting a vm/ct, so we have to remove it first from the HA before it is able to start normally again. Requesting HA start for CT 140 Unable to create new inotify object: Too many open files at...

anyone