Failed OTA update to 0.4.0.1 leaves system unbootable – "No current.rootfs, not safe to prune"

DIY Community Support
1

Hi Community,

I’m running StartOS on a GMKtec NUCBox M6 Ultra (x86_64).

Timeline

  • Fresh install using StartOS 0.3.5.1 installer USB.

  • Successfully upgraded to 0.4.0 through the StartOS UI.

  • Installed Bitcoin Knots and Fulcrum.

  • Both completed IBD and were fully synced.

  • Attempted OTA update to 0.4.0.1.

  • Update failed with:



Filesystem I/O Error: No current.rootfs, not safe to prune

After rebooting, the system no longer boots into StartOS. It reaches the StartOS bootloader but eventually only offers “Start Fresh” or “Recover”.

Investigation performed

Booted Ubuntu Live USB and inspected the StartOS partitions.

Findings:

  • Boot partition (/dev/nvme0n1p2) mounts successfully.

  • Root partition (/dev/nvme0n1p3) mounts successfully.

  • /current contains a complete root filesystem.

  • /config/config.yaml is intact and correctly references:

    • EFI: /dev/nvme0n1p1

    • Boot: /dev/nvme0n1p2

    • Root: /dev/nvme0n1p3

  • LVM and encrypted package-data volumes are intact.

  • vgimport and vgchange -ay activate the volume group successfully.

  • next/ is empty.

  • Searching the mounted boot partition finds no *.rootfs or current.rootfs files.

I also found this community thread describing the same update error:

https://community.start9.com/t/cant-update-to-startos-0-4-0-1/5445

The suggested fix references recreating current.rootfs, but my boot partition contains no .rootfs files to point to.

Question

Is there a supported way to repair the boot metadata or complete the interrupted OTA update so the existing installation can boot again without reinstalling StartOS?

My goal is to preserve the existing node, blockchain, and installed services if possible.

*troubleshooted with and had the above prepared by ChatGPT. Happy to answer any questions that will help.

2

To add:

Recovery attempts

  • Booted the original 0.3.5.1 installer USB and attempted recovery. The installer could see the existing installation but recovery failed with an RPC error before any recovery could be completed.

  • Created a new 0.4.0.1 installer USB and attempted recovery again. The installer detected the existing disks but only presented the “Select Drives” screen and never prompted for a recovery password or recovery file.

3

The solution to the issue you encounter, was presented in the topic you posted in your OP. But I think you are now several steps past the ability to use that solution. At this point you may have corrupted the data partition.

You can try re-flashing your server with 0.4.0 beta 9 using the preserver data option.

If you can get your server up and running again with beta 9, we can then move on to the 0.4.0.1 update.

If this does not work, you’ll likely have to start fresh, or recover from backup. The backup does not contain blockchain data, so this may not accomplish your goal.

4

Ok I flashed StartOS 0.4.0 Beta 9, selected Preserve, and the installation completed successfully.

After booting I now receive:

RPC ERROR: Migration Failed unknown version 0.4.0

So the preserved data appears to be detected, but migration fails before the server initializes.

5

I’m pretty sure your data partition is corrupt. You’ll need to restore your services from backup, and wait for the IBD. What version of StartOS was your last backup from?

6

I don’t have a backup. This is a new server I setup last week specifically for a new bitcoin stack after my 1tb node ran out of space. So just had Knots + Fulcrum installed and fully synced so far. Ok so there’s no way to recover a corrupt partition and I’ll need to start a new server from scratch then? If so, can you confirm the safest procedure for wiping/reinstalling from here?

7

Since you have no data or money at risk, just do a fresh install of 0.4.0.1, and overwrite the data partition.

It’s always recommend to create a backup before making changes to your server. But it sounds like you have nothing at risk here, except the time it takes to do the IBD.

1 Like
8

Thanks Rexter - appreciate your assistance. Fresh install done and IBD underway.

1 Like