Search results

yes, keep close to baremetal. so no another cache like writecache. DB shouldn't be corrupt but I don't want to be fired in production.

it's another bug with the installer, updating only scsi driver from Windows Device Manager is enough to fix it.

are both disks checked in boot order in VM options ?

it's not PVE specific , Hyper-V is same. I've done some fast tests with CrystalDiskMark , as worst case Q1T1 then max IOPS Q32T16 : https://forum.proxmox.com/threads/disk-speeds-inside-a-vm.157684/post-725631

It's not PVE specific , I've just done some test with CrystalDiskMark (worst case Q1T1 then max IOPS Q32T16 ) Hyper-V is equal. Tried on VMware Workstation too, little better, Reads even better but I guess a cache fake it. Screenshots attached. on HPE DL20 Gen11 / 1 x SATA SSD 480GB HPE Read...

it seems OP shutdown from PVE because hang occured during reboot initiated within guest. as VM hang, gracefully shutdown from PVE can't be honored. a screenshot of console would have helped, perhaps the next time.

weird, it shouldn't, as VM has only virtual HW, software doesn't know anything about physical hardware or hypervisor updates, perhaps fails because another trigger.

where hang ? screenshot of console help. is backup done to PBS ? pve version ? kernel version ? host rebooted if updated ? (why Win2k in title ?! remove it)

what disk model in old and new ?

no, virtio block is another driver, which currently missing io thread. fix here is for virtio scsi driver, used when vdisk attached as scsi + scsi controller set to virtio scsi single.

#9 https://forum.proxmox.com/threads/windows-guests-prompting-safely-remove-hardware-for-critical-devices.17490/post-586107

check disk manager from the bare metal host. Windows server software raid used ?

have you read the GitHub link ?!

https://pve.proxmox.com/wiki/Renaming_a_PVE_node + do not set hostname as public domain name.

switch / attach vDisk as SCSI with controller set to Virtio SCSI Single. "inject" / install virtio scsi drivers with dism command. Don't forget to use version v266 which fix hang when high iops. Like https://gist.github.com/TomCan/9644966 Reboot once to Safemode can help if first reboot doesn't...

we are agree. it seems more a wording problem than a wrong assertion.

Not fully understand as I'm not English, but 'saves on disks writes' are done indirectly, because cache optimize data before write cells.

I mean speed up volume(s) ONLY on writes : sync writes and small writes, thanks to DRAM cache of the RAID controller protected by battery.

it's not, but there is necessarily a cache when there is PLP

RAID cache accelerator protected by battery speed up even a single disk without RAID. it's seems you haven't tried yet a SSD PLP enterprise. I can't write correctly in English to more explain, keep search and read, myself understand the point after many weeks if not months.