Search results

thank you for responding. Here is your requested info: dir: local path /var/lib/vz content backup,vztmpl,snippets,iso shared 0 zfspool: local-zfs pool rpool/data content rootdir,images sparse 1 zfspool: CTdisks pool TANK/proxmox/CTdisks...

Where is my file? I have a VM with disk: VMdisks:vm-201-disk-0,size=32G I check VMdisks storage and see the disk in the list(only VM running at the moment so just that one. I check datacenter storage for location which is a ZFS type. TANK/proxmox/VMdisks I do a zfs list | grep VMdisks and...

it might be related to the formatted target. I mounted a second disk, this time EXT4 formatted and backing up VM's worked. The non working one is exFAT. When i check the automounts on libreelec i get: The non working one: /dev/sdb1 on /var/media/Harro type exfat...

I reinstalled to 7.1 and problem persists. Same error for backing up a VM. ERROR: Backup of VM 201 failed - unable to open '/mnt/pve/BackupVMenCT/dump/vzdump-qemu-201-2021_12_04-13_57_42.tmp/qemu-server.conf' at /usr/share/perl5/PVE/VZDump/QemuServer.pm line 210. INFO: Failed at 2021-12-04...

Im not sure if its related to my topic at all anymore. Maybe update-initramfs -u -k all broke more then i ever imagined, even a zpool on secondary disks? I found out the following: 1. disconnecting 4 sata disks(software zfs raid10) makes proxmox boot correctly. 2. reconnecting them lands on...

thank you for your reponse! that sounds like pretty tough. Is there some guide available about this? Its all new stuff for me to digest. Ill go and make me a 6.4 bootable usb stick.

i rebooted and tried the older kernel .128 but same problem. update-initramfs -u -k all -k all flag broke both kernels? any way to undo my actions?

I have yet to reboot a second time. I have raid1 zfs as boot and a zfs 4 disk raid10 as storage. I might have choosen the wrong file to edit since I have a bios and NOT uefi. /etc/kernel/cmdline contained 1 line regarding zfs pools I think

Hello, I wanted to add a GPU to my box and decided to take the plunge to attempt to enable passthrough and it failed. Im on the latest 6.4 proxmox. My steps: 1. added intel_iommu=on to nano /etc/default/grub making it GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on" updating grub gave me...

i have made regular dirs from the folders inside /TANK/shares and moved the contents to it. I can now read/write to them as Harro:Harro. So its def related to ZFS.

Your manual CIFS mount worked. Its a quick fix though

Hey, I have a user called Harro:Harro with uid:gui 1000:1000 on proxmox host as well as exactly the same inside a container. I can map the ID's fine and user Harro can read/write on the host via a mountpoint. The LXC is privileged. Something i dont get: mp0...

It's super weird. Résumé. 1. I can mount an USB disk on a raspberry pi over cifs and read write to it from proxmox shell. 2. Lxc backups to that disk work. 3. VM backups don't work

/mnt/pve/KodiSlaapkamer/dump/vzdump-qemu-201-2021_11_05-10_14_07.tmp/qemu-server.conf is the the long string and/or illegal characters?

I just remounted a cifs again to the same raspberry pi, but now i choose a different dir (just something accessible on the SDcard) and the VM started backing up! So unfortunately in my case its something related to that USB disk connected to the raspberry.

Nice to know it might not be related to Libreelec. Its a trimmed down mediacenter OS of Kodi running on a raspberry pi in the bedroom, hooked up to the TV. I have a 5tb disk connected to it trough USB. Its worked before, now it doesnt.... ill go check out your solution thx!

Thx. So it might be some mismatch of SMB versions? I've been backupping to Local storage for vms... Is your backup also a Kodi/libreelec install?

Yes its in the zfs list command In a working running LXC container (those working from backup) and i can browse the mountpoint + subdirs + files just fine. They are all Harro:Harro. In fact i can name the user inside the lxc whatever i want (www-data for nextcloud) as long as the IDs match with...

I have lxc mapping issues as well, stated here: https://forum.proxmox.com/threads/lxc-idmapping-host-container-newlt-created-files-work-old-files-not-visible.96593/#post-418660 But even when try a fresh lxc for debian 10 and also 11 and booting them gives me this. Apart from the many errors on...

Hey, I had to reinstall Proxmox 6.4 due to failed upgrade to 7. I pulled the lxc containers from backup and got them running, with proper lxc mappings as before. NEW LXC containers behave weird. Inside a fresh LXC ubuntu: (Harro is my name) groupadd -g 1000 Harro useradd -u 1000 -g Harro...