Struggling to backdate Knots for Core conversion

Services Support
1

  1. Exact error: cannot migrate from #knots:29.3.1:0 to #knotsprerdts:29.3:28

  2. Current package: “Bitcoin Knots (Legacy)”, git hash v29.3.knots20260508

  3. Context: version arrived via automatic StartOS 0.3.5.1 → 0.4.0 upgrade on Sep 21

    Any advice here?

    Cheers

2

There is no error here at all, there is just a message. It says that you cannot migrate from one service for one particular cryptocurrency to an different service with a similar name for a different cryptocurrency.

It’s not clear here whether you want to run “Bitcoin” or “Blakecoin”.

If you wanted to run “Bitcoin”, you’d probably have migrated from Knots to Core or preRDTS perhaps a month or two before updating StartOS in order to run the latest version of services before updating StartOS. At this point, since you’re not running Bitcoin, you’d have to uninstall Blakecoin and install a Bitcoin service for the first time (you’re not currently running one)

If you wanted to run “Blakecoin”, then your StartOS update process makes a lot more sense, but your attempt to switch to Bitcoin after the fact doesn’t make sense at all (if this was your intention, surely you’d have done it a month or two ago?). There’s no Blakecoin client on StartOS’s own registries, you’d need to source and sideload Knots 29.4, for which I’d hope (and expect) that there’s a migration part for your situation.

3

I have exactly the same issue and source package: #knots:29.3.1:0.

My Bitcoin Knots (Legacy) node is stuck at block 961,639 despite both a chainstate reindex and a full blockchain reindex.

I have tried:

#knots:29.3.1:0 → #knotsprerdts:29.3:28

Result: cannot migrate from #knots:29.3.1:0 to #knotsprerdts:29.3:28

I also tried:

#knots:29.3.1:0 → Bitcoin Core 31.1:17

Result: cannot migrate from #knots:29.3.1:0 to 31.1:17

I specifically want to preserve the existing downloaded blockchain (blocks and chainstate) rather than uninstalling and downloading the entire blockchain again.

Is there a supported intermediate/sideload package with a migration path from #knots:29.3.1:0 that will preserve the existing blockchain data?

If so, which exact package/version should be sideloaded?

4

Same situation here, running bitcoin knots 29.3.0:0 We recently updated our Start9 server from version 0.3.5.1 to 0.4.0.1, following the recommended update procedure.

Our server is currently running Bitcoin Knots version 29.3.0:0. After completing the update and rebooting the server, Bitcoin Knots and several other services, including Sparrow, were marked as Legacy. Additionally, some services that depend on Bitcoin Knots are reporting an incorrect version or dependency-related error.

Trying to switch from knots:29.3.0:0 to bitcoin core 31.1.17 but results:

Updating Failed Unknown Error: Error: cannot migrate from #knots:29.3.0:0 to 31.1:17
5

wow trying to switch from knots to core? seems like trolling to me