Search results

@Onslow : this seems effective. So I need to upload this ISO image to the node first, then attach it to the VM, then boot on this image, right? @leesteken : shame on me, I don't have any backup! I was actually reorganizing the VMs and planned to make a backup after that... Karma stroke first...

Dear Community, I struggled last week-end to restart a VM which stopped during a power outage (this is running on a homelab server). I manage to open the Proxmox application once the power is back but the VM (OpenMediaVault) cannot restart and display SELinux : could not open policy file...

Thanks to all of you! I applied the above procedure this morning and all went pretty well!

OK, got it!

Thanks guys! Actually, what is surprising is that I managed to copy the whole disk-1 content as it was a genuine HDD some weeks ago! It means, at that time (and I blame on myself for not remembering how ‍♂️), I found a path to the disk and launched a common cp command to backup all data. I...

Thanks for your quick answer! Here are the outputs: qm config 100 agent: 1 balloon: 4096 boot: order=scsi0;net0 cores: 4 memory: 8192 name: OMV net0: virtio=52:45:69:61:DE:CC,bridge=vmbr0,firewall=1 numa: 0 onboot: 1 ostype: l26 scsi0: data:vm-100-disk-0,size=88G scsi1...

Dear Community, I have a OpenMediaVault VM with 2 disks, the second one being used for media storage. I've changed this for an external USB drive (being able to share the drive with friends) and I now want to reduce the size of the vm-100-disk-1. Is there any method other than removing and...

Hi all! I'm reviving this thread as I'm seeking additional advises. I gave up trying to understand why the previous 'backups' volume is not accessible anymore (due to some issue during a node renaming operation), but I'd like now to recreate the missing volume. Here's the context: The PVE...

OK, thanks Fiona for all your efforts! One last question: do you have any idea if reverting the renaming process could help solving the issue? Thanks for any help!

Hi Fiona, Did you manage to have a look at the PBS log files? How can I restore the datastore1 usage within PVE/PBS? Thanks in advance for your help!

Apart from the renaming operations, I didn't change anything either on PVE or PBS as all I wanted is to retrieve some VM backups and import them into the second node ("move VMs")... Here is the PBS logfile at the same date: https://we.tl/t-6VrXkY6he9.

Thanks Fiona! Here's the logfile: WeTransfer https://we.tl/t-lXZXjuzhcD, I hope you'll find some clues therein as the file is pretty huge!

Hi Fiona! Can you please tell me exactly which files could be helpful? All I find is a /var/log/pve/tasks folder with tens of logfiles in it, whether for PVE or PBS... Is there way to fix this? Thanks for your help!

Yes, this folder is empty on the PBS server. Actually, there's a /mnt/datastore/backups folder on the PBS server, and a /mnt/pve/backups folder on the PVE, so I may has mistaken one for the other. However, both are totally empty (ls -al). It seems some operations were correctly performed in...

Surprinsingly... root@pbs:~# ls -al /mnt/datastore/datastore1 ls: cannot access '/mnt/datastore/datastore1': No such file or directory I SSHed into the PBS server and confirmed there's no datastore1 folder. There's however a 'backups' folder, but it's empty. This folder was normally used by...

Hi Fiona, Here's the output of the various commands you requested for PVE, probably too much... root@pbs:~# cat /etc/proxmox-backup/datastore.cfg datastore: datastore1 comment gc-schedule daily path /mnt/datastore/backups/datastore1 root@pbs:~# lvs File descriptor...

Hi Fiona, thanks for the information! I suspect sde1 is a USB disk which is used by a VM as a video files storage (Open Media Vault), so I won't bother you with this... Regarding PBS: The fingerprint has the correct value in storage.cfg. PVE is able to ping PBS. The datastore cannot be...

Thanks Fiona! Here's the command output: root@LAB-server1:~# lsblk -f NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT sda ├─sda1 │...

Hi @fiona, Here the outputs for the commands above: root@LAB-server1:~# pveversion -v proxmox-ve: 7.4-1 (running kernel: 5.15.158-2-pve) pve-manager: 7.4-19 (running version: 7.4-19/f98bf8d4) pve-kernel-5.15: 7.4-15 pve-kernel-5.13: 7.1-9 pve-kernel-5.4: 6.4-4 pve-kernel-5.15.158-2-pve...

Hi all, Any advice on this issue? Is there any way to "reattach" the backups + local-lvm volumes to the new names? Thanks in advance for any help!