I have 3 different Ubuntu VM's and since upgrading to Sonoma they have experienced file system corruptions which prevent them from booting. I do have snapshots enabled and can roll back but it keeps happening randomly. Anyone else experiencing this? I have another thread in the Windows section about Windows 1 getting file system corruptions The strange thing is I have Red Hat, Rocky, Alma, Oracle and Fedora VM's that haven't had this issue happen to them for the time being.
Seeing this on a Debian 12 installation. After multiple attempts I was finally able to get it to successfully install, but it randomly decided the filesystem is corrupt and goes read only. The corruption seems to be so severe that running back just finds
Running fsck just finds a huge list of errors, and the drive is basically unrecoverable. Parallels 19 was fine under Ventura, so it appears to be a Sonoma bug?
@dkomaran are you running the failing VM's from an external drive? I was using an almost brand new external Samsung SSD, which I know to be good, but I was seeing VM corruption. Today I created a new VM on the local HDD, and so far 2 hours in and it is working without issue. Previously even the installation would fail 9 times out 10.
@serv exFat, as I use the same drive with Windows. I can try reformatting as APFS and test. As it's pretty much guaranteed to die during any high write load, such as installing an OS.
@serv Actually, APFS only failed on the first attempt. I've since update to 19.1, and 6 installs on APFS have been flawless. Going back to exFAT still fails.
Thanks for the info @sgaitskell. We're too observing system level reliability issues with exFAT on Sonoma. For those using external storage I'd recommend either delaying the upgrade to Sonoma or reformatting the drive as APFS.
