I am about at wits end. After upgrading about a week ago I can no longer see the shares on my unraid box. I have tried about everything mentioned in the static thread relating to this type of problem with no success. The web interface works to the unraid server. I can ping the server by name or ip address. I cannot access any shares through either windows file explorer or using the net use command. Net use gets a system error 64, the specified name is longer available. File explorer gets an error 84, unspecified. I verified that the unraid server is the master browser, i have put in registry entries to make sure windows machines don't try to become the master. I'm not sure what else to try. Has any one run into this situation?

How did you confirm that your server is in fact the master browser? There is a small plugin (called Local Master) that can help. Are you using it? If you post your diagnostics zip someone will be able to see if you have any underlying issues.

Go to Tools - Diagnostics and post your complete diagnostics zip. Sounds like you have established that all the networking side of things should be working, but you haven't said anything at all about whether you actually have any files to share. Possibly filesystem corruption on cache or another drive is crippling the user shares.

I did install the Local Master plugin, that was how I verified that it was set correctly. This system has been up and running for about two years and there are certainly files to share. I also verified that my imac cannot see the shares either. I am attaching the diagnostics.zip file and I appreciate any help you guys can provide!

leslietower-diagnostics-20170128-1147.zip

Most of your shares have both include and exclude set. It is recommended that you only use include or only use exclude. There is never any reason to use both, since if you include specific disks, then all other disks are excluded, and if you exclude certain disks, then all other disks are included.

 

It looks like you also have disk shares enabled. It is a good idea to not share disks and just use user shares. If you mix disk shares and user shares when copying or moving files you can lose data. This is why disk shares are disabled by default. Search for User Share Copy Bug.

 

None of this is likely to be the cause of your problem though.

 

Are you sure your server is on the same workgroup?

 

Can you use console/telnet/ssh?

 

You mentioned trying things from some thread. Which thread exactly?

The thread I was referring to was the Windows Issues with UnRaid thread. The server is on the same workgroup. This is really frustrating as everything worked great for over a year. I ran the upgrade and things still worked for about a day and then it all dropped. Just not sure what would have changed.

 

I was able to connect via telnet.

You should get rid of unmenu from the "go" file on the flash drive (config folder) and then reboot

 

Not necessarily the cause, but you are running an unpatched unmenu.

 

Your go file should only be this:

#!/bin/bash
# Start the Management Utility
/usr/local/sbin/emhttp &

Additionally, looks like you've got your onboard sata ports set to be IDE mode.  You'll get far far better performance out of the drives by setting them to be AHCI in the BIOS

 

This keeps popping up in the syslog too:  TCP: request_sock_TCP: Possible SYN flooding on port 8080. Sending cookies. Check SNMP counters.

 

I was able to connect via telnet.

From the command line, what do you get with these?

ls -la /mnt

ls -la /mnt/user

 

This keeps popping up in the syslog too:  TCP: request_sock_TCP: Possible SYN flooding on port 8080. Sending cookies. Check SNMP counters.

That's the unMenu port. Probably best to get rid of it like Squid said. And since you have that still hanging around I have to wonder what else you still have on your flash from before v6.

Couldn't insert a screen cap, here goes.

ls -la /mnt

 

drwxr-xr-x    8  root      root    160 Jan 27 20:35  ./

drwxr-xr-x  18 root      root    400 Jan 28 11:48  ../

drwxrwxrwx  1 nobody  users    0  Jan 17 03:42  cache/

drwxrwxrwx  3 nobody  users  19  Jan 17 03:41  disk1/

drwxrwxrwx  4 nobody  users  27  May 15 20:15  disk2/

drwxrwxrwx  7 nobody  users 107  Jan 23 19:06  disk3/

drwxrwxrwx  1 nobody  users    0  Jan 23 19:06  user/

drwxrwxrwx  1 nobody  users  19  Jan 23 19:06  user0/

 

The output from ls -la /mnt/user is very similar but lists all of the user shares that I have set up. If you need me to, I can list those also.

 

One thing that I did notice; in the network.cfg file in the diagnostics list there were no entries any of the settings. Could that be causing the problem?

 

Also, I cleaned up go to remove the unmenu load. Should I also remove the unmenu directory from the usb?

 

This keeps popping up in the syslog too:  TCP: request_sock_TCP: Possible SYN flooding on port 8080. Sending cookies. Check SNMP counters.

That's the unMenu port. Probably best to get rid of it like Squid said. And since you have that still hanging around I have to wonder what else you still have on your flash from before v6.

Looking at your go file, it looks like you have somehow concatenated 2 lines, the one that starts unMenu, and the one that loads the autoinstall packages from unMenu PKG Manager. But the concatenation stuck together the uu command at the end of one and the cd command at the beginning of the other so I don't think those commands can actually be executing, but maybe the find command after the && does run. But if so, where does it think . is?

 

I think you should copy your config folder, do a clean install, and copy your config folder back, but don't copy the go file.

Okay, I'm going to give the clean install a try. It has been since 2015 so I'm going to have to look up how to do it. One more thing that shouldn't have anything to do with the problem. I added a UPS to the system right after the upgrade. I would be surprised if that had anything to do with a networking issue but I just wanted to give you the whole picture.

Thank you!!! The clean install worked and everything is back up and running. I'm going to get some of the cleanup done that you suggested. Thank you again for all the help getting this working.