cdiv

I took a look at the time machine docker container and it doesn't appear to be doing much unraid isn't already going. I tried changing my smb-extra to match and no joy. Which makes me think this is a problem external to samba. So I tried changing my time machine share's export setting to no and instead of letting unraid configure samba to share it, configure the share myself in smb-extra, pointing the share at /mnt/disk2/Cadence TM instead of /mnt/user/Cadence TM. This bypasses the unraid process that manages which drive to put a particular file on, which means the entire share has to be on one drive and you can't use the cache. And TM started working. Haven't used it long enough to be sure, but if it keeps working, this might be a good work-around.

Except when there isn't Interesting... when I took that screenshot, I hadn't yet visited the update OS page... I just clicked the (i) in the yellow banner on the top of whatever unraid page I had up. Opening the release notes from the update OS page works, and now that I've done that the release notes will appear if I open the release notes from the yellow banner.

Ok, so I think I spoke too soon about Time Machine working. I haven't gotten a successful backup since yesterday morning. I tried "server multi channel support = no" with no improvement. Also, since macOS insists the server has server-side search enabled even though "spotlight = no", I tried "rpc_server:mdssvc = disabled" which disables spotlight support entirely. macOS is no longer thinking server search is enabled, but that hasn't helped Time Machine. "rpc_server:mdssvc = disabled" is probably a better solution to Spotlight breaking than setting the indexer to gnome tracker, since we don't have gnome tracker anyway, for whatever that's worth. (Actually setting up a search index would be awesome, but I can't be bothered.)

Or, y'know, maybe the solution is to roll back and reinstall rc3 until it works? I just reinstalled rc3 to try troubleshooting this mess again and... it works fine. With my normal smb-extra.conf. I... what? The only thing different this time is it's doing a parity check because it didn't shut down cleanly. (I'm blaming Docker, but I wasn't paying attention) I can't imagine that's at all relevant. I'll attach my smb-extra.conf in case it's helpful to someone... smb-extra.conf.txt

(I removed the Unassigned Devices and Recycle Bin sections from the above quote in an attempt at brevity.) The Time Machine issue is so frustrating, 'cause what seems to fix it for others does nothing for me. I emptied my smb_extra.conf and replaced it with that one and... no joy. I'm trying to come up with anything that might make the same settings work for others but not me and... this sounds like insanity to me, but the only thing I can come up with is maybe `fruit:metadata = stream` is the only relevant part of the config, and not because the metadata needs to be stored as xattrs instead of in a netatalk-compatible way, but because changing the location effectively clears the metadata... which wouldn't happen for me because that was a setting I played around with previously, so I already have metadata stored in both formats. I haven't been able to test this theory yet... and it'll be a few days until I can test it. And honestly, I don't think it's likely... but I think the rest of the config is a red herring. `fruit:nfs_aces = no` is already set by unraid in rc3. `fruit:zero_file_id = yes` is the default according to the documentation. `fruit:encoding = native` changes how unicode in filenames gets stored, but there are no files with unusual characters in Time Machine disk image file names (unless maybe if your computer name contains them) `spotlight backend = tracker` changes the spotlight index source for server-side spotlight searches to Gnome Tracker, which isn't installed or configured on unraid. I don't think setting that should fix anything, but apparently it fixes spotlight... but Time Machine doesn't need spotlight for the share anyway. `veto files = /._*/.DS_Store/` blocks the creation of .DS_Store files and hides existing ones along with the files that store resource forks from SMB users. I don't think that's a problem for Time Machine and I'd rather have DS_Store working, so I hope that's not the solution. That leaves `fruit:metadata = stream` which changes how macos xattrs are stored and `vfs objects`. The only vfs object listed in that config that we aren't already loading on each share is acl_xattr, and that's for supporting Windows access control lists, which shouldn't be relevant here. So yeah. Unless anyone comes up with a better idea before I get a chance, I think I'm gonna try deleting the xattrs from the Time Machine backup and see if that helps. Honestly, I doubt it will, but... I got nothin'.

Feel free to add it. No real need to credit me, it isn't like I have any other posts here for people to look at 😀

If anyone's interested, here's the YTDL_OPTIONS string I'm using. It'll embed english subtitles and chapter markers (for videos that have them). It'll also fix the permissions on the downloaded video. (The downloaded subtitles file will be deleted, change already_have_subtitle to true to keep it)