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

Cannot start Ubuntu on build 19033.1 #4725

Closed
kpeters-cbsi opened this issue Dec 2, 2019 · 16 comments
Closed

Cannot start Ubuntu on build 19033.1 #4725

kpeters-cbsi opened this issue Dec 2, 2019 · 16 comments
Assignees

Comments

@kpeters-cbsi
Copy link

Please use the following bug reporting template to help produce issues which are actionable and reproducible, including all command-line steps necessary to induce the failure condition. Please fill out all the fields! Issues with missing or incomplete issue templates will be closed.

If this is a console issue (a problem with layout, rendering, colors, etc.), please post to the console issue tracker.

Important: Do not open GitHub issues for Windows crashes (BSODs) or security issues. Please direct all Windows crashes and security issues to [email protected]. Ideally, please configure your machine to capture minidumps, repro the issue, and send the minidump from "C:\Windows\minidump".\

See our contributing instructions for assistance.

Please fill out the below information:

  • Your Windows build number: 19033.1

  • What you're doing and what's happening: When I type "bash" at the Windows command prompt, I get "The Windows Subsystem for Linux instance has terminated"

  • What's wrong / what should be happening instead: bash / Ubuntu should start.

  • Strace of the failing command, if applicable: N/A

  • Logs: bash logs.zip

@benhillis benhillis self-assigned this Dec 2, 2019
@benhillis
Copy link
Member

@kpeters-cbsi - It looks like you are hitting a timeout waiting for the VM to start. Is this a very slow machine by chance? Does this hit 100% of the time or only sometimes?

@kpeters-cbsi
Copy link
Author

kpeters-cbsi commented Dec 2, 2019 via email

@benhillis
Copy link
Member

@kpeters-cbsi - if you install a new distro (like debian) does this still reproduce?

@kpeters-cbsi
Copy link
Author

kpeters-cbsi commented Dec 2, 2019 via email

@benhillis
Copy link
Member

Interesting... I wonder if there was something about your old VHDX that was causing mounting the VHD to take a long time.

@kpeters-cbsi
Copy link
Author

The only weirdness I can think of is that I had an SSHFS mount in fstab that I haven't since restored.

@benhillis
Copy link
Member

Ah interesting... that could definitely cause issues if your ssh server isn't responding.

@ghost
Copy link

ghost commented Dec 5, 2019

@benhillis I had meet the same issue
windows build number: 19035.1000
the ubuntu(wsl2) can not start, the windows crashed when I press the icon.
After I reinstall ubuntu and set version to 2, nothing effect.

NO VMware or VirtualBox, and How can I get the useful log, like lxcore_user.etl etc.

@awson
Copy link

awson commented Dec 5, 2019

Windows build number: 19035.1000
Wsl 2 is slow as hell at startup (but still starts).

(Yesterday I've been stuck in #4731, today I've upgraded to 19035.1, the network issue has been gone, but it's now horrible slow at startup)

@gloveboxes
Copy link

gloveboxes commented Dec 6, 2019

yeah, same issue. Take about 40 seconds to start a bash shell (Ubuntu 18.04). It started happening with slow ring build 19035. Noticed if you press ctrl+c it kills whatever is hanging and takes you to the command prompt. Running on the latest Surface Laptop 3, 16GB, i7. I think WSL CPU usage is up too, I noticed my laptop is constantly hot...

@Biswa96
Copy link

Biswa96 commented Dec 6, 2019

I'm using WSL with 19035, no issue.

@archilkarchava
Copy link

The only weirdness I can think of is that I had an SSHFS mount in fstab that I haven't since restored.

probably related #4738

@gloveboxes
Copy link

I uninstalled Ubuntu 18.04 and reinstalled. I worked as expect until I did an apt update/upgrade of the distro and now it's back to the slow start again...

@pds2208
Copy link

pds2208 commented Dec 7, 2019

Same issue and it was on a new build and straight after an apt update/upgrade. Before the apt it was fine.

@ricardosantos9521
Copy link

This was happening to me too in Ubuntu, but i remembered the last package that was updated (wslu). I uninstalled it and it works great again (sudo apt autoremove --purge wslu).

@pds2208
Copy link

pds2208 commented Dec 8, 2019

This was happening to me too in Ubuntu, but i remembered the last package that was updated (wslu). I uninstalled it and it works great again (sudo apt autoremove --purge wslu).

Thanks! This fixed it.

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

No branches or pull requests

8 participants