-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: repo migration errors #182
Comments
Note: I realized after posting this that the current repo version isn't output in the logs, and that repo version 14 is the version the executing binary is configured to, not the one on the machine the binary is running on. This could be converted into a feature request to add output showing the current version of the repo. may be related to https://github.com/protocol/bifrost-infra/issues/2765 |
it does seem like repo-migration is broken for one particular windows user: what parameter, and what's incorrect about it? The user seems to run into this issue anytime they try to update ipfs-desktop passed version 0.28.0 (which had kubo v0.20.0). see ipfs/ipfs-desktop#2607 |
Yes. That's me with the issue. I'm stuck on v 0.28.0 and if I try to update to a more recent version, I get the error message as above. |
This is the error message that I get whenever I try to update: Error: migration fs-repo-13-to-14 failed: fork/exec C:\Users\User\AppData\Local\Temp\migrations3454220631\fs-repo-13-to-14.exe: The parameter is incorrect. |
Still stuck. With IPFS-Desktop Then i updated again to the latest version 0.31.0 and this is the error message that I get: Initializing daemon... Error: migration fs-repo-13-to-14 failed: fork/exec C:\Users\User\AppData\Local\Temp\migrations3296180791\fs-repo-13-to-14.exe: The parameter is incorrect. |
@Goodebags if you manually rerun the failed command |
Thanks for your reply.
Error: migration fs-repo-14-to-15 failed: fork/exec C:\Users\User\AppData\Local\Temp\migrations634027305\fs-repo-14-to-15.exe: The parameter is incorrect. I own a couple of PCs. Is it possible to migrate the node and all of the data (so the links continue to work) from this one that's struggling to one of the others? |
...and if I run that command now, I get: C:>C:\Users\User\AppData\Local\Temp\migrations3296180791\fs-repo-13-to-14.exe -path=G:\IPFS.ipfs -verbose=true |
@Goodebags for the record, quick questions:
|
Hi Lidel and thanks for replying |
Triage notes:
|
Wow! Awesome. Well done! Initializing daemon...
So I guess, all good now!? |
Many users are reaching out to ipfs-desktop reporting issues with repo migration.. One in particular caught my eye:
From ipfs/ipfs-desktop#2629:
If the user is on repo version 14, why is kubo/fs-repo-migrations downloading 11-to-12, 12-to-13, and 13-to-14?
Other similar repo migration failures:
The text was updated successfully, but these errors were encountered: