Hi
I have downloaded the most recent version of the Kali 64bit Virtualbox VM.
What is happening is the VM will be running for a couple of hours.
Then I'll try to save something or create a file, and get an error that the filesystem is now read-only.
I reboot the VM and after the grub page, It goes straight to the initramfs shell (ash I believe).
Here, I am told their are errors with /dev/sd1 and I need to run fsck manually.
I can do this and it temporarily fixes the issue, but it always reoccurs.
The initramfs temporary fix goes like this:
(initramfs) fsck /dev/sd1
press 'y' to a host of questions
(initramfs) exit
I can then reboot the system again.
- I am running the VM on an NvME SSD, on a new host system. Bought just a couple months ago.
- I don't have any problems with the SSD in any other context, and this has now happened on a separate HDD too.
- I have tried ticking the 'Solid State Drive' checkbox in Virtualbox while using the SSD, but it slows kali down horribly
- This problem only started in the last week, originally with a completely different kali VM. It's why I downloaded the most recent one,
and did a fresh install. Perhaps this indicates a Virtualbox config change.. though I don't recall making any.
Can anyone shed light on this for me? I haven't had much luck googling as yet.
Thanks for reading
