I powered on my Sheevaplug, after being unplugged for several days vacation.
It didn't become available on the network after waiting over 60s, which is the length of time I remember it taking before. The disk was whirring and it turns out it took several extra minutes running fsck.
Why the fsck? Were my filesystems not cleanly unmounted for some reason?
It runs Debian Jessie.
$ systemd-analyze blame 2min 26.613s systemd-fsck@dev-mapper-vg_brick\x2dlv_backup.service 2min 13.294s systemd-fsck@dev-mapper-vg_brick\x2dlv_attic.service 1min 55.661s systemd-fsck@dev-mapper-vg_brick\x2dlv_home.service 35.407s systemd-fsck@dev-mapper-vg_brick\x2dlv_aptcache.service $ journalctl -b Jan 01 02:17:57 brick systemd: Found device /dev/mapper/vg_brick-lv_aptcache. Jan 01 02:17:57 brick systemd: Starting File System Check on /dev/mapper/vg_brick-lv_aptcache... Jan 01 02:17:57 brick systemd-fsck: aptcache: Superblock last write time (Sun Apr 2 20:58:31 2017, Jan 01 02:17:57 brick systemd-fsck: now = Tue Jan 1 02:17:57 2013) is in the future. Jan 01 02:17:57 brick systemd-fsck: FIXED.