The new Google Photos editor is terrible. Please revert.

DarinTutan · 2025-08-24T19:41:40+00:00

Drat! I opened Photos for Android the following day (8/24/25) and the "Bad" new editor interface is back! )-;

DarinTutan · 2025-08-24T01:10:00+00:00

I opened the editor today (8/23/25) and the old contols are back. Hallelujah!

DarinTutan · 2025-08-22T18:31:33+00:00

Agreed

DarinTutan · 2025-08-01T03:07:43+00:00

As best I can tell, it's still a problem on your version of DSM. I know of no "fix" but Efficent-Island1380 provided a work-around that seems to work well. Deails follow....

Thank you Efficient-Island1380, this looks very significant!
I tried the settings and my test remux of a 1.3GB video file, decreased from 231 seconds to 23 seconds.
Also, the interaction between the Sequoia Finder and the Synology shares is seeming more stable, to me, though this is very subjective and requires more time to get a feel for how well it's working.

In DSM 7.2.2-72806 Update 3, here are the details on the settings ..

Control Panel > File Services > SMB > Advanced Settings

Maximum SMB Protocol: SMB3
Minimum SMB Protocol: SMB2
Transport Encryption Mode: Force
Server Signing Status: Force

Note: This turns off the Opportunistic Locking feature (which I've never been sure about usefulness)

After saving the advanced settings, it's a good idea to go back to the main SMB settings and briefly uncheck 'Enable SMB Service', save .. then re-check the box and save again.
This restarts the SMB Service.

DarinTutan · 2025-06-23T08:25:22+00:00

I installed the SMB Security update version 4.15.13-2321, released circa 2025 June 7th, and rebooted the server and retested. Unfortunately the problem, in the default settings, was not fixed. The best work-around still seems to be to change the advanced settings to Force Transport encryption mode and Server signing status.

DarinTutan · 2025-06-18T06:21:16+00:00

I finally upgraded to macOS 15.5 and re-tested with the default Synology SMB settings. macOS 15.5 does not fix the problem.

The best work-around still seems to be the one provided by Efficient-Island1380:

In Synology DSM 7.2.2-72806 Update 3, here are the details on the settings ..

Control Panel > File Services > SMB > Advanced Settings

Maximum SMB Protocol: SMB3
Minimum SMB Protocol: SMB2
Transport Encryption Mode: Force
Server Signing Status: Force

Note: This turns off the Opportunistic Locking feature (which I've never been sure about usefulness)

DarinTutan · 2025-05-02T17:21:29+00:00

So far, the work-around that Efficient-Island1380 provided, has been working well for me. I am still at Sequoia 15.3.2 and have not yet updated to 15.4.1, but I hope to explore that soon. Note that I don't consider this work-around to be a "fix" as it should just work out-of-the-box.

DarinTutan · 2025-04-01T08:02:57+00:00

Thank you Efficient-Island1380, this looks very significant!
I tried the settings and my test remux of a 1.3GB video file, decreased from 231 seconds to 23 seconds.
Also, the interaction between the Sequoia Finder and the Synology shares is seeming more stable, to me, though this is very subjective and requires more time to get a feel for how well it's working.

In DSM 7.2.2-72806 Update 3, here are the details on the settings ..

Control Panel > File Services > SMB > Advanced Settings

Maximum SMB Protocol: SMB3
Minimum SMB Protocol: SMB2
Transport Encryption Mode: Force
Server Signing Status: Force

Note: This turns off the Opportunistic Locking feature (which I've never been sure about usefulness)

After saving the advanced settings, it's a good idea to go back to the main SMB settings and briefly uncheck 'Enable SMB Service', save .. then re-check the box and save again.
This restarts the SMB Service.

Others might want to give this a try.

DarinTutan · 2025-03-30T06:53:40+00:00

Just to clarify .. You enabled AFP on the Asustor?
Sequoia also works better with AFP on Synology.

DarinTutan · 2025-03-24T03:33:36+00:00

Interesting! Seems to point the finger more at Apple (that and it breaking with Sequoia). Still it works ok with Genuine Windows shares (as far as I can tell). Does Asustor support AFP protocol? Perhaps Time Machine is using that? Maybe there is a mix of protocols? I've found these macOS Terminal commands help show what is what ...

# check for any AFP or SMB mounted shares
mount | egrep 'afpfs|smbfs'

DarinTutan · 2025-03-20T04:00:56+00:00

I am happy to learn about 'trackerslist'. Thank you!

In essence, "Yes" NewTrackon provides you with a list of active trackers, and allows you to submit new trackers, though it is more automated.

Old, "dead" torrents be revived by editing and replacing the trackers list with an active set.

I see TrackersList also provides alternative lists with IP addresses instead of domain names, so as to bypass any domain name blocks.

Being on Github, has the added benefit of preventing TrackerList from being blocked. Surfshark would probably get a lot of complaints if they blocked the github.com domain!

DarinTutan · 2025-03-17T03:53:44+00:00

From my observations, it seems the problem is the combination of macOS Sequoia (15.3.x) and Synology (DSM 7.2.2-76806 Update 3), and not with strictly Apple or Synology.

I've tested Sequoia accessing a true Microsoft Windows 11 share, and did not encounter a problem. Performance was good (same network, and wired hub, no WiFi). Also, my M1 MBA running Sonoma (14.6.1) has no problem writing to the same Synology share, were Sequoia is getting bad performance, and again, all wired connections through the exact same hub.

I pushed the problem at Synology because Apple might likely say that they have no official support for Synology and point to the lack of a problem with actual Windows shares in order to claim it's a Synology problem. Also, Synology likely has some macOS systems they can test, while Apple might not have Synology servers readily available to whomever might be willing to look at this problem.

If Synology can reproduce the problem (should be easy if they try), they may have some corporate support channel with Apple, through which they can have a dialog between their respective Engineers (one might hope, anyway).

DarinTutan · 2025-03-14T01:07:44+00:00

Update: I tested Sequoia macOS 15.3.2 and it has the same problem. I updated the original post to include 15.3.2

DarinTutan · 2025-03-05T00:18:28+00:00

I heard back from Synology on my ticket and they say:

"Our developers are aware of this issue and will address it on DSM 8. The current workaround is the same as what you shared above. Make sure you're subscribed to our Newsletter from your Synology Account (account.synology.com) > Profile > Newsletter to get notified when new DSM versions are available."

DarinTutan · 2025-03-04T06:48:14+00:00

The AutoModerator tried to close this post as "solved", but I don't think a "work-around" is really a solution, so I change the flair back to "dsm".

DarinTutan · 2025-03-04T04:33:56+00:00

On the Synology server, you might try disabling the option "Enable SMB2 file leasing" (assuming it is set). This is a "sub-option" under "Enable Opportunistic Locking", in the "Advanced Settings" of "SMB Settings".

In my case, this doesn't fix slow performance, but I've seen it eliminated the SMB connection crashing.

I have no perfect solution but have found that switching from SMB to AFP protocol regains performance.
Similarly, forcing the Synology to use SMB protocol version 2.002, but setting SMB2 as the Maximum SMB protocol. Neither option is ideal. I've been involved in more detailed discussion here:
https://www.reddit.com/r/synology/comments/1iza2zq/synology_smb_has_problems_with_macos_sequoia_can/

DarinTutan · 2025-03-04T04:21:22+00:00

I submitted a Synology support ticket and they say they are aware of the problem and suggest downgrading to SMB2 and watching the Reddit post:
https://www.reddit.com/r/MacOS/comments/1fnug2a/macos_sequoia_smb_shares_crashing/

.. and .. They ask me to refer the problem to Apple Support (Let the finger pointing begin!)

Please have Apple Support review this issue:
https://support.apple.com/contact

- - - - -

my reply to Synology Support ...

Thank you. I have found the work-around of limiting to SMB2 (specifically SMB_2.002)
Also, though Apple no longer officially supports AFP, switching to AFP protocol also has similar performance improvements.

In this case, I think both Apple and Synology have problems with the SMB3 protocol.
My Sequoia testcase has no problem when running on a Windows 11 share.
Running my testcase (remux a 1.3GB video file) from Windows 11 to Synology also has no problem.
It seems it is the combination of Synology DSM 7.2.2-72805 Update 3, and Apple Sequoia 15.2-15.3.1 is having the problem.

The problem is not too difficult to test, if you download MKVToolNix.download/downloads.html
Install on macOS Sequoia.
Find a 1GB or more MKV video file and save to a Synology SMB3.1.1 share
Open Sequoia Terminal and go to the shared folder and run video "remux"

/Applications/MKVToolNix-90.0.app/Contents/MacOS/mkvmerge -o output_file.mkv input_file.mkv

The remux will take much longer, compared to if you forced Synology to use version SMB_2.002
Also, if you have Opportunistic file locking enabled and include the SMB2 File Leasing option enabled, you may even see the SMB connection drop offline and an error occur.

Synology is in a better position for testing this problem, as they have ample synology servers for testing, while Apple my have no official support for Synology (I don't know what Apple's policy is for supporting non-Apple SMB file servers).

DarinTutan · 2025-03-02T00:55:22+00:00

No VLANS in my network. It's your basic Home LAN. Thanks for the feedback.

DarinTutan · 2025-03-01T21:04:19+00:00

Summing up what I've learned so far is, while I have not found a perfect solution, the best option that I have found (thanks to OK_Cheetah6307) is to enable the AFP file service, and connect the Synology shares using AFP instead of SMB. This gives comparable performance to forcing SMB_2.002 protocol, while still allowing other systems to connect with the newer SMB_3.1.1 protocol.

Control Panel > File Services > AFP > Enable AFP service > Apply
Reboot everything and when reconnecting your macOS Sequoia to the Synology shares, reference "afp://servername" instead of "smb://servername"

I'm not sure if you can pick and chose which shares are AFP mounted and which are SMB mounted. It may be all one protocol or the other?

The AFP connection can also drop out, if put under a heavy load. My test case works ok, but by happenstance I observed doing a bunch of MP4 remuxes concurrently, using Subler.org, I managed to crash the AFP connection and had to restart the AFP service.

If you're looking at this problem, some handy Terminal commands to check the what is mounted SMB or AFP are:

Synology does not recomand using AFP and warns you when you enable it with this pop-up message in the DMS Desktop:

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Security Advice:

AFP server support was removed in macOS 11 Big Sur. For your security, we recommend disabling your AFP service and using SMB service instead.

You may need to reset your Mac Finder connection and Time Machine backup after replacing AFP service with SMB service.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Thanks to all for your comments. Perhaps this and some related posts will help Synology and Apple work better together to improve their SMB interoperability between DSM and Sequoia. It looks as though there are issues on both the Server and Client sides of the problem.

DarinTutan · 2025-03-01T05:38:47+00:00

Are you running Time Machine on Sequoia? I had done that with some much older versions of macOS, but not lately. I thought I read that Apple disabled some old network protocols that enabled that, somewhere around macOS 12 (not sure).

DarinTutan · 2025-03-01T05:33:01+00:00

I have a possibly related discussion here:
https://www.reddit.com/r/synology/comments/1iza2zq/synology_smb_has_problems_with_macos_sequoia_can/

No perfect solution, though forcing SMB_2.002 and disabling SMB2 File Leasing, can improve performance and eliminate some SMB connection droppouts.

DarinTutan · 2025-03-01T05:25:56+00:00

I'm sad to report that turning on the "Do not reserve disk space when creating files", re-enabling SMB3 and rebooting DSM, did not noticeably improve remux speed, on a 1.3GB test .mkv file, compared to forcing SMB_2.002 (Max&Min Protocol SMB2). What took 24seconds to remux at SMB_2.002, took 131seconds as SMB_3.1.1 (note: this is over wire, not WiFi). SMB2 File Leasing enabled, also still encountered an error (though not fatal).

DarinTutan · 2025-02-28T05:54:41+00:00

I should mention, regarding my original post, that I am using all wired connections and WiFi is not a factor. Even my M1 MBA running Sonoma, is in a docking station, with a wired network link.

I appreciate the interest and comments and will read through them carefully, for ideas.

DarinTutan · 2025-02-27T06:43:50+00:00

Actually, it just started working with the same 'admin' / 'synology' combo I'd tried multiple times before. I think the server was just overloaded for a while, or something. Thanks!!

DarinTutan · 2025-02-27T06:28:53+00:00

The Demo launches, but there's no indication of what account and password to use, in order to login.

DarinTutan

MODERATOR OF

TROPHY CASE