Disk management error on reboot

cpm23.kft4c · January 10, 2025, 4:08pm

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 · January 10, 2025, 4:23pm

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 · January 10, 2025, 4:32pm

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 · January 10, 2025, 4:40pm

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 · January 11, 2025, 2:48pm

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.

system · January 13, 2025, 2:48pm

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.

George · October 22, 2025, 6:18pm

This results from a bug in StartOS v0.3.5.1 which won’t be fixed until StartOS v0.4.0 comes out, but it is still in alpha stage, so the thing to do is flash this 035 disk repair fix iso, available here:

Then take these steps:

flash the iso to a usb thumb drive, and boot that thumb drive in your server.
Visit http://start.local
select “Re-install StartOS”
Remove USB & Reboot to the new installation.
Visit http://start.local again and select:
Recover > Use existing drive

At first boot, it should do the disk repair, hopefully successfully so it might take up to hours to boot. But once it does the disk should be repaired (assuming it’s not beyond repair – if you get errors, it may be).

Once it has run it’s course, your server should be available again at its regular, unique name that follows the pattern adjective-noun.local. You’ll want to reset SSH access since you’re now on a dev build which won’t be reverted to the prod track until StartOS v0.4.0. The other option is to now flash back to prod 0351 again after the disk repair function runs. Or follow these steps to continue with the diskrepair fix dev build:

Setup SSH access

SSH in to the server, using the following:
hostname: adjective-noun.local
username: start9
password: embassy
command line example to ssh in:

ssh start9@youruniqueadjective-noun.local

On the ssh shell, perform the following commands (one by one, waiting for each one to complete before you paste the next one):

sudo /usr/lib/startos/scripts/chroot-and-upgrade
#at the resulting shell, do:
sed -i "s/^\(PasswordAuthentication yes\)/#\1/g" /etc/ssh/sshd_config
exit

The server should then reboot, and everything should be back to normal.