I upgraded from rc3 to rc5 and lost access to files. I followed the directions from another post and ran the New Permissions, but still cannot access. I cannot access the shares or the disks, but can access new shares I create and the flash drive of course. This is my first post, so please let me know if I missed anything you need to help.

 

 

 

 

syslog.zip

Are you using a user other than ROOT?

I was using another user name in addition to root before I tried to fix it. However after checking, it appears that I was using root to access the shares from at least 2 Win7 computers.

 

I would like to use it with anonymous access on my network.

 

When I run the new permissions utility, it only seems to access the parity disk and disk1.

Is that normal?

Shouldn't it access all the disks to reset the permissions?

I was using another user name in addition to root before I tried to fix it. However after checking, it appears that I was using root to access the shares from at least 2 Win7 computers.

 

I would like to use it with anonymous access on my network.

 

When I run the new permissions utility, it only seems to access the parity disk and disk1.

Is that normal?

Shouldn't it access all the disks to reset the permissions?

 

Check Control Panels->Credentials Manager on the Windows machines to see how they are logging in.

I was forcing new credentials every time I tried to access the share folders from windows.

 

After beating my head on the desk and doing everything I could think of, I finally rolled back to 5.0rc3 and my shares are accessible again.

 

Although I can access the shares again, it is only with root. Still cannot access anything with new user accounts. 

 

I

Delete the following files in the config directory and then reboot:

passwd

shadow

smbpasswd

 

You will have to re-add the users.

Also don't export "Files and Documents" via NFS until next -rc.  There is a bug in handling NFS export names with spaces in them.*

 

* For the curious: documentation for 'exports' file says you can enclose the export path in quotes and it should work.  But when I added this fix, there is still an error message generated in the system log which says that the path can't be exported, for example:

 

exportfs: Warning: /mnt/user/Files and Documents does not support NFS export.

 

However, it actually works!  That is, despite the warning you are able to mount the export just fine from an nfs client (though I only tested using linux nfs client via mount command).  I looked at the source code for 'nfs-utils' package, and indeed the warning message is bogus.

 

The command used on the client side was:

 

mount "tower:/mnt/user/Files and Documents" /mnt/nfstest