I do on some of mine because it makes some of the automation i have for them simpler to maintain when it is also applied to x86 hardware or virtual machines. It used to be a huge pain to use on a pi but it works pretty well these days, especially since about 24.04 I want to say.
Oh it is certainly not just you, I am sometimes confused reading them even for commands I have used for years and I know what flag I am looking for but don’t remember the exact syntax or something hah! I am glad they are there but they are definitely not a complete guide to any command, especially built-ins.
Interestingly, this is something AI has been very useful for to me, less searching because I can describe the outcome I want and it figures out what I am talking about generally.
Okay so the disks aren’t also on UPS? That might actually be even worse than the whole thing getting turned off, ZFS is definitely not meant to be run on removable disks like that.
Okay so when you say “unplug the power” do you mean shut it down first or just pull the plug? The latter is a great way to corrupt your storage pools as ZFS uses memory for read and write cache etc by default. You definitely need to do a graceful shutdown especially if there is data that was recently written to disk, that’s why a UPS is so recommended. That said you can usually import an existing pool when that happens, I think there is a UI menu for it now.
Have you tried adding 239.255.255.250/32 to your outbound subnets variable? This is the multicast address for SSDP which mDNS ultimately relies on if I remember right, I recall having to do this for Plex in the past.
Just to make sure, all of your links need to be in quotes if they are not. The : in a url can make some yaml parsers think that it is another block, there are other URL safe characters in general that are special characters in yaml so it’s a good idea to put them in quotes.
This is a cool idea! This sounds a lot like what DANTE and AES67 or AVB are used for in pro audio (mixing console sends multichannel and outputs can subscribe to one or more channels), maybe they have some ideas on timing sync which I think would be the hardest part as others have said, it is crazy how small of a jitter your brain can hear.
I remember your first post a year or so ago and dang you have been busy, it looks really great. I will definitely be installing this at home to organize product manuals and such.
I don’t have anything to add but I am glad someone posts this every week, I always find something new, so please keep it up :D
Just to add my 2c, I just started using this the other day just as an quick UI for ollama and I was blown away at how many features it has and i think the interface is well done. It’s really a great tool so far and I’ll definitely be using it more going forward!
I know you solved it but for anyone that finds this later this feature/behavior is typically called “NAT Hairpin” in case you are looking for a setting to enable or disable, hope this helps!
I found this diagram on SO at one point but I can’t find the post and it is the best explanation I have found for how all of the files work for bash and zsh, each color is an individual path of execution (eg, follow the red line).
Bottom line though, it only really matters if you are overriding something that is already defined, for example I tell my users to use zshrc and I provide defaults and common things in zprofile because zshrc is executed last when they login.
+1 for Raindrop, that app is amazing, I keep watching for a self-hosted version/alternative that is as good and they are getting closer. The killer feature for me is being able to highlight stuff and then when you visit the site again you see what you have highlighted (in addition to saving them elsewhere). I also pay for premium because it’s great, I don’t use a ton of the pro features either.
So if I understand this right you will need to change the network on the port attached to the synology in your UniFi configuration or set the vlan tag in the synology OS, I would do the former. It sounds like you just added a second network/vlan to the existing interface which means you actually created a trunk and are getting the old network untagged and the new network with vlan tags which the synology is dropping. Synology OS also doesn’t really support trunked ports through the UI (even though it does support a port that only uses a vlan tag) so it’s much easier to just leave them untagged.
This is awesome, I look forward to the weekly updates and have found lots of great tools from that. Keep up the awesome work, it is very much appreciated!
They also make this one which uses a CM4 but you can control 4 machines! I have been eying it now that I can get CM4s again, thanks for the post!
Do you want to not use your DL380? IF no it might make a good moonlight host!
I don’t use unraid by my advice for everyone is that you can’t have too many backups of data that you really care about, use the 3-2-1 rule at a minimum.
Also, welcome to your new hobby you will love and hate at the same time sometimes :D
hmm the last line in the log above there says:
“[Fatal ConsoleApp: The requested address is not valid in this context. This can happen if another instance of Sonarr is already running another application is using the same port (default: 8989) or the user has insufficient permissions Press enter to exit.“
So that sounds like that the container might be running but sonarr is not. Did you ever get it working?
So I had a few thoughts. I’m not sure that you can use the docker device flag with a directory as you have there, I think it expects a device node, you can pass that directory as a volume (-v) though.
If that doesn’t work you might also try running the VM with host-passthrough mode set on the CPU as well if it isn’t set that way already, sometimes that is also required for pass through to work from my experience. Also, make sure you passed through the whole device node, sometimes there are audio devices you have to pass through with the GPU device or you will get odd errors like those initialization ones you had. I’m not sure if this is the case for Intel iGPU though offhand though. Are you able to use
intel_gpu_topon the VM to access the GPU? None of that is necessarily specific to proxmox though (but probably applies to anything libvirt powered) so YMMV.Edit: I realized you may not know what a “device node” is, that is the full path to the device, like /dev/dri/renderD128 vs /dev/dri which is actually a directory.