why don't you guys just relax, this happened before and guess what, a few months later released a new update.  Things just don't happen over night.  I know it doesn't take long to post a quick update but stop all the whining, you sound like a bunch of 12 year olds.  Sorry had to vent

I am running out of room so I decided it was time to upgrade from 4.7 to rc6-r8168-test.

 

Ran a parity check (passed) and commented out the unmenu entry in my go file.  Did the upgrade per the instructions in the wiki.  Re enabled the cache and ran the permissions utility.  Nfs was disabled so I re-enabled it (I use it for one share).  Unmemu remains commented out.

 

I cannot access 3 of my shares.  I cannot see any common setup problem.  I picked one and changed its settings to match a share I can access, then rebooted.  Problem persists.  Here are the config files:

 

DVDA.cfg (This share works)

# Generated settings:

shareComment="DVDA Rips"

shareInclude=" disk4"

shareExclude=""

shareUseCache="no"

shareAllocator="fillup"

shareSplitLevel=""

shareFloor="0"

shareExport="e"

shareSecurity="public"

shareReadList=""

shareWriteList=""

shareExportNFS="-"

shareExportNFSFsid="0"

shareSecurityNFS="public"

shareHostListNFS=""

shareExportAFP="-"

shareSecurityAFP="public"

shareReadListAFP=""

shareWriteListAFP=""

shareVolsizelimitAFP=""

Movies.cfg (This share doesn't work)

# Generated settings:

shareComment="SD Movies"

shareInclude="disk5"

shareExclude=""

shareUseCache="no"

shareAllocator="fillup"

shareSplitLevel=""

shareFloor="0"

shareExport="e"

shareSecurity="public"

shareReadList=""

shareWriteList=""

shareExportNFS="-"

shareExportNFSFsid="0"

shareSecurityNFS="public"

shareHostListNFS=""

shareExportAFP="-"

shareSecurityAFP="public"

shareReadListAFP=""

shareWriteListAFP=""

shareVolsizelimitAFP=""

 

What I mean by doesn't work is that from Win 7 I can see the share but if I try to open it I get a "refers to a location that is unavailable" error.  Note that I can access the data if I go through the disk# share.  The other 2 shares I cannot access are more complicated as they have multiple drives involved.

 

Any help would be greatly appreciated.  Log is attached.

 

Edit:  WTF?  Just tried it from a 2008 R2 server and I can access.  Go back to my win7 box and get the same error.  Windows sucks!

unraidlog.txt

why don't you guys just relax, this happened before and guess what, a few months later released a new update.  Things just don't happen over night.  I know it doesn't take long to post a quick update but stop all the whining, you sound like a bunch of 12 year olds.  Sorry had to vent

 

Don't beat up Tom's groupies.  It takes a company a long time to build up a loyal customer base like Tom has.  I just wish he would take advantage of his groupies more, and make the most active ones members of his inner circle, to accelerate the program.  I'm sure Tom disagrees with me so we'll just let it be.

why don't you guys just relax, this happened before and guess what, a few months later released a new update.  Things just don't happen over night.  I know it doesn't take long to post a quick update but stop all the whining, you sound like a bunch of 12 year olds.  Sorry had to vent

 

Don't beat up Tom's groupies.  It takes a company a long time to build up a loyal customer base like Tom has.  I just wish he would take advantage of his groupies more, and make the most active ones members of his inner circle, to accelerate the program.  I'm sure Tom disagrees with me so we'll just let it be.

 

There's another thread for this in the Lounge.  PLEASE post there instead of mucking up this thread.

Rebooted my PC and can now access all the shares.  Thank you Microsoft for wasting part of my Saturday. 

Rebooted my PC and can now access all the shares.  Thank you Microsoft for wasting part of my Saturday.

Enabling the Local Master setting in the SMB settings in the UI could help to prevent this.  If another machine on the network is Browse Master and is not always present then share discovery can become frustrating at best.  (It's not entirely Microsoft's fault, but the timings that they use for their Browse Master discovery process don't make it any better.)

Rebooted my PC and can now access all the shares.  Thank you Microsoft for wasting part of my Saturday.

 

Hah!  Isn't that par for the course for a PC running Windows though?

Rebooted my PC and can now access all the shares.  Thank you Microsoft for wasting part of my Saturday.

 

Hah!  Isn't that par for the course for a PC running Windows though?

 

Yes - because the Windows PC will try to be browse master.  Setting the server to take on that role should help.