[Pkg-sysvinit-devel] Bug#362128: Bug#354163: Getting the machine to power down?

[Petter Reinholdtsen]

[Andreas Tille]
> I think I will use the very same system.

Thank you.  The umounting of file systems are obviously not working as
it should.  I read that from your shutdown load.

Try replacing in /etc/init.d/umountfs the line saying

  PATH=/usr/sbin:/usr/bin:/sbin:/bin

with a line saying

  PATH=/sbin:/bin:/usr/sbin:/usr/bin

I am starting to suspect the problem is that you have one set of tools
in /{s}bin/, and a different set of tools with the same names in
/usr/{s}bin/.  Try also to add 'set -x' early in umountfs, to see what
the script do when it fails.

Your problem might also be related to the NFS mount points, and the
fact that portmap is killed before nfs umounting is tried (bug
#258420).  If this is the case, I am working on a fix.

The shutdown sequence you typed in seem to jump from S30urandom
directly to S90reboot without running S31umountnfs.sh, S32portmap,
S35networking, S40umountfs and S60umountroot.  I fail to understand
how that can happen.

> This is right according to all my knowledge. What confuses me is that
>    Shutdown: hda
> seemed to have done successfully according to the screen dump which
> is really.

It confuses me too. :)

> I just have reinstalled 2.86.ds1-10 and when I do the `shutdown -h
> now' the end shows some more text and no broken grep call - if you
> think it makes sense to get these lines I'm willing to write down
> these as well but have no good idea how to copy the screen once the
> box is switched off.

It would be useful to have the output from a run with set -x as
described above, but that will be quite a lot to type, so we can wait
to see if the PATH changes help first.

Friendly,
-- 
Petter Reinholdtsen