-
Notifications
You must be signed in to change notification settings - Fork 250
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
[ERROR] Filesystem version 0 is not recognized. #81
Comments
Is it a legacy distro installed by lxrun/bash? |
Yes, it was installed by |
Please try the latest dev build mentioned in readme to verify if it's been fixed. |
Okay, now it ran, gave some warnings like this:
Now bash.exe fails to run. (If its a big hassle to fix it, then I can install other package, like the one from the MS Store. Probably its works with that) |
In the meantime, I figured, that most of the files were not moved from the Appdatalocal |
If there are files inside And could you please provide some more information, which will be helpful for me the reproduce and fix this issue:
Thanks! |
Now I'm out of the wood with ubuntu1804, so no hurry from my side. |
I just successfully reproduced this in a VM. I found out that there's a bug that the source directory isn't deleted after moving, so the files left in |
I think it makes sense to support lxrun.exe. Although the executable has been removed since v1809, it is still present in v1803, which is stated to be supported in readme. Also it's possible that a distro created by lxrun.exe exists on a supported system which is upgraded from v1803 or even earlier. |
Root caused found: v0 and v1 filesystem has different directory layouts. v1 puts everything under My plan is:
This will also fix the known bug that the contents of the home directory will be lost after manipulating on Legacy distros. Althogh it is possible to implement a writer for v0 filesystems and leave @mqmq0 Could you please help test it when I get the updates ready? |
Yeah, sure. I just installed a fresh Legacy distro. |
@mqmq0 I just figured out that it's much easier to implement this by copying the whole installation directory instead of just rootfs so this information is no longer needed 😅 |
Ok, read your edit later then generating this, so here you go nevertheless: Expires in a day. |
i have the same problem as u |
i solve this problem. i just installed my ubuntu but not start and init it. i guess this tool cant't find the rootfs path if u do not init the system.
|
@742362144 No, even if you have initialized the legacy instance, the move operation won't work either. The real problem, as I have said in previous comments, is its inability to deal with the different directory layout of the legacy filesystem. The store apps use a newer version of filesystem so the tool just works well. |
any news on this issue? |
I'm sorry but it's only two months before the college entrance exam in China so I'm extremely busy and have little time for this. I'm still working on it but I can't give any ETA. |
The bug should have been fixed. 🎉 |
E:\LxRunOffline-v3.3.3>LxRunOffline move -n Legacy -d "D:\WSL"
[ERROR] Filesystem version 0 is not recognized.
How to solve?
The text was updated successfully, but these errors were encountered: