theothermatt_b

They said in "Extra Params or something like that" you can just "drop in all the docker CLI stuff" which is helpful if you know exactly what that means. I'm unclear what the docker command line stuff would be, but I believe they're referring to the Extra Parameters section. This section (for this container) already has a few parameters there, in the format: --param=VALUE --secondparam=SECOND_VALUE I have no idea what precisely to put here to add a healthcheck.

I have a docker image (qbittorrent) with a vpn built in that I use. It works great, EXCEPT that every couple of days, the vpn dies. The WebUI still works fine, but you can't curl to any address from the command line, and i get a notice from some sites that i'm no longer seeding. I did some digging on this and found a thing people can add to their docker image called a healthcheck? Sorry if this is obvious, i'm very new to docker and unraid. Basically you'd add something like: healthcheck: test: ["CMD-SHELL", "curl -f http://google.com || exit 1"] interval: 10s timeout: 5s retries: 5 I have no idea how to add that to a docker image i got from the community. Plus, if I add it, will it get wiped out the next time I go into the docker settings and re-apply? Searching here and elsewhere hasn't provided much help. Is this an option for me?

I just found this thread and was having the same issue. I have my docker apps on a custom network created by the command line. All of them seem to work with it fine, but the WebGUI for Photoprism only loads if i change it to Host.

Thank you for all of that! So it sounds like the "you should have been doing this ahead of time" things are: 1) have your flash drive getting backed up routinely either by a plugin or through Unraid Connect 2) backup your appdata folder regularly through a plugin Other than that, the system has fail-safes already in place for most other single-piece-of-hardware failures.

It feels like answers to these questions are in a dozen different places, some older than others and may not apply. I don't want to be scared of hardware failure due to lack of knowledge, so I'd like to just ask about the different scenarios here. Flash drive dies I believe the solution here is to already have a backup of your flash drive, either through Unraid Connect (according to Unraid, this should backup any flash drive changes within a minute or two of them happening, so your backup should ideally be current), through manually backing it up, or through a backup plugin like Appdata Backup (which backs up your flash drive onto your array, although without a working flash drive i'm not sure how you get to the backup... hm.) ' What's the best solution here? Array drive dies Get a new drive of the same size or larger, and let the parity drive rebuild the data. I believe any data on the dead drive is completely inaccessible until you replace the drive. Is this accurate? Parity drive dies I believe you can get to all your data, but it's not "safe" until you get a new parity drive and rebuild it. Accurate? Cache drive dies Assuming you don't have two cache drives in a raid setup, you should be using a backup plugin like Appdata Backup to backup your appdata folder, otherwise you've just lost your appdata folder and with it all or most settings in any docker containers. The docker container settings that you can get to through Unraid are fine, but things like movie collections in plex, or indexer lists in jackett, are all potentially gone. (This is the one that happened to me, that made me want to make this thread) Is this correct? Motherboard dies If you can't (or don't want to) get the same motherboard... can you just plug all your hard drives and flash drive into a new motherboard, and everything will boot up just fine? That seems too simple. I feel like Unraid wouldn't get the drives in the right order or something? What's the solution here?

Same (or at least very similar) here: It was working fine an hour ago (I think?), but after a reboot, i'm getting this.

No absolutely! It made a ton of sense, I just had to dig up how to get around it (which was not hard to do). And it worked perfectly!

Hey I just wanted to pop in here and say thanks for this series of plugins. I used them for the very first time today and (after doing a little bit of reading because the disk already had a filesystem that i had to delete first), it's currently in the middle of an Erase and Clear. Thanks!!

THANK YOU. I navigated to my local server via IP address instead of server name (192.168.1.xxx instead of unraid.home), and it worked instantly!!

Yeah, I can see my server, except it says the last check in was September. The server is online right now, so that's obviously wrong. I wish someone would pop in here with any sort of troubleshooting advice.

I just tried uninstalling and reinstalling the plugin, no dice.

I've been trying out Unraid for almost a month and finally bought "Basic" I tried to connect my server to Unraid Connect and it just sits at the "signing in" screen indefinitely. I've tried it after rebooting and with multiple browsers, still no dice. Anyone have any ideas? unraid-diagnostics-20231101-0824.zip

Yeah wait hold up. I thought I was just not understanding something. It DOES say that everything is connected to the Intel B660 chipset. In fact there aren't any duck duck go results (in english at least) containing "asus" "b660m" and "asm1061" @mgutt is it possible you're thinking of the ASRock B660M? That one mentions ASM1061... EDIT: Looking at the Device Stats screen in Powertop, I do see mention of ASMxxxx stuff, but its ASM1062 and ASM107x. Unclear if that matters.

lol well, awesome... Thanks for the quick replies!

Is ASM1061 on every SATA port on this board? If so, I guess i'd be looking at an add-on card at some point. Also, I believe you on the power supply, but I'm curious how you know that. Is it missing some sort of feature i should have been looking for?