[systemd-devel] /home Fails to Mount During Boot

[Garry T. Williams]

Recently, my /home file system fails to mount during boot.  The
relevant message is:

    systemd[1]: Job dev-sda4.device/start timed out.
    systemd[1]: Timed out waiting for device dev-sda4.device.

I'm dropped to a prompt for root's password and after receiving a
shell prompt, the command "mount /home" completes without error and
after exiting the shell the boot-up proceeds normally.

This is sort of new behavior.  I saw it once or twice during the last
few months, but now, after updating to kernel 3.10.3-300.fc19.x86_64,
it happens on each boot.

How can I debug this problem?

systemd-204-9.fc19.x86_64
kernel-3.10.3-300.fc19.x86_64

/etc/fstab:

    /dev/sda4 /home btrfs noatime 0 0

The /home file system is a raid1 btrfs across two identical drive
partitions, sda4 and sdb4.

Log:

Jul 27 17:33:42 vfr systemd[1]: Mounted /boot.
Jul 27 17:33:42 vfr kernel: EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Jul 27 17:33:42 vfr kernel: SELinux: initialized (dev md0, type ext4), uses xattr
Jul 27 17:35:08 vfr systemd[1]: Job dev-sda4.device/start timed out.
Jul 27 17:35:08 vfr systemd[1]: Timed out waiting for device dev-sda4.device.
Jul 27 17:35:08 vfr systemd[1]: Dependency failed for /home.
Jul 27 17:35:08 vfr systemd[1]: Dependency failed for Local File Systems.
Jul 27 17:35:08 vfr systemd[1]: Dependency failed for Mark the need to relabel after reboot.
Jul 27 17:35:08 vfr systemd[1]: Dependency failed for Relabel all filesystems, if necessary.
Jul 27 17:35:08 vfr systemd[1]: Triggering OnFailure= dependencies of local-fs.target.
Jul 27 17:35:08 vfr systemd[1]: Stopped Daily Cleanup of Temporary Directories.
Jul 27 17:35:08 vfr systemd[1]: Stopped IPv4 firewall with iptables.
Jul 27 17:35:08 vfr systemd[1]: Stopped ABRT Xorg log watcher.
Jul 27 17:35:08 vfr systemd[1]: Stopped CUPS Printer Service Spool.
Jul 27 17:35:08 vfr alsactl[427]: alsactl 1.0.27.2 daemon started
Jul 27 17:35:09 vfr systemd-journal[278]: Allowing system journal files to grow to 100.0M.
Jul 27 17:35:08 vfr systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
Jul 27 17:35:08 vfr systemd[1]: Started Tell Plymouth To Write Out Runtime Data.
Jul 27 17:35:08 vfr systemd[1]: Started Recreate Volatile Files and Directories.
Jul 27 17:35:08 vfr systemd[1]: Started Security Auditing Service.
Jul 27 17:35:08 vfr systemd[1]: Starting Update UTMP about System Runlevel Changes...
Jul 27 17:35:08 vfr systemd[1]: Started Update UTMP about System Runlevel Changes.
Jul 27 17:35:08 vfr systemd[1]: Startup finished in 1.311s (kernel) + 1.778s (initrd) + 1min 32.142s (userspace) = 1min 35.231s.
Jul 27 17:35:08 vfr auditd[428]: Started dispatcher: /sbin/audispd pid: 438
Jul 27 17:35:08 vfr audispd[438]: priority_boost_parser called with: 4
Jul 27 17:35:08 vfr audispd[438]: max_restarts_parser called with: 10
Jul 27 17:35:08 vfr audispd[438]: audispd initialized with q_depth=120 and 1 active plugins
Jul 27 17:35:08 vfr auditd[428]: Init complete, auditd 2.3.1 listening for events (startup state enable)
Jul 27 17:35:08 vfr sedispatch[443]: Connection Error (Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory): AVC Will be dropped
Jul 27 17:35:08 vfr sedispatch[443]: Connection Error (Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory): AVC Will be dropped
Jul 27 17:35:13 vfr auditctl[429]: No rules
Jul 27 17:35:13 vfr auditctl[429]: AUDIT_STATUS: enabled=0 flag=1 pid=0 rate_limit=0 backlog_limit=320 lost=0 backlog=0
Jul 27 17:35:13 vfr kernel: [127B blob data]
Jul 27 17:35:38 vfr systemd[1]: Starting Stop Read-Ahead Data Collection...
Jul 27 17:35:38 vfr systemd[1]: Started Stop Read-Ahead Data Collection.
Jul 27 17:40:15 vfr kernel: device fsid 6c3aeff6-9a50-4481-a175-7b98980eb638 devid 1 transid 674749 /dev/sda4
Jul 27 17:40:15 vfr kernel: btrfs: disk space caching is enabled
Jul 27 17:40:16 vfr kernel: SELinux: initialized (dev sdb4, type btrfs), uses xattr

-- 
Garry T. Williams