Search results

Why does it need to be upgraded via backports? I have upgraded it without having them. I am not questioning your knowledge, just trying to understand why. Thanks!

root@pm1:~# dd if=/dev/zvol/almacen/vm-108-disk-0 of=/dev/zvol/almacen/vm-155-disk-2 67108864+0 registros leídos 67108864+0 registros escritos 34359738368 bytes (34 GB, 32 GiB) copied, 646,636 s, 53,1 MB/s The disk is sbd but doesn show any partition

done as we said, when mounting the drive it said "mount unknown filesystem type '(null)'"

So if I understood correctly: 1- Create VM 2- Create new zvol 3- dd if=/dev/zvol/almacen/vm-108-disk-0 of=newzvol 4- Mount new zvol to new VM Is that right?

You can move zvols by using "zfs send | zfs receive". I would only work with the copy to rescue stuff so you don't do more harm to the zvol. Do you mean I could create a volume and mount it to extract data? Please laborate and THANKS A MILLION!

ok thanks

Done it with no errors... I am pretty desperate to get the data back from that machine and it got corrupted after a reboot

For some reason the VM got corrupted and I was trying to see if I can mount it somewhere to recover the data What can I do in this situation?

ZFS LIST will return the below but when I go the directory only subvolumes are present. Where are the vm disks?

LACP bond works flawlessly. I am about to set the MTU on proxmox to 9000. Any tips on how to do so?

When you say both sides, do you mean the mikrotik switch as well? Beacuse I had a bond on mikrotik side with balance-rr too. I have just changed mikrotik and proxmox to LACP bond. Lets see what happens

Believe it or not I have managed to fix the issue after talking to you. I was pretty sure the problem was on the network and I have tried so many different settings on Mikrotik side but I had never considered proxmox bond could be the problem. And it was! As soon as I destroyed the bond it...

I have not tried to modify the bond, the idea was to expand the bandwidth. Do you think this could be an issue? Here is the log, from the time I rebooted the server till I started moving the disk and failed Dec 04 13:57:09 PMXNODE1 sshd[2689]: Accepted password for root from 10.28.0.1 port...

System topology Hypervisor: Proxmox 6.3-2 | 2x 10Gb bonded (balance-rr) Switch: Mikrotik 10Gb receives to a bonded port (also balance-rr), transmit hash policy Layer 2 and 3 Storage: Dell ISILON Protocol: NFS I am completely frustrated after 3 days of troubleshooting with no luck, please help...