6/10/2023 0 Comments Extfs windows blockedIs it possible that the nerwer mod to the kernel that vmware does doesn't handle this new kernel and SSD hardware correctly?Īs I said, I did a "touch /forcefsck" and rebooted. I had tried out running a Windows 10 instance on vmware workstation a year ago, on debian 10 for a couple of weeks, and never got these errors at the time. My current debian is 11.4, with uname showing the kernel as " 5.10.0-16-amd64 #1 SMP Debian 5.10.127-2". The disk is barely a year old, and I have seen no anomalous behavior with any other apps. smartctl shows the " Percentage Used" as 1% so that's light wear. The output of a " smartctl -a /dev/nvme0" is attached (rather lengthy to put inline.), along with the output of " nvme error-log". Product: NVMe SSD Controller PM9A1/980PROĬapabilities: storage pm msi pciexpress msix nvm_express bus_master cap_list My disk description from a " lshw -class disk -class storage" shows as:ĭescription: Non-Volatile memory controller ![]() I get about 20 error dialogs during the boot of the virtual Windows instance. blk_update_request: critical medium error, dev nvme0n1, sector 821085720 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0Īug 13 11:47:40 debian kernel: blk_update_request: critical medium error, dev nvme0n1, sector 82ġ085720 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 The main system partition (/) a partition layout is attached, along with the error message. The system appears to work when Continues are pressed perhaps if there is an under-the-hood setting for getting vmware to apply that response by default, maybe that could be a triage solution. But again: I'd rather just get vmware workstation pro to work. If I am given the nebulous advice of just creating another vmx, with all the Microsoft keys I would have to reenter, I'd sooner take my chances with qemu. I considered getting paid support incidents, but that will be insane if it cannot be fixed! (because it's debian 11 or whatever.) I am evaluating your product I really want to get it. ON TOP OF THAT: I did a "touch /forcefsck" and rebooted, to make sure it was not due to a filesystem error on the linux platform itself. vmdk" from the linux platform to make sure that wasn't corrupt. Given that the error indicates a disk error, in Windows I did a "chkdsk /f", rebooted, did a whole lot of Continues (!), then after reboot also did (as administrator.) the following to make sure this was not due to a misleading error due to missing components:ĭism /Online /Cleanup-Image /RestoreHealthĪlso did a "vmware-vdiskmanager -R. Observation: why can't you just have an ability to set a default response, like Continue, so it reports all disk errors to the virtual operating system? (if that's what they are.) ![]() If I persistently attempt Continue, it moves forward with the boot of Windows 10. If the file resides on a remote filesystem." error, with the choices of Cancel, Continue, and Retry. I am getting the infamous "The operation on file.vmdk failed.
0 Comments
Leave a Reply. |