# Disk management error on reboot

**URL:** <https://community.start9.com/t/disk-management-error-on-reboot/2394>\
**Category:** StartOS Support\
**Created:** [January 10, 2025, 4:08pm UTC](https://community.start9.com/t/disk-management-error-on-reboot/2394 "2025-01-10T16:08:58Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![cpm23.kft4c](https://community.start9.com/letter_avatar_proxy/v4/letter/c/6de8d8/32.png) [@cpm23.kft4c](https://community.start9.com/u/cpm23.kft4c)\
**Post date:** [January 10, 2025, 4:08pm UTC](https://community.start9.com/t/disk-management-error-on-reboot/2394/1 "2025-01-10T16:08:58Z")

</div>

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 }

 ![Screenshot 2025-01-10 at 16.04.19](https://community.start9.com/uploads/default/original/2X/d/d12deeb99143d5a392b5d848e99dd4c77ce09a65.png)

---

<div class="post-metadata">

**Author:** ![Jeremy](https://community.start9.com/user_avatar/community.start9.com/jeremy/32/407_2.png) [@Jeremy](https://community.start9.com/u/Jeremy)\
**Post date:** [January 10, 2025, 4:23pm UTC](https://community.start9.com/t/disk-management-error-on-reboot/2394/2 "2025-01-10T16:23:24Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![cpm23.kft4c](https://community.start9.com/letter_avatar_proxy/v4/letter/c/6de8d8/32.png) [@cpm23.kft4c](https://community.start9.com/u/cpm23.kft4c)\
**Post date:** [January 10, 2025, 4:32pm UTC](https://community.start9.com/t/disk-management-error-on-reboot/2394/3 "2025-01-10T16:32:17Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Jeremy](https://community.start9.com/user_avatar/community.start9.com/jeremy/32/407_2.png) [@Jeremy](https://community.start9.com/u/Jeremy)\
**Post date:** [January 10, 2025, 4:40pm UTC](https://community.start9.com/t/disk-management-error-on-reboot/2394/4 "2025-01-10T16:40:17Z")

</div>

> [@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](https://docs.start9.com/0.3.5.x/flashing-guides/index). Feel free to review and let us know any questions you may have accordingly.

---

<div class="post-metadata">

**Author:** ![cpm23.kft4c](https://community.start9.com/letter_avatar_proxy/v4/letter/c/6de8d8/32.png) [@cpm23.kft4c](https://community.start9.com/u/cpm23.kft4c)\
**Post date:** [January 11, 2025, 2:48pm UTC](https://community.start9.com/t/disk-management-error-on-reboot/2394/5 "2025-01-11T14:48:02Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![system](https://community.start9.com/uploads/default/original/1X/2dcde8aa6ad3ce3d7873096ee4b3e5395e19a7b5.png) [@system](https://community.start9.com/u/system)\
**Post date:** [January 13, 2025, 2:48pm UTC](https://community.start9.com/t/disk-management-error-on-reboot/2394/6 "2025-01-13T14:48:31Z")

</div>

Closed on January 13, 2025, 2:48pm UTC

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

---

<div class="post-metadata">

**Author:** ![George](https://community.start9.com/user_avatar/community.start9.com/george/32/91_2.png) [@George](https://community.start9.com/u/George)\
**Post date:** [October 22, 2025, 6:18pm UTC](https://community.start9.com/t/disk-management-error-on-reboot/2394/7 "2025-10-22T18:18:07Z")

</div>

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:

> **[startos-0.3.5.2-de5ca3b-disk\_repair\_fix~dev\_x86\_64-nonfree.iso](https://cloud.start9labs.com/s/J5BDGzE9ocP8XNE)**
>
> Start9 - Sovereign Computing

Then take these steps:

1. [flash](https://docs.start9.com/0.3.5.x/flashing-guides/os-x86) the iso to a usb thumb drive, and boot that thumb drive in your server.
2. Visit [http://start.local](http://start.local)
3. select “Re-install StartOS”
4. Remove USB & Reboot to the new installation.
5. Visit [http://start.local](http://start.local) again and select:
6. 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:

1. Setup [SSH access](https://docs.start9.com/0.3.5.x/user-manual/ssh)

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):

```auto
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.