Search results

hey, falls du chrome verwendest kannst du mal das addon "allow cors:access-control-allow-origin" probieren. das hat bei mir zumindest bei anderen projekten geholfen bei denen ich den fehler hatte, wobei ich dir nicht sagen kann was genau das macht :confused: soweit ich das verstanden habe ist...

hey, thanks for your answer. i just solved my problem by switching to 4tb ssd's instead of the 1tb samsung 960 Pro's. there my used space jumped from 885gb to 1.69tb, so well over the usable space on my smaller drives. kinda unfortunate, but it is what it is :)

Update2: Still not able to migrate, even from the second disk, so it's not because of raid settings.

Update: Moving the disk to another internal hard drive (also 1TB) of machine one works - it just refuses to send it to the other machine somehow.

if I was you I'd first make a backup of the disk using dd or clonezilla or something like that. then id try what Aaron was suggesting, but on the backup, so you don't damage your data any further. if you can't restore anything - which is sadly a pretty high chance depending on the settings you...

hey, the setup you suggested should be ideal, because the main io for the vm happens on its disk and not on the disk for the host. In theory, only using the m.2 should be slower because you take away bandwidth that could be used for the vm

Hey, I am migrating from CentOS to proxmox and have a problem setting up my storage: I've got two machines, each with 2* Samsung 1TB SSDs (mirrored), both running Proxmox. I've got one VM with a 800GB raw image on machine one and want to replicate it onto machine two. So I first set up the zfs...