Tuesday, November 27, 2018

A Device Attached to The System is Not Functioning .. windows sucks


This is the latest issue I had with windows 10. Everything started at the moment I started considering using NFS in my  Linux server setup in order to introduce some kind of shred files system between all boxes including my Windows 10 box. My Synology NAS supports NFS out of the box and all my Linux systems as well. It was rather simple to configure a shared space /pub on the Linux servers.
NFS was not working on my windows 10 box in the feature was "Services NFS" was not available for activation.

On the next morning, it turned out that I am not able to mount any of shares of my NAS box! Windows was asking all the time die the credentials of the share mount point of my NFS filesystem on the NAS., even though it was not existing anymore on the NAS. It seems as if windows has some internal variables which are not cleared. So every time I was trying to persuade windows
not to forget the connection to my NAS I ended in this message

"A Device Attached to The System is Not Functioning"

So I was pretty much blocked. Looking at the proposed solutions in the referenced article simply running the file system scan does not help but a more drastic way like reinstalling the drivers or resetting my windows might help.  I decided it might help to install some client I have been using previously to mount ssh file systems to my windows box. So I got my self the latest version of exandrive  and after installing expandrive the issue miraculously vanished. Actually, this kind of magic really sucks.


References


//1// A Device Attached to The System is Not Functioning [Fixed]