- Cannot see V: drive from Explorer, even after starting Crossmeta services.
This requires restart of Explorer program if Crossmeta services are being started manually after Explorer program was launched or you do a simple logoff and relogin.
- V: drive is write protected
If crossmeta service was not cleanly shutdown the root file system requires consistency check using fsck program. To repair root file system run the following command after starting Crossmeta services.
fsck -y /dev/loop0