-
[Plugin] Mover Tuning
Is there an eli5 for this plugin, because I'm not understanding parts of it. In the attached image, I have the description/help box showing for each of the "Mover Tuning - Filters," but the first line in each one just seems like a jumble of words that sort of make sense, but I can't figure out what exactly they each do.
-
[Plugin] Appdata Cleanup Plus
I am really confused by this plugin. I just want to delete the jellyfin stuff that it's showing. the old one I just clicked the checkbox and deleted it. That's all I need to do, but I can't even find a delete button in this thing.
-
Why did the 7.3.0 update come up with Onboarding when booted?
Awesome. Thanks. Good to know.
-
Why did the 7.3.0 update come up with Onboarding when booted?
I'm pretty new to Unraid, having built my system in December. Prior to today, I had only done one OS update to 7.2.5, and after that update, the system just booted, I logged and and continued on. Today, I update to 7.3.0, and upon booting, it comes up with an onboarding thing that I don't even remember from my initial building of the system, and certainly didn't get it last week when I update to 7.2.5. It really freaked me out for a moment because I was afraid I had just royally f*cked something up and killed my nas. Thankfully, just selecting skip was all I needed to do, but good lord did that freak me out. Why did it do that, and why this update and not 7.2.5?
-
Unable to access WebUI. Made no changes.
Awesome. That is most useful. I'll look into the Innodisk for sure.
-
Unable to access WebUI. Made no changes.
Any idea of the quality of the nand used on the 64Gb emmc in Steam Decks? Is it the same lower quality nand used in most flash drives, or does it have similar wear tolerance to regular ssd's? I've been trying to find a good use for it since I replaced it with a 256Gb ssd.
-
Unable to access WebUI. Made no changes.
I guess I don't get why they aren't always on and running continuously by default. You never know when or what is going to happen, and if you only run logs after something happened, how is that going to help you?
-
Unable to access WebUI. Made no changes.
So, don't write to the boot drive if it's a flash drive, which mine is. I don't have a reliable enough remote location, or even a reliable enough network, to go remote. I'm left with local, and since the whole reason I'm at this point, is because I lost access to any shares, using cache/share isn't a good idea. Now I'm just back to USB, only external this time, and since a flash drive isn't recommended, I have to use an external SSD, which just sound like overkill. Maybe I'm missing something here, but is writing the logs to the drive really that bad that i'll kill a flash drive that fast, because otherwise, I don't see a good option for those of us on a shoestring budget.
-
Unable to access WebUI. Made no changes.
It's working. Trying to figure out what happened though.
-
garfnodie started following Unable to access WebUI. Made no changes.
-
Unable to access WebUI. Made no changes.
Checked my docker containers as I know had a few set to autostart, but only one, binhex-jackett, is running. None of them have autostart turned on anymore, even binhex-jackett that did start.
-
Unable to access WebUI. Made no changes.
Here is the diagnostic file.davids-server-diagnostics-20260428-1503.zip
-
Unable to access WebUI. Made no changes.
Way ahead of you on that. Here's (001) what I had when I first plugged in the kb and monitor, last line is just me hitting escape to see if kb is working. I had to rearrange a couple of things, and when I turned back to my screen, it looked like it finished starting up. A little surprised, I checked Chrome, and still not webui. I login as root on the CLI, check chrome again, still not webui. Still confused, but I manually initial a reboot using the cli, but it hangs on this (003) and even I knew I was just going to have to do a hard power down at this point. It's back up and running now, webui is working, shares are all accessible over the network, and parity check is running. I did record the boot up as best I could with my phone, and I can post it to YT and share if you really want, though I suspect some log snooping might be more useful, if you're willing to help me. I'm assuming I should get ssh running too, if you could point me to the proper guide, I'll get that done asap. Something similar has happened once before, but it was not too long after I built it, so I just chalked it up to being an Unraid noob.
-
Unable to access WebUI. Made no changes.
I'm on my Mac, just started transferring some files to my NAS's SMB shares using Finder. I switch back to the other workspace that has my browser (Chrome), and it happens to be on the tab that is the Unraid WebUI. I never even did anything in the WebUI, but it just auto reloaded on it's own, and I haven't been able to access the webui since. My file transfers continued just fine, and I was still able to access all my shares, and plex still worked, just couldn't get to Unraid's own webui. Restarted my Mac, and now I can't access me shares, still can't get to the Unraid webui, but plex is still running just fine. I never setup ssh, didn't' know I needed to, and pressing the power button doesn't shutdown. I'm trying to avoid a hard shutdown with a long press of the power button, as I do know that works. I made no changes to anything, not my mac, not my network, not my router settings, nothing on unraid. Nothing. I had literally just got up, did some organizing of my recent downloads and just started dumping them to the NAS. I do use a commercial VPN, Proton in this case, but it's caused no issues in the past, but even so, I still turned it off, but still can't access the Unraid webui. edit: ended up doing a hard shutdown, and it's back up and runningnow. Trying to understand what happened and why though.
-
.fuse_hidden[nnnnn...] files being created, can't delete directory
Thirteen years later, and this still works. I was about to pull my hair out over two fuse files.
-
Support for [laromicas] ROMVault docker container
This worked for me. I couldn't even get RomVault to run for the first time after installing it, but I could see that it did create the directory inside appdata, so I just used the file manager built right into Unraid's webgui, and changed the permissions of the romvault volder to Nobody. Container started right up first try after changing the folder permissions.
garfnodie
Members
-
Joined
-
Last visited