Unmounting Filesystem Failing

Question

After the recent initscripts upgrade, whenever I poweroff or reboot my EeePC 901, the root filesystem is not unmounted, and at reboot the disk is fscked.
Unmounting Filesystem [Fail]
Remounting Root Filesystem Read-only [Fail]
All of the daemons are successfully reported stopped (including Laptop-mode which I stop with a script in rc.local.shutdown when on battery: https://bbs.archlinux.org/viewtopic.php … 14#p930314).
The laptop is completely up-to-date. How would I go about diagnosing what is preventing the clean shutdown?

Answer 1

jasonwryan wrote:
Sure.
# <file system> <dir> <type> <options> <dump> <pass>
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs defaults 0 0
#/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
UUID=78b9738e-dd5b-4616-a6dc-1ca8c96e0209 / ext2 defaults,noatime 0 1
UUID=f1e7eedd-66e0-4e86-821d-f57b1fa2c0ca /home ext2 defaults,noatime 0 1
tmpfs /var/log tmpfs size=1M 0 0
Hmm, nothing at all stands out here, and we we explicitly don't unmount API filesystems or anything else mounted on a RAM based FS. I'd be curious what's running right before the call to umount. Just before line 55 of /etc/rc.shutdown where everything is unmounted, can you stick in a call to ps and lsof?
/bin/ps aux > /ps.out; /usr/sbin/lsof > /lsof.out
Unrelated -- you don't need those /dev/{pts,shm} entries anymore. They're mounted by /etc/rc.sysinit. Also, your home should have a passno of 2, not 1, meaning fsck it after root. (reference fstab(5)).