Is my Start9 server borked?

I have tried restarting and rebuilding (to no effect). Should I try repairing?
Logs:

Start9 error logs

2025-06-15T13:27:38-04:00 2025-06-15T17:27:38.999029Z ERROR inner_main: startos::bins::start_init: Device EMBASSY_6WQF5PW6HBM3XX7MQ2B4BVVYBGNQNBETMKNDHWYFURIR443IW56Q_main already exists.

2025-06-15T13:27:38-04:00 2025-06-15T17:27:38.999057Z DEBUG inner_main: startos::bins::start_init: Device EMBASSY_6WQF5PW6HBM3XX7MQ2B4BVVYBGNQNBETMKNDHWYFURIR443IW56Q_main already exists.

2025-06-15T13:27:41-04:00 2025-06-15T17:27:41.792139Z ERROR inner_main:init: startos::context::diagnostic: Error: Disk Management Error: Device EMBASSY_6WQF5PW6HBM3XX7MQ2B4BVVYBGNQNBETMKNDHWYFURIR443IW56Q_main already exists.

2025-06-15T13:27:41-04:00 : Starting diagnostic UI

2025-06-15T13:27:41-04:00 2025-06-15T17:27:41.799298Z DEBUG inner_main:init: startos::context::diagnostic: Error { source:

2025-06-15T13:27:41-04:00 0: Device EMBASSY_6WQF5PW6HBM3XX7MQ2B4BVVYBGNQNBETMKNDHWYFURIR443IW56Q_main already exists.

2025-06-15T13:27:41-04:00 0:

2025-06-15T13:27:41-04:00 Location:

2025-06-15T13:27:41-04:00 startos/src/util/mod.rs:163

2025-06-15T13:27:41-04:00━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━SPANTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

2025-06-15T13:27:41-04:00 0: startos::disk::main::mount_fs

2025-06-15T13:27:41-04:00 at startos/src/disk/main.rs:266

2025-06-15T13:27:41-04:00 1: startos::disk::main::mount_all_fs

2025-06-15T13:27:41-04:00 at startos/src/disk/main.rs:326

2025-06-15T13:27:41-04:00 2: startos::disk::main::import

2025-06-15T13:27:41-04:00 at startos/src/disk/main.rs:209

2025-06-15T13:27:41-04:00 3: startos::bins::start_init::setup_or_init

2025-06-15T13:27:41-04:00 at startos/src/bins/start_init.rs:23

2025-06-15T13:27:41-04:00 4: startos::bins::start_init::inner_main

2025-06-15T13:27:41-04:00 at startos/src/bins/start_init.rs:198

2025-06-15T13:27:41-04:00 Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.

2025-06-15T13:27:41-04:00 Run with RUST_BACKTRACE=full to include source snippets., kind: DiskManagement, revision: None }

Looks like a Btrfs label conflict / metadata error:
Device _main already exists. This is an issue with the drive or data corruption.

Run Repair Drive from the Diagnostic UI first.

:heavy_check_mark: If it succeeds → reboot and you’re good.

✘ If it fails → flash the latest image and Recover (or restore from backup). Hopefully you backed everything up.

Rebuild won’t fix this because the disk isn’t mounting and it just rebuilds the containers

Thanks @Rick. I’ll try what you suggested. I don’t have everything backed up but I’m not too worried about losing anything.

@Rick It just returns to the same screen after repair.

Please tell me about your hardware setup, so I can provide further guidance.