I think I should say a little more about my "power failure" which may be relevant. I installed the NUT 2.4.3 package for use with a Cyberpower CP1500AVRLCD UPS system. I set it up with a usb connection using the usbhid-ups driver. Everything worked very well and I was pretty much done when I decided to test the "upscmd <ups> shutdown.stayoff" command. I expected this to run the usual shutdown procedure, but, as far as I could tell (my server is in another room) it did an immediate power off instead. The next two boots were very odd : part way into the boot process the machine would start to go into hibernation, where it would stay for exactly two minutes (as shown by /var/log/pm-suspend.log), before waking up and resuming the boot process. After two boots I disconnected the UPS usb cable and disabled NUT by setting "MODE=none" in /etc/nut/nut.conf and the hibernation problem went away. Amongst the fscks in my boot logs I found
init: mounted-tmp main process (877) terminated with status 127 mountall: Event failed which I eventually discovered is caused by the /tmp (non-) cleaning bug https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/523587 I figured stale files in /tmp might have been responsible for the strange behaviour on boot, and fixed this bug on my system by changing /etc/init /mounted-tmp.conf to read "start on local-filesystems". Now I'm not so sure... It seems to me that even if mountall is still running and the boredom timer does trigger the re-fsck and re-mount, it would not do so if the partitions were still mounted. So I'm wondering if maybe the NUT command did not simply power off my system, but instead did some sort of highly abbreviated shutdown, like killall5, umount -a, followed by a power off. I'm wondering if that umount command, or the trigger to run it, is still lurking somewhere in my system, and is discovered at boot causing the re-fsck problem. This is all speculation at the moment, but it's what I'll be investigating next. If anyone has any idea where NUT might have lodged a umount -a command on my system, please speak up. Thanks -- mountall runs fsck, all clean, mounts, twice... out of boredom? https://bugs.launchpad.net/bugs/605687 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
