(Solved) irritated with your new RCs dealing with file permissions


Recommended Posts

Time to Vent  >:(

I have been going thru the threads here and Im quite dissapointed with the new versions of the 5.0 Rc doesnt support open file access like it has in the past.

 

 

I just recently got a new Main board from a friend and wanted to fire up the pro license I had when I was running 4.7 a year ago. I figured I would give the 5.0 RC a try Had a nice donation from a fellow IT manager of 16 750 Gb laptop drives guess they didnt need them for SSDs replacing them.

 

I figured lets go with the 5.0 Loaded it up everything seem to be all good  150MB speed on parity shares were ready and open . I started a 40GB copy before I went to bed. Woke up found it stopped at 40% telling me that it cant copy no more because I have no permissions!

 

Why would it allow files to be copied and then stop mid stream and say no permissions???? Again this is a Brand new load No upgrade

 

1)I read threads that say Open file permissions are not supported as you need to use credentials now. Why ? I dont want to use a L/P I have friends over who I want to share I really dont want to bother with L/Ps when they visit. IF I trust them to come into my house I Will trust them to fire up thier laptop and attached to my server.

 

2)I see another thread about if you have issues go to Rc4 .. posted by an admin problem is you cant find a valid link to allow yo to download RC4

 

3) another says add the smb-extra.conf file to your config with the acl set to no. Did that no change

 

 

I know have an open server with no L/P requirment is BAD ... a dozen of you unix gods out there are thinking "This guy is a windows looser!" Yea maybe I am, Maybe I just like stuff to work and not have to fuss with it when I come home and relax.

 

Anyhow this is mainly a vent I need to say. Looks like Im going back to classic 4.7 becuase this "New" 5.0 permissions should work out of the box. and yea I know its a Release candidate/beta. Still something simple as the file sharing concept should just work with no Fuss.

 

 

Anyhow I still love your product I bought two pro licenses . Just fix the File permissions thx. :'(

 

-Tek

 

 

 

 

 

Link to comment

Login & password is not required. Configure the share as public and anyone can connect and read/write to the share. I'm not sure what happened to your server and there's no way of telling without a syslog. The latest version, -rc9a, was released today and it includes a fixes to share access.

Link to comment

Time to Vent  >:(

I have been going thru the threads here and Im quite dissapointed with the new versions of the 5.0 Rc doesnt support open file access like it has in the past.

 

 

I just recently got a new Main board from a friend and wanted to fire up the pro license I had when I was running 4.7 a year ago. I figured I would give the 5.0 RC a try Had a nice donation from a fellow IT manager of 16 750 Gb laptop drives guess they didnt need them for SSDs replacing them.

 

I figured lets go with the 5.0 Loaded it up everything seem to be all good  150MB speed on parity shares were ready and open . I started a 40GB copy before I went to bed. Woke up found it stopped at 40% telling me that it cant copy no more because I have no permissions!

 

Why would it allow files to be copied and then stop mid stream and say no permissions???? Again this is a Brand new load No upgrade

Correct that shouldn't happen, and I've never seen that happen btw.

 

1)I read threads that say Open file permissions are not supported as you need to use credentials now. Why ? I dont want to use a L/P I have friends over who I want to share I really dont want to bother with L/Ps when they visit. IF I trust them to come into my house I Will trust them to fire up thier laptop and attached to my server.

Not true at all, use Public or Secure shares.  You don't need passwords.  There is a case that could come up though: if you do have users assigned and one of those names happens to match the login name of a friend logged into his windows PC, or happens to match the netbios name of his machine, then samba will want them to enter a password.  For example, suppose you have a legitimate user named "mary", and then your friend, happened to be named Mary logs into her laptop as "mary", or her machine netbios name happens to be "mary", then samba (linux component implementing windows networking) will think the "mary" user you defined is trying to access and will ask for a password.  But as you can see this should be a corner case.

 

2)I see another thread about if you have issues go to Rc4 .. posted by an admin problem is you cant find a valid link to allow yo to download RC4

Every new release of a -beta or -rc supersedes all previous versions, although most releases are accessible here:

http://download.lime-technology.com/download/

 

3) another says add the smb-extra.conf file to your config with the acl set to no. Did that no change

Not suprised.

 

I know have an open server with no L/P requirment is BAD ... a dozen of you unix gods out there are thinking "This guy is a windows looser!" Yea maybe I am, Maybe I just like stuff to work and not have to fuss with it when I come home and relax.

Not at all!  I'm with you, I just want it to work and it's a constant struggle to weight simplicity against flexibility.

 

Anyhow this is mainly a vent I need to say. Looks like Im going back to classic 4.7 becuase this "New" 5.0 permissions should work out of the box. and yea I know its a Release candidate/beta. Still something simple as the file sharing concept should just work with no Fuss.

 

 

Anyhow I still love your product I bought two pro licenses . Just fix the File permissions thx. :'(

Get it to fail again and then post or send me the system log.  Also be sure and use the latest release.

Link to comment

Why would it allow files to be copied and then stop mid stream and say no permissions????

Correct that shouldn't happen, and I've never seen that happen btw.

 

 

I've reported something similar in the past.

 

I run Jdownloader on my Ubuntu desktop with the downloaded files written to an unRAID user share.

 

Every so often, it will randomly decide that the permissions are not sufficient to allow the file to be written ... after it's already written several hundred megabytes of the file.  This must be a bug somewhere, but nothing is ever recorded in the syslog, so it's impossible to provide any evidence.

Link to comment

Thanks for the replies.

 

I already moved everything over to my other server before I left for work today.

 

Which this is what blows my mind.  I "MOVED" the files not copy which means I need write access to delete. But when I need to copy to the Unraid server I have no create access.

 

Seems like the access issue is with Create not working right. I can read,modify and delete.

 

Also if I go to the share \\server\Disk1 , Disk2, etc. I can read write modify and Create ! Seems the shares them self are having issues but using the disk# shares everything have preoper access.

 

So tonight  Im going to dismount every drive from the cage and run a quick partition wipe on all 16 drives using my portable sata drive slots.  Reinstall the drives with no partitions  Load the rc9 build with no upgrades again. Start the copy once more. If it errors again with permissions I will give you a syslog.

 

 

thanks for the help.

 

-Tek

 

Link to comment

You're creating your own issues. If you're running the RC's and have run the new permission script and have your shares set to public then any computer has full access them.

 

Are you running programs or doing work directly on the server? I haven't had one permission issue that wasn't self inflicted by doing file work directly on the server.

Link to comment

You're creating your own issues. If you're running the RC's and have run the new permission script and have your shares set to public then any computer has full access them.

 

Are you running programs or doing work directly on the server? I haven't had one permission issue that wasn't self inflicted by doing file work directly on the server.

 

Way I understood his description was that this was a "fresh" build, ie, no previously existing files.

Link to comment

You're creating your own issues. If you're running the RC's and have run the new permission script and have your shares set to public then any computer has full access them.

 

Are you running programs or doing work directly on the server? I haven't had one permission issue that wasn't self inflicted by doing file work directly on the server.

 

Way I understood his description was that this was a "fresh" build, ie, no previously existing files.

 

That is correct No mods no upgrade fresh off the USB key.

 

will have a report later on this issue when I go home will know if my 250 GB copy completed with no permission errors.

Link to comment

 

I know have an open server with no L/P requirment is BAD ... a dozen of you unix gods out there are thinking "This guy is a windows looser!" Yea maybe I am, Maybe I just like stuff to work and not have to fuss with it when I come home and relax.

 

 

A bit of a harsh statement. We all want things simply to work amd many of us are Windows users. I ran into several permissions issues, but often they were my only fault and solved by running the New Permissions script. And Windows has its issues too/

Link to comment

An Update I ran a fresh installs with 5RC8, RC9 and RC10:

 

Process was as follows:

 

1.Ran Diskpart / Clean  on 3 750 Gig hatachi 2.5 Sata's

2.Formatted USB key clean new load

3.Copied reg key

4.Added Disks and formatted them.

5.Created a Share with Cache

6.Created a Share without Cache.

7.No mods No extras no user accounts vanilla build

 

 

RC8 again failed with permissions mid copy this time at 25% of 100GB. I was able to resume copy if I went to the Disk1 on the UNC share and not the one the direct Share I created.  I could Also could not delete from cache drive and files refused to move when I executed the "Move Now" button These files were stuck. Ran change permission function did nothing.

 

 

RC9 Files failed again on a fresh copy this time at 40% of the same 100GB. However Cache drive flushed correcty. Same symptom  could fully access everything if I mapped thru the Disk# default shares.  Ran change permission No change.

 

RC10 100% successful everything copied over. Cache flushed.  I added the remaining disks to the Unraid management parity built. all is well.

 

I dont have Syslogs for the RC8 and 9 I was doing this while dealing with honeydo's 

 

However here is the link to the Main board that was given to me.

http://www.newegg.com/Product/Product.aspx?Item=N82E16813128358

 

Here is the drive types I have that were donated to me :

http://www.newegg.com/Product/Product.aspx?Item=N82E16822145449

 

Hope this helps looks like the RC10 build works.  ;D

 

 

 

Link to comment
  • 2 months later...

You're creating your own issues. If you're running the RC's and have run the new permission script and have your shares set to public then any computer has full access them.

 

Are you running programs or doing work directly on the server? I haven't had one permission issue that wasn't self inflicted by doing file work directly on the server.

 

My disks are set to public, ran the new permission script, when my Popbox V8 tried to access, I got the log on screen demanding user ID and password which I have never used. Tried to create a new user with password, Cannot sign with new user!!! 5RC11 did something bad since the 5Beta14 worked perfectly, no log on ever showed up. Please some body tell me how to get rid of this log on screen since I would want to build a newer server using the new 5 final and not my 5Beta.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.