Take the bottom off and there it is.
1 Like
I really thought this thread could be closed. My apologies:
this morning, on booting my iMac, I see this - apparently two (versions of) my Nucleus:
Any ideas, please?
Had something similar on my Mac once, run a chkdsk, should solve it.
1 Like
Helpful and re-assuring, Michel; thanks!
Anyone know what it happens?
Looks like the same folder mounted twice on the Mac. Shouldn’t really be a problem
1 Like
Hi Mark
I follow you 100%
And with HI-FI, design is a really important factor as well (for me as well).
And I think Nucleus nailed the design 
1 Like
Thanks, Mario! Hasn’t done it again. But I do like everything to be perfect 
I continue to fail to understand this impulse to close threads… Are we running out of virtuality?
1 Like
Are you’re referring to this Bill?
…This topic will close 2 days after the last reply…
Hi @Mark_Sealey,
The auto-topic closing in 2 days was set by the system as this topic was marked as solved about 50 posts ago.
I’ve now removed the solution marker, and the topic will auto-close 1 month after the last post.
1 Like
You guys are aiming at a 500 thread for sure….
1 Like
Trying. But I don’t see how we can get there.
Unless…
1 Like
Mario
It happened again this morning. A restart brought things back to normal.
But if it keeps doing it, I think I should probably open a ticket with Roon Support. If for no other reason than I won’t know into which (of the two ‘instances’) to do regular imports.
Could there be a bug which is also causing another phenomenon with my Nucleus: I can’t remove the ‘Exclude from Backups’ in Time Machine’s Options?
Or is that simply because TM doesn’t like working over SMB and so disallows us to try and back it up that way?
(I do have other multiple clones of Nucleus: music files via macOS/CCC, and the Roon database via Roon’s own backup routines.)
Generally speaking, the SMB server (Nucleus) only advertises the shares on the network and it’s the client (your Mac) that performs the mounting into its own filesystem. And I think this is what happens here, the Nucleus is the passive part. So you need to figure out why your Mac is mounting the SMB share twice.
It certainly happened before for other people, googling “SMB share mounted twice Mac” finds many instances, e.g.
https://www.reddit.com/r/macsysadmin/comments/dsw68s/smb_share_win_2019_server_shows_twice_on_mac/
It actually probably doesn’t matter. File servers are designed for sharing files to different clients at the same time, which would have them mounted. Usually it would be different machines mounting the shares, it’s just that in your case it’s the same machine apparently doing it twice.
I don’t think that TM backs up network-shared mounted folders, so there’s probably no need to exclude it. I certainly didn’t exclude it from my backups and it never occurred to me, but I am not home and can’t verify. I’m pretty sure though (and nobody on Google seems to be talking about doing that)
Well, you could have saved yourself this aggravation by getting a new mac mini - can you still return the Nucleus?
1 Like
Mario,
Thanks so very much (yet again!) for taking the time and trouble to re-assure me.
Yes, I see what you mean. I have been looking for a setting somewhere that might cause two such commands to be run at boot, and - depending on the order in which things happen at boot time - an attempts is made to do something that’s already happened?
For instance, I do have InternalStorage the Volume set to open in System Settings > General > Login items - as implied here.
Thanks, Yes. I need to do some exploring there too
OK. I’ll experiment some more.
Of course I could always try to unmount/eject on ‘apparent instance’!
What’s the worst that could happen? I’d just reboot, which is what I did the last time, when that fixed it.
== TM ==
It certainly seems that way, doesn’t it. Although a very quick glance at this page briefly gave me hope. I say that because I was toying with the idea specifically of including InternalStorage in my TM backups - in addition to the clones I’ve got running nicely
A very Happy New Year, Mario, to you and yours - and with all appreciation for your help!
I’m very happy with my Nucleus, @Audio_Bill, and as Mario says, this is likely a macOS issue.
1 Like
Yes, I guess something like this, and as per your following comments I think you are on the right track
I think the worst that can happen is probably that it doesn’t look neat.
Happy new year to you too, as I am writing this bang on midnight
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.