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.

macOS Big Sur Beta 6 - unRAID 6.8.3 SMB Shares Potentially Broken

Featured Replies

I've been using unRAID 6.8.3 flawlessly for several months now and just a heads up with macOS Big Sur Beta 6, I cannot connect to my unRAID box via SMB.

I do not have AFP enabled, SMB has been tested with and without "Enhanced macOS interoperability" and no luck.

I wouldn't deem this to be an unRAID bug because it works with all other Operating Systems and it worked with Big Sur Beta 5 no problems.

 

If anyone wants to test anything, I'm pretty open to it

  • Replies 63
  • Views 15.4k
  • Created
  • Last Reply

FYI - I have the same problem connecting to Netgear SMB shares with multiple NAS units running 6.10.3

 

Everything worked prior to this version of Big Sur.

 

I can't connect using the IP address and I can't connect using DEVICENAME.local either.

 

I have confirmed that other machines on my network can connect to these machines using SMB. I also turned on Mac OS Optimized mode on and off on the Netgear units to no avail.

 

Hope this corroborates a problem with SMB in Big Sur latest 11.0 Beta (20A5364e)

 

I registered here to reply to this post.

Edited by xjrguy

  • Author

Thank you @xjrguy - I did file a bug report with Apple. Bug number is FB8622248.

 

I am able to connect to my Drobo 5N, just not my unRAID.

Edited by xaositek

Hi! I have the same issue, starting with Big Sur Beta 6, I can't connect thru SMB to my Unraid !  Very annoying.   Is anyone was able to configure NFS in the meantime?

  • Author
9 minutes ago, Pducharme said:

Is anyone was able to configure NFS in the meantime?

I haven't attempted it, not sure if Fuse is Big Sur compatible either.

 

I'm doing what I need to over SSH, my Drobo is still my primary NAS at the moment, unRAID is running Docker images and VMs for me.

Edited by xaositek

I wonder if there isn't an updated Samba package available that can fix this.  Are we running latest Samba on 6.9 Beta 25 ?

  • Author
6 minutes ago, Pducharme said:

I wonder if there isn't an updated Samba package available that can fix this. 

I started doing some digging to file a proper bug report (side note Apple updated my ticket and there are more than 10 reports on this issue) and it appears to be a permissions or kernel problem based upon the attached screenshot.

 

Screen Shot on 9-3-20 at 10.42.50 PM.png

Mmm ok.  Is there a command that we could run on our Apple Big Sur that will fix the Permission ?? would be an easyfix! Probably not, but who knows! :)

 

If not, I suppose we can wait for Apple Big Sur Beta 7... 

 

  • Author

I didn't stop to think why the Drobo still worked but unRAID didn't until you poked the "huh" trigger in my head.

 

I checked and the Drobo is still mounting over AFP FS - since I'm on unRAID 6.8.3, I can test this in a bit later as a temporary work around.

14 hours ago, Pducharme said:

I wonder if there isn't an updated Samba package available that can fix this

Just to reply, nope, I'm running a big sur vm also in a manjaro linux machine with smb enabled, updated as of today with the stable channel.

 

13 hours ago, Pducharme said:

If not, I suppose we can wait for Apple Big Sur Beta 7...

Better to wait for the 11.0.2 :D

 

Edited by ghost82

On 9/3/2020 at 9:56 PM, xaositek said:

I cannot connect to my unRAID box via SMB

As a workaround manually load the kext:

sudo kextload /System/Library/Extensions/smbfs.kext

Note that you need to load it at each boot.

  • Author
1 hour ago, ghost82 said:

As a workaround manually load the kext:


sudo kextload /System/Library/Extensions/smbfs.kext

Note that you need to load it at each boot.

Confirmed this does fix it! Great job @ghost82!

@ghost82 thanks for the workaround :) hopefully they will fix it in the imminent new Beta release.

No problem, glad it helped in some way.

 

OT: this is the first time I'm following the beta development of a macOS system and the feeling is not so good..I mean..SMB (as an example) is quite a basic functionality, we are not talking about a bug manifesting in very particular situations..as many other bugs..

There should be also some issue with macOS big sur development, it seems they are a bit in delay with the beta releases compared to ios, tvos, etc...not sure we will see the release by the beginning of october..If I have to bet I would say the release would come out the last week of October.

Edited by ghost82

  • Author

Fixed in Beta 7. We can close this thread.

This SMB issue is not yet fixed as of Sep 21, 2020! macOS Big Sur Version 11 Beta (20A5364e) still needs the above work around on a MacBook Retina , 12-inch, Early 2016.

4 hours ago, Anandesh said:

This SMB issue is not yet fixed as of Sep 21, 2020! macOS Big Sur Version 11 Beta (20A5364e) still needs the above work around on a MacBook Retina , 12-inch, Early 2016.

Right, because you are running beta 6, update to beta 7 and the issue is solved as reported.

  • 3 weeks later...

Solved....it seemed solved...until you try to move something (big? such as a 700 mb file, for me it seems it's anything bigger than 67,1 mb) from the shared drives and find that it fails and big kernel panic...ahhhh (beta 9)

Edited by ghost82

  • 2 weeks later...

Do you still have issue with smb and big sur (beta 10)?

I'm trying to move a 700 mb file from my share to my big sur desktop and all I get is a -8084 error.

I have enough space (80+ gb) and the file is not corrupt.

I also tried to force smb protocol to 3.

Smaller files are transferred.

The same 700 mb file under Catalina transfers without issues.

  • Author
3 hours ago, ghost82 said:

Do you still have issue with smb and big sur (beta 10)?

I'm trying to move a 700 mb file from my share to my big sur desktop and all I get is a -8084 error.

I have enough space (80+ gb) and the file is not corrupt.

I also tried to force smb protocol to 3.

Smaller files are transferred.

The same 700 mb file under Catalina transfers without issues.

I’ve used Beta 10 to transfer multiple 1gb (and larger) files to and from my array without issues. I’ve tested this pulling from the cache or from the array, neither has presented issues.

40 minutes ago, xaositek said:

I’ve used Beta 10 to transfer multiple 1gb (and larger) files to and from my array without issues. I’ve tested this pulling from the cache or from the array, neither has presented issues.

mmm this is weird...for me ahah :D

Can you post your smb config please?Which unraid version?

  • Author
10 minutes ago, ghost82 said:

mmm this is weird...for me ahah :D

Can you post your smb config please?Which unraid version?

6.9 beta 30, settings are attached as a screenshot. AFP is beta 30 is no longer a thing, so it's SMB only.

Screen Shot 2020-10-19 at 8.07.13 AM.png

Nothing, for me it's partially broken...but on unraid 6.8.3, and not for all files (I was able to transfer some 1gb files, but failed to transfer others).

On Catalina all is ok.

In my opinion there's still some bug in big sur.

  • 4 weeks later...

RC2 20B28: smb broken again?Can't see my server from mac os :(

If smb is broken again, I have really no words.......

  • Author
5 minutes ago, ghost82 said:

RC2 20B28: smb broken again?Can't see my server from mac os :(

If smb is broken again, I have really no words.......

I haven't been able to replicate your concern. I am on RC2 and have successfully connected and moved/copied files from my 6.9B30 unRAID system without problems.

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.