SMB is still broken on Mac OS Sonoma (14.3).
The issue is when looking at mounted shares via SMB, the files/folders have a red "slash" through them with access denied. They initially show fine but a few seconds later they change.
I have been having issues since updating TOS from 5.1.67 or so.
The only share that works correctly through SMB is "public".
I have contacted support and confirmed the sharing settings are the same for the other shares (full read/write) but the issue persists. I can't control my "home" directory, which also has issues. I can create a new folder via the Mac Finder and it immediately is marked with the red line through it and permission denied.
I use WebDAV for connections and the permissions are fine -- maybe even better/aster through the Finder.
I believe Time Machine backups go through SMB to the public share -- which is where I put my Time Machine backup -- finally backup better than when I had it in another share.
I want to be able to use SMB properly so I can decide whether to use SMB or WebDAV.
Have other Mac users seen this problem in more recent updates? I'm on an F4-220 with the latest 5.1.123 after recently wiping everything to do a clean install of 5.1.103 for the sizing issues from the TOS 4.x days.
TOS 5.1.123 (X86) is Released for Update
Re: TOS 5.1.123 (X86) is Released for Update
@bbezanson,
I was always having issues with SMB from day one using v4.2 (shipped with) and much of v5.1 until I did a NEW install (which you said you also did), and this fixed the Root partition size which I believe was the main issue I was facing with VERY slow SMB. I have not had any issues with access across home, public, or private sections of the device. Sorry to heat you are still experiencing problems. I have multiple Mac devices with both older and current MacOS version, using SMB, and things have been solid. Prior to doing a new install, Timemachine on the device would take days or weeks to finish. Afterwards, all appears to be normal both with speeds and permissions. I know this does not fix your issue, but I can say for me, I have not been seeing this using Mac devices via SMB. Best of luck on the troubleshooting and or working with Support.
I was always having issues with SMB from day one using v4.2 (shipped with) and much of v5.1 until I did a NEW install (which you said you also did), and this fixed the Root partition size which I believe was the main issue I was facing with VERY slow SMB. I have not had any issues with access across home, public, or private sections of the device. Sorry to heat you are still experiencing problems. I have multiple Mac devices with both older and current MacOS version, using SMB, and things have been solid. Prior to doing a new install, Timemachine on the device would take days or weeks to finish. Afterwards, all appears to be normal both with speeds and permissions. I know this does not fix your issue, but I can say for me, I have not been seeing this using Mac devices via SMB. Best of luck on the troubleshooting and or working with Support.
Re: TOS 5.1.123 (X86) is Released for Update
trying straight to a higher OS number caused issues for me. what helped was to first install the file that is on the Webpage, this will get you to 5.0.176 but will make the system partition 8GB (check though), then manually update to 5.1.24 and only after that go to a higher version.bbezanson wrote: ↑26 Jan 2024, 06:01 SMB is still broken on Mac OS Sonoma (14.3).
The issue is when looking at mounted shares via SMB, the files/folders have a red "slash" through them with access denied. They initially show fine but a few seconds later they change.
I have been having issues since updating TOS from 5.1.67 or so.
The only share that works correctly through SMB is "public".
I have contacted support and confirmed the sharing settings are the same for the other shares (full read/write) but the issue persists. I can't control my "home" directory, which also has issues. I can create a new folder via the Mac Finder and it immediately is marked with the red line through it and permission denied.
I use WebDAV for connections and the permissions are fine -- maybe even better/aster through the Finder.
I believe Time Machine backups go through SMB to the public share -- which is where I put my Time Machine backup -- finally backup better than when I had it in another share.
I want to be able to use SMB properly so I can decide whether to use SMB or WebDAV.
Have other Mac users seen this problem in more recent updates? I'm on an F4-220 with the latest 5.1.123 after recently wiping everything to do a clean install of 5.1.103 for the sizing issues from the TOS 4.x days.
Re: TOS 5.1.123 (X86) is Released for Update
{L_BUTTON_AT}quella
Just curious (I don't use MAC) but have you checked SMB Advance settings for anything MAC/IOS related?
F5-221 5.1.123, 8GB System Partition on 3 x 4TB Traid; 3TB EXT4
F2-221 TOS6 (Beta), 8GB System Partition on 2 x 6TB in Traid. (Latest Update 11/04/24)
F2-221 TOS6 (Beta), 8GB System Partition on 2 x 6TB in Traid. (Latest Update 11/04/24)
Re: TOS 5.1.123 (X86) is Released for Update
Updated to 5.1.123. No obvious problems except first attempt "Failed to Update"!
F5-221 5.1.123, 8GB System Partition on 3 x 4TB Traid; 3TB EXT4
F2-221 TOS6 (Beta), 8GB System Partition on 2 x 6TB in Traid. (Latest Update 11/04/24)
F2-221 TOS6 (Beta), 8GB System Partition on 2 x 6TB in Traid. (Latest Update 11/04/24)
Re: TOS 5.1.123 (X86) is Released for Update
Updated to 5.1.123 from .103. Fine. Thank you
- Gandalf1369
- Posts: 82
- Joined: 26 Feb 2020, 01:34
Re: TOS 5.1.123 (X86) is Released for Update
Also updated from .103 to .123 without any issues. So far so good . . .
F5-221 with 4x5TB drives in Raid 5 (Plex Media Server, TOS 4.2.44)
F4-220 with 2x8TB, 1x6TB in JBOD (Docker, PiHole, Uptime-Kuma, tnfsd-x64, TOS 5.1.131)
F4-220 with 2x8TB, 1x6TB in JBOD (Docker, PiHole, Uptime-Kuma, tnfsd-x64, TOS 5.1.131)
Re: TOS 5.1.123 (X86) is Released for Update
Thanks for your feedback, we'll verify it in the lab.
Re: TOS 5.1.123 (X86) is Released for Update
When updating to version 5.1.123 I have noticed that the USB drives have been listed as mnt/@usb/usbshareN/xxxxxx
instead of the previous name volumeX/@usb/usbshareN/xxxxxx.
Terrible consequences: Applications that referenced files located on USB devices can no longer access them. It is necessary to rename the libraries that contain them in those applications. For example Plex.
We hope that this change is definitive and does not return to the previous nomenclature.
(translated with google)
instead of the previous name volumeX/@usb/usbshareN/xxxxxx.
Terrible consequences: Applications that referenced files located on USB devices can no longer access them. It is necessary to rename the libraries that contain them in those applications. For example Plex.
We hope that this change is definitive and does not return to the previous nomenclature.
(translated with google)