Disk management error on reboot

[cpm23.kft4c]

Hi,

I installed the Monero community package and rebooted a few times during the initial sync. I rebooted my device yesterday and now see the attached screen when browsing to the device’s control panel.

Any advice on what I should do from here?

`Disk management error.

enabling repair mode Opening filesystem to check… Checking filesystem on /dev/mapper/EMBASSY_HRAF7F5CWHL6ZBDG7FODTA7BFFFD76P5FYWJJ3FTKVXFV7DSKDLA_package-data UUID: 88163197-7caa-40a8-a47f-bad8e3f551b0 repair mode will force to clear out log tree, are you sure? [y/N]:`

Logs

2025-01-10T15:41:40+00:00 2025-01-10T15:41:40.903910Z ERROR inner_main : startos::bins::start_init: enabling repair mode 2025-01-10T15:41:40+00:00 Opening filesystem to check… 2025-01-10T15:41:40+00:00 Checking filesystem on /dev/mapper/EMBASSY_HRAF7F5CWHL6ZBDG7FODTA7BFFFD76P5FYWJJ3FTKVXFV7DSKDLA_package-data 2025-01-10T15:41:40+00:00 UUID: 88163197-7caa-40a8-a47f-bad8e3f551b0 2025-01-10T15:41:40+00:00 repair mode will force to clear out log tree, are you sure? [y/N]: 2025-01-10T15:41:40+00:00 2025-01-10T15:41:40.903926Z DEBUG inner_main : startos::bins::start_init: enabling repair mode 2025-01-10T15:41:40+00:00 Opening filesystem to check… 2025-01-10T15:41:40+00:00 Checking filesystem on /dev/mapper/EMBASSY_HRAF7F5CWHL6ZBDG7FODTA7BFFFD76P5FYWJJ3FTKVXFV7DSKDLA_package-data 2025-01-10T15:41:40+00:00 UUID: 88163197-7caa-40a8-a47f-bad8e3f551b0 2025-01-10T15:41:40+00:00 repair mode will force to clear out log tree, are you sure? [y/N]: 2025-01-10T15:41:43+00:00 2025-01-10T15:41:43.689701Z ERROR inner_main :init : startos::context::diagnostic: Error: Disk Management Error: enabling repair mode 2025-01-10T15:41:43+00:00 Opening filesystem to check… 2025-01-10T15:41:43+00:00 Checking filesystem on /dev/mapper/EMBASSY_HRAF7F5CWHL6ZBDG7FODTA7BFFFD76P5FYWJJ3FTKVXFV7DSKDLA_package-data 2025-01-10T15:41:43+00:00 UUID: 88163197-7caa-40a8-a47f-bad8e3f551b0 2025-01-10T15:41:43+00:00 repair mode will force to clear out log tree, are you sure? [y/N]: : Starting diagnostic UI 2025-01-10T15:41:43+00:00 2025-01-10T15:41:43.699115Z DEBUG inner_main :init : startos::context::diagnostic: Error { source: 2025-01-10T15:41:43+00:00 0: enabling repair mode 2025-01-10T15:41:43+00:00 Opening filesystem to check… 2025-01-10T15:41:43+00:00 Checking filesystem on /dev/mapper/EMBASSY_HRAF7F5CWHL6ZBDG7FODTA7BFFFD76P5FYWJJ3FTKVXFV7DSKDLA_package-data 2025-01-10T15:41:43+00:00 UUID: 88163197-7caa-40a8-a47f-bad8e3f551b0 2025-01-10T15:41:43+00:00 repair mode will force to clear out log tree, are you sure? [y/N]: 2025-01-10T15:41:43+00:00 Location: 2025-01-10T15:41:43+00:00 startos/src/util/mod.rs:163 2025-01-10T15:41:43+00:00 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ SPANTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2025-01-10T15:41:43+00:00 0: startos::disk::main::mount_fs 2025-01-10T15:41:43+00:00 at startos/src/disk/main.rs:266 2025-01-10T15:41:43+00:00 1: startos::disk::main::mount_all_fs 2025-01-10T15:41:43+00:00 at startos/src/disk/main.rs:326 2025-01-10T15:41:43+00:00 2: startos::disk::main::import 2025-01-10T15:41:43+00:00 at startos/src/disk/main.rs:209 2025-01-10T15:41:43+00:00 3: startos::bins::start_init::setup_or_init 2025-01-10T15:41:43+00:00 at startos/src/bins/start_init.rs:23 2025-01-10T15:41:43+00:00 4: startos::bins::start_init::inner_main 2025-01-10T15:41:43+00:00 at startos/src/bins/start_init.rs:198 2025-01-10T15:41:43+00:00 Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it. 2025-01-10T15:41:43+00:00 Run with RUST_BACKTRACE=full to include source snippets., kind: DiskManagement, revision: None }

[Jeremy]

Hi @cpm23.kft4c, have you attempted any of the 3 actions listed under possible solutions? If not, I would suggest running the repair drive one to start. Per the help text, be sure not to do anything to the server while the process runs.

[cpm23.kft4c]

Hi Jeremy,

Yes, I’ve tried both a drive repair, and system rebuild but both options bring me back to this screen after a reboot.

Thanks

[Jeremy]

@cpm23.kft4c

a few times during the initial sync

The next recommended step would be to reflash the OS. You can find the flashing guides here. Feel free to review and let us know any questions you may have accordingly.

[cpm23.kft4c]

Thanks. A reflash seems to have fixed the issue. I wonder if the XMR node was the cause of this. Running the bitcoin IBD atm.