Help setting up new unRAID SageTV9 server

[glenner]

Hey guys, so I've got my new hardware... and am trying to figure out my way through my first unRAID / SageTV9 setup. I could use some tips finding my way around as I'm really confused on how best to set things up initially. I haven't found a really clear roadmap on how to setup unRAID from scratch to get SageTV9 up and running optimally. Does such a document exist?

So far I've done this:

1. Setup hardware: i7-7700, Asus Prime H270 ATX, 32GB, 2 x Samsung 960 EVO 250GB M.2 PCI.E SSD, 2 x 4TB WD Red
2. USB booted 30 day trial of unRAID 6.3.5
3. Installed Community Apps plugin, and a bunch of other plugins (unassigned drives, various dynamix system tools, preclear, etc.)
4. Changed the webUI to black background (way nicer :-)
5. I am now preclearing the two 4TB drives. Wow don't hold your breath!

But so what do I need to do as next steps? Is it something like this:

1. assign one 4TB drive as a data drive for now once it is precleared. (assign the other 4TB drive as a parity drive later once the rig is more fully setup and I have migrated my other data drives from my old setup).
2. assign the two M.2 the cache pool now. I was thinking I would setup this up as the RAID0 setup which I think I saw done in a tutorial video. This provides improved performance and capacity (both SSDs are used in parallel to read and write), while sacrificing redundancy (unclear to me how an M.2 SSD can fail, and if it did, I would not lose much except for mostly a bunch of recent recording?).
3. setup shares? not sure if I need to setup shares up front now, and if so which shares are typically setup.
4. install stuckless SageTV9 docker app. does this need special configuration in the template?
5. install SageTV9 client app on a windows laptop
6. configure SageTV9 and setup EPG using client app. (I'm not clear what to define for recordings directories, etc. Will recordings be saved on my cache drive)
7. setup cache mover to run hourly to move recordings to the array (think I saw that in another post)

Any help is really appreciated, and I apologize in advance for my newbie questions, or if these questions are covered somewhere else. I'm hoping to get unRAID SageTV up and running this weekend and do a basic proof of concept with my extenders. If it all looks good, I'll migrate my recordings and videos from my current Win setup later. I'll also migrate, preclear, and add my old data drives over to unRAID one by one...

Thanks.

[SWKerr]

I have recently went thru setting up my first unRIAD server. I actually started on a new Ryzen server but then moved it to my older File\SageTV server. Even without the Dockers I would recommend unRAID just for the disk Array file server functionality.

Here is a YouTube channel with a lot of unRAID setup videos: https://www.youtube.com/channel/UCZD...MqTOrtA/videos
Most useful for a noob: "How to setup and install the best plugins for unRAID"

Cache Drive: I started with a 525GB M2 but ended up using an older 256GB Sata drive. I think a stripped disk like setup would be overkill. You could mirror the second one for redundancy but for the risk you could just backup the important stuff to the Array or an external drive. You will want to put any VMs on the cache drive for performance reasons. I have my recording drive on it as well and like you mentioned put on the mover for 1 hour sweeps.

Flash Drive: I would backup the \config directory on the flash drive once you have everything up and running. You will also want to make a backup of the VMs if you force them to stay on the cache drive.

Setup the Array: I have 3x4TB and 2x3TB WD Reds in the Array. I setup initially with the 3x4TB with one as a parity drive. I did not preclear any of the drives initially just setup the Array and it went pretty quickly. I am guessing first parity build checks everything. I did do a pre-clear when I added the 2x3TB drives to the Array just so it would not be offline forever.

Docker Setup: There is a "RecordedTV" Path that gets setup by default. It was not clear to me at the time but that path will end up with sub-directories like \tv; \video; \music; \pictures etc. These will all be automatically mapped in SageTV when you start it up. (You can change\add sources later)
I would just start with the defaults and see if you like it. (I think you have to setup the default folders as SMB shares if you want that functionality.)
I am using "/mnt/user/RecordedTV/" This was a folder I had setup for recording with Emby as well but SageTV added the other sub-folders it wanted automatically.

Note: Something that was not clear to me initally was that you would need a mini client or extender to configure the SageTV server initially. A PC Client does not seem to work until after the server is up. (Placeshifter may also work???)

I think all the shares are setup to use the cache drive by default but I would check to make sure. Just make sure it is not No or Only.

Tuners: I think the HDHR tuners were just available automatically. But I had to add "unRAID DVB Edition" plugin in order to get the HD-PVR to work.

Final Note: I used the Docker for about a week but I could not get the HD-PVR to work reliably. I am now running SageTV from a Windows10 VM with my Hauppauge Colossus Passed-Thru to the VM. I had some problems with this initially as well but I think I have it stable now. The HD-PVR had not been used in years so I can not be certain of the cause of the stability issues I had with it. The HDHR worked perfectly in the Docker.

[glenner]

Originally Posted by SWKerr

I have recently went thru setting up my first unRIAD server. I actually started on a new Ryzen server but then moved it to my older File\SageTV server. Even without the Dockers I would recommend unRAID just for the disk Array file server functionality.

Here is a YouTube channel with a lot of unRAID setup videos: https://www.youtube.com/channel/UCZD...MqTOrtA/videos
Most useful for a noob: "How to setup and install the best plugins for unRAID"

Cache Drive: I started with a 525GB M2 but ended up using an older 256GB Sata drive. I think a stripped disk like setup would be overkill. You could mirror the second one for redundancy but for the risk you could just backup the important stuff to the Array or an external drive. You will want to put any VMs on the cache drive for performance reasons. I have my recording drive on it as well and like you mentioned put on the mover for 1 hour sweeps.

Flash Drive: I would backup the \config directory on the flash drive once you have everything up and running. You will also want to make a backup of the VMs if you force them to stay on the cache drive.

Setup the Array: I have 3x4TB and 2x3TB WD Reds in the Array. I setup initially with the 3x4TB with one as a parity drive. I did not preclear any of the drives initially just setup the Array and it went pretty quickly. I am guessing first parity build checks everything. I did do a pre-clear when I added the 2x3TB drives to the Array just so it would not be offline forever.

Docker Setup: There is a "RecordedTV" Path that gets setup by default. It was not clear to me at the time but that path will end up with sub-directories like \tv; \video; \music; \pictures etc. These will all be automatically mapped in SageTV when you start it up. (You can change\add sources later)
I would just start with the defaults and see if you like it. (I think you have to setup the default folders as SMB shares if you want that functionality.)

Note: Something that was not clear to me initally was that you would need a mini client or extended to configure the SageTV server initially. A PC Client does not seem to work until after the server is up. (Placeshifter may also work???)

I think all the shares are setup to use the cache drive by default but I would check to make sure. Just make sure it is not No or Only.

Tuners: I think the HDHR were just available automatically. But I had to add "unRAID DVB Edition" plugin in order to get the HD-PVR to work.

Final Note: I used the Docker for about a week but I could not get the HD-PVR to work reliably. I am now running SageTV from a Windows10 VM with my Hauppauge Colossus Passed-Thru to the VM. I had some problems with this initially as well but I think I have it stable now. The HD-PVR had not been used in years so I can not be certain of the cause of the stability issues I had with it. The HDHR worked perfectly in the Docker.

Thanks for the feedback! I've been watching the youtube videos from the spaceinvader guy... very useful. I also followed his plugin video to install the CA plugin, unassigned disks, etc. But clearly, the vids do not tell me what to do every step of the way on a SageTV setup. :-)

Yeah.. So far, I have an array with just one 4 TB data disk and 2 x 250GB cache pool RAID1. I brought the array online. I've installed the SageTV docker. I just left all the default options in the template. I'm hoping that is the way to go.

I got this in the log:

************************************************
SageTV unRAID/Docker (Container Version: 1.0.2) is running

If this is your first time, install the Windows/Mac/Linux Placeshifter or the Android MiniClient and complete the configuration
Setting up tuners, scheduling recordings, installing plugins, etc, requires using the Placeshifter or MiniClient
To gain browser access, install the Jetty WebServer Plugin
- The SageTV Team -
*** Running /etc/rc.local...
*** Booting runit daemon...
*** Runit started as PID 103
Starting server mode
Jun 30 19:19:50 unraid syslog-ng[110]: syslog-ng starting up; version='3.5.6'

Main is starting

So would seem I'm good to go... I started my Windows v9 SageTV client, and it does not seem to connect to the server. I've never used placeshifter... How do I use that? Are you saying I need to try to connect to the SageTV server using one of my HD300 extenders and set it up that way?

Thanks.

[SWKerr]

Not sure if the HD300 would work but I used the Miniclient I has installed on my FireTV box. If you had any Android tablet or phone it should work. If you have a HD300 handy I would try it.
I have not used Placeshifter in years but it installed and behaved just like the PC Client if I recall.

Also: I found Putty and WinSCP handy tools for unRAID.

[stuckless]

Originally Posted by glenner

So would seem I'm good to go... I started my Windows v9 SageTV client, and it does not seem to connect to the server. I've never used placeshifter... How do I use that? Are you saying I need to try to connect to the SageTV server using one of my HD300 extenders and set it up that way?

Thanks.

Does it see the server? Or does it see it, but, won't connect? I would try the HD300 if you have one, or, even the windows placeshifter (not the full client)

[glenner]

Originally Posted by SWKerr

Not sure if the HD300 would work but I used the Miniclient I has installed on my FireTV box. If you had any Android tablet or phone it should work. If you have a HD300 handy I would try it.
I have not used Placeshifter in years but it installed and behaved just like the PC Client if I recall.

Also: I found Putty and WinSCP handy tools for unRAID.

So I'll use this thread to track my status as I work my way through setting up my new unRAID /w SageTV setup from scratch. I'll try to track major steps I followed and specifically outline any tricky areas or places where I needed to deviate from the defaults.

But so.. I was able to quickly setup SageTV server last night on unRAID. Just installed the docker app, accepted template defaults. Noted that it took quite a while for the docker to install. My Chrome browser said the request was unresponsive twice and offered to kill the browser. I waited through and eventually got the log that the app was installed.

I was able to connect to the unRAID SageTV server using my HD300 extender. Had to disconnect and reconnect the power cable to extender to be able to choose the new unRAID server which it detected. I have always wondered if there is an easier way to switch the SageTV server on an extender. Ideally it could be done through the UI without the hard reset.

I used the extender to run through the setup config wizard, setup tuners, and SD EPG. Took 15 minutes.

I've been using cygwin ssh and Filezilla to connect to unRAID and browse the file structure. May use WinSCP or Putty too going forward... good idea.

I am also really surprised I cannot connect to the unRAID SageTV server using a Windows SageTV9 client. Is that for sure? That's kind of a bit of significant limitation in that case... I was hoping to be able to use my various Windows boxes to connect to the unRAID SageTV server instance. I don't have any android devices. Just extenders, Windows PCs, and iOS devices in my house.

I was able to setup a few recordings using the extender... Seems to work well so far... so that's good progress.

Another thing I noticed is that yes I have the "sagemedia" share at /mnt/user/sagemedia. Under that dir, Sage created external, music, pictures, tv, and videos folders for me automatically. Only "tv" has files in it... Those are the test recordings I created. But the sagemedia share is not setup for cache. The recordings are being saved on disk1 directly. Is this normal? I would have throught that with my 2 cache drives defined, Sage would default to saving my new recordings somewhere on the cache. What is a good recommended setup for setting up these SageTV folders? Should I change the cache config for the whole "sagemedia" share to "preferred"?

[Tiki]

Yes, of course you can use a full Sage Client with the UnRAID version of Sage. However, you can't use it to CONFIGURE the Sage Server.

If you go to the Settings menu on a full Client, you will only be affecting the settings for that Client - not the Server.

If you go to the Settings menu on a Mini-Client (Placeshifter, Extender, or Android mini client), many of those Settings affect the Server.

[stuckless]

Originally Posted by glenner

Another thing I noticed is that yes I have the "sagemedia" share at /mnt/user/sagemedia. Under that dir, Sage created external, music, pictures, tv, and videos folders for me automatically. Only "tv" has files in it... Those are the test recordings I created. But the sagemedia share is not setup for cache. The recordings are being saved on disk1 directly. Is this normal? I would have throught that with my 2 cache drives defined, Sage would default to saving my new recordings somewhere on the cache. What is a good recommended setup for setting up these SageTV folders? Should I change the cache config for the whole "sagemedia" share to "preferred"?

NOt sure I fully understand, but sagetv docker has no knowledge of unRAID. If you want your recordings to be on a cache drive then you'll need to configure the sagemedia share to be a cache share (likely preferred). Some people use a cache, and some people do not, but in all cases you control that, not sagetv or the docker container.

[SWKerr]

Originally Posted by glenner

I am also really surprised I cannot connect to the unRAID SageTV server using a Windows SageTV9 client. [B]Is that for sure? That's kind of a bit of significant limitation in that case...

You can not use the Client to do the initial configuration.
But...after you have completed the initial setup the PC based SageTV client works just as it did under windows.

[SWKerr]

Originally Posted by glenner

Another thing I noticed is that yes I have the "sagemedia" share at /mnt/user/sagemedia. Under that dir, Sage created external, music, pictures, tv, and videos folders for me automatically. Only "tv" has files in it... Those are the test recordings I created. But the sagemedia share is not setup for cache. The recordings are being saved on disk1 directly. Is this normal? I would have throught that with my 2 cache drives defined, Sage would default to saving my new recordings somewhere on the cache. What is a good recommended setup for setting up these SageTV folders? Should I change the cache config for the whole "sagemedia" share to "preferred"?

I did not take the defaults and let the Docker setup the sagemedia folder so I can't say for sure how it is setup. The fact it says disk1 would concern me it is writing directly to a disk and not a share. Does \sagemedia show up on the Shares Tab? If yes I would just change the cache to be "Yes" (Not Prefer) . It is possible to write directly to a disk but you really want to go to a share that is managed in balanced way by the unRAID Array. It may not be a big deal since you just have one Disk and the parity drive now but if you add another disk later it may end up being a problem.

[Fuzzy]

unRAID is very versatile, and there are a ton if ways you can configure your system with your particular setup. The simplest, since you appear to have enough cache space for it, is to set the sagemedia share cache setting to 'Yes'. This will write files first the cache, and then the "mover" script will move them to their final resting place on the array. You CAN set the share to cache 'no', but that will mean the recordings will be written directly to the share, which depending on the number of recordings and performance of the array (parity disk limited, most likely), it could have problems keeping up.

I'll use the sagemedia share to explain a bit how things are laid out in unRAID.

/mnt/disk1/sagemedia is the path to the sagemedia folder on disk 1
/mnt/disk2/sagemedia is the path to the sagemedia folder on disk 2
etc
/mnt/cache/sagemedia is the path to the sagemedia folder on the cache disk
/mnt/user/sagemedia is the path to the combination of all the above sagemedia folders

With cache mode set to 'yes', files written to the /mnt/user/sagemedia folder will write files to the cache drive, and mover - when it runs - will 'fix' this by moving the files to the mount point, unraid will then decide which disk to put that file on (there are a number of things that can go into this decision, but it's pretty transparent).

You could actually set up a share for each of your physical disks, and restrict that share to a single drive; point sage to each of those shares, and tell sage to run in 'Bandwidth' mode, which will spread the recording load among the different drives directly, but you'll still be limited by the speed of the parity disk, even if each disk would normally be able to keep up.

The limitation here is that, by default, the mover script only runs once a day. You may not have room on your cache for a whole day's worth of recordings, so you should probably increase that frequency. This is done in unRAID's settings, under Scheduler. I have it set for hourly.

You don't want to set the cache to 'prefer'. That means that it will 'want' to have the files ON the cache, so mover will actually move files off of the array and onto the cache until the cache no longer has room for it.

[SWKerr]

Originally Posted by Fuzzy

unRAID is very versatile, and there are a ton if ways you can configure your system with your particular setup. The simplest, since you appear to have enough cache space for it, is to set the sagemedia share cache setting to 'Yes'. This will write files first the cache, and then the "mover" script will move them to their final resting place on the array. You CAN set the share to cache 'no', but that will mean the recordings will be written directly to the share, which depending on the number of recordings and performance of the array (parity disk limited, most likely), it could have problems keeping up.

I'll use the sagemedia share to explain a bit how things are laid out in unRAID.

/mnt/disk1/sagemedia is the path to the sagemedia folder on disk 1
/mnt/disk2/sagemedia is the path to the sagemedia folder on disk 2
etc
/mnt/cache/sagemedia is the path to the sagemedia folder on the cache disk
/mnt/user/sagemedia is the path to the combination of all the above sagemedia folders

With cache mode set to 'yes', files written to the /mnt/user/sagemedia folder will write files to the cache drive, and mover - when it runs - will 'fix' this by moving the files to the mount point, unraid will then decide which disk to put that file on (there are a number of things that can go into this decision, but it's pretty transparent).

You could actually set up a share for each of your physical disks, and restrict that share to a single drive; point sage to each of those shares, and tell sage to run in 'Bandwidth' mode, which will spread the recording load among the different drives directly, but you'll still be limited by the speed of the parity disk, even if each disk would normally be able to keep up.

The limitation here is that, by default, the mover script only runs once a day. You may not have room on your cache for a whole day's worth of recordings, so you should probably increase that frequency. This is done in unRAID's settings, under Scheduler. I have it set for hourly.

You don't want to set the cache to 'prefer'. That means that it will 'want' to have the files ON the cache, so mover will actually move files off of the array and onto the cache until the cache no longer has room for it.

Great explanation. I have everything set to Yes except the RecordTV share. I guess I have not been burned since MCEBuddy moves everything from this location to a DVR share that is set to Yes. Just changed it to Yes just in case something changes.

[glenner]

Originally Posted by Tiki

Yes, of course you can use a full Sage Client with the UnRAID version of Sage. However, you can't use it to CONFIGURE the Sage Server.

If you go to the Settings menu on a full Client, you will only be affecting the settings for that Client - not the Server.

If you go to the Settings menu on a Mini-Client (Placeshifter, Extender, or Android mini client), many of those Settings affect the Server.

Hey all, really appreciate the feedback... I was away for the long weekend, but hope to pick up where I left off and continue setting up my new unRAID box.

But so, I've been able to connect to unRAID via the SageTV windows client finally. I've figured out now all "windows clients" are not the same. I had installed the full Windows server package (SageTVSetup_9.1.2.662.exe) on a laptop (say laptop "A"). I was using this as a test V9 setup specifically to ensure I could get the new EPG working. When you install this package, you get the SageTV server service. And you get a SageTV "client" icon on your desktop. I always thought this was the "SageTV client". But this client behaves differently than the client you get if you just use the window SageTV client installer.

I was using this client to try to connect to the unRAID SageTV docker I had setup. But this client does not seem to go through the "sage server discovery" and never finds the unRAID server instance. It only finds the local SageTV server on the same laptop A.

I then installed the other package SageTVClientSetup_9.1.2.662.exe on laptop "B". I guess this is the "full client" and this one does detect SageTV servers on my network, and will prompt me on startup to specify which v9 SageTV server I want to connect to, either the one on laptop A, or the one on unRAID.

So using this "full client" on laptop "B", or one of my extenders, I am able to connect and configure the unRAID instance.

I'm still not clear why the "client" installed on laptop "A" cannot be used to connect to other SageTV servers...

[glenner]

Originally Posted by stuckless

NOt sure I fully understand, but sagetv docker has no knowledge of unRAID. If you want your recordings to be on a cache drive then you'll need to configure the sagemedia share to be a cache share (likely preferred). Some people use a cache, and some people do not, but in all cases you control that, not sagetv or the docker container.

Thanks Stuckless. Please pardon my unRAID newbieness... I will get up to speed I promise :-)

I guess I figured that since I have an SSD cache pool present, and since it generally makes sense for performance reasons for recordings to be written first to the cache, before being swept to the array periodically... ...that during the sagetv docker install, it would automatically create the sagemedia shares with the setting useCacheDisk=yes.

But I guess the default is "no", and that it is just something I need to manually tweak afterwards.

[glenner]

Originally Posted by Fuzzy

unRAID is very versatile, and there are a ton if ways you can configure your system with your particular setup. The simplest, since you appear to have enough cache space for it, is to set the sagemedia share cache setting to 'Yes'. This will write files first the cache, and then the "mover" script will move them to their final resting place on the array. You CAN set the share to cache 'no', but that will mean the recordings will be written directly to the share, which depending on the number of recordings and performance of the array (parity disk limited, most likely), it could have problems keeping up.

I'll use the sagemedia share to explain a bit how things are laid out in unRAID.

/mnt/disk1/sagemedia is the path to the sagemedia folder on disk 1
/mnt/disk2/sagemedia is the path to the sagemedia folder on disk 2
etc
/mnt/cache/sagemedia is the path to the sagemedia folder on the cache disk
/mnt/user/sagemedia is the path to the combination of all the above sagemedia folders

With cache mode set to 'yes', files written to the /mnt/user/sagemedia folder will write files to the cache drive, and mover - when it runs - will 'fix' this by moving the files to the mount point, unraid will then decide which disk to put that file on (there are a number of things that can go into this decision, but it's pretty transparent).

You could actually set up a share for each of your physical disks, and restrict that share to a single drive; point sage to each of those shares, and tell sage to run in 'Bandwidth' mode, which will spread the recording load among the different drives directly, but you'll still be limited by the speed of the parity disk, even if each disk would normally be able to keep up.

The limitation here is that, by default, the mover script only runs once a day. You may not have room on your cache for a whole day's worth of recordings, so you should probably increase that frequency. This is done in unRAID's settings, under Scheduler. I have it set for hourly.

You don't want to set the cache to 'prefer'. That means that it will 'want' to have the files ON the cache, so mover will actually move files off of the array and onto the cache until the cache no longer has room for it.

Thanks Fuzzy. I agree with SWKerr. This a great explanation of a highly useful concept critical to running SageTV, which I have not seen documented clearly anywhere else. So thanks. I've set useCacheDisk=yes for my sagemedia folder, and set my mover to run hourly. I can see recordings being saved to the cache and then moved to the array data disks.

[glenner]

The next issue I'm trying to solve is to get my media shares setup and accessible by Sage.

But so I was trying to setup a structure that made sense to me as follows:

1. "movies" share (cache=no, use any disk) - this holds all my movies. needs to be imported by sage as videos
2. "pictures" share (cache=no, use only disk 2) - this holds my family photos. it is well organized in folders. I don't really want this split across multiple physical disks. needs to be imported by sage as pictures
3. "homevideos" share (cache=no. use only disk 2) - this holds my family digital videos collected from cameras, iphones, etc. also well organized. I don't really want this split across multiple physical disks. needs to be imported by sage as videos
4. "music" share (cache=no. use only disk 2) - this holds my mp3 collection organized in folders. needs to be imported by sage as music.

These 4 shares contain all the personal media I normally collect. Each shares is quickly accessible via SMB on my windows laptops. The shares would presumably also be used when setting up Plex, or any other media server.

But when I go into the detailed setup for Sage, it cannot find these shares as import directories.

I only see /var/media/music, /var/media/videos, and /var/media/pictures are there defined already. On the docker tab, I see /var/media maps to /mnt/user/sagemedia, which contains music, videos, and pictures subfolders. But I don't really want to put my media directly under the /mnt/user/sagemedia subfolders. Do I have to?

I also see on the docker tab, /var/mediaext maps to /mnt/user/media/videos. These volume mappings seem to have all been setup by default for me.

If I create the 4 shares as defined above, I expect my media to be found at these locations:

1. /mnt/user/movies
2. /mnt/user/pictures
3. /mnt/user/homevideos
4. /mnt/user/music

Does it make sense to setup my 4 custom shares like that? What are others doing for this in terms of setting up shares for media and making them accessible in Sage.

How do I get Sage to see, and import from my 4 custom media shares?

Also... I have an SMB share mounted on unRAID that has a mount point like this "/mnt/disks/AUDI_EXT_HD5". This windows external drive has my old Sage recordings on it. I wanted to have Sage import these recordings as videos as well. How can I get Sage to see this SMB share as a video import directory?

[glenner]

Originally Posted by glenner

The next issue I'm trying to solve is to get my media shares setup and accessible by Sage.

If I create the 4 shares as defined above, I expect my media to be found at these locations:

1. /mnt/user/movies
2. /mnt/user/pictures
3. /mnt/user/homevideos
4. /mnt/user/music

Does it make sense to setup my 4 custom shares like that? What are others doing for this in terms of setting up shares for media and making them accessible in Sage.

How do I get Sage to see, and import from my 4 custom media shares?

My bad... I just figured out the sagetv docker has a /tower or in my case /unraid (I set my hostname to unraid) volume mapping that points to /mnt/user where all the shares are. So I can find any share under /mnt/user...

I'm still not sure how I can get Sage to find my SMB share which is mounted here: /mnt/disks/AUDI_EXT_HD5

[graywolf]

Stop sagetv docker
Edit sagetv docker
(Going from memory) should have near bottom Options for additional paths
Should be able to create a new path to /mnt/disks
Start sagetv docker
Should now be able to get to it

[Fuzzy]

Originally Posted by glenner

My bad... I just figured out the sagetv docker has a /tower or in my case /unraid (I set my hostname to unraid) volume mapping that points to /mnt/user where all the shares are. So I find any share under /mnt/user...

I'm still not sure how I can get Sage to find my SMB share which is mounted here: /mnt/disks/AUDI_EXT_HD5

FYI, the /unraid volume mapping to /mnt/user is always called unraid. It was put into the docker template for just this reason, the ability for the SageTV docker to find any of your local shares via direct access instead of needing to go through samba to get there.

Regarding the earlier question about why sagemedia was created with cache=no, realize that SageTV is not creating a share. The docker template maps it's internal /var/media to the host's /mnt/user/sagemedia which in doing so, it creates the /mnt/user/sagemedia folder. Creating a folder in /mnt/user is what creates the sharepoint, and it does so using unRAIDs default settings (configured in Global Share Settings).

[Fuzzy]

If you are trying to get sage to map to a samba share that is NOT on you unraid server, you should have sage talk to that share directly via samba. Do so by browsing to it in sage. Go up in folders until you find Network, and then browse down to your server and share from there.