Home NAS Solution

also, I’m testing it now, but some people thing that creating a file: /etc/nsmb.conf

with the following contents:

[default]
signing_required=yes
protocol_vers_map=6

solves it.

I am trying that now with my mac that does disconnect. Will see what happens.
 
Here you are...

Greenshot 2026-01-19 13.33.22.png



Greenshot 2026-01-19 13.34.05.png
 
1.5 hours in, MBP lid is closed, and I VNC’d in. Still connected to the shares. Doesn’t mean much - it could disconnect 3 minutes from now. But at least it didn’t disconnect right away! :-)
 
1.5 hours in, MBP lid is closed, and I VNC’d in. Still connected to the shares. Doesn’t mean much - it could disconnect 3 minutes from now. But at least it didn’t disconnect right away! :-)
Watching with interest. My Plex also always works without issue, it's just my Mac Studio that has the issue.
 
Well, after several attempts with different configs it's just not going to work for my video editing, it will need to be more of a storage solution instead of dealing with workflow which is okay because it'll allow me to archive off older work and keep my SSD drives freed up.
 
I am again experiencing just how crappy Synology is. For several days now I am unable to login to the administrative interface. The NAS works and I can connect to the file shares — but access via web or SSH times out. It's like the services are stuck. I will need to do a soft reset this weekend and pray that the data is safe. This is the third major incident with Synology across two different NAS models in six years of ownership, which I deem completely unacceptable. Not to mention that Time Machine regularly breaks down. I'll be moving to a .S. Ubiquity NAS at the next possible opportunity.

P.S. Just as I wrote I tI managed to login. I guess this piece of *** got scared :D. It's still rather unresponsive. Appears that a data scrubbing task is running, but that should not render the admin console inaccessible.

P.P.S. Canceling the data scrubbing fixed the responsiveness issue. I also found out that the data scrub has not been completed in over two years, although it's set up to automatically run every week.
 
Last edited:
I am again experiencing just how crappy Synology is. For several days now I am unable to login to the administrative interface. The NAS works and I can connect to the file shares — but access via web or SSH times out. It's like the services are stuck. I will need to do a soft reset this weekend and pray that the data is safe. This is the third major incident with Synology across two different NAS models in six years of ownership, which I deem completely unacceptable. Not to mention that Time Machine regularly breaks down. I'll be moving to a .S. Ubiquity NAS at the next possible opportunity.

P.S. Just as I wrote I tI managed to login. I guess this piece of *** got scared :D. It's still rather unresponsive. Appears that a data scrubbing task is running, but that should not render the admin console inaccessible.

P.P.S. Canceling the data scrubbing fixed the responsiveness issue. I also found out that the data scrub has not been completed in over two years, although it's set up to automatically run every week.
I'm going to try to get a UNAS Pro 4. Do you happen to have other UI equipment?
 
I'm going to try to get a UNAS Pro 4. Do you happen to have other UI equipment?

I have a Dream Machine Pro, a Unifi Access Point, and a Unifi Switch. Never had any issues running 10GB fiber internet. It's a massive overkill for a single home, but I like shiny stuff, and the ability to quickly configure guest networks and VPN is very helpful.
 
Well, after several attempts with different configs it's just not going to work for my video editing, it will need to be more of a storage solution instead of dealing with workflow which is okay because it'll allow me to archive off older work and keep my SSD drives freed up.

This is how I approach astrophotography work. NAS holds projects, local SSD holds my working copy. Putting aside any issues macOS might have keeping shares mounted consistently that you are hitting, it's also just much slower for stuff where latency/throughput matters. But it's perfect for offloading a project that's done, and then getting it backed up offsite to someplace like B2.

I'll be moving to a .S. Ubiquity NAS at the next possible opportunity.

I'd be curious to know if the NFS features are robust these days. My home server cluster at the moment relies on NFS between VMs and a TrueNAS server for shared storage. One reason I don't use something like the UNAS is because it's not clear if I can replicate my setup, as their documentation seems thin on the ground, and quick to get stale as they do work.
 
This is how I approach astrophotography work. NAS holds projects, local SSD holds my working copy. Putting aside any issues macOS might have keeping shares mounted consistently that you are hitting, it's also just much slower for stuff where latency/throughput matters. But it's perfect for offloading a project that's done, and then getting it backed up offsite to someplace like B2.
Now comes the pain of transferring files, 4TB is taking 3 days. Ugh.
 
I have a Dream Machine Pro, a Unifi Access Point, and a Unifi Switch. Never had any issues running 10GB fiber internet. It's a massive overkill for a single home, but I like shiny stuff, and the ability to quickly configure guest networks and VPN is very helpful.
1769643905433.png

I don’t have a problem….
 
Finally figured out the problem with my Synology. It turns out one of the HDDs failed. However, instead of warning or informing me about the issue, the system decided "this is fine" and continued to use the disk like nothing happened. I had timeouts of 11ms for RAID access according to the kernel logs. No wonder the system was unresponsive.

Needless to say, this is terrible user experience. The only reason I was able to identify the issue is because I spent more than two hours trying various diagnostic tools and studying logs via an SSH connection on an extremely sluggish system. A non-terminal savvy user has no chance. Not cool, Synology.

I won't be repairing the RAID. I will back up the more important stuff elsewhere and try my luck with a new system.
 
Finally figured out the problem with my Synology. It turns out one of the HDDs failed. However, instead of warning or informing me about the issue, the system decided "this is fine" and continued to use the disk like nothing happened. I had timeouts of 11ms for RAID access according to the kernel logs. No wonder the system was unresponsive.

Needless to say, this is terrible user experience. The only reason I was able to identify the issue is because I spent more than two hours trying various diagnostic tools and studying logs via an SSH connection on an extremely sluggish system. A non-terminal savvy user has no chance. Not cool, Synology.

I won't be repairing the RAID. I will back up the more important stuff elsewhere and try my luck with a new system.
JFC this is scary, you would think it would alert you to the failed drive, I mean it does about everything else so it seems like a pretty huge oversight.
 
JFC this is scary, you would think it would alert you to the failed drive, I mean it does about everything else so it seems like a pretty huge oversight.

Yep. I mean, I’m fine with the logic of drives failing, that’s why RAID exists. It’s much harder to justify the logic of the system repeatedly insisting to read the drive that’s continuously throwing errors. It is possible that I ran into an odd corner case where the drive is failing but health thresholds are still formally met - but the logs were literally filled with entries like “error reading sdb”. One would think that heuristics like “more that 10 read errors per minute indicate drive failure” would be part of the basic RAID system. What an odd experience…
 
Yep. I mean, I’m fine with the logic of drives failing, that’s why RAID exists. It’s much harder to justify the logic of the system repeatedly insisting to read the drive that’s continuously throwing errors. It is possible that I ran into an odd corner case where the drive is failing but health thresholds are still formally met - but the logs were literally filled with entries like “error reading sdb”. One would think that heuristics like “more that 10 read errors per minute indicate drive failure” would be part of the basic RAID system. What an odd experience…
Is it one of those dynamic RAID systems (where the drive space can be larger than your actual drive size)?
 
Even though no matter what I try the NAS still routinely disconnects from the Mac Studio I've decided to just accept it as mentioned before and only use it as a backup solution.

I've returned my Mac Studio Display, because paying $1700 without HDR is ludicrous, but I did like the fact that I could use all those extra thunderbolt ports. So upon returning it at the Apple Store I picked up a CalDigit TS5 so I can continue to plug in a ridiculously excessive amount of SSD drives. :mrgreen:
 
Even though no matter what I try the NAS still routinely disconnects from the Mac Studio I've decided to just accept it as mentioned before and only use it as a backup solution.

I've returned my Mac Studio Display, because paying $1700 without HDR is ludicrous, but I did like the fact that I could use all those extra thunderbolt ports. So upon returning it at the Apple Store I picked up a CalDigit TS5 so I can continue to plug in a ridiculously excessive amount of SSD drives. :mrgreen:

With last years news that Apple developed (or at least patented) an image sensor with 20 stops of dynamic range, I wonder if the rumored Studio Display update will have HDR capability. Supposedly it will soon be announced.
 
With last years news that Apple developed (or at least patented) an image sensor with 20 stops of dynamic range, I wonder if the rumored Studio Display update will have HDR capability. Supposedly it will soon be announced.
I really should have read up on the current model before buying it but never in a million years would've guessed something that expensive wouldn't have the basic HDR functionality that most monitors at less than half that price do. It's like they figure the name "Apple" will be good enough for some reason, really disappointed in this one.
 
Back
Top