R2 Beta 3 Shutdown problem and error messages

[j...@lelantos.org]

I own a Sony VAIO Z (including an Intel Core i5, with VT-d activated, and
a double SSD mounted in RAID 0).

In a first time I installed Qubes R2 beta 2, without issue: my system
worked normally.

Like Qubes R2 beta 3 has been released this week, I uninstalled Qubes R2
beta 2 and I formated my SSDs before installing the new release.

The installation went smoothly. And I installed all available updates for
Dom0 and fedora-18-x64.

But, with the R2 beta 3, I have a problem for shutting down my computer.


First, when I boot the laptop I receive the following error message, after
the GRUB starting screen:

[ 1.660071] systemd[1]: Job multipathd.service/start deleted to break
orderin
g cycle starting with basic.target/start

(The first number, between square brackets, change at each time.)


Then, when I shutdown (or reboot) my laptop I receive the following error
message:

[ 1.660071] systemd[1]: Job multipathd.service/start deleted to break
orderin
g cycle starting with basic.target/start
dracut Warning: Cannot umount /oldroot
dracut Warning: total 0
dracut Warning: lr-x------ 1 root 0 64 Dec 13 16:28 0 -> /dev/console
dracut Warning: l-wx------ 1 root 0 64 Dec 13 16:28 1 -> /dev/console
dracut Warning: lr-x------ 1 root 0 64 Dec 13 16:28 2 -> /dev/console
dracut Warning: lr-x------ 1 root 0 64 Dec 13 16:28 255 -> /shutdown
mdadm: Cannot get exclusive access to /dev/md126:Perhaps a running
process, mounted filesystem or active volume group?
mdadm: Cannot get exclusive access to /dev/md126:Perhaps a running
process, mounted filesystem or active volume group?
mdadm: Cannot stop container /dev/md127: member md126 still active
Powering off.

The main problem is that my computer don't want to shutdown (or reboot) by
itself after this error message... I have to do it manually.


Do you think that this problem can be resolved?

[Franz]

Lenovo x230 was able to shutdown correctly with r2b2, but it freezes to a black screen with a cursor in the high left corner with r2b3 clean install

best

Franz

--
You received this message because you are subscribed to the Google Groups "qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users...@googlegroups.com.
To post to this group, send email to qubes...@googlegroups.com.
Visit this group at http://groups.google.com/group/qubes-users.
For more options, visit https://groups.google.com/groups/opt_out.

[david.s...@gmail.com]

I own a x230t and I just ordered a second R&D SSD. I guess that was a good call.

[imspe...@gmail.com]

I too have a shutdown issue. It never shuts down, just stalls on the latest beta, for me.

The bar takes forever, about ten minutes to reach the end, and then it just freezes. If I press shift-tab (or ctrl-tab, I forget which), I read the following dialog, among other messages:

Could not detach DM /dev/dm-0: Device or resource busy
Not all DM devices detached, 1 left
Cannot finalize remaining file systems and devices, giving up

I have to do a cold boot to reset it. A soft boot doesn't work.

[Taichung Guy]

The same for me (Lenovo Thinkpad T430s). When attempting to shutdown or restart from Xfce or KDE menus the system after a while freezes and has to be shutdown manually.
To have a proper shutdown I have to close all the apps then, from dom0 terminal, shutdown the different AppVM and then execute "shutdown now" command.

[cprise]

I'm still lacking my appvms (restore problems) so haven't run many apps yet... But this problem has occurred once on my T430s since I installed R2B3 yesterday. The last message on the console was that it was turning system off, but it just sat there with the fan noisily blowing hot air for over 5 mins; then I forced it off.

[Christopher Lee]

I have the same shutdown problem with R2B3 on my Thinkpad T430, both on attempted shutdown and reboot.  This didn't occur under R2B2.

[cprise]

On 12/15/13 12:04, cprise wrote:

I'm still lacking my appvms (restore problems) so haven't run many apps yet... But this problem has occurred once on my T430s since I installed R2B3 yesterday. The last message on the console was that it was turning system off, but it just sat there with the fan noisily blowing hot air for over 5 mins; then I forced it off.

FWIW, the shutdown problem occurred only that one time, so far. Since then, shutdowns have behaved just like under R2b2 (the system acts like its stuck in a race condition for 70-90 seconds, then shuts off or restarts).

[Axon]

Christopher Lee:

> I have the same shutdown problem with R2B3 on my Thinkpad T430, both on
> attempted shutdown and reboot. This didn't occur under R2B2.
>

Yes, I'm experiencing the same issue as others in this thread. I believe
the problem is with the netvm not shutting down, as I stated here:
https://groups.google.com/d/topic/qubes-users/Iy5R-wsCAOc/discussion

The following currently seems to be a successful workaround:

1. Shut down all programs running in AppVMs.
2. [dom0] qvm-shutdown --all --exclude=netvm
3. [dom0] qvm-kill netvm
4. [dom0] shutdown now

This should also prevent the error that people who have RAID devices are
seeing.

[Axon]

Axon:

I should add: I don't know what the qvm-kill command actually *does*, so
I don't know whether it's dangerous. However, we have little choice,
since the netvm won't shut down on its own and has to be killed one way
or the other.

Does anyone know what qvm-kill actually does? Is it "safe"?

[Marek Marczykowski-Górecki]

It does "hard poweroff" of the VM. It's better to do qvm-shutdown first, then
if it doesn't work use qvm-kill - in case of this problem, netvm system will
be already shutdown (and hung on some late shutdown task). Actually this would
work better:
qvm-shutdown --all --wait
--wait option will kill VM after 60s timeout.

BTW This is now tracked here:
http://wiki.qubes-os.org/trac/ticket/763
I'm able to reproduce this problem on my test machine, so first step to fix
the problem ahead.

--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

[Axon]

Marek Marczykowski-Górecki:

Ah, that is helpful. Thank you. I will now run the following script when
I want to shut down (which is actually the one I was using before I
added the qvm-kill part):

#!/bin/bash
qvm-shutdown --all --wait
shutdown now

[Rob Townley]

Is there any kinda timeline on when that patch will show up in updates?

[Rob Townley]

[Marek Marczykowski-Górecki]

On 21.03.2014 04:48, Rob Townley wrote:
> Is there any kinda timeline on when that patch will show up in updates?

There are already in current-testing repository. Most likely at the beginning
of next week will be available as ordinary updates.

[Thierry Bon]

I've same issue on my R2B3 EliteBook 8440p.

The following is a successful workaround:

1. Shut down all programs running in AppVMs.
2. [dom0] qvm-shutdown --all --exclude=netvm
3. [dom0] qvm-kill netvm
4. [dom0] shutdown now

How can I change dom0 KDE shutdown button script ?

[Thierry Bon]

Hi,

How can we test this fix manually ?
(I've already make a full software update with lab/testing repository)

[Rob Townley]

when you enter "poweroff" at the command line or choose shutdown from
the KDE menu and the system hangs before powering off, then the
patches failed. If your machine powers off, then the patch works.

If you want more details, press CTRL-ALT-F2, logon as root.
#qvm-ls (examine vm status)
#qvm-shutdown --exclude=netvm --all
#qvm-ls

(examine vm status)

#qvm-shutdown netvm
#qvm-ls
#qvm-ls (did it stop like the other VMs?)

Electriciy was interrupted and the machine was reset. i applied
updates and now it shuts down just fine.
YEAH:)

[Rob Townley]

Thierry,

i missed your previous postings ... What do you mean by "testing it manually?"

[Thierry Bon]

Patch must be applied with all vm down ?

[Thierry Bon]

Hi,

I've patched my system with all VM up.
But it's doesn't fix issue...

Is there a way to modify shutdown process by adding qvm-shutdown script in shutdown script ?
(rc.d ?? )

Thierry