/qubes-issues

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

R4.0-rc1 fails to shutdown #2957

Open
JPL1 opened this Issue Aug 2, 2017 · 18 comments

Comments

Assignees
No one assigned
Labels
Projects
None yet
Milestone
  Release 4.0 updates
8 participants
@JPL1 @JoeThielen @holiman @marmarek @mickewen @OldPeasant @andrewdavidwong @blacklight447
@JPL1

JPL1 commented Aug 2, 2017

Qubes OS version R4.0-rc1

Gets stuck on 'device-mapper failing to remove...' - I can check next time I shut down if you need more info

@marmarek marmarek added bug P: major labels Aug 2, 2017

@marmarek marmarek added this to the Release 4.0 milestone Aug 2, 2017

@JoeThielen

This comment has been minimized.

Show comment
Hide comment
@JoeThielen

JoeThielen Sep 8, 2017

Qubes OS version R4.0-rc1

Did this for me too. Rebooted twice, shutdown once. All failed with the same thing.

I had already updated Qubes via dom0, if that matters (installed & updated today).

JoeThielen commented Sep 8, 2017

Qubes OS version R4.0-rc1

Did this for me too. Rebooted twice, shutdown once. All failed with the same thing.

I had already updated Qubes via dom0, if that matters (installed & updated today).
@JoeThielen

This comment has been minimized.

Show comment
Hide comment
@JoeThielen

JoeThielen Sep 8, 2017

Screenshot attached. There were many more instances of "Command failed" that scrolled by before this.

errors

JoeThielen commented Sep 8, 2017

Screenshot attached. There were many more instances of "Command failed" that scrolled by before this.

errors
@holiman

This comment has been minimized.

Show comment
Hide comment
@holiman

holiman Sep 14, 2017

Having the exact same issue (and an almost identical photo), also R4.0-rc1
Running on a Librem13v2, with two ssd-disks, automatically paritioned. Always fail to shutdown, sometimes with the messages above, sometimes with just a black screen.

holiman commented Sep 14, 2017 •
edited
Edited 1 time
  • @holiman holiman edited Sep 14, 2017 (most recent)

Having the exact same issue (and an almost identical photo), also R4.0-rc1
Running on a Librem13v2, with two ssd-disks, automatically paritioned. Always fail to shutdown, sometimes with the messages above, sometimes with just a black screen.
@holiman

This comment has been minimized.

Show comment
Hide comment
@holiman

holiman Sep 27, 2017

Anything I can do to help debug this? It's very annoying.

holiman commented Sep 27, 2017

Anything I can do to help debug this? It's very annoying.
@holiman

This comment has been minimized.

Show comment
Hide comment
@holiman

holiman Sep 27, 2017

Anything I can do to help debug this? It's very annoying.

holiman commented Sep 27, 2017

Anything I can do to help debug this? It's very annoying.
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Sep 28, 2017

Member

Stopping qubes-core.service should shutdown all the VMs, but for some reason it doesn't work. This is why all those "Device or resource busy" errors are there.
Maybe something is wrong with ordering? Try adding After=qubesd.service to /usr/lib/systemd/system/qubes-core.service, then execute systemctl daemon-reload and see how it works then.
Member

marmarek commented Sep 28, 2017

Stopping qubes-core.service should shutdown all the VMs, but for some reason it doesn't work. This is why all those "Device or resource busy" errors are there.
Maybe something is wrong with ordering? Try adding After=qubesd.service to /usr/lib/systemd/system/qubes-core.service, then execute systemctl daemon-reload and see how it works then.
@holiman

This comment has been minimized.

Show comment
Hide comment
@holiman

holiman Sep 28, 2017

I was about to try this, but since I just previously did a dom0-upgrade with current-testing enabled, I thought I'd see if it had already been resolved.

Turned out it had, seems not to be an issue any longer. LMK if you want any additional info anyway.

holiman commented Sep 28, 2017

I was about to try this, but since I just previously did a dom0-upgrade with current-testing enabled, I thought I'd see if it had already been resolved.

Turned out it had, seems not to be an issue any longer. LMK if you want any additional info anyway.
@holiman

This comment has been minimized.

Show comment
Hide comment
@holiman

holiman Sep 29, 2017

Hm, interestingly, it seems the problem was not fixed by my upgrade. I used xfce for a couple of logins, instead of i3wm, and had no problems. Now, I went back to i3, and the problem was there again.

When I exit i3, I first logout, then do a shutdown. Whereas exiting from xfce, it's a one-step process. Maybe that has something to do with it ?

I'll retry with your suggestion later.

holiman commented Sep 29, 2017

Hm, interestingly, it seems the problem was not fixed by my upgrade. I used xfce for a couple of logins, instead of i3wm, and had no problems. Now, I went back to i3, and the problem was there again.

When I exit i3, I first logout, then do a shutdown. Whereas exiting from xfce, it's a one-step process. Maybe that has something to do with it ?

I'll retry with your suggestion later.
@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Oct 29, 2017

I have a shutdown bug in qubes 4.0rc2 but my screen is totally black

ghost commented Oct 29, 2017

I have a shutdown bug in qubes 4.0rc2 but my screen is totally black
@mickewen

This comment has been minimized.

Show comment
Hide comment
@mickewen

mickewen Oct 30, 2017

I see this too but shutdown always ends with a black screen but still powered up. I've tried logging out before shutting down as well as while still logged in. I have also done a dom0 upgrade and tried the After=qubesd.service suggestion as mentioned above although I'm not sure where to add it in the qubes-core.service file. Any help appreciated.
Motherboard is a Gigabyte B150M-HD3, BIOS ver. F20d. 8G DDR3.
Qubes R4.0-rc2 is installed on a 960 EVO NVMe, 250G. I used the Auto option in the installer to a blank drive.
I tried doing sudo halt from dom0 as well and it seemed to do more but still ended with a black screen.

I'm happy to try things out if anyone has more suggestions.

mickewen commented Oct 30, 2017 •
edited
Edited 1 time
  • @mickewen mickewen edited Oct 30, 2017 (most recent)

I see this too but shutdown always ends with a black screen but still powered up. I've tried logging out before shutting down as well as while still logged in. I have also done a dom0 upgrade and tried the After=qubesd.service suggestion as mentioned above although I'm not sure where to add it in the qubes-core.service file. Any help appreciated.
Motherboard is a Gigabyte B150M-HD3, BIOS ver. F20d. 8G DDR3.
Qubes R4.0-rc2 is installed on a 960 EVO NVMe, 250G. I used the Auto option in the installer to a blank drive.
I tried doing sudo halt from dom0 as well and it seemed to do more but still ended with a black screen.

I'm happy to try things out if anyone has more suggestions.
@OldPeasant

This comment has been minimized.

Show comment
Hide comment
@OldPeasant

OldPeasant Nov 9, 2017

On my System76 Galago Pro running R4.0-rc2, shutdown always fails (black screen, but keyboard still lit) if sys-net is still running when I try to shutdown Qubes.
When I first shutdown all VMs (looks like sys-net is the bad guy) so only dom0 remains running and then shutdown, it works fine.

(I'm new to Qubes, so I don't know which additional infos might be important. Will be happy to provide additional info, just tell me what you need)

OldPeasant commented Nov 9, 2017

On my System76 Galago Pro running R4.0-rc2, shutdown always fails (black screen, but keyboard still lit) if sys-net is still running when I try to shutdown Qubes.
When I first shutdown all VMs (looks like sys-net is the bad guy) so only dom0 remains running and then shutdown, it works fine.

(I'm new to Qubes, so I don't know which additional infos might be important. Will be happy to provide additional info, just tell me what you need)
@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Nov 10, 2017

Member

On my System76 Galago Pro running R4.0-rc2, shutdown always fails (black screen, but keyboard still lit) if sys-net is still running when I try to shutdown Qubes.
When I first shutdown all VMs (looks like sys-net is the bad guy) so only dom0 remains running and then shutdown, it works fine.

This reminds me of #1581 (see the comments for some handy scripts to automate shutting down all domUs before dom0).
Member

andrewdavidwong commented Nov 10, 2017

On my System76 Galago Pro running R4.0-rc2, shutdown always fails (black screen, but keyboard still lit) if sys-net is still running when I try to shutdown Qubes.
When I first shutdown all VMs (looks like sys-net is the bad guy) so only dom0 remains running and then shutdown, it works fine.

This reminds me of #1581 (see the comments for some handy scripts to automate shutting down all domUs before dom0).
@OldPeasant

This comment has been minimized.

Show comment
Hide comment
@OldPeasant

OldPeasant Nov 11, 2017

This reminds me of #1581 (see the comments for some handy scripts to automate shutting down all domUs before dom0).

Thanks! I now use one of those scripts and shutdown is smooth!

OldPeasant commented Nov 11, 2017 •
edited
Edited 1 time
  • @OldPeasant OldPeasant edited Nov 11, 2017 (most recent)

This reminds me of #1581 (see the comments for some handy scripts to automate shutting down all domUs before dom0).

Thanks! I now use one of those scripts and shutdown is smooth!
@mickewen

This comment has been minimized.

Show comment
Hide comment
@mickewen

mickewen Nov 14, 2017

Manually shutting down sys-net works for me too. Thanks.

mickewen commented Nov 14, 2017

Manually shutting down sys-net works for me too. Thanks.

@andrewdavidwong andrewdavidwong referenced this issue Dec 9, 2017

Closed

Shut Down does not shut down the computer #3371

@blacklight447

This comment has been minimized.

Show comment
Hide comment
@blacklight447

blacklight447 Dec 14, 2017

I talked to a user in the unoffical telegram group who goes by the name jackpot, he's on 3.2 and seems to have the same issue. He also sended me the picture below.

issue

So it doesn't seem to be a 4.0 specfic issue.

blacklight447 commented Dec 14, 2017 •
edited
Edited 1 time
  • @blacklight447 blacklight447 edited Dec 14, 2017 (most recent)

I talked to a user in the unoffical telegram group who goes by the name jackpot, he's on 3.2 and seems to have the same issue. He also sended me the picture below.

issue

So it doesn't seem to be a 4.0 specfic issue.
@JPL1

This comment has been minimized.

Show comment
Hide comment
@JPL1

JPL1 Dec 14, 2017

This is fixed for me with rc3

JPL1 commented Dec 14, 2017

This is fixed for me with rc3
@OldPeasant

This comment has been minimized.

Show comment
Hide comment
@OldPeasant

OldPeasant Dec 16, 2017

Same for me: Problem is resolved with 4.0-rc3. As well as starting VMs: Every now and then failed in 4.0-rc2, works just fine in 4.0-rc3. The Qubes team did a great job with rc3!

OldPeasant commented Dec 16, 2017

Same for me: Problem is resolved with 4.0-rc3. As well as starting VMs: Every now and then failed in 4.0-rc2, works just fine in 4.0-rc3. The Qubes team did a great job with rc3!
@blacklight447

This comment has been minimized.

Show comment
Hide comment
@blacklight447

blacklight447 Dec 17, 2017

Does anyone here know then what solved the issue, and if the solution can be backported to 3.2

blacklight447 commented Dec 17, 2017

Does anyone here know then what solved the issue, and if the solution can be backported to 3.2

@andrewdavidwong andrewdavidwong modified the milestones: Release 4.0, Release 4.0 updates Mar 31, 2018

@andrewdavidwong andrewdavidwong added the C: other label Apr 3, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment