thany

It should just work if I follow the utterly basic steps from the tutorial. Whatever the result of those steps is, that's what I've got. If you think it works differently on every machine, please consider fixing that. My reason for encryption is two-fold: 1. Don't bother the client with it. Just connect to the target, and done. 2. Offload for performance reasons. And again, what's the point of having a container if it doesn't add any value by being a container? I mean, an unencrypted uncompressed regular plain "raw" container of files is no better than just a shared folder. UNLESS it's used to make clients boot from it. Or am I missing something?

Not working. I added a FileIO container (or whatever it's called) of 500GB. Done. Then I created a target using that file, created a LUN using that target, and used the iSCSI Initiator panel in Windows 10 to connect to it. Host is found, LUN is found, but when I connect to it, it just says `Unable to Login to the target.` No further information appears to be available. I don't know what to do next. Also could you, author, please read your own tutorial? It's really difficult to follow, because it's written quite poorly. Not just typos and grammar errors (which to me stand out like a thorn), but also skipping over things as if to assume the user knows everything about it already. I guess it just needs some love, and love is not what it's gotten so far. Another question: what can I do in terms of encryption? Since it's essentially a virtual disk, I thought it'd be meaningful to add encryption. Would be nice if it could layer in veracrypt or similar. Without encryption, it's just a container for a filesystem, making it only useful for... I dunno, getting clients to boot off of it maybe.

I had this a few times now, that CouchDB isn't persisting its settings, or at least its CORS settings. At some point, not neccesarily even after restarting the container, so perhaps after updating it only, I'm getting CORS errors in the clients "suddenly" and I have to get in there to fix it again. This has happened 3 or 4 times over the past few months. So let's say this happens about once every 2 months or so - not sure that this is helpful though. I'm not seeing any files appearing in the mapped config folder. That folder has 777 permissions, so it should be able to create its persistent config there, if it wants to. Otherwise I don't know where else the config goes. The databases are persisted perfectly fine, so it is capable of persisting data, generally speaking. What can be done to fix this?

This is still happening. When I attempt to insert a block of code into a post, that popup never goes away without destroying it in the devtools inspector. Can this please be fixed? It might help a lot of other people too, who don't take the effort to report it, and just muddle through or give this forum the finger. We don't want that, do we.

I suspect the fact that vhost0 doesn't get an IP-address (for whatever reason I can't figure out yet) might have something to do with it. I think that might be the interface VMs get connected to when they attempt to access their Unraid host: root@unraid:~# ifconfig vhost0 vhost0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 02:60:71:10:c2:74 txqueuelen 500 (Ethernet) RX packets 3361579 bytes 208546658 (198.8 MiB) RX errors 0 dropped 2700291 overruns 0 frame 0 TX packets 37913 bytes 1592346 (1.5 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

And here's the diagnostics that I forgot to add. unraid-diagnostics-20240511-1216.zip

I've got two VMs that can't reach reach Unraid itself, and Unraid can't reach them either. Other than that, their and Unraid's networking works totally fine. To give you a practical overview: VM cannot ping Unraid VM CAN ping the internet VM CAN ping other devices on the network VM CAN ping the router Unraid cannot ping VM Unraid CAN ping the internet Unraid CAN ping other devices on the network Unraid CAN ping the router Other devices on the network CAN ping VM Other devices on the network CAN ping Unraid And when I say "ping" I also mean "establishing any sort of connection". Also, all these have been attempted by their IP-address, just to eliminate name resolution issues. So it seems there's something going on ONLY between Unraid and the VMs. It goes for all VMs, among which are both Windows and Linux based ones. I cannot find for the life of me anything in the way of VM network settings. Usually hypervisors have some kind of VM network settings thing, don't they? The "Network source" is set to "vhost0" and "Network model" is set to either "virtio" or "virtio-net". I'm not sure what these mean exactly, but they've always worked fine, and so they ought to work fine now as well. I shouldn't have to emphasise that network does work fine, so I'm guessing this bit of config is correct. It's just very specifically the communication between VMs and Unraid. So how do I fix this? Has Unraid recently added some type of restriction/security measure to prevent VMs from accessing their hypervisor? I'm sorry that I don't know exactly since when this happened. Definitely not for months, I reckon. I only know for sure when I discovered this problem, which is just now. As for the network topology: it literally couldn't be simpler. No VLANs, no advanced networking stuff. Just a router and some clients.

I see this docker requires as many as 7 ports to be mapped. In the settings they are just called Host Port 1-7. 1. Can you please give them meaningful names? 2. Until then, can you list what they're for?

I was never asked to do that when I installed the docker. So how could I possibly have known to do this? Or indeed, how should I have known that it's apprently /config? Edit: scratch that, it's under "more settings", it's mapped to appdata/unms perfectly fine. And there is stuff in there. But I've also got another directory appdata/unifithat also has data. Could be renamed or something and reset itself because of that?

My UniFI docker (you call it unms) seems to have lost its login information. Seems it's not being persisted anywhere, which makes sense, because there's no directory mapping. Nobody wants have to go through the setup every time Unraid has gone through a reboot, or the docker updated, or some other stop/start cycle. Can this be fixed please?

I just found that couchdb isn't persisting its config. I added CORS configuration, and it started doing what I needed it to do perfectly. But as soon as the docker had to restart (or maybe after an update? not sure actually), this bit of configuration is gone, and all config fields are back to what looks like default/initial config. Can this be fixed please? This is probably a config in the dockerfile or definition of fields for Unraid. Pretty sure this is not a bug in couchdb itself.

Getting only 9MB/s to my SSD cache. Just by copying a big file through windows networking to a share that uses an SSD as cache. Such SSDs are fast enough to saturate the 1Gb ethernet connection from the client, and the unraid server is connected on 10Gb. There are no other processes accessing the array. Even without cache, directly to the HDDs then, it should still easily be able to saturate a 1Gb network. The other way, server to client, is even worse at around 6MB/s. I also don't see anything that is blocking up the CPU, memory utilisation, or any other significant I/O. It's also not intermittent. The slow speed is constant. It will not improve if I leave the file copy going. It also doesn't improve if I let things settle by giving it a few minutes and then trying again. Another thing worthy of note is that in the "main" tab, I see 0.0B/s for every disk/ssd involved all the time (in both directions). It's like it's copying to/from the memory cache, which would be great, but should be able to saturate ten network connections with bandwidth to spare. So that doesn't explain why it's so slow. Rather I think something is broken. I would expect at least 100MB/s in each direction. And preferably also see that reflected on the "main" tab. So what's blocking it up? unraid-diagnostics-20231228-1504.zip

It was alright for a while, but it suddenly started happening again. I doubleclicked on a link in a reply that I was quoting (not yet submitted) which pops up the link editor popup. That would not go away, so I couldn't proceed to submit my reply (well, that is without hackery in the devtools). Cookies cannot cause such behaviour, and if clearing cache would solve it (not tried yet) it would only mean you're telling the browser to cache your files too aggressively, or invalidate them incorrectly. Either way, it's 100% reproducible now. I see a "MultiQuote" tooltip just floating around and I'm afraid to attach a screenshot, because the popup for it will never go away, leaving me effectively unable to attach one. Edit: clear cache (and refresh the page) doesn't help.

Yup, that was it. I must've added it at some point, yes... Totally missed this one. That wasn't it, because of the above, but I tried it anyway and it said it cleaned up 6 "configurations". I wish it would say what configurations they are, that it cleaned up. It kinda doesn't feel right when it cleans up something without me knowing what that is. Or alternatively, make it so that cleaning up won't be neccesary

That feels like something that I would have to put in somewhere deep into the OS somehow, which then does its job. But if I ever need to touch it for whatever reason, I'm going to have the greatest difficulty finding where it got buried again. So basically the answer is "no it's impossible, unless you like to hack it in" which means if it ever stops working (or starts working too well), I'm on my own. I would rather stick with supported features, which is why it would be nice to be able to use the "scheduler" for more than just the mover, and have the option to make it do a selection of action at certain intervals. Basically, make the scheduler more configurable and do more stuff. Then it's also (more) visible just in the web UI, so it's not buried somewhere in some script or config file that I won't know about anymore after a week. It's okay though. And thanks for the reply, but no thanks

Sorry, I've been on holiday since my TS. Here are my diagnostics. But as said, such file/directory simply doesn't exist anywhere, as proven by that `find` command. Or did I do it wrong? And surely if Windows discovers I have no access to a share, it would show an error about it, but that time I saw *nothing* pop up. After upgrading unraid to the latest version however, I get the error "The network path cannot be found" which usually means the server name is incorrect, even though other shares on the same server work fine. unraid-diagnostics-20231221-1411.zip

When connecting to my unraid through a VPN, I don't get any output. When I connect locally, it works fine. I do get the popup "updating plugins" or "updating the container", but it never gets any content. For the plugin updater, I decided to just hit the close button after some time, and refreshed the page only to see that the plugins did actually get updated. That's why My assessment is that *only* the verbose output in the popup isn't working, whereas the actual updating process in the background is (or seems to be) working totally fine. As for updating a docker, the three loading "balls" keep animating seemingly forever. Again, after allowing it some time to do its thing, I refreshed the page to find the docker updated. Even stranger, when I open the network tab in the devtools, the output starts working. Maybe there's something not quite right with XHR calls or something, because the "Main" page wasn't showing any meaningful content either. I thought it was just slow (which it is) but now that I'm typing this out, it might be related. Any ideas?

"Just" as if it's obvious 😕 It's not. Can you please add some sensible defaults?

Okay, like I said, can this be added?

When I go to \\unraid I can see a share called "downloading" that no longer exists. It's been a while since I've accessed unraid this way, but iirc, this share existed on a ZFS pool that I've removed. Somehow the share still lingers. Trying to open it in Windows, just doesn't do anything. No error or nothing, just as if I never clicked it. The confusing bit is that it doesn't show up on the shares tab in the web UI. So my question: where exactly is it pulling shares from, when returning the list of shares when accessing unraid via SMB? I have already done find . -name "downloading" in the root with 0 results. So at least we know it's not a file/directory with that name, that's causing this phantom share to exist. I've also created a share with that name, and then deleted it. That doesn't fix it either. I'm using Unraid 6.12.4.

Sorry, I know this has been asked before, but in my defence, it was asked many years ago. By having said that, I do know this can be done through userscript. But I don't prefer installing userscripts, because they feel like going outside the scope of the system you're applying them to. Kind of like applying user script/styles to a website - it may break at any future update. So here's hoping Unraid now supports this option natively. I just want to add a schedule where I set up on which time of which days the disks are required to be spun up. The flip side could be to just never spin them down. And sure, some drives are designed to do that, but I'm not sure that mine are. Sure they are enterprisey-like drives, but that doesn't mean they are designed for 24/7 spinning, and even then, that still doesn't mean spin cycles are actually bad. And besides, I like to save power where I reasonably can, because I kind of like this planet 😊 Anyway, I digress. If this feature exists, where is it please? If it doesn't exist, pretty please to add it? 🙏🏻

I've just installed CouchDB with the default settings, and the first thing it does after starting, is stopping itself. The log says: ************************************************************* ERROR: CouchDB 3.0+ will no longer run in "Admin Party" mode. You *MUST* specify an admin user and password, either via your own .ini file mapped into the container at /opt/couchdb/etc/local.ini or inside /opt/couchdb/etc/local.d, or with "-e COUCHDB_USER=admin -e COUCHDB_PASSWORD=password" to set it via "docker run". ************************************************************* I understand what it says, but I don't know how to act upon it. I don't know how to pass commnadline arguments, or where I'm expected to put an ini file, or even what exactly to put there. Dear author, could you please change the docker such that a default setup at least works? And/or add fields in the docker to enter a username/password to use? Much obliged

It's not working. I *know* that I'm accessing a files from the main array, I *know* which share I'm accessing it on, and I can *see* with my own two eyeballs my access is producing disk I/O activity. All three monitor are enabled. Even though I might be seeing hundreds of MB/s being written and/or read, the File Activity plugin happily shows no activity whatsoever. Then why do I need File Activity plugin? Because sometimes I also see some kind of ghost file activity of about 5MB/s being written that for whatever reason blocks up most other I/O. And that too doesn't show up, even though that's actually the important bit that I need to know about. So how do I make it actually show activity that is definitely occurring?

I'm just trying to make the simplest possible ZFS pool: one drive, no fancy settings. Here's what I did: 1. Stop the array 2. Add pool - giving it a name and 1 slot 3. Assign into it a totally empty new spinning rust drive 4. Click on the pool name 5. Set the filesystem to zfs 6. Set autotrim to Off 7. Apply & Done 8. Start the array Actual result: That one drive says "Unmountable: Unsupported or no file system" Expected result: Since I said the pool should be of the ZFS filesystem, I would expect it to make new (empty!) disks that filesystem. It doesn't make sense to yell at the user for the filesystem not being present, when the OS probably should have created the filesystem as part of creating the pool. So my question is two-fold: 1. What is the responsibility of the OS when it comes to creating a pool of new devices, and creating filesystem structures on it? 2. Where can I find a concise but complete guide on how exactly to create a ZFS pool? For now: I'm just going to use the FORMAT option near the bottom on the Main tab, in hopes that it will satisfy the new pool with an actual filesystem. I'm also going to hope that in a future version of unRAID, this process will have recieved some more love, giving the user a smoother experience without them being yelled at