kickhiminthenards

Uh ok, so after testing things out a bit more, I had to do some more stuff with permissions for the folders. I added a separate watch folder as well, because it'll start encoding whatever is placed in there, on its own. So about the permissions, I changed all of them to full control in the datasets, as well as created a User - apps in the list of permissions, with "Apply permissions recursively" turned on (I didn't enable it for "child datasets" since I figured the folders doesn't have any manually added datasets below it) and then it worked with sub-folders and normal browsing in handbrake of the video files separated by their own sub-folders. I don't think I have anything else left to add, and I bet I'm probably the most tech illiterate here, but I hope someone will find it helpful at least. Keep in mind that I'm using the updated electric eel for truenas scale, so it might be different and maybe even without any problems whatsoever if you're using the version of electric eel that came with the hexOS install.

Or maybe I didn't even need to create that dataset for handbrake since I didn't place the config file manually in it, idk. Anyway, as long as it works then all's well that ends well. (The timer had expired for editing the post, otherwise I would've just added this there.)

@Dylan Thank you for your help! It really helped me get a better understanding of the bigger picture in regards to all this, and it helped me kinda jerryrig my own solution to it. Thing is, shortly after installing the OS I had also decided to update truenas scale, which I found out later that it isn't recommended to do so. It didn't break anything for me at least, so I just figured it's all good. But after having wrestled with the guides you sent me, and stumbling upon a random reddit thread, I ended up finding out that the issue causing this whole mess was that I had basically done a "default installation" of pretty much everything in Handbrake when doing it via truenas scale. So part of what the latest version of electric eel (truenas) did, was change how the apps are handled - and how they are placed, which is more relevant for this - which messed with how handbrake sets up storage paths to "watch" and output from how it's installed. The people in the reddit thread were talking about how it's essentially a "1-click solution" to change the already-existing apps to fit that update, but they didn't really talk much about when installing from scratch. Which is where that guide by Theo about radarr and sonarr really helped out, because it made me familiar with the finnicky nature of the storage options and premade datasets when installing something. So this is what solved it: (I had already deleted handbrake quite a while ago, so at this point it's without the app installed) I made a dataset for handbrake, in /mnt/HDDs/Applications/ with permissions set to user, group, and other, with root and read/write/execute (I figured why not, I didn't really feel like taking it one permission at a time and I'm fine with leaving it as it is now, but up to you (the reader) if you want to be more cautious about it). I did not make a config sub-dataset like the sonarr/radarr guide suggests for sonarr/radarr. I then installed handbrake with mostly the default options still as they are. However, I left the config storage to iXVolume because I figured it's not something I need to be messing with anywhere other than in the UI for the app and there it was already working fine previously - and then I changed all of the other storage options to Host paths with a folder I've set up myself. (I should've made more folders for it in order to separate the pre-encoded from the re-encoded video files, but I just wanted to get it over with to see how it goes.) So I gave it a shot, and it works fine now. Well, kind of. I still can't see the HDDs folder, although I could at one point during my trials and errors but then it wouldn't give me access so I decided to try something else. But now the built-in view of "storage" in the app's UI can see the video files just fine, in a place where I can place them; because Applications isn't accessible (nor viewable) to place files in, which is where I'm guessing Handbrake had assigned as its "storage" pathway before. Anyway, lesson learned without too much harm done, that I'm gonna have to mix things up a bit to work with the updated electric eel version of truenas scale, since HexOS is still meant to be used with the version it came with during its installation. Thank you for the help! It did push me in the right direction.

Sorry about the way I phrased it, I just wasn't really sure about how to phrase it. Nor am I sure even now. But the app literally can't see the HDDs folder. It can see the /mnt/-folder (as well as the rest of them), but when accessing /mnt/ then it shows nothing within the folder. So I can't select the video files to be encoding with the app. I have no idea why.

Hi, so I just wanted to know if anyone has tried out handbrake in the truenas scale-layer yet? It seems really limited in its ability to identify folders, and both truenas and hexOS are kinda limited when it comes to folders as well. I can get into root and so on just fine when digging, but Handbrake can't even see the HDDs pool in /mnt/. I'm new to Linux, so it's best if you (the reader) don't assume prior knowledge. All I know is that I have certainly been warned about configuring folder permissions in Linux from what I could find online and so on, but I was hoping I wouldn't encounter such issues; but now that I have, I'd very much appreciate if there's anyone who could help me out! Google hasn't been any help for me so far.

Yeah, I'm not sure about that part either, or if it even needs OS support beyond the support for the hardware itself. But in case it does, I figured it's best to make the HexOS team aware of the desire to use it for that at least, as a rendering server so to speak.

Yeah I figured, but it's that part about deep link that I'm interested in, and what I want to use the hardware for.

Hi, so first of all I'd like to think of myself as a target demo for HexOS. I got myself my first NAS half a year ago, and it was a plain asustor one with its inherently low specs which I meant to be solely for storage at the time when I bought it. It was also the first time I've used anything linux-based afaik, other than steamOS. I ended up delving deeper into the world of NAS systems, and I really liked to explore portainer and docker images. Unfortunately because of the limitations of the unit, it limited what I could do by quite a lot; so I decided to go for a custom NAS instead, and when I heard about HexOS from LTT videos I figured it's a perfect match since it's meant to simplify everything. So far, I've really liked my experience with HexOS, although it's admittedly a bit barebones in terms of features; but that's what truenas scale makes up for. Anyway, so I was looking into the parts to get for a custom NAS build that I wanted to get, and that's when I stumbled upon intel deep link. It was also soon time for the release of battlemage when I was looking into all this, and so I went for it. I got myself a b580 limited edition, and a 12900K, hoping to be able to use deep link in handbrake, which iirc is one of the few programs that can utilize deep link. But the current hiccup I've got is that it couldn't recognize the discrete GPU whatsoever upon installing HexOS a week ago, which I guess is because truenas doesn't support battlemage yet but got it in their roadmap for 2025? So anyway, I'm not making this post about the inability to recognize the b580. I'm making this post because this part of the forum is described as being about "hardware you want to use", so I'm just doing this to mention I want to use the b580 with the 12900K for rendering in handbrake, as pure feedback; I don't mean for it to be a thread to discuss anything. Thank you for reading, and have a nice day!

When I updated truenas, hexos has kept working as it's supposed to.