According to the nostr:nprofile1qqs9df4h2deu3aae83fmet5xmrlm4w5l9gdnsy3q2n7dklem7ezmwfcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz3rhwvaz7tekd3jks6rev3ehyargv9nk66tnxe6h2dn5w43kuerk0fmnwcm4vfc8z6mgweu8j7fhdfhkjmmrxs6k66mnwg6x2cty9ehku6t0dchsz9mhwden5te0wfjkccte9ehx7um5wghxjmnxduhs5nd6j2 community forum this is caused by bad power and/or data supply.

A hard reset is the answer. I'll give it a whirl when i get home.

The hardware is a mini pc with its original power pack a 1TB ssd card.

As frustrating as it is, the troubleshooting is quite fun 😁

nostr:nevent1qqsfjev8c62tfq5v6zvgtqfeq59gtrh3ydgpwlpwcffxqejjf2elwnsppemhxue69uhkummn9ekx7mp0qgsft3lcv7qz48rulvwjkfpmu9fzxjryut8e7c85v7hr90cu7p0cn7crqsqqqqqpdfc52v

There shouldn't be any issue with leaving your server running all the time. There was an issue a while back where if you left a session logged in for days and days it might lock that session, but that shouldn't give you the error you are seeing there. While there is a lot to be said for buying a pre-built one I wouldn't go there yet. Here are a couple things to try. If you haven't powercycled the StartOS server definitely try that. If you set up SSH try to SSH in to the server even when the graphical access doesn't work. You might be able to learn more about the problem. Looking at the error it seems like the OS (and database) can't write to the file system. It could be a hardware / driver issue. In this case after SSH in to the server you could check the filesystem "fsck". If none of that works, ping me again and we'll dig deeper. Don't give up on it though!!!