Removing nfs-common did not change anything. Everything was fine first thing this morning I did an apt-get update and du - there were no new packages, no changes. (Eastern Time, US), it is now almost 8PM.
My data folders live on sdc3 (a conventional drive), they are linked to /home on sda2 (a SSD). Everything works, other than my desktop background and dropbox, those files are on the unmounted sdc3.
I did a du by going to tty1, becoming root and issuing systemctl isolate multi-user.target. Following the du which finished uneventfully I rebooted
Start-Date: 2015-10-08 12:42:19
Commandline: apt-get dist-upgrade
Upgrade: man-db:amd64 (2.7.3-1, 2.7.4-1), librsvg2-2:amd64 (2.40.10-1, 2.40.11-1), os-prober:amd64 (1.67, 1.68), libexiv2-14:amd64 (0.25-2, 0.25-2.1), xserver-xorg-input-all:amd64 (7.7+9, 7.7+12), libpam-systemd:amd64 (226-4, 227-1), xserver-xorg-core:amd64 (1.17.2-1.1, 1.17.2-3), udev:amd64 (226-4, 227-1), xserver-common:amd64 (1.17.2-1.1, 1.17.2-3), libspice-server1:amd64 (0.12.5-1.2, 0.12.5-1.3), libudev1:amd64 (226-4, 227-1), libmm-glib0:amd64 (1.4.10-1, 1.4.12-1), python-six:amd64 (1.9.0-5, 1.10.0-1), librsvg2-common:amd64 (2.40.10-1, 2.40.11-1), systemd-sysv:amd64 (226-4, 227-1), libcairomm-1.0-1v5:amd64 (1.10.0-1.2, 1.12.0-1), modemmanager:amd64 (1.4.10-1, 1.4.12-1), systemd:amd64 (226-4, 227-1), libsigc++-2.0-0v5:amd64 (2.6.1-1, 2.6.1-2), xserver-xorg:amd64 (7.7+9, 7.7+12), libnss-myhostname:amd64 (226-4, 227-1), libsystemd0:amd64 (226-4, 227-1), x11-common:amd64 (7.7+9, 7.7+12), python3-six:amd64 (1.9.0-5, 1.10.0-1), libpq5:amd64 (9.4.4-2, 9.4.5-1), exfat-utils:amd64 (1.2.1-1, 1.2.1-2)
End-Date: 2015-10-08 12:42:49
Upon reboot, the screen stayed black for an unusual amount of time before the sddm screen appeared. It still seems to be taking a long time, but I have never timed it. I get an error from Dropbox, since it can't find it's data.
cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
#Entry for /dev/sda1 :
UUID=f5236926-cfcd-4df4-9439-f26a29f1d6c9 / ext4 noatime,commit=120,errors=remount-ro 0 1
#Entry for /dev/sda2 :
UUID=c84955dd-4a65-4bbf-aabb-0166f8af7b26 /home ext4 defaults,relatime,errors=remount-ro 0 2
#Entry for /dev/sda3 :
UUID=4dabe4a5-4b70-4d93-a4ca-97ae840b1204 none swap sw 0 0
#Entry for /dev/sdb1 :
UUID=44228B67228B5D34 /disks/disk2part1 ntfs-3g defaults,auto,users,locale=en_US.utf8 0 0
#Entry for /dev/sdb2 :
UUID=EE96907496903ED1 /disks/disk2part2 ntfs-3g defaults,auto,users,locale=en_US.utf8 0 0
#Entry for /dev/sdc2 :
UUID=030cf640-699f-423f-98ea-f89e06ad9278 /disks/disk3part2 ext4 auto,users,rw,exec,relatime 0 0
#Entry for /dev/sdc3 :
UUID=0b8ed16b-f34f-4e98-aebd-5912ed524de4 /disks/disk3part3 ext4 auto,users,rw,exec,relatime 0 0
The UUID's have not changed.
# blkid /dev/sdc3
/dev/sdc3: LABEL="data" UUID="0b8ed16b-f34f-4e98-aebd-5912ed524de4" TYPE="ext4" PARTUUID="f5fda669-03"
# ls -l /dev/disk/by-uuid
total 0
lrwxrwxrwx 1 root root 10 Oct 8 19:41 0b8ed16b-f34f-4e98-aebd-5912ed524de4 -> ../../sdc3
As I stated earlier, I can open Dolphin, click the Data(sdc3) folder and it will mount after I provide the root password.
If I issue mount /dev/sdc3 it will mount, and if I issue mount -a all the sdc partitions mount.
At that point I can open Dropbox, change the background, etc. Everything seems to work fine unless I reboot.