“sudo ecryptfs-recover-private” gives “find: ‘/run/user/1000/gvfs’: Permission denied” after botched (?) upgrade

EDIT 1: I reinstalled 16.04 having booted through the CD but with the HDD installed, now I can read the "readme.txt" and I can click on the "access-your-private-data.desktop" and it seems to run for a few minutes without a window opening and then it stops. When I try running sudo ecryptfs-recover-private I get

INFO: Searching for encrypted private directories (this might take a while)...
find: ‘/run/user/1000/gvfs’: Permission denied

I have a Lenovo E540 (i7) with a 16GB SSD and 1TB HDD. I had the system and swap on the SSD and my data (/home) on the HDD. I tried updating from 14.04 to 16.04. I got asked to confirm the driver EULA but I couldn't select the "OK". I quit the installation. After trying to boot up all I got was an empty screen. I created a 16.04 live cd on a different machine and booted up with that. I removed my hdd prior to this because I didn't want to risk loosing any data. After the installation I shut the notebook down and installed the HDD. I booted up and my HDD appears as a volume and when opened there's two files "access-your-private-data.desktop" "readme.txt" neither of which I can open. I had all my files on the HDD, please help me.

ecryptfs-recover-private doesn't have to search through every file, if you add where your old encrypted home at the end then it will only look there. For example ecryptfs-recover-private /location/to/search.

You can search yourself, looking for any encrypted files, for example with a GUI search utility, or
find [mountpoint] -type f -iname "*ecryptfs*"

To see exactly what ecryptfs-recover-private does, just look at it, it's a bash script. Running this would display it with less:
less $( which ecryptfs-recover-private )

And it's search is this:
find / -type d -name ".Private"

You're probably just seeing regular "permission denied" errors if you tried searching everything everywhere, some folders don't want to be searched. Your home's not supposed to be in /run/user/1000/gvfs anyway so don't worry about it.