u/Catch_22_

So all the docker containers use enviro variable [IP] to pull the host server IP so when you use the context menu in the UI to direct you tot he web ui of the docker, bam. Done.

However I want live in my tailscale as I have multiple sites tied together and navigate my servers via that network.

Normally I just use my bookmarks that are already defined with the correct tailscale IP but sometimes I'm in the UI and instinctively use it

I know I can manually update the dockers but when I spin up a new unraid server I have to painstakingly update all the dockers URLs and then do it again in my book marks.

In an effort to cull at least half that work, is there a place to define in unraid the IP variable? If not is there a corresponding tailscale IP variable?

For many months I've been trying to pin down an issue I have with a F4-424 (I also have a F6-424 that I have not experienced this issues with yet).

These systems consist of large cap spinning disks in the bays and 2 nvme drives in the side slots. The OS is Unraid and current.

At times of heavy load my cache will "blip" and stop correctly communicating to the OS. The cache is configured in the typical btrfs pool for protection.

Under a long sustained load a single or both nvme drives will drop, unraid gives the alert that a drive has failed but otherwise the pool in the dashboard/main looks to be intact. (this may just be a bug with unraid updating the dashboard as I cannot see details of the drive if I select it)

If I reboot the device, the nvme drives will show as missing preventing a standard mount of the array. (leaving the array offline - letting the drives cool - for X amount of time has no effect, leading me to think this is not a heat issue, as well as I have no alarms leading up to the crash to indicate the drives have reached their manufacture warning or maximum heat limits. These I have looked up and defined over the defaults from unraid) - I also have had heat-sinks on these from day 1.

A full shutdown is the only method for the system to see the drives again. After a full shutdown the system will come up fine, array in tact and functional. Naturally unraid detects an unclean shutdown and is looking to run a parity check.

Now you might be thinking this is the nvme drives - Ive replaced them already. I had a smaller cache pool set and because of this figured it must be a bad drive, I replaced them with a different vendor/size (deleted and recreated the array) and its still occurring. The class of the nvme also went down so its less I/O and potentially less heat as well.

I'm left with thinking this must come down to the TerraMaster device. I cant find any firmware/BIOS downloads for this thing. I dont think there is a difference with the F6 vs F4 other than the back plane size. Both have the same 32 GiB DDR5 RAM (same vendors) as well.

The only main difference I know of is the loads are run on the F4 and then replicated to the F6 over the network. The F6 is mostly idle unless doing indexing/parity checks.

So I have a raid1 btrfs cache setup on 2 nvme drives, the only data I keep on these drives static are the system/appdata directories. I keep everything else in a monolithic "media" share that is cache->array.

Easy peasy.

During a large data download I managed to fill the cache faster than expected, my mover had not run yet (I dont use mover tuning) and it knocked my docker containers offline as expected in that scenario.

I kicked off the mover service and as it ran I was checking other things and noted that the balance task was saying it was recommended. It showed it was scheduled anyway so I ran it manually - full re-balance. I don't know if this relates but I suspect so - thats why I mention it.

For some reason now my cache always shows 50% full. Running mover quickly (a few seconds) finishes without error. Utilization is 50% on cache. Looking on the pool (512GB cache) shows system/appdata taking 60GB and and "media" (the share that is cache->array) is 179GB.

Any ideas why the mover would ignore these files and not be moving them to the array? Would this relate to the balance task I manually ran?

I suspect I should rerun the balance but pick raid1 but figured I should get clarification before I got any deeper into this issue.

I have been doing some data organization (hoarder) and came across something I have been toting around for nearly 20 years. When I was late teen I got into digital photography as it was coming on to the market and took loads of photos. Long story short I packed up all my photos into a truecrypt container file for safe keeping. I had accessed this many times without issue, last in 2012, before I backed it up and then went on with life. A bout 5-7 years later I pulled the drive out and tried to open it up as I had done many times before only to find that I either don't recall the exact password (more like order) or its succumb to bit rot.

I have drug this 100GB file around for ages and every once in a blue moon I take another stab and getting into it. Today I noted that my veracypt says it dosn't support old truecrypt vol. I figured perhaps that could be the root of my issue and realized there is new truecrypt?

Regardless, can anyone point me in the direction of any tools to help recover this container? I'm sure I know 95%+ of the password (its a set of passphrases strung together) but cant seem to get the order right - I assume. I also have no way to verify that the container is not corrupt.

Most of the articles I have read are focused on whole vol and not the containers. I dont know if thats undercutting my efforts. I also vulgarly recall using whirlpool as an option (that I cant seem to locate in the latest versions of truecrypt. It stands out because whirlpool seemed so cool at the time.

What are my options? Thank you

Old man here who's been back on land for many years but its time to put my boots on and get back to sea.

I have a media library I manually curated for ages. I have been using Nova Player to play back on my Shield and its been great. No need to host a server as it pulls everything I need direct from SMB, playback, metadata etc.

In building out my stack I'm looking into a single point of search to request media. Enter the Seerrs.

My question is - it seems Seerrs need the media player back-end (Jellyfin, etc) and I know I can connect the Shield to the back-end player but - why would I want to?

What is Jellyfin able to provide on the back-end with my stack that the front end of Nova Player isn't already doing?

The way I look at this is - additional resources used on my NAS running the docker that wont be used (unless someone here can point out what I am overlooking)

Thanks for any enlightenment here.