Jump to content
  • Big Sur missing Xserve sidebar glyph


    CS01-HS

    Maybe an oversight by Apple or maybe intentional.

    NAS is my unraid server.

    940981563_ScreenShot2020-11-17at5_47_08AM.png.ef1b34fe0086a946b55f44aaf12ca4e0.png

     

    The closest supported server type I found was macpro-2019-rackmount so I customize the smb.service with the following script:

    cp -u /etc/avahi/services/smb.service /etc/avahi/services/smb.service.disabled
    cp /boot/extras/avahi/smb.service /etc/avahi/services/
    chmod 644 /etc/avahi/services/smb.service
    touch /etc/avahi/services/smb.service.disabled

    Where /boot/extras/avahi/smb.service looks like:

    <?xml version='1.0' standalone='no'?><!--*-nxml-*-->
    <!DOCTYPE service-group SYSTEM 'avahi-service.dtd'>
    <!-- Generated settings: -->
    <service-group>
     <name replace-wildcards='yes'>%h</name>
     <service>
      <type>_smb._tcp</type>
      <port>445</port>
     </service>
     <service>
      <type>_device-info._tcp</type>
      <port>0</port>
      <txt-record>model=MacPro7,1@ECOLOR=226,226,224</txt-record>
     </service>
    </service-group>

    which gives me this:

    467124774_ScreenShot2020-11-17at5_55_00AM.png.501846d0d9189f04629435881bc192b8.png

     

    Poking around I found a pretty good server glyph in an assets package (server.rack.svg) but it's not a recognized bonjour type and I don't know how to add it.

    2112585361_ScreenShot2020-11-17at5_41_47AM.png.17dca0eb0553b45609a8a0c51f8ef9e2.png

    • Like 2



    User Feedback

    Recommended Comments

    That must surely be a problem with Big Sur. Both the icon in the main Finder window and the smaller one in the sidebar are fine in High Sierra (Unraid servers are Lapulapu (6.9.0-beta35), Mandaue (6.8.3) and Northolt (6.8.3)).

    327904415_ScreenShot2020-11-18at00_51_33.png.1cc97f140716da4c35582b795a3c6a91.png

     

    • Like 1
    Link to comment

    I set it up as a user script to run hourly but honestly can't remember why.

     

    It would make sense to put those lines in config/go so it's run on startup, but maybe that doesn't work because smb.service is overwritten on array start?

     

    The fix for that would be to set the user script to run on array start but I didn't do that either, strange.

    Link to comment

    Maybe Apple made the decision to stop providing icons for hardware it hasn't manufactured for a number of years. I see two possible ways forward:

     

    • Ask Apple to consider reversing that decision
    • Make a feature request for Unraid to specify a different icon

     

    I suspect the second is the more likely to be successful. If I'm honest, I think the new Apple icons are more for decoration than for giving meaningful information, anyway.

    Link to comment
    11 hours ago, John_M said:

    Maybe Apple made the decision to stop providing icons for hardware it hasn't manufactured for a number of years. I see two possible ways forward:

     

    • Ask Apple to consider reversing that decision
    • Make a feature request for Unraid to specify a different icon

     

    I suspect the second is the more likely to be successful. If I'm honest, I think the new Apple icons are more for decoration than for giving meaningful information, anyway.


    The icon is correctly visible in the same view like the screenshot you attached above, the only bug about it is the small icon in the sidebar that appears as a generic blank sheet.

    Link to comment
    On 1/19/2021 at 4:12 PM, CS01-HS said:

    The fix for that would be to set the user script to run on array start but I didn't do that either, strange.

     

    I will try that.

    Link to comment
    On 1/19/2021 at 4:12 PM, CS01-HS said:

    I set it up as a user script to run hourly but honestly can't remember why.

     

    I probably understood why, this morning I set a new icon (Macmini) manually in the smb.service file, everything worked until now, I don't know how, but the Xserve icon returned.

    • Like 1
    Link to comment
    10 hours ago, Gian Marco Cinalli said:

    The icon is correctly visible in the same view like the screenshot you attached above, the only bug about it is the small icon in the sidebar that appears as a generic blank sheet.

     

    How does that make it an Unraid bug?

    Link to comment
    19 minutes ago, Gian Marco Cinalli said:

    In fact it isn't, it's just a Bug Sur bug.

     

    Which was my point back in November!

     

    On 11/18/2020 at 1:04 AM, John_M said:

    That must surely be a problem with Big Sur.

     

    This is a place for reporting bugs in the current pre-release version Unraid, not other operating systems.

    Link to comment
    2 hours ago, John_M said:

    This is a place for reporting bugs in the current pre-release version Unraid, not other operating systems.

     

    I assumed Apple was phasing out old model types, in which case it'd make sense for unraid to use a more recent one. But right, maybe they just forgot and plan to fix it.

    Link to comment

    This is still an issue. The Xserve glyph seems to be removed for good. (Tested on macOS 12 Monterey 12.3.1 (21E258)).

    I think that if it's a mistake on Apple's side, they would have fixed it since the initial Big Sur release. Even the last major OS release didn't add the glyph back.

    It would be nice if UNRAID could just change the default to the Mac Pro rackmount icon. The current "file" icon is somewhat confusing.

    (TrueNAS also uses "model=MacPro7,1@ECOLOR=226,226,224")

     

    Also, for now I'd recommend the following script (if you don't want the file icon). This will replace the model=Xserve with the correct model for the Mac Pro rackmount icon. If the file ever changes in future UNRAID versions, this should still work.

    sed -i -e 's/model=Xserve/model=MacPro7,1@ECOLOR=226,226,224/g' /etc/avahi/services/smb.service

    I set it to run at "Array Startup", but I didn't restart my UNRAID server just yet. I just manually ran the script once (which worked).

    Edited by TheJulianJES
    Link to comment

    FYI I opened a feature request for this as it's still an issue and I didn't see any others open.

    Also, I used TheJuianJES's script and run it at array startup but had to throw in a 60 second sleep before it since something else was wiping smb.service right after it made the change. I haven't been running it for long so it's possible something else will come by and reset it after a while.

    On 4/8/2022 at 7:50 PM, TheJulianJES said:
    sed -i -e 's/model=Xserve/model=MacPro7,1@ECOLOR=226,226,224/g' /etc/avahi/services/smb.service

     

    My full script below
     

    #!/bin/bash
    sleep 60
    sed -i -e 's/model=Xserve/model=MacPro7,1@ECOLOR=226,226,224/g' /etc/avahi/services/smb.service
    /etc/rc.d/rc.samba restart

     

    Edited by thellamapaul
    Link to comment

    UP

     

    This issue still occurs, not possible for the dev to force this change in next releases ?

     

    Tried the sed command just below, and it works like a charm, but, if you modify anything related to shares, the old icon turns back. Means, impossible to only use a user script (or, run this one manually for every change you made).

     

    PS Mac OS Sonoma

    Edited by Copyright
    Add detail regarding the OS
    Link to comment

    Isn't it a problem to restart the service every hour if you have large copies in progress, e.g., Time Machine or similar? That's a concern for me, but I've thought of it, too.

    Link to comment

    The sed command shouldn’t restart the service. The script running every hour just makes sure that the correct text is in that file.

    Link to comment

    I was referring to thellamapaul's post, but indeed, every hour without restarting the service, but just making sure the line is the right one is a great idea too.

    • Like 1
    Link to comment

    While I was digging through the Flash drive to see where the "Xserve" was defined, I noticed that "shareAvahiSMBModel" variable, in the /boot/config/share.cfg file is set to Xserve. I changed it to use MacPro7,1@ECOLOR=226,226,224 instead (which matches with my config in Extra smb parameters in the webui).

     

    Then, I went ahead and modified the currently "loaded" avahi config, /etc/avahi/services/smb.service, replacing the "_device-info._tcp" to use the same MacPro7,1 flag. This fixed all the issues with the sidebar icon in Finder. Haven't rebooted yet to verify this config is loaded on boot.

     

    However, I had another issue where connecting to the SMB share with the iP address (using say, smb://192.16x.xxx.xxx/ShareName) created a duplicate in the sidebar (one with the broadcast Avahi/mDNS/Bonjour name, and one with the raw IP address). To fix this, I changed my smb connections to use the Avahi url directly, smb://server_name._smb._tcp.local/ShareName). Now it works well, and Finder doesn't have a generic file icon anymore.

     

    For context this issue occurs because Finder moved to using SF Symbols in the sidebar after Big Sur. Unfortunately the Xserve / RackMac icon which Unraid uses by default has no matching UTTypeSymbolName mapping inside SF Symbols which is why it breaks just for the Finder sidebar. (Source: Reddit discussion about this)

    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.

×
×
  • Create New...