Background: I recently attempted a CPU upgrade and it appeared that everything was ok. After a few hours, however, the system began freezing, crashing, and rebooting erratically. Eventually Unraid wouldn't load because the system would crash before unraid had fully booted. So I swapped back in the old CPU, and the system boots as expected. When I got the system back up, I ran memtest for a while (no errors) and checked filesystems on the array drives (no errors), and pulled the unraid USB drive and ran chkdsk on it (no errors). Edit: And parity check finished today with 0 errors.

 

Problem: I can't access any of my shares from Windows Explorer. I can still access the server through SSH and the GUI in a browser. I still see TOWER in my network, but trying to open it in explorer (or accessing directly with \\TOWER) gives the error: "0x80070035 The network path was not found." I haven't changed any settings for the user shares in Unraid, but I double-checked anyway and confirmed that my user account has full read/write access to the shares I'm trying to access. Needless to say, I have lost all access to my network drives that were mapped to the various unraid shares.

 

Any ideas for how to track this down?

Edited December 2, 20178 yr by scud133b

Do you happen to have Windows 10 and having received a recent update? Because M$ have played around with the networking functionality in Win10 and turned off support for SMB version 1, which breaks the ability to locate other devices on the network.

Tried it on my Win 10 test machine with the latest fall creators update - all is working fine...

Install "every" new update and test it again.

Edited December 1, 20178 yr by Zonediver

8 minutes ago, Zonediver said:

Tried it on my Win 10 test machine with the latest fall creators update - all is working fine...

Install "every" new update and test it again.

Note that the creators update doesn't block Windows from using shares - but introduces problems with browsing for other non-windows hosts. If you map network drives etc, Windows will still support the shares.

I did just do the Fall Creator's update earlier this week. I figured it must be related to Samba because everything else still works (Plex server, SSH, web GUI, etc). Are you familiar with any workarounds or checks to see if the latest windows update is the culprit?

 

Edit: My mapped networked drives have broken. For example, had a "games" share (\\tower\games) that was mapped to G: and it won't connect anymore, so that seems to conflict with what @pwm just said.

Edited December 1, 20178 yr by scud133b

You can map the drives using IP instead. It's the name discovery of hosts that breaks, when M$ turned off use of SMBv1.

 

Fall Creator's expects to be able to do name resolution using DNS, so another workaround is that you edit the hosts file in Windows and adds name/IP of the missing equipment.

Updating HOST file with unraid address fixed all my issues, which occured regardless if I connected by server name or IP.

 

This fix worked before and after fall update 

Host file was it! Seems to have nothing to do with the hardware failure, just a Windows issue. I had to add the IP Address and name of the server to the HOST file like this:

 

x.x.x.x     tower

Tutorial if anyone else needs it: https://www.howtogeek.com/howto/27350/beginner-geek-how-to-edit-your-hosts-file/

Edited December 2, 20178 yr by scud133b