We've found the issue. This was due to a partition having the incorrect type in the configuration files. We're however still unsure what triggered the issue, since it didn't have any problems with this before. PolarisM, along with Polaris should be back up and running, and fully up-to-date. Apologies for the inconvenience.