I now have this working.
There were two things which I changed:
A typo in the /etc/fstab file .. the line in the question above is correct. however ...
More importantly after some testing I created a new directory /wdmirror changed its ownership to the user I log in with pi. Changed permissions to read and write as well. Using the /wdmirror directory ...
as noted in a comment- @guiverc, white-space is also a delimiter, and so is a comma...
so the right answer ( or- my mistake ) is
UUID=3edefcc8-04fb-449b-9e72-9bda7e443f65 /home/guy/newHD ext4 defaults,x-gvfs-show 0 0
so - use comma, without white-space
Check your file systems for both / and /home...
boot to a Ubuntu Live DVD/USB in “Try Ubuntu” mode
open a terminal window by pressing Ctrl+Alt+T
type sudo fdisk -l
identify the /dev/sdXX device name for your "Linux Filesystem(s)"
type sudo fsck -f /dev/sdXX, replacing sdXX with the number(s) you found earlier
fsck both / and /home partitions
repeat the ...
A sudden power interruption can eventually cause big damage. Indeed, the failure to startup in your case may be due to problems with the partition containing your /home folders.
First, you may attempt if checking and repairing the file system solves the issue. For this, work from a live session started from a live DVD or live USB.
If problems persist after ...
I tried ntfs-3g but had no luck. In the end, I plugged the drive into a Windows 10 PC and ran chkdsk. It fixed the problem and the drive works in Ubuntu machines now.
In windows, click the start button and type cmd
Open the cmd app (like a terminal in Linux)
chkdsk E: /f
Remember to replace the E with the letter that your drive mapped to when you plugged ...
In this example I implied that we work as root. If you don't, apply sudo su or sudo when needed.
Your system may use different init system than Systemd, but Cron is pretty universal.
You can simply use /etc/fstab to pre-define your mount options and whatnot.
USERNAME@HOSTNAME_OR_IP:/REMOTE/DIRECTORY /LOCAL/MOUNTPOINT fuse.sshfs defaults,...