Recent content by JL17

Ok thanks for your help!

can I change the driver in the file-restore?

/dev/loop0p1 on /mnt/test type fuseblk (ro,relatime,user_id=0,group_id=0,allow_other,blksize=4096) Mounts ok using that commands, I can acces all the files. The problem is when I try to do a "file restore" from GUI

Using this commands: proxmox-backup-client map vm/101/2024-01-10T07:15:12Z drive-virtio1.img --repository root@pam@192.168.1.2:8007:bk1 --ns jls ls -lah /dev/loop0* mkdir /mnt/test mount -r /dev/loop0p1 /mnt/test ls /mnt/test/

Hello, i have the same problem with an NTFS disk backup. If I try to do a "file restore" from GUI, i get the message: mounting 'drive-scsiXX.img.fidx/part/1' failed: all mounts failed or no supported file system (400) The file-restore log (/var/log/proxmox-backup/file-restore/qemu.log) show...

Hello. Have the same problem as described on post #1. Workarounded following @Whatever instructions. Added mitigations=off on the end of /etc/kernel/cmdline (not "cdmfile" in my case) and disabling KSM using systemctl disable --now ksmtuned Steps made: 1. nano /etc/kernel/cmdline ->...

Thanx for the info Fiona! Very usefull

Hi fiona, this grub bug yo mention persists on proxmox v8? Is there any workaround to avoid the bug? Thanx in advance!

+1

Same question here. Cannot find any configuration option to retry backups when fail

Sorry i forgot to mention that i am on ZFS. Found the soluition here: https://forum.proxmox.com/threads/disable-spectre-meltdown-mitigations.112553/ nano /etc/kernel/cmdfile (change this line) root=ZFS=rpool/ROOT/pve-1 boot=zfs mitigations=off proxmox-boot-tool refresh reboot Thanx everyone!

thanx! This works!

thanx for your answer! did it but the warning stills there: changed this line on /etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT="quiet mitigations=off" made update-grub and reboot, but the warning persist. Maybe i did somethjing wrong?

can this warning be disabled?

Thanx bbgeek! you pointed me in the right direction, I had to stop the VM, remove the original volume, renaming snap with same name as original and give it RW permissions. I leave the commands that I used in case someone is in the same situation: lvremove pve/vm-202-disk-0 lvrename...