Skip to content
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

WSL2 Conversion failed #4102

Open
dsolodow opened this issue Jun 12, 2019 · 48 comments
Open

WSL2 Conversion failed #4102

dsolodow opened this issue Jun 12, 2019 · 48 comments
Assignees
Labels

Comments

@dsolodow
Copy link

@dsolodow dsolodow commented Jun 12, 2019

Windows version: Insider Fast 19817 Pro x63

What I expected:
Convert installed WSL distro (Ubuntu) to wsl2

What happened:
message stating that conversion failed

image

@dsolodow

This comment has been minimized.

Copy link
Author

@dsolodow dsolodow commented Jun 12, 2019

@mscraigloewen @benhillis - transferring from Twitter. :)

@benhillis

This comment has been minimized.

Copy link
Member

@benhillis benhillis commented Jun 12, 2019

Thanks for posting, could you please collect logs during the failed conversion?

https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-detailed-logs

@benhillis benhillis added the wsl2 label Jun 12, 2019
@dsolodow

This comment has been minimized.

Copy link
Author

@dsolodow dsolodow commented Jun 12, 2019

wsl.zip

Here you go.

@benhillis

This comment has been minimized.

Copy link
Member

@benhillis benhillis commented Jun 12, 2019

Interesting... when converting the filesystem to the ext4 vhd, there are a bunch of errors about the hard link target not existing, for example:

./home/redacted/gems/doc/stringio-0.0.2/rdoc/js/jquery.js: Hard-link target './usr/lib/ruby/2.5.0/rdoc/generator/template/darkfish/js/jquery.js' does not exist.

I'll dig into this a bit more, thanks for reporting!

@benhillis benhillis added the bug label Jun 13, 2019
@benhillis benhillis self-assigned this Jun 13, 2019
@johnturek

This comment has been minimized.

Copy link

@johnturek johnturek commented Jun 13, 2019

#metoo
Repro:

  1. Fresh install of Windows 18917. Bitlocker enabled AAD Joined to Microsoft (FTE)
  2. Added WSL Feature
  3. Istalled Ubuntu 18.04
  4. Launched Ubuntu, created a user
  5. wsl --set-version Ubuntu-18.04 2

Conversion in progress... takes longer than it did when i was testing with non-insiders internal build with feature flag enabled....

Then fails with "Unspecified error"

@uow-dmurrell

This comment has been minimized.

Copy link

@uow-dmurrell uow-dmurrell commented Jun 13, 2019

Then fails with "Unspecified error"

@johnturek I got this, but fixed by freeing up disk space from ~10gb free to 22gb free. Not sure what the minimum is. Maybe it needs a temp space to work in?

@zawarski

This comment has been minimized.

Copy link

@zawarski zawarski commented Jun 13, 2019

Then fails with "Unspecified error"

@johnturek I got this, but fixed by freeing up disk space from ~10gb free to 22gb free. Not sure what the minimum is. Maybe it needs a temp space to work in?

I had almost the exact same experience. I had about 10gb free and it failed with 'Unspecified error". I freed up 23gb, ran command again and it succeeded.

@benhillis

This comment has been minimized.

Copy link
Member

@benhillis benhillis commented Jun 13, 2019

This is very useful, I think there are a couple issues here, the "Conversion Failed" issue and the "Unspecified error" failure, both with different root causes. In both cases I should plumb more information back to the user. That would at least make it more clear that disk space is the issue for some of these failures.

@benhillis

This comment has been minimized.

Copy link
Member

@benhillis benhillis commented Jun 13, 2019

I've found a way to help me diagnose this issue, if you are unable to convert to WSL2, could you run this command from WSL1 and share any stderr output?

sudo /mnt/c/Windows/System32/lxss/tools/bsdtar -C / -c --one-file-system --xattrs -f /dev/null .

@dsolodow

This comment has been minimized.

Copy link
Author

@dsolodow dsolodow commented Jun 13, 2019

: tar format cannot archive socket: tar format cannot archive socket

@benhillis

This comment has been minimized.

Copy link
Member

@benhillis benhillis commented Jun 13, 2019

@dsolodow - Was the exitcode 0?

@dsolodow

This comment has been minimized.

Copy link
Author

@dsolodow dsolodow commented Jun 13, 2019

@dsolodow - Was the exitcode 0?

Yes.

@benc-uk

This comment has been minimized.

Copy link

@benc-uk benc-uk commented Jun 14, 2019

I've had Unspecified error and Conversion failed. I'm converting my Ubuntu 18.04 distro
One time vmmem was using over 12GB of memory!

I've tried from regular and run-as-admin prompts and it makes no difference
I have over 200GB of free disk space

Is there any way to really debug/fix this?

@benc-uk

This comment has been minimized.

Copy link

@benc-uk benc-uk commented Jun 14, 2019

@benhillis I just ran

sudo /mnt/c/Windows/System32/lxss/tools/bsdtar -C / -c --one-file-system --xattrs -f /dev/null .

and it completed with no output or error message
But the WSL conversion is still failing :(

@benhillis

This comment has been minimized.

Copy link
Member

@benhillis benhillis commented Jun 14, 2019

@benc-uk - Interesting, would you be able to take a trace?

@benc-uk

This comment has been minimized.

Copy link

@benc-uk benc-uk commented Jun 14, 2019

@benhillis

This comment has been minimized.

Copy link
Member

@benhillis benhillis commented Jun 14, 2019

@benc-uk - Correct.

@Biswa96

This comment has been minimized.

Copy link

@Biswa96 Biswa96 commented Jun 14, 2019

Try this test:

  1. Export distro to a file: wsl.exe --export Ubuntu-18.04 C:\folder\file.tar.gz
  2. Import to new name: wsl.exe --import MyDistro C:\folder C:\folder\file.tar.gz
  3. Convert: wsl.exe --set-version MyDistro 2
@benhillis

This comment has been minimized.

Copy link
Member

@benhillis benhillis commented Jun 14, 2019

@Biswa96 - You can import directly to WSL2, it will be much faster.
wsl.exe --import MyDistro C:\folder C:\folder\file.tar.gz --version 2

@benhillis

This comment has been minimized.

Copy link
Member

@benhillis benhillis commented Jun 14, 2019

./var/lib/gems/2.5.0/doc/power_assert-1.1.3/rdoc/js/jquery.js: Hard-link target './var/lib/gems/2.5.0/doc/test-unit-3.2.8/rdoc/js/jquery.js' does not exist.

It looks like extracting the tar file is failing due to this check in libarchive: libarchive/libarchive#596

@gperciva - I create and extract a tar stream and I'm hitting warnings about hard link targets not existing, and bsdtar is returning a non-zero exit code. Is there any way to work around this issue by creating or extracting the tar with different set of arguments? Here's what I do today

Create:
bsdtar -C / -c --one-file-system --xattrs -f - .

Extract:
bsdtar -C / -x -p --xattrs -f -
@avdi

This comment has been minimized.

Copy link

@avdi avdi commented Jun 21, 2019

I'm also getting "Conversion Failed", what info can I contribute to be useful?

@gperciva

This comment has been minimized.

Copy link

@gperciva gperciva commented Jun 21, 2019

libarchive/libarchive#596 just gives a reason why the extract fails. Before that, libarchive would fail silently on that example.

The next step in this issue is to figure out why you're trying to make a hard link to a file which doesn't exist.

@benhillis

This comment has been minimized.

Copy link
Member

@benhillis benhillis commented Jun 21, 2019

@gperciva - Thanks, digging into that now.

@cleemesser

This comment has been minimized.

Copy link

@cleemesser cleemesser commented Jun 23, 2019

I get the following error when trying to convert:

For information on key differences with WSL 2 please visit https://aka.ms/wsl2
The requested operation could not be completed due to a virtual disk system limitation.  Virtual hard disk files must be uncompressed and unencrypted and must not be sparse.

Not sure if this is the same error or something different. I've collected logs if it the problem is not simply that you can't have a encrypted C:\ OS drive.

If I try running powershell as admin, I get a different error:

PS C:\Users\code> wsl --set-version Debian 2
Conversion in progress, this may take a few minutes...
For information on key differences with WSL 2 please visit https://aka.ms/wsl2
The operation timed out because a response was not received from the virtual machine or container.

Windows version 1903 build 18922.1000
Note that I have (and am required to use for compliance reasons) bitlocker enabled on all drives on this and all work computers.

@craigloewen-msft

This comment has been minimized.

Copy link
Member

@craigloewen-msft craigloewen-msft commented Jun 24, 2019

@cleemesser your issue looks to be a duplicate of #4103 I'd recommend following the discussion there.

@avdi

This comment has been minimized.

Copy link

@avdi avdi commented Jun 25, 2019

Is there some way I can get more info about my "Conversion failed" error? I'd really like to play with WSL2, but I'm stuck at this rather opaque message when trying to convert my Ubuntu instance.

Thanks!

@benhillis

This comment has been minimized.

Copy link
Member

@benhillis benhillis commented Jun 25, 2019

There are a set of fixes that should address most of these issues on the way to an insider build soon. These fixes include more details on why the conversion failed (if there are remaining issues).

@QingGo

This comment has been minimized.

Copy link

@QingGo QingGo commented Jun 30, 2019

I encount the same "Unspecified error" when I use:
wsl --set-version Ubuntu 2

and then I found this issue, and try to use these command below:

wsl.exe --export Ubuntu C:\ubuntu\ubuntu_file.tar.gz
wsl.exe --import MyUbuntu C:\ubuntu C:\ubuntu\ubuntu_file.tar.gz  --version 2

also encount the same "Unspecified error".

I noticed that the file size of "ubuntu_file.tar.gz" that I exported is more than 14GB because I have been using my WSL1 Ubuntu for a few months . When I import this file for WSL2, I noticed that my memory usage grow very quickly and finally up to 98%. My computer have total 16 GB memory and the process "Vmmem" take more than 8GB memory. Finally "Unspecified error" appear in the powershell again. Maybe memory not enough is one of the reason to encount "Unspecified error", So I want to know if there is a way to use less memory when converting WSL1 to WSL2?

My windows version is 18922.rs.

If you want to know any another informaion for debug, feel free to contact me.

Thank you

@znmeb

This comment has been minimized.

Copy link

@znmeb znmeb commented Jul 4, 2019

I just updated to Win10 Pro 190268-1650. I had a Fedora Remix WSL installed and got "unspecified error" trying to convert it to WSL 2. I'm going to try again - installing Ubuntu 18.04 LTS, Debian and openSUSE Leap to see if any of them work.

P.S.: I also have Docker for Windows on this machine. I opened Hyper-V Manager and I can see the Moby VM - it's the only VM. If the conversion had worked, would I see another VM for WSL 2?

  • Debian: Conversion complete
  • fedoraremix: Unspecifed error
  • Ubuntu 18.04: Unspecified error
  • openSUSE-Leap-15-1: Conversion complete

So I have two running with WSL 2. I'm going to try setting the default to 2 and reinstalling the two that didn't convert.

That did the trick!!

 wsl --list --all --verbose
  NAME                  STATE           VERSION
* openSUSE-Leap-15-1    Stopped         2
  Debian                Stopped         2
  Ubuntu-18.04          Stopped         2
  fedoraremix           Stopped         2
@avdi

This comment has been minimized.

Copy link

@avdi avdi commented Jul 13, 2019

I just updated to Win10 Pro 190705-1333 and once again got:

PS C:\Users\avdi_000> wsl --set-version Ubuntu 2 --verbose
Conversion in progress, this may take a few minutes...
For information on key differences with WSL 2 please visit https://aka.ms/wsl2
Conversion failed.

Is there any way I can find out more about why it failed?

@craigloewen-msft

This comment has been minimized.

Copy link
Member

@craigloewen-msft craigloewen-msft commented Jul 15, 2019

Please see @benhillis's comment above, there are a set of fixes coming to Windows Insiders that will help address these issues. Thank you for your patience :)

@clshortfuse

This comment has been minimized.

Copy link

@clshortfuse clshortfuse commented Jul 28, 2019

I was able to solve my issue by removing out all my node_modules projects folders and npm cache clean --force. On WSLv1, installing node packages would sometimes give me BSODs and EACCES errors as detailed in #14 so I figured cleaning those folders out would help.

Edit: For reference, I was getting the same tar format cannot archive socket error.

Edit2: Getting 0x80080005 now, but I guess it's progress. Rebooted. Working now. :)

@Menci

This comment has been minimized.

Copy link

@Menci Menci commented Aug 10, 2019

I got this error message with logging enabled:

D:\logs>wsl --set-version Ubuntu-18.04 2
Conversion in progress, this may take a few minutes...
For information on key differences with WSL 2 please visit https://aka.ms/wsl2
Importing the distribution failed.
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/resize_policy/sample_resize_trigger.hpp: Write failed
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/resize_policy/sample_size_policy.hpp: Write to restore size failed
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/rc_binomial_heap_/constructors_destructor_fn_imps.hpp: Write to restore size failed
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/rc_binomial_heap_/debug_fn_imps.hpp: Write to restore size failed
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/rc_binomial_heap_/erase_fn_imps.hpp: Write to restore size failed
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/rc_binomial_heap_/insert_fn_imps.hpp: Write to restore size failed
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/rc_binomial_heap_/rc.hpp: Write to restore size failed
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/rc_binomial_heap_/rc_binomial_heap_.hpp: Write to restore size failed
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/rc_binomial_heap_/split_join_fn_imps.hpp: Write to restore size failed
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/rc_binomial_heap_/trace_fn_imps.hpp: Write to restore size failed
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/rb_tree_map_/constructors_destructor_fn_imps.hpp: Write to restore size failed
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/rb_tree_map_/debug_fn_imps.hpp: Write to restore size failed
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/rb_tree_map_/erase_fn_imps.hpp: Write to restore size failed
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/rb_tree_map_/find_fn_imps.hpp: Write to restore size failed
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/rb_tree_map_/info_fn_imps.hpp: Write to restore size failed
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/rb_tree_map_/insert_fn_imps.hpp: Write to restore size failed
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/rb_tree_map_/node.hpp: Write to restore size failed
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/rb_tree_map_/rb_tree_.hpp: Write to restore size failed
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/rb_tree_map_/split_join_fn_imps.hpp: Write to restore size failed
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/rb_tree_map_/traits.hpp: Write to restore size failed
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/pat_trie_/constructors_destructor_fn_imps.hpp: Write to restore size failed
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/pat_trie_/debug_fn_imps.hpp: Write to restore size failed
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/pat_trie_/erase_fn_imps.hpp: Write to restore size failed
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/pat_trie_/find_fn_imps.hpp: Write to restore size failed
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/pat_trie_/info_fn_imps.hpp: Write to restore size failed
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/pat_trie_/insert_join_fn_imps.hpp: Write to restore size failed
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/pat_trie_/iterators_fn_imps.hpp: Write to restore size failed
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/pat_trie_/pat_trie_.hpp: Write to restore size failed
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/pat_trie_/pat_trie_base.hpp: Write to restore size failed
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/pat_trie_/policy_access_fn_imps.hpp: Write to restore size failed
./usr/lib/gcc/x86_64-w64-mingw32/7.3-win32/include/c++/ext/pb_ds/detail/pat_trie_/r_erase_fn_imps.hpp
@mureni

This comment has been minimized.

Copy link

@mureni mureni commented Aug 15, 2019

Can someone give me a hint as to how long "a few minutes" is? I've been in this "Conversion in progress" stage for well over 30 minutes now on a SSD with ~28GB free.

Edited: Turns out it was Windows Defender Realtime Protection having a fit. Cancelled previous attempt via Ctrl-C (risking whatever may happen by doing so) and temporarily disabled Realtime Protection; completed the conversion in ~4 minutes. Likely related to #1932.

@ericblade

This comment has been minimized.

Copy link

@ericblade ericblade commented Aug 23, 2019

fwiw, I am also getting a conversion failed on a brand new install:

install windows
install video drivers
upgrade to skip ring
reinstall video drivers
install wsl1 with ubuntu-16.04 from store
set default version to wsl 2
attempt to convert ubuntu-16.04 to wsl2
conversion failed

however, it worked on the second attempt, with no differences between them

@DGollings

This comment has been minimized.

Copy link

@DGollings DGollings commented Aug 31, 2019

Received the same error, in my case it was due to a running ssh-agent(-wsl).
Commenting it out of my zshrc fixed it:
The command in question
eval $(myuser/scoop/apps/ssh-agent-wsl/current/ssh-agent-wsl -r -b)

Maybe conversions should ignore all/any user profiles?

@ojacques

This comment has been minimized.

Copy link

@ojacques ojacques commented Sep 25, 2019

/home/redacted/gems/doc/stringio-0.0.2/rdoc/js/jquery.js: Hard-link target './usr/lib/ruby/2.5.0/rdoc/generator/template/darkfish/js/jquery.js' does not exist.

I had similar errors on my conversion:

PS C:\WINDOWS\system32>  wsl --set-version Ubuntu-18.04 2 --verbose
Conversion in progress, this may take a few minutes...
For information on key differences with WSL 2 please visit https://aka.ms/wsl2
Importing the distribution failed.
./var/lib/gems/2.5.0/doc/rubygems-update-2.7.4/rdoc/js/jquery.js: Hard-link target './var/lib/gems/2.5.0/doc/rubygems-update-3.0.2/rdoc/js/jquery.js' does not exist.
./var/lib/gems/2.5.0/doc/rubygems-update-2.7.4/rdoc/fonts/Lato-Light.ttf: Hard-link target './var/lib/gems/2.5.0/doc/rubygems-update-3.0.2/rdoc/fonts/Lato-Light.ttf' does not exist.
./var/lib/gems/2.5.0/doc/rubygems-update-2.7.4/rdoc/fonts/Lato-LightItalic.ttf: Hard-link target './var/lib/gems/2.5.0/doc/rubygems-update-3.0.2/rdoc/fonts/Lato-LightItalic.ttf' does not exist.
./var/lib/gems/2.5.0/doc/rubygems-update-2.7.4/rdoc/fonts/Lato-Regular.ttf: Hard-link target './var/lib/gems/2.5.0/doc/rubygems-update-3.0.2/rdoc/fonts/Lato-Regular.ttf' does not exist.
./var/lib/gems/2.5.0/doc/rubygems-update-2.7.4/rdoc/fonts/Lato-RegularItalic.ttf: Hard-link target './var/lib/gems/2.5.0/doc/rubygems-update-3.0.2/rdoc/fonts/Lato-RegularItalic.ttf' does not exist.

bsdtar: Error exit delayed from previous errors.

And indeed, if I check in WSL1, those links are broken. I suspect this is related to a Jekyll install I have on my wsl1 / Ubuntu. But it could be anything in your Linux with broken hard links.

This is what fixed it for me:

  • Fix the broken links from within WSL1
  • Run the conversion again
  • 🎉 Enjoy WSL2!
PS C:\WINDOWS\system32>  wsl --set-version Ubuntu-18.04 2 --verbose
Conversion in progress, this may take a few minutes...
For information on key differences with WSL 2 please visit https://aka.ms/wsl2
Conversion complete.
@vbsteven

This comment has been minimized.

Copy link

@vbsteven vbsteven commented Oct 3, 2019

I had a similar issue with tar format cannot archive socket while trying to upgrade. I fixed it by logging into wsl and deleting all files in the /tmp folder.

@scottfweintraub

This comment has been minimized.

Copy link

@scottfweintraub scottfweintraub commented Oct 6, 2019

I also solved this by clearing /tmp. shrug.

@alexign

This comment has been minimized.

Copy link

@alexign alexign commented Oct 13, 2019

I confirm that clearing the contents of /tmp made the conversion possible. There were a lot of stuff from VSCode remote development such as sockets left

@poizan42

This comment has been minimized.

Copy link

@poizan42 poizan42 commented Nov 11, 2019

I have the same issue, but clearing out /tmp didn't help.

@prayagsingh

This comment has been minimized.

Copy link

@prayagsingh prayagsingh commented Jan 3, 2020

Then fails with "Unspecified error"

@johnturek I got this, but fixed by freeing up disk space from ~10gb free to 22gb free. Not sure what the minimum is. Maybe it needs a temp space to work in?

worked for me. I was getting below error. I freed up almost 5gb(from ~11gb to 16gb ) but during the conversion the memory consumption by Vmmem went up to 98% and space left in the C directory was around 2.4gb.
Error:
./home/alpha/GoWorkspace/.cache/govendor/github.com/hyperledger/fabric/vendor/github.com/docker/docker/pkg/ioutils/temp_unix.go: Write to restore size failed

@Tyar098

This comment has been minimized.

Copy link

@Tyar098 Tyar098 commented Jan 3, 2020

Same issue with message:

PS C:\Users\XXX> wsl --set-version Ubuntu 2
Conversion in progress, this may take a few minutes...
For information on key differences with WSL 2 please visit https://aka.ms/wsl2
Exporting the distribution failed.
bsdtar: (null)

deleting tmp folder worked for me 🍻

@edburns

This comment has been minimized.

Copy link

@edburns edburns commented Jan 6, 2020

Here is another instance of the conversion failing:

ver

Microsoft Windows [Version 10.0.19041.1]

Hardware: Surface Book 2.

C:\Users\edburns>wsl --set-version Ubuntu 2
Conversion in progress, this may take a few minutes...
For information on key differences with WSL 2 please visit https://aka.ms/wsl2
Importing the distribution failed.
./var/lib/gems/2.5.0/doc/jekyll-3.8.6/rdoc/js/jquery.js: Hard-link target './var/lib/gems/2.5.0/doc/jekyll-watch-2.2.1/rdoc/js/jquery.js' does not exist.
./var/lib/gems/2.5.0/doc/jekyll-3.8.6/rdoc/fonts/Lato-Light.ttf: Hard-link target './var/lib/gems/2.5.0/doc/jekyll-watch-2.2.1/rdoc/fonts/Lato-Light.ttf' does not exist.
./var/lib/gems/2.5.0/doc/jekyll-3.8.6/rdoc/fonts/Lato-LightItalic.ttf: Hard-link target './var/lib/gems/2.5.0/doc/jekyll-watch-2.2.1/rdoc/fonts/Lato-LightItalic.ttf' does not exist.
./var/lib/gems/2.5.0/doc/jekyll-3.8.6/rdoc/fonts/Lato-Regular.ttf: Hard-link target './var/lib/gems/2.5.0/doc/jekyll-watch-2.2.1/rdoc/fonts/Lato-Regular.ttf' does not exist.
./var/lib/gems/2.5.0/doc/jekyll-3.8.6/rdoc/fonts/Lato-RegularItalic.ttf: Hard-link target './var/lib/gems/2.5.0/doc/jekyll-watch-2.2.1/rdoc/fonts/Lato-RegularItalic.ttf' does not exist.
./var/lib/gems/2.5.0/doc/i18n-0.9.5/rdoc/js/jquery.js: Hard-link target './var/lib/gems/2.5.0/doc/jekyll-watch-2.2.1/rdoc/js/jquery.js' does not exist.
./var/lib/gems/2.5.0/doc/i18n-0.9.5/rdoc/fonts/Lato-Light.ttf: Hard-link target './var/lib/gems/2.5.0/doc/jekyll-watch-2.2.1/rdoc/fonts/Lato-Light.ttf' does not exist.
./var/lib/gems/2.5.0/doc/i18n-0.9.5/rdoc/fonts/Lato-LightItalic.ttf: Hard-link target './var/lib/gems/2.5.0/doc/jekyll-watch-2.2.1/rdoc/fonts/Lato-LightItalic.ttf' does not exist.
./var/lib/gems/2.5.0/doc/i18n-0.9.5/rdoc/fonts/Lato-Regular.ttf: Hard-link target './var/lib/gems/2.5.0/doc/jekyll-watch-2.2.1/rdoc/fonts/Lato-Regular.ttf' does not exist.
./var/lib/gems/2.5.0/doc/i18n-0.9.5/rdoc/fonts/Lato-RegularItalic.ttf: Hard-link target './var/lib/gems/2.5.0/doc/jekyll-watch-2.2.1/rdoc/fonts/Lato-RegularItalic.ttf' does not exist.
./var/lib/gems/2.5.0/doc/eventmachine-1.2.7/rdoc/js/jquery.js: Hard-link target './var/lib/gems/2.5.0/doc/jekyll-watch-2.2.1/rdoc/js/jquery.js' does not exist.
./var/lib/gems/2.5.0/doc/eventmachine-1.2.7/rdoc/fonts/Lato-Light.ttf: Hard-link target './var/lib/gems/2.5.0/doc/jekyll-watch-2.2.1/rdoc/fonts/Lato-Light.ttf' does not exist.
./var/lib/gems/2.5.0/doc/eventmachine-1.2.7/rdoc/fonts/Lato-LightItalic.ttf: Hard-link target './var/lib/gems/2.5.0/doc/jekyll-watch-2.2.1/rdoc/fonts/Lato-LightItalic.ttf' does not exist.
./var/lib/gems/2.5.0/doc/eventmachine-1.2.7/rdoc/fonts/Lato-Regular.ttf: Hard-link target './var/lib/gems/2.5.0/doc/jekyll-watch-2.2.1/rdoc/fonts/Lato-Regular.ttf' does not exist.
./var/lib/gems/2.5.0/doc/eventmachine-1.2.7/rdoc/fonts/Lato-RegularItalic.ttf: Hard-link target './var/lib/gems/2.5.0/doc/jekyll-watch-2.2.1/rdoc/fonts/Lato-RegularItalic.ttf' does not exist.
./var/lib/gems/2.5.0/doc/em-websocket-0.5.1/rdoc/js/jquery.js: Hard-link target './var/lib/gems/2.5.0/doc/jekyll-watch-2.2.1/rdoc/js/jquery.js' does not exist.
./var/lib/gems/2.5.0/doc/em-websocket-0.5.1/rdoc/fonts/Lato-Light.ttf: Hard-link target './var/lib/gems/2.5.0/doc/jekyll-watch-2.2.1/rdoc/fonts/Lato-Light.ttf' does not exist.
./var/lib/gems/2.5.0/doc/em-websocket-0.5.1/rdoc/fonts/Lato-LightItalic.ttf: Hard-link target './var/lib/gems/2.5.0/doc/jekyll-watch-2.2.1/rdoc/fonts/Lato-LightItalic.ttf' does not exist.
./var/lib/gems/2.5.0/doc/em-websocket-0.5.1/rdoc/fonts/Lato-Regular.ttf: Hard-link target './var/lib/gems/2.5.0/doc/jekyll-watch-2.2.1/rdoc/fonts/Lato-Regular.ttf' does not exist.
./var/lib/gems/2.5.0/doc/em-websocket-0.5.1/rdoc/fonts/Lato-RegularItalic.ttf: Hard-link target './var/lib/gems/2.5.0/doc/jekyll-watch-2.2.1/rdoc/fonts/Lato-RegularItalic.ttf' does not exist.
./var/lib/gems/2.5.0/doc/concurrent-ruby-1.1.5/rdoc/js/jquery.js: Hard-link target './var/lib/gems/2.5.0/doc/jekyll-watch-2.2.1/rdoc/js/jquery.js' does not exist.
./var/lib/gems/2.5.0/doc/concurrent-ruby-1.1.5/rdoc/fonts/Lato-Light.ttf: Hard-link target './var/lib/gems/2.5.0/doc/jekyll-watch-2.2.1/rdoc/fonts/Lato-Light.ttf' does not exist.
./var/lib/gems/2.5.0/doc/concurrent-ruby-1.1.5/rdoc/fonts/Lato-LightItalic.ttf: Hard-link target './var/lib/gems/2.5.0/doc/jekyll-watch-2.2.1/rdoc/fonts/Lato-LightItalic.ttf' does not exist.
./var/lib/gems/2.5.0/doc/concurrent-ruby-1.1.5/rdoc/fonts/Lato-Regular.ttf: Hard-link target './var/lib/gems/2.5.0/doc/jekyll-watch-2.2.1/rdo

This was output after about ten minutes of waiting.

@rkingsbury

This comment has been minimized.

Copy link

@rkingsbury rkingsbury commented Jan 9, 2020

Another instance here. The error occurred after 10-20 minutes.

PS C:\Users\ryans> wsl --set-version Ubuntu 2
Conversion in progress, this may take a few minutes...
For information on key differences with WSL 2 please visit https://aka.ms/wsl2
Exporting the distribution failed.
: tar format cannot archive socket: tar format cannot archive socket: tar format cannot archive socket: tar format cannot archive socket: tar format cannot archive socket: tar format cannot archive socket: tar format cannot archive socket: tar format cannot archive socket: tar format cannot archive socket: tar format cannot archive socket: tar format cannot archive socket: tar format cannot archive socket: tar format cannot archive socket: tar format cannot archive socket: tar format cannot archive socket: tar format cannot archive socket: tar format cannot archive socket: tar format cannot archive socket: tar format cannot archive socket: tar format cannot archive socket: tar format cannot archive socket: tar format cannot archive socket: tar format cannot archive socket: tar format cannot archive socket: tar format cannot archive socket: tar format cannot archive socket: tar format cannot archive socketbsdtar: (null)
@achempak

This comment has been minimized.

Copy link

@achempak achempak commented Jan 12, 2020

I ran into this error as well. Deleting /tmp did not work. Temporarily disabling Windows security did work.

@edburns

This comment has been minimized.

Copy link

@edburns edburns commented Jan 22, 2020

I fixed the links and the conversion worked as well.

C:\Users\edburns>wsl -l -v
  NAME      STATE           VERSION
* Ubuntu    Stopped         2

@Plazmaz

This comment has been minimized.

Copy link

@Plazmaz Plazmaz commented Jan 29, 2020

For me this was triggered by a slightly different error. I had metasploit installed in my WSL, and had the directory whitelisted. The process of converting over triggered windows defender and caused this error. FWIW Running an strace of the bsdtar command others have posted was enough to help me find the offending file, which lead me to this answer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
You can’t perform that action at this time.