Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

4.7 to 5.0rc8 - unable to write to shares

Featured Replies

Did the upgrade. Checked all the disks. Did the permission fix. Recreated the users.

 

Am able to read from shares; but mostly cannot write to them.

 

Restarted the array. Stop/started the array. Restarted the PCs (XP, Win7, and Win8).

 

Did the smb-extra.conf fix found here.

 

Sometimes, it will allow me to copy a file, but ridiculously slow and/or errors. But I can read fast.

 

I've been searching off and on all day... can't find a fix.

Well.... its not consistent with that you state that is sometimes works, but try this out anyhow if you want: Make sure you are mounting your shares from windows with an appropriate user, if you still mount with "root" then that will cause issues.. You need to remove the previous mount / browse permissions forcefully, windows remembers them and that causes issues..

  • Author

Thanks, Helmonder. The client machines are using various user names. I've tried with "public" shares (presumably don't need login authorization?) and with users that authenticate on other shares.

 

I say that is's "mostly" because it seems like sometimes I can drop / write a file, but in the rare case that it succeeds it takes a LONG time to get around to doing so.

 

I do not have my cache drive enabled right now. Not sure if that'd have THIS kind of effect.

have you tried without this smb-conf extra fix ?  I am not using it and everything works.. Might be for an older release ?

  • Author

I grabbed this from the "system log" button in the menu. If there's a better / more thorough way, let me know.

 

After reboot (and wandering off with some honey-dos), I started the array and tried unsuccessfully to copy a file from two different PCs using a "public" share called temp. They both failed to write. The XP error is "Cannot copy filename.ext: The specified network name is no longer available.

 

Reading from both clients works great. Quite fast, in fact.

syslog_unraid.txt

Did the upgrade. Checked all the disks. Did the permission fix. Recreated the users.

 

Am able to read from shares; but mostly cannot write to them.

 

Restarted the array. Stop/started the array. Restarted the PCs (XP, Win7, and Win8).

 

Did the smb-extra.conf fix found here.

 

Sometimes, it will allow me to copy a file, but ridiculously slow and/or errors. But I can read fast.

 

I've been searching off and on all day... can't find a fix.

 

Show the output of the following commands:

 

ls -lR /mnt/user/guest-share  (fill in the correct share name)

ethtool eth0

ifconfig

  • Author

The output from that first one was... uh... crazy long.

 

Every FILE shows: -rw-rw---- 1 nobody users

Every FOLDER shows: drwxrwx 1 nobody users

 

 

 

Settings for eth0:

        Supported ports: [ TP ]

        Supported link modes:  10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Supports auto-negotiation: Yes

        Advertised link modes:  10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Advertised pause frame use: Symmetric Receive-only

        Advertised auto-negotiation: Yes

        Speed: 1000Mb/s

        Duplex: Full

        Port: Twisted Pair

        PHYAD: 0

        Transceiver: internal

        Auto-negotiation: on

        MDI-X: Unknown

        Supports Wake-on: pumbg

        Wake-on: g

        Current message level: 0x00000033 (51)

        Link detected: yes

 

root@UNRAID1:~# ifconfig

eth0      Link encap:Ethernet  HWaddr 6c:f0:49:e7:58:c8

          inet addr:192.168.253.5  Bcast:192.168.253.255  Mask:255.255.255.0

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:111614 errors:0 dropped:6 overruns:0 frame:0

          TX packets:234748 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:17223863 (16.4 MiB)  TX bytes:215225435 (205.2 MiB)

          Interrupt:48 Base address:0x6000

 

lo        Link encap:Local Loopback

          inet addr:127.0.0.1  Mask:255.0.0.0

          UP LOOPBACK RUNNING  MTU:16436  Metric:1

          RX packets:9 errors:0 dropped:0 overruns:0 frame:0

          TX packets:9 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:646 (646.0 B)  TX bytes:646 (646.0 B)

 

 

Samba version?

Post the parity drive SMART report. Post all SMART repots.

I have exactly the same problem. Upgraded from 4.7 to 5.0rc8a today. Can't write to anything even with public shares. no syslog events triggered when writing failed. I'm using teracopy in windows 7 and I get "Target: access denied".

 

With no errors or indication of anything being wrong I'm not sure what to try next.

Some additional info: after removing all windows credentials, then rebooting PC, when I browse to the smb share of the unraid server I am not prompted for user/pass even though all shares are set to "secure". no write permissions at all.

  • Author

dgaschk, I ran the short smart tests the other day and some had stuff reporting, but nothing fatal. the parity is clean.

 

running the long test on the parity drive now.

 

you thinking I should run the short or long? and is there a way to run them on all drives - similar to the way the bubba interface did in 4.7? I assume loading bubba is not the way to go with 5.0...

Sorry for partially hijacking this thread but I think we actually have the same problem.

 

I resolved it on my end by doing the following:

 

- deleted all of my windows credentials for the unraid server (type "credentials" in the windows 7 start menu to find the control panel for this)

- changed all of my SMB shares to "private" (they were "secure" before).

- stopped and started the array.

- browsed the unraid server from windows. Windows finally prompted me for user/pass. I entered my read/write user pass and now have full r/w access to my shares.

 

It appears as though I was browsing the "secure" shares as some kind of guest before. Switching to "private" disabled browsing unless authenticated.

 

Hope this helps,

Ben

Sorry for partially hijacking this thread but I think we actually have the same problem.

 

I resolved it on my end by doing the following:

 

- deleted all of my windows credentials for the unraid server (type "credentials" in the windows 7 start menu to find the control panel for this)

- changed all of my SMB shares to "private" (they were "secure" before).

- stopped and started the array.

- browsed the unraid server from windows. Windows finally prompted me for user/pass. I entered my read/write user pass and now have full r/w access to my shares.

 

It appears as though I was browsing the "secure" shares as some kind of guest before. Switching to "private" disabled browsing unless authenticated.

 

Hope this helps,

Ben

 

That is consistent with my first thoughts:

 

http://lime-technology.com/forum/index.php?topic=24271.msg210908#msg210908

 

Looks like you have written down a better procedure to change this.. Wonder if the OP's issue is also fixed now..

  • Author

Thanks for all the help, guys. I'm still having the same issues.

 

I've wiped the users and rebuilt them. I've changed settings in the shares many times.

 

If I set shares so that I should /not/ be able to access them, then reboot the PCs, it acts accordingly. At least in the Win8 system, I don't have to reboot, just kill the connections with net use /delete.

 

What I'm experiencing is very... odd. When attached as a user who /should/ have rights, I can delete or rename any file. I cannot copy a file to the share from a PC. In Win8 and Win7, it does it's "calculating" thing, maybe says "20% progress", then kicks an error about the server not being available ("There is a problem accessing \\unraid1\temp" in Win7). Of course, it is.

 

Occasionally (haven't found a pattern yet), the file then shows as being present in the share and I can see it from another  system at that point and it appears to be full size. It is, of course, corrupt / not valid.

 

I can copy a very small file (< 100KB) and it will work. But anything over those small sizes, it does the "calculating" thing, then fails - either with a small "percent complete" on the indicator or not.

  • Author

Bump.

 

I've re-run the permissions script. I have the same results.

 

On three different machines (one each of XP, Win7, Win8), if I attempt to attach to a share that the user does NOT have rights to, I am unable to attach (as expected). If the user /should/ have rights, I'm able to see the files.

 

If I attempt to WRITE a file, small files succeed (~100K or so) and everything larger fails.

 

I'm not sure where I should be looking or what I should be trying to change at this point.

There are problems in the Samba version (3.6.7)  in V5rc8.  See here for some information:

 

        http://lime-technology.com/forum/index.php?topic=22647.0

 

The cure was to replace version 3.6.7 with version 3.6.8  The fix is provided here:

 

        http://lime-technology.com/forum/index.php?topic=22604.msg206583#msg206583

 

And more explanation about it here:

 

        http://lime-technology.com/forum/index.php?topic=22604.msg208948#msg208948

 

Hope this helps you with your problem!

 

 

  • Author

Well, I'll be... that seems to have worked!

 

Thank you,  thank you, thank you!  ;D ;D ;D

 

It doesn't seem to be ripping fast or anything... but it seems to be working.

I'll test sync'ing up my backups... that's always a good read/write test.

 

Fingers crossed!  ::)

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.