Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #176322 > unrolled thread

shutdown fails to power off host

Started byBob McGowan <ramjr0915@gmail.com>
First post2017-01-05 08:10 +0100
Last post2017-01-18 10:30 +0100
Articles 12 — 9 participants

Back to article view | Back to linux.debian.user


Contents

  shutdown fails to power off host Bob McGowan <ramjr0915@gmail.com> - 2017-01-05 08:10 +0100
    Re: shutdown fails to power off host Bob McGowan <ramjr0915@gmail.com> - 2017-01-05 08:20 +0100
      Re: shutdown fails to power off host Johann Spies <johann.spies@gmail.com> - 2017-01-17 10:40 +0100
        Re: shutdown fails to power off host Hans <hans.ullrich@loop.de> - 2017-01-17 11:40 +0100
          Re: shutdown fails to power off host Bob McGowan <ramjr0915@gmail.com> - 2017-01-18 04:30 +0100
        Re: shutdown fails to power off host <tomas@tuxteam.de> - 2017-01-17 11:40 +0100
          Re: shutdown fails to power off host Curt <curty@free.fr> - 2017-01-17 19:10 +0100
            Re: shutdown fails to power off host Joe <joe@jretrading.com> - 2017-01-17 20:10 +0100
            Re: shutdown fails to power off host Verde Denim <tdldev@gmail.com> - 2017-01-18 14:30 +0100
              Re: shutdown fails to power off host Hans <hans.ullrich@loop.de> - 2017-01-18 14:40 +0100
    Re: shutdown fails to power off host Joerg Desch <news@jdesch.de> - 2017-01-18 08:50 +0100
      Re: shutdown fails to power off host Michael Biebl <biebl@debian.org> - 2017-01-18 10:30 +0100

#176322 — shutdown fails to power off host

FromBob McGowan <ramjr0915@gmail.com>
Date2017-01-05 08:10 +0100
Subjectshutdown fails to power off host
Message-ID<sWals-7XR-3@gated-at.bofh.it>
I have done a search of the debian-user archive, using the same text as
the subject, and found several references to emails with similar
problems.  However, no exact solution was proposed.

And this actually only happens on one of the two systems I have Debian
installed on.

I'm using testing (stretch).

When I shutdown my desktop system, the screen displays messages from
systemd (I presume), the last of which is "Reached target Shutdown".

It then just sits there.  I have taken to using a power strip with a
switch as a way to quickly turn the host off, once it has reached the
target.

On my laptop, I see the same message, followed by powering off the system.

Tonight, I happened to take longer than usual to get to my desktop
system, and while writing down the exact wording of the message, the
kernel panicked.

My laptop is around ten years old, an HP Pavilion dv9000, the desktop is
about half that age, a home built "gamer" level hardware system.

Any ideas what I should be looking for?  The fact the kernel panics on
my desktop would imply to me there is a kernel configuration issue of
some sort, but I have no idea where to start.

Thanks,

Bob

[toc] | [next] | [standalone]


#176323

FromBob McGowan <ramjr0915@gmail.com>
Date2017-01-05 08:20 +0100
Message-ID<sWav7-82I-1@gated-at.bofh.it>
In reply to#176322
On 01/04/2017 10:59 PM, Bob McGowan wrote:
> I have done a search of the debian-user archive, using the same text as
> the subject, and found several references to emails with similar
> problems.  However, no exact solution was proposed.
> 
> And this actually only happens on one of the two systems I have Debian
> installed on.
> 
> I'm using testing (stretch).
> 
> When I shutdown my desktop system, the screen displays messages from
> systemd (I presume), the last of which is "Reached target Shutdown".
> 
> It then just sits there.  I have taken to using a power strip with a
> switch as a way to quickly turn the host off, once it has reached the
> target.
> 
> On my laptop, I see the same message, followed by powering off the system.
> 
> Tonight, I happened to take longer than usual to get to my desktop
> system, and while writing down the exact wording of the message, the
> kernel panicked.
> 
> My laptop is around ten years old, an HP Pavilion dv9000, the desktop is
> about half that age, a home built "gamer" level hardware system.
> 
> Any ideas what I should be looking for?  The fact the kernel panics on
> my desktop would imply to me there is a kernel configuration issue of
> some sort, but I have no idea where to start.
> 
> Thanks,
> 
> Bob
> 

My apologies, I failed to mention:

I'm using Xfce4 as my windowing system on both hosts.

And I'm using the 'shutdown' menu option from the "Action Buttons" panel
plugin.

Bob

[toc] | [prev] | [next] | [standalone]


#176781

FromJohann Spies <johann.spies@gmail.com>
Date2017-01-17 10:40 +0100
Message-ID<t0ypc-5hh-35@gated-at.bofh.it>
In reply to#176323

[Multipart message — attachments visible in raw view] — view raw

On 5 January 2017 at 09:09, Bob McGowan <ramjr0915@gmail.com> wrote:

> On 01/04/2017 10:59 PM, Bob McGowan wrote:
> > I have done a search of the debian-user archive, using the same text as
> > the subject, and found several references to emails with similar
> > problems.  However, no exact solution was proposed.
> >
> > And this actually only happens on one of the two systems I have Debian
> > installed on.
> >
> > I'm using testing (stretch).
> >
> > When I shutdown my desktop system, the screen displays messages from
> > systemd (I presume), the last of which is "Reached target Shutdown".
> >
>

I get that when I use 'sudo halt'

When I use 'sudo halt -p'  it powers off.

So I would suggest you look at the underlying command on the button of the
computer which do not power off and change the command.


Look at 'man shutdown'  for the options when you use 'shutdown'  in stead
of 'halt'.

Regards
Johann

[toc] | [prev] | [next] | [standalone]


#176783

FromHans <hans.ullrich@loop.de>
Date2017-01-17 11:40 +0100
Message-ID<t0zlh-5WC-33@gated-at.bofh.it>
In reply to#176781
I remember this discussion from sime time ago. Debian has changed a real 
poweroff from "halt" to "halt -p". The second one is according to the manual.

As far as I remeber, "shutdown" is just a wrapper fpr the halt command, but I 
am not quite sure. 

But one thing was cleared: To poweroff a debian systenm, the command "halt -p" 
is recommended.

Besides: This behaviour is also now in kali linux integrated, which was also 
using the command "halt" for a long time. But now it's "halt -p", too, also on 
the livefile.

Best

Hans

[toc] | [prev] | [next] | [standalone]


#176796

FromBob McGowan <ramjr0915@gmail.com>
Date2017-01-18 04:30 +0100
Message-ID<t0P6G-7de-9@gated-at.bofh.it>
In reply to#176783
On 01/17/2017 02:39 AM, Hans wrote:
> I remember this discussion from sime time ago. Debian has changed a real 
> poweroff from "halt" to "halt -p". The second one is according to the manual.
> 
> As far as I remeber, "shutdown" is just a wrapper fpr the halt command, but I 
> am not quite sure. 
> 
> But one thing was cleared: To poweroff a debian systenm, the command "halt -p" 
> is recommended.
> 
> Besides: This behaviour is also now in kali linux integrated, which was also 
> using the command "halt" for a long time. But now it's "halt -p", too, also on 
> the livefile.
> 
> Best
> 
> Hans
> 

Hi,

Thanks for the suggestions and insight to the problem.

In my case:

1.  The problem was with *any* "shutdown", from the command line, via
halt or shutdown, or through menus of the window system.

2.  The comment by joe@jretrading.com about unmount issues rings a bell,
I think I saw something about failure to sync at one point.

3.  I did try 'halt -p', same result.

4.  There have been two or three updates since I sent my original
question, and the system is now halting and powering off as expected.

Bob

[toc] | [prev] | [next] | [standalone]


#176784

From<tomas@tuxteam.de>
Date2017-01-17 11:40 +0100
Message-ID<t0zlh-5WC-35@gated-at.bofh.it>
In reply to#176781
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, Jan 17, 2017 at 11:35:28AM +0200, Johann Spies wrote:
> On 5 January 2017 at 09:09, Bob McGowan <ramjr0915@gmail.com> wrote:
> 
> > On 01/04/2017 10:59 PM, Bob McGowan wrote:
> > > I have done a search of the debian-user archive, using the same text as
> > > the subject, and found several references to emails with similar
> > > problems.  However, no exact solution was proposed.
> > >
> > > And this actually only happens on one of the two systems I have Debian
> > > installed on.
> > >
> > > I'm using testing (stretch).
> > >
> > > When I shutdown my desktop system, the screen displays messages from
> > > systemd (I presume), the last of which is "Reached target Shutdown".
> > >
> >
> 
> I get that when I use 'sudo halt'
> 
> When I use 'sudo halt -p'  it powers off.

"halt" is "shutdown" -- at least from where you are shooting. From halt's
man page:

     If halt or reboot is called when the system is not in runlevel
     0 or 6, in other words  when  it's  running  normally, shutdown
     will be invoked instead (with the -h or -r flag). For more info
     see the shutdown(8) manpage.

> So I would suggest you look at the underlying command on the button of the
> computer which do not power off and change the command.
> 
> Look at 'man shutdown'  for the options when you use 'shutdown'  in stead
> of 'halt'.

I agree, it should be in the options. That said, one of the systems I take
care of *sometimes* ends up in this state (i.e. "Reached target ..."), but
most of the time actually powers off.

Since it's a desktop I told the users that it's safe to power off the thing
when in this state and filed it under "unsolved hardware/init system quirks".

regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlh98ooACgkQBcgs9XrR2kYHnwCdEUocDUqU6+ZCEKaVwVnhFRp0
yFwAn2t/TFQNikQsV+Y+79RWUWXr7Xp0
=7fMt
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]


#176787

FromCurt <curty@free.fr>
Date2017-01-17 19:10 +0100
Message-ID<t0GmK-1VI-5@gated-at.bofh.it>
In reply to#176784
On 2017-01-17, <tomas@tuxteam.de> <tomas@tuxteam.de> wrote:
>
> Since it's a desktop I told the users that it's safe to power off the thing
> when in this state and filed it under "unsolved hardware/init system quirks".

I suffer from one of these unsolved quirks. Occasionally my machine will
shutdown correctly but will not power off. I have detected no
discernible pattern (or discerned no detectable pattern).

I power the machine off manually when the quirk occurs.


> regards
> - -- tomás
>
>


-- 
“It is enough that the arrows fit exactly in the wounds that they have made.”
Franz Kafka

[toc] | [prev] | [next] | [standalone]


#176789

FromJoe <joe@jretrading.com>
Date2017-01-17 20:10 +0100
Message-ID<t0HiO-2uu-29@gated-at.bofh.it>
In reply to#176787
On Tue, 17 Jan 2017 18:00:00 +0000 (UTC)
Curt <curty@free.fr> wrote:

> On 2017-01-17, <tomas@tuxteam.de> <tomas@tuxteam.de> wrote:
> >
> > Since it's a desktop I told the users that it's safe to power off
> > the thing when in this state and filed it under "unsolved
> > hardware/init system quirks".  
> 
> I suffer from one of these unsolved quirks. Occasionally my machine
> will shutdown correctly but will not power off. I have detected no
> discernible pattern (or discerned no detectable pattern).
> 
> I power the machine off manually when the quirk occurs.
> 

Me too. Sid on LVM2, AMD video on Giga MB, fails maybe 10%-20% of
shutdowns. The small amount of evidence suggests trouble dismounting the
hard drive, with the device mapper showing an unknown number of devices
having failed to clear, and no sound of the heads parking. Replacing
the hard drive (just age, not for this problem) has improved speeds of
some actions, and not changed this behaviour at all.

There is also trouble booting sometimes, which appears not to correlate
at all with the shutdown trouble. I think that is something to do with
video driving, but I can't get any kind of evidence for that, either,
other than that it always crashes when the display switches from low-res
text to high-res text. Nothing in any log, nothing at all to put in a
bug report. Hey, it's sid.

-- 
Joe

[toc] | [prev] | [next] | [standalone]


#176806

FromVerde Denim <tdldev@gmail.com>
Date2017-01-18 14:30 +0100
Message-ID<t0Ytl-4D1-39@gated-at.bofh.it>
In reply to#176787

On 1/17/2017 1:00 PM, Curt wrote:
> On 2017-01-17, <tomas@tuxteam.de> <tomas@tuxteam.de> wrote:
>> Since it's a desktop I told the users that it's safe to power off the thing
>> when in this state and filed it under "unsolved hardware/init system quirks".
> I suffer from one of these unsolved quirks. Occasionally my machine will
> shutdown correctly but will not power off. I have detected no
> discernible pattern (or discerned no detectable pattern).
>
> I power the machine off manually when the quirk occurs.
>
>
>> regards
>> - -- tomás
>>
>>
>
+1 - I have a win 8 vm that currently exhibits this lovely feature -  i 
boot the host, bring up the vm, log in, and get a black (blank) session 
window. I can force it to shut down by selecting "shut down" for the 
virtual machine and then closing the session window. I can also suspend 
the machine through normal action function. But either resuming the 
machine or shutting down and re-initializing brings the login and 
post-login brings the black hole of nothing. I've been scratching my 
head as to how this machine got into this state since it did seem to 
work the first 5 or  6 times I brought it up. Virtual machines seem 
(sometimes) to have their moments just as hosts do.

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

[toc] | [prev] | [next] | [standalone]


#176807

FromHans <hans.ullrich@loop.de>
Date2017-01-18 14:40 +0100
Message-ID<t0YCZ-4Gk-1@gated-at.bofh.it>
In reply to#176806
I had this issue in the past. Sometimes I could fix it by just reinstalling 
grub and the kernel.

However, what that fixed? Dunno, but worked for me.

Best

Hans

[toc] | [prev] | [next] | [standalone]


#176800

FromJoerg Desch <news@jdesch.de>
Date2017-01-18 08:50 +0100
Message-ID<t0Tah-1cB-9@gated-at.bofh.it>
In reply to#176322
Am Wed, 04 Jan 2017 22:59:46 -0800 schrieb Bob McGowan:

> When I shutdown my desktop system, the screen displays messages from
> systemd (I presume), the last of which is "Reached target Shutdown".

Just a thought...

I'm running Debian Jessie and I see the same behavior with my Thinkpad 
T500.

In my case the reason is the Network Manager. I have 2 NFS shares mounted 
over Wifi. The Network Manager stops Wifi before unmounting the NFS 
shares. This leads to a looooong time out. After that, I see the "Reached 
target Shutdown" message and the system in still powered.

I have to unmount the NFS volumes first and than I can shutdown the 
system.

[toc] | [prev] | [next] | [standalone]


#176801

FromMichael Biebl <biebl@debian.org>
Date2017-01-18 10:30 +0100
Message-ID<t0UJ4-2cD-17@gated-at.bofh.it>
In reply to#176800

[Multipart message — attachments visible in raw view] — view raw

Am 18.01.2017 um 08:44 schrieb Joerg Desch:
> Am Wed, 04 Jan 2017 22:59:46 -0800 schrieb Bob McGowan:
> 
>> When I shutdown my desktop system, the screen displays messages from
>> systemd (I presume), the last of which is "Reached target Shutdown".
> 
> Just a thought...
> 
> I'm running Debian Jessie and I see the same behavior with my Thinkpad 
> T500.
> 
> In my case the reason is the Network Manager. I have 2 NFS shares mounted 
> over Wifi. The Network Manager stops Wifi before unmounting the NFS 
> shares. This leads to a looooong time out. After that, I see the "Reached 
> target Shutdown" message and the system in still powered.
> 
> I have to unmount the NFS volumes first and than I can shutdown the 
> system.

You could unmount the NFS shares via a dispatcher hook
See man NetworkManager → pre-down


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web