I was using a guide in order to create a basic Jira plugin as sort of a experimental/hands-on way to get comfortable and familiar with the Jira SDK and with creating plugins regarding Listeners. I am running Ubuntu on a VM, and I followed all the steps included in the guide. My VM started to freeze, and I thought it was maybe Jira at first but now I know there is something wrong with the VM itself. I get this error:
An error has occurred during virtual machine execution! The error details are shown below. You may try to correct the error and resume the virtual machine execution. The I/O cache encountered an error while updating data in medium "ahci-0-0"(rc=VERR_DEV_IO_ERROR). Make sure there is enough free space on the disk and that the disk is working properly. Operation can be resumed afterwards.
The details say:
fatal=false, errorID=BLKCACHE_IOERR
I looked into the log file and this is right where it goes wrong/throws an error:
00:01:06.499361 I/O cache: Error while writing entry at offset 102912000 (110592 bytes) to medium "ahci-0-0" (rc=VERR_DEV_IO_ERROR)
Not really sure what to do. I have important stuff in the VM and I really don't want to set it up all over again.
So, while in scaled or full screen mode inside VirtualBox installed on Windows, you need to press Right Ctrl + C key combination to exit scaled mode.
When the keyboard and mouse input is captured in the virtual machine, you cannot move the pointer out of the virtual machine window and all keystrokes and button clicks go to the virtual machine. To release the keyboard and mouse back to the primary OS, press Ctrl+Alt.
To exit seamless mode, just press the host key and L again. You'll also find a VirtualBox menu above your taskbar, which you can hover over to view. Click View and select Switch to Seamless Mode again to disable seamless mode.
The solution is simply to enable the cache I/O host. It can be activated in the configuration of the machine, Storage »SATA Controller" Use the cache I/O host (all other values are those used by default VirtualBox). After this change the error disappears
I ended up finding a fix with the help of antiduh:
I cloned my old vdi into a new vdi using: VBoxManage clonehd Linux.vdi LinuxClone.vdi
Once that happened I opened up VirtualBox and created a new VM and when it came to the Hard Disk section, instead of creating a new virtual disk I selected my existing LinuxClone.vdi file and when I started it up, it ran! I got the idea from this article.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With