After many trials and tribulations of trying to mount a remote Windows 10 Home file system on an Ubuntu 16.04 resulting in a "mount error(5), Input/output error" message, the problem has been resolved as follows:

Situation:
Linux system running Ubuntu 16.04, kernel 4.4.0.66-generic (call it System-Linux for reference), trying to mount four remote drives hosted on a Windows 10 Home system (call it System-W10 for reference). Three of the drives would mount OK, fourth drive gave error message.

All drives could be mounted from other Windows 10 systems and Windows 7 systems. New mount points could be created and mounted on System-W10 for other Windows-7/10 systems.

Removing all other remote drives and mount points from System-Linux did not solve problem.

Diagnosis:
Check the Windows system event log (Event Viewer--Windows Logs--System) for Event ID 2011, Source srv)

Resolution:
Increase registry entry, IrpStackSize, on the Windows 10 system (System-W10) by 5 (or as necessary if mounting multiple remote Linux drives).

regedit: HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/LanmanServer/Parameters

Note: IRPStackSize is case sensitive and may not exist on a Windows system, in which case, it will have to be created.

It appears that each remote Linux mount needs a Irp stack allocation whereas a remote Windows mount does not.

Hope this helps.

please mark your thread [SOLVED] in Thread Tools (menu at top of thread).
thanks.

Thank you again for this post.

I had this same problem and I have about 8 shares that when I reboot the PC, some would not be mounted and give this error.

After months of just dealing with similar problems including lazy unmounting the shares and rebooting at times, finally shares mount 1-2-3.

We ran into NFS err 5 from a Windows NFS server.

In our case, it turns out the application was trying to create a directory with colon : in the name, which Windows doesn't allow. Off error for Windows to throw for that problem.