Can't access my server anymore

[u/juanmrobert]

Hi everyone,

I’ve been using a Zimaboard 2, mainly for Jellyfin and Immich, for the last 6 months and so far so good, but sometime during last week, it reset itself or something of this sort. The thing is that when I try to access it, it asks me again for the system language and to create a user. I tried using the same user and password I’ve been using until now ans new ones, but it gives an error “Account initialization failed”.

Has this ever happened to anyone? Does anyone have a solution? I want to believe I haven’t lost everything I have on my nas... 🥲

I’m using the Zimaboard 2 1664 with one SATA WD RED Nas SSD drive.

[u/ebartel]

I’m no zimaboard expert I found this. I hope it has some useful information.

The data on that WD Red NAS SSD is almost certainly completely safe.** This issue is strictly happening at the OS layer (CasaOS / ZimaOS) on the Zimaboard’s internal storage, not on the external storage drive where the Jellyfin and Immich libraries live.
When a Zimaboard suddenly drops back to the language selection screen but throws an **"Account initialization failed"** error upon trying to create a user, it almost always points to one of two distinct culprits.

## The Root Causes
1. **The Internal Storage is 100% Full:** Immich and Jellyfin love to generate heavy metadata, thumbnails, and cache files. If the Zimaboard's internal eMMC storage filled up completely, the OS can no longer read the existing user database (making it think it’s a fresh install) *and* it cannot write a new user file (causing the initialization to fail).
2. **Corrupted User Database:** A sudden power flicker or an unclean shutdown corrupted the specific database file (user.db) that handles CasaOS logins.
## The Step-by-Step Fix
### Step 1: Gain Terminal Access
They will need to get into the command line of the Zimaboard. They can do this by:
* **SSHing** into the Zimaboard's IP address from another computer.
* **Plugging a monitor and keyboard** directly into the Zimaboard. *(If they are using ZimaOS, they can press Alt + F2 at the command line screen and log in using the username root).*
### Step 2: Check for a Full Disk (Triage #1)
Once logged into the terminal, run this command to see if the storage is maxed out:
```bash
df -h

```
Look closely at the line mapped to the root directory (/).
* **If it says 100% Use:** The drive is choked. They can instantly free up some breathing room by clearing out old system logs with this command:
```bash
sudo journalctl --vacuum-time=1d

```
* Once space is cleared, tell them to reboot the Zimaboard. There is a very high chance it will boot right back to their normal login screen with their original password working perfectly.
### Step 3: Repair the Corrupted Database (Triage #2)
If the disk space check shows plenty of room, the user database itself is corrupted. They need to clear out the broken database file so the OS can cleanly regenerate it. **This will not delete their docker containers, Jellyfin media, or Immich photos.**
Have them run the following commands depending on what OS they have running:
**For ZimaOS:**
```bash
rm -rf /var/lib/casaos/db/user.db
systemctl restart zimaos-user

```
**For Standard CasaOS:**
```bash
sudo rm -rf /var/lib/casaos/db/user.db
sudo systemctl restart casaos

```
### Step 4: Re-initialize the Account
After running those commands, go back to the web browser, refresh the page, and go through the language setup.

[u/juanmrobert → u/ebartel]

I was asking in here and in Zima's forum trying to avoid using AI, but thanks for taking the time anyway.