D dawei New Member Apr 25, 2022 3 0 1 Apr 25, 2022 #1 According to the old post, I learned that the problem was being repaired in 2018. I want to know whether there is a suitable solution now Last edited: Apr 25, 2022
According to the old post, I learned that the problem was being repaired in 2018. I want to know whether there is a suitable solution now
F flotho Renowned Member Sep 3, 2012 82 4 73 Dec 3, 2022 #2 Hi, working with latest v7 up to date on a cluster with ceph and running an ansible script for stopping then deleting ct, I also get this error. Did you found any tips ?
Hi, working with latest v7 up to date on a cluster with ceph and running an ansible script for stopping then deleting ct, I also get this error. Did you found any tips ?
F flotho Renowned Member Sep 3, 2012 82 4 73 Dec 3, 2022 #3 by the way I'm using the proxmox modue and not the CLI inside proxmox
N n0bie Member Dec 28, 2021 69 2 13 37 Sep 19, 2024 #4 do we get solution for this case? yes i face this issue until now, running proxmox 7.4 yes i am using proxmox module from modulegarden latest version. this make the disk left as "orphan disk"
do we get solution for this case? yes i face this issue until now, running proxmox 7.4 yes i am using proxmox module from modulegarden latest version. this make the disk left as "orphan disk"
