The subject says it all.  I had XP and map to my unraid shares with a valid unraid login, and had no issues at all.  I did a fresh install of Windows 7 and I can map and read the data on my unraid, but I get an error message when trying to write.  The weird part is the error will pop up, but after several files have copied just fine.  For example, I go to copy a dir with lots of subs and files to the unraid share.  It might get 60% complete, then the following error will show up,

ERROR: Cannot write x:\apps\blabla\aerith2.mid!

Please remove the write protection!

 

I can only hit OK, and it terminates the copy job.  I've tried skipping that one file, and it just happens later on another file.  I figured if I had a permission issue, I wouldn't even get past the first file or sub, so I don't get it.  I have full Ownership and Full Access on the Windows side and I can copy the files from and to any of the 3 internal windows drives.  This error only happens when I try to copy to unraid.  Furthermore, I tried taking ownership via Windows permissions, and now if I'm connected as root, I can't delete or create sub dir.  I have another account that is setup on my unraid, that one still works, except I get the above error.

 

I think this must have something to do with windows, but even that troublies me because I thought the files on the unraid are controled by unix permissions and root always has full control.  If I'm connected to the unraid share with root, why does my copy fail?

I've tried searching for this, but as you can see, its not a case of Access or No Access, it's part Access and that is killing me.

Just did another test, which doesn't give me any answers, but might help somebody help me. 

 

I got the error on a specific file, which was about 5 dir down, copy failed.  I went to that sub dir and started a new copy job from there, and it worked just fine.  It seems to be related to permissions on subs, but only some.  This is dam weird.

 

What should the permissions look like from a Windows pc?  I looked it shows Tower/steve with Special access....this directory only...when I try to change it to This Folder, sub, and files, it acts like it works, but really don't change anything, meaning when I go back to check, it's back to Specal...

crap, forgot one more thing. Tower\root doesn't show up in the permission list now, which might explain how come I can't do crap while mapped as Root.  How do I add root back?  I tried the ADD and when I try to Check Name for root, it fails.

if you are indeed still running version 4.2 and not 4.4.2 or higher then I suggest you upgrade.  There have been a lot of fixes since 4.2 and some nice speed improvements using the 4.5beta11 version.

sorry, I'm running 4.4.2.  Crap, I guess I posted in the wrong place.  Do I need to repost, or is there a easy way to move it to the right forum section?

sorry, I'm running 4.4.2.  Crap, I guess I posted in the wrong place.  Do I need to repost, or is there a easy way to move it to the right forum section?

 

This will work fine.  I remember reading that SMB has been upgraded in the 4.5beta's to work better with Windows 7 so you might consider upgrading to the newest beta.

ok, good idea.  I will try that.  But first, I want to be sure the permissions on the unraid side are correct.  Is there a way to fix this from the server side, so that root has full control again?  I obviously can't fix this from the windows side.

 

Thanks!

I'm in no way a Linux guru, so hopefully others will correct me, but I do have a couple of comments.

 

Root is always recreated on each boot, so you don't have to do anything to it but reboot.

 

Your file copy failures don't sound at all like permission issues to me, because if they can work once, they always work.  In other words, they either work or they don't work, they can't work some of the time but not the rest of the time.  My feeling is that this may be a timeout problem.  A series of copies starts, and buffers and caches are filled, so then the transfer is paused, but this particular machine may have too small a timeout for these transfer pauses.  unRAID quite commonly pauses transfers to parity protected drives, and it does appear that copies succeed for a little while before failing.  It is not uncommon for write errors to be wrongly worded, and not clearly indicate the true issue.

 

How much memory do you have installed on your unRAID server?

 

I apologize, I try hard to make my thoughts understandable, but the above does not seem very well worded at all.  I hope you will find a helpful clue anyway.

Hi,

 

did upgrading unRAID resolve your issues ? I'm running 4.4.2 and also get

random "remove write protection" errors when copying files to unRAID samba

shares from my Windows 7 machine.

 

 

Regards,

 

Matthias.