Ok. I don't have a theory as to what would be short-circuiting the tail end of /etc/rc0.d for this case. As far as I can see, logind just calls 'poweroff', which should do the right thing - and certainly, sendsigs should always be followed by umountnfs.sh, networking, umountfs, umountroot, and {halt,reboot}. If these scripts are not being called (as opposed to their output simply not being shown on the console), then that can only be due to something force-halting the system.
Is there any chance you could capture the output of 'udevadm monitor -e' in this situation? I would like to verify that the udev events are what we expect.
It might also be helpful to locally divert /sbin/reboot with a wrapper that records the args, and the details about the calling process, for later analysis.
Ok. I don't have a theory as to what would be short-circuiting the tail end of /etc/rc0.d for this case. As far as I can see, logind just calls 'poweroff', which should do the right thing - and certainly, sendsigs should always be followed by umountnfs.sh, networking, umountfs, umountroot, and {halt,reboot}. If these scripts are not being called (as opposed to their output simply not being shown on the console), then that can only be due to something force-halting the system.
Is there any chance you could capture the output of 'udevadm monitor -e' in this situation? I would like to verify that the udev events are what we expect.
It might also be helpful to locally divert /sbin/reboot with a wrapper that records the args, and the details about the calling process, for later analysis.