Start OS refuses to start, says "_main already exists. "

StartOS Support
1

I moved so my mini PC was off for a month. My other mini PC was off for a month but it boot up and synced with the BTC network.

The error "Disk management error.

Device EMBASSY_3J6XIWMTJJ554KRFEYPOVMBAIDBKOWTTNDY6ZVERMWHJ6M3DWXNQ_main already exists. "

I have restarted my mini PC, did a system rebuild, and I “repaired” the drive.

Nothing helps.

Logs

2025-02-18T18:20:06-06:00 2025-02-19T00:20:06.942121Z ERROR inner_main: startos::bins::start_init: Device EMBASSY_3J6XIWMTJJ554KRFEYPOVMBAIDBKOWTTNDY6ZVERMWHJ6M3DWXNQ_main already exists. 2025-02-18T18:20:06-06:00 2025-02-19T00:20:06.942139Z DEBUG inner_main: startos::bins::start_init: Device EMBASSY_3J6XIWMTJJ554KRFEYPOVMBAIDBKOWTTNDY6ZVERMWHJ6M3DWXNQ_main already exists. 2025-02-18T18:20:09-06:00 2025-02-19T00:20:09.724045Z ERROR inner_main:init: startos::context::diagnostic: Error: Disk Management Error: Device EMBASSY_3J6XIWMTJJ554KRFEYPOVMBAIDBKOWTTNDY6ZVERMWHJ6M3DWXNQ_main already exists. 2025-02-18T18:20:09-06:00 : Starting diagnostic UI 2025-02-18T18:20:09-06:00 2025-02-19T00:20:09.727545Z DEBUG inner_main:init: startos::context::diagnostic: Error { source: 2025-02-18T18:20:09-06:00 0: Device EMBASSY_3J6XIWMTJJ554KRFEYPOVMBAIDBKOWTTNDY6ZVERMWHJ6M3DWXNQ_main already exists. 2025-02-18T18:20:09-06:00 0: 2025-02-18T18:20:09-06:00 Location: 2025-02-18T18:20:09-06:00 startos/src/util/mod.rs:163 2025-02-18T18:20:09-06:00 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ SPANTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2025-02-18T18:20:09-06:00 0: startos::disk::main::mount_fs 2025-02-18T18:20:09-06:00 at startos/src/disk/main.rs:266 2025-02-18T18:20:09-06:00 1: startos::disk::main::mount_all_fs 2025-02-18T18:20:09-06:00 at startos/src/disk/main.rs:326 2025-02-18T18:20:09-06:00 2: startos::disk::main::import 2025-02-18T18:20:09-06:00 at startos/src/disk/main.rs:209 2025-02-18T18:20:09-06:00 3: startos::bins::start_init::setup_or_init 2025-02-18T18:20:09-06:00 at startos/src/bins/start_init.rs:23 2025-02-18T18:20:09-06:00 4: startos::bins::start_init::inner_main 2025-02-18T18:20:09-06:00 at startos/src/bins/start_init.rs:198 2025-02-18T18:20:09-06:00 Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it. 2025-02-18T18:20:09-06:00 Run with RUST_BACKTRACE=full to include source snippets., kind: DiskManagement, revision: None }

2

It would appear there’s some kind of issue with the logical volumes, specifically the one for the OS, or worse, with the physical disk or the partitions.

You should go through the reflashing process and reinstall StartOS, choosing to keep the existing data when asked.

https://docs.start9.com/0.3.5.x/flashing-guides/os-x86

3

The first attempt to reflash failed. I am waiting for the second attempt. If that fails, I am done, for now. Tomorrow I am supposed to get a Samsung 990 pro NVME SSD and a Samsung 870 SSD, both of those are for this server.

The current NVME SSD is a SP (Silicon Power).

4

I bought and installed a 990 Pro NVME SSD and an 870 pro M.2 SSD for my Beelink SER5 mini PC.

I redownloaded Start9 OS, flashed it, and waited two days for Monero to sync which it did. To save power, I turned off my mini pc from the web menu but when I powered back on, the same error occurred. I tried everything on the diagnostic menu. Start9 OS is broken again. I am lost. Brand new hard drives, fresh verified download of Start9 OS from github. I have another Beelink mini PC (same as my XMR node) running as a BTC node, it works great. Me=?

Log
2025-03-01T19:00:22-06:00 2025-03-02T01:00:22.380360Z ERROR inner_main: startos::bins::start_init: Device EMBASSY_NACMOTMQTPVXPAH45G7S7PK2OHIPR7AUXAABUK5X5KNRT33QNKMQ_main already exists. 2025-03-01T19:00:22-06:00 2025-03-02T01:00:22.380376Z DEBUG inner_main: startos::bins::start_init: Device EMBASSY_NACMOTMQTPVXPAH45G7S7PK2OHIPR7AUXAABUK5X5KNRT33QNKMQ_main already exists. 2025-03-01T19:00:25-06:00 2025-03-02T01:00:25.159560Z ERROR inner_main:init: startos::context::diagnostic: Error: Disk Management Error: Device EMBASSY_NACMOTMQTPVXPAH45G7S7PK2OHIPR7AUXAABUK5X5KNRT33QNKMQ_main already exists. 2025-03-01T19:00:25-06:00 : Starting diagnostic UI 2025-03-01T19:00:25-06:00 2025-03-02T01:00:25.163639Z DEBUG inner_main:init: startos::context::diagnostic: Error { source: 2025-03-01T19:00:25-06:00 0: Device EMBASSY_NACMOTMQTPVXPAH45G7S7PK2OHIPR7AUXAABUK5X5KNRT33QNKMQ_main already exists. 2025-03-01T19:00:25-06:00 0: 2025-03-01T19:00:25-06:00 Location: 2025-03-01T19:00:25-06:00 startos/src/util/mod.rs:163 2025-03-01T19:00:25-06:00 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ SPANTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2025-03-01T19:00:25-06:00 0: startos::disk::main::mount_fs 2025-03-01T19:00:25-06:00 at startos/src/disk/main.rs:266 2025-03-01T19:00:25-06:00 1: startos::disk::main::mount_all_fs 2025-03-01T19:00:25-06:00 at startos/src/disk/main.rs:326 2025-03-01T19:00:25-06:00 2: startos::disk::main::import 2025-03-01T19:00:25-06:00 at startos/src/disk/main.rs:209 2025-03-01T19:00:25-06:00 3: startos::bins::start_init::setup_or_init 2025-03-01T19:00:25-06:00 at startos/src/bins/start_init.rs:23 2025-03-01T19:00:25-06:00 4: startos::bins::start_init::inner_main 2025-03-01T19:00:25-06:00 at startos/src/bins/start_init.rs:198 2025-03-01T19:00:25-06:00 Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it. 2025-03-01T19:00:25-06:00 Run with RUST_BACKTRACE=full to include source snippets., kind: DiskManagement, revision: None }

5

Is this something you can confirm only happens with Monero? If you install fresh, and run Bitcoin Core and Knots, does the same thing happen? Knowing whether it does or doesn’t might point to an error in Monero rather that the physical drive.