I have posted this in StartOS support but thinking this is actually the right place for it.
As I was installing a new service, I lost connection to my server and when I rebooted it, it was in diagnostic mode.
Disk Management Error: Device EMBASY_xxx_main already exists.
I have tried to rebuild the system but this did not work. Should I try repair now?
Hardware: Intel Mac mini with 2tb ssd, 8gb RAM and a usb drive plugged in for backups.
Full diagnostic logs:
2025-01-20T22:57:17+00:00 2025-01-20T22:57:17.835908Z ERROR inner_main: startos::bins::start_init: Device EMBASSY_BYM2CIDY2PVRTAG2JVZCCJJF4MAX2GRNGRFPEO4ADLYED2AYY63A_main already exists.
2025-01-20T22:57:17+00:00 2025-01-20T22:57:17.835931Z DEBUG inner_main: startos::bins::start_init: Device EMBASSY_BYM2CIDY2PVRTAG2JVZCCJJF4MAX2GRNGRFPEO4ADLYED2AYY63A_main already exists.
2025-01-20T22:57:20+00:00 2025-01-20T22:57:20.599136Z ERROR inner_main:init: startos::context::diagnostic: Error: Disk Management Error: Device EMBASSY_BYM2CIDY2PVRTAG2JVZCCJJF4MAX2GRNGRFPEO4ADLYED2AYY63A_main already exists.
2025-01-20T22:57:20+00:00 : Starting diagnostic UI
2025-01-20T22:57:20+00:00 2025-01-20T22:57:20.606274Z DEBUG inner_main:init: startos::context::diagnostic: Error { source:
2025-01-20T22:57:20+00:00 0: Device EMBASSY_BYM2CIDY2PVRTAG2JVZCCJJF4MAX2GRNGRFPEO4ADLYED2AYY63A_main already exists.
2025-01-20T22:57:20+00:00 0:
2025-01-20T22:57:20+00:00 Location:
2025-01-20T22:57:20+00:00 startos/src/util/mod.rs:163
2025-01-20T22:57:20+00:00 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ SPANTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
2025-01-20T22:57:20+00:00 0: startos::disk::main::mount_fs
2025-01-20T22:57:20+00:00 at startos/src/disk/main.rs:266
2025-01-20T22:57:20+00:00 1: startos::disk::main::mount_all_fs
2025-01-20T22:57:20+00:00 at startos/src/disk/main.rs:326
2025-01-20T22:57:20+00:00 2: startos::disk::main::import
2025-01-20T22:57:20+00:00 at startos/src/disk/main.rs:209
2025-01-20T22:57:20+00:00 3: startos::bins::start_init::setup_or_init
2025-01-20T22:57:20+00:00 at startos/src/bins/start_init.rs:23
2025-01-20T22:57:20+00:00 4: startos::bins::start_init::inner_main
2025-01-20T22:57:20+00:00 at startos/src/bins/start_init.rs:198
2025-01-20T22:57:20+00:00 Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
2025-01-20T22:57:20+00:00 Run with RUST_BACKTRACE=full to include source snippets., kind: DiskManagement, revision: None }
Update: Ran repair. Now diagnostic logs shows a prompt:
Disk management error.
enabling repair mode Opening filesystem to check... Checking filesystem on /dev/mapper/EMBASSY_BYM2CIDY2PVRTAG2JVZCCJJF4MAX2GRNGRFPEO4ADLYED2AYY63A_package-data UUID: 65c58de0-37ed-4306-8db6-c63ce6633b89 repair mode will force to clear out log tree, are you sure? [y/N]:
But there is no way to interact with this.
Tried reinstalling the OS but get the following error when restoring from the existing drive:
Error
RPC ERROR: Disk Management Error enabling repair mode Opening filesystem to check... Checking filesystem on /dev/mapper/EMBASSY_BYM2CIDY2PVRTAG2JVZCCJJF4MAX2GRNGRFPEO4ADLYED2AYY63A_package-data UUID: 65c58de0-37ed-4306-8db6-c63ce6633b89 repair mode will force to clear out log tree, are you sure? [y/N]:
I assume that if I restore from encrypted back up (about a week old) my lightning channels will be force closed…?
So I was able to reinstall StartOS, and using it directly from the GUI (HDMI to the server) I tried to transfer data from the startos drive to a new one. The screen showed “calculating size” and is now comepletely frozen (can’t move mouse, loading bar not moving).
I am apparently only talking to myself here but if someone knows anything about these issues or has had them please reach out. I would pay for support but, well my node is not online.
We have a guide for transferring data on StartOS.
Use an Existing Data Drive - Guide
If you want to recover from a backup, then this guide is what you need (Keep in mind that recovering from a backup will always close all open lightning channels. Funds will return eventually to the Lightning node On-Chain wallet).
You’re definitely not talking to yourself, it’s just that start9.me is the primary line of support and where there’s more activity (sometimes). We’re hoping to grow this forum and have users pitch in to help each other.
It looks like something went quite wrong with that disk and StartOS isn’t able to mount the data partition. I think from the description and how far you got in the StartOS install process that the issue affecting the disk is only affecting that data partition. Then, when you tried to transfer the data, which also means StartOS needs to mount the partition, that also failed.
Bitcoin has something of a gift for exposing issues with RAM and SSDs, considering it’s so intensive and needs absolute perfection across the entirely of the memory and storage used, something not so important when (perhaps in the case of a DIY repurposing) that the disk was used for saving documents and web browsers cache.
I think you have two options…
A: Make use of the backups and restore from those onto a quality expensive new disk.
B: Surgically mount that bad data partition and see if you can rescue the LND data and transfer it over (possibly risky)
Okay, thanks. Are there any guides or anything about mounting the bad partition and transferring LND data? I assume there is nothing to lose at this point since I will be restoring from a backup (and lose channels) as a last resort at this point anyway.
Thanks