thumdinger

joined 2 years ago
sorted by: new top controversial old
Cloud Free Smart Home in c/selfhosted
[–] thumdinger 2 points 5 days ago* (last edited 5 days ago)

I use the Amplipi from Micro-Nova for whole-home audio and I love it. It’s local, open source and has a Home Assistant integration.

The main unit has 6 zones, but expansions units can be added. I think it supports up to 4 simultaneous streams. We use 2x AirPlay streams, and a turn table connected via RCA, but many other options are supported. They detail it all on their website and GitHub repo.

SMB not working in Scale 23.10 (following Core migration) [SOLVED] in c/[email protected]
[–] thumdinger 2 points 1 year ago

Yeah they must have removed the fields in 23.10. Thanks again

SMB not working in Scale 23.10 (following Core migration) [SOLVED] in c/[email protected]
[–] thumdinger 1 points 1 year ago (2 children)

Thanks for the clue. I haven't been able to find anything in my config. Is there supposed to be a text field for setting auxiliary parameters, or are we just referring to advanced options here? Do they need to be configured via the shell in Scale? I've included screenshots of my SMB/share config below.

Next step will be to just install Scale fresh and re-config from scratch, importing the existing pool. This will hopefully eliminate any odd parameters that shouldn't have been carried over from BSD.

Also, and I'm just venting now, why isn't any of this mentioned in the Truenas article for the migration, or the supplemental "Preparing to Migrate..." article...?

https://www.truenas.com/docs/scale/gettingstarted/migrate/migratingfromcore/

https://www.truenas.com/docs/scale/gettingstarted/migrate/migrateprep/

Samba Config

Advanced Settings

Config for a new share, created for a new test dataset:

I have tried both the default share parameters, and the private SMB dataset and shares options for Purpose

7
SMB not working in Scale 23.10 (following Core migration) [SOLVED] (self.truenas)
submitted 1 year ago* (last edited 1 year ago) by thumdinger to c/[email protected]
4 comments fedilink
 

Hey all, not a lot of activity here yet, but hopefully someone can offer some advice!

I'm having major regrets following migration from Core to Scale. The migration via update file went smoothly, but immediately apparent on starting up Scale, all of my SMB shares were broken. Both Linux and Windows clients are unable to connect.

I have since tried creating new users/groups (I noticed that my normal user and group with id's 1000 had been changed to 1001 in Scale), stripping ACL's and recreating, and deleting the shares and recreating. Failure to connect on each attempt.

Is there something I'm missing relating to the migration that prevents SMB from working? I'm not well versed in the inner working, or shell command available for troubleshooting, so most of this has been attempted through the GUI.

Also, I realise I have shot myself in the foot. Like an idiot, I saw the feature flag update message when Scale first started. I clicked through and upgraded without even thinking. I realised what I had done when I restored my Core VM from the previous day - the pool was offline, with zpool import showing an unsupported feature message. So any path back to Core is off the cards I think.

Any help is appreciated...

EDIT:

I think I have found the culprit. I downloaded the debug info and had a look at the SMB config (specifically net_config.txt). For some bizarre reason, the SMB interface had bound to an old IP address (two or three home network revisions ago - not used in many years).

[GLOBAL]

interfaces = 127.0.0.1 192.168.0.200

By selecting the systems current IP address in the optional "Bind IP Addresses" field in the global SMB service settings (under advanced), I've been able to rebind it to the correct address, and I have access (tested in Linux only so far)! phew...

/r/selfhosted in c/[email protected]