JonathanM

Counterfeit electronics many times work fine, it's just the QC that's non-existent, and since it doesn't have the manufacturers backing there is no real warranty. The people making them don't care how many work or not, as long as some work for a while. Do you have forced ventilation over the heatsink? Those cards get rather warm, and marginal chips can fail when they get too hot.

Either should work, but I used http://localhost:3333. http://127.0.0.1:3333 would be the equivalent if you would rather use IP's.

The deadline was for new purchases of the old type licenses, there is no such deadline for updates to existing legacy licenses.

Got it, I hope. I swear I read the documentation.

Not quite what I meant, see my previous reply, I thought the indexer settings you added to prowlarr were replicated to the arr's. Which would mean the localhost setting that works to hit bitmagnet inside the vpn wouldn't work, because the arr's needed the full IP.

Oh, I misunderstood, I thought the indexers you added to prowlarr were synchronized and updated to the arrs. So the only indexer listed in the arr's is the local prowlarr after you get everything set up?

Redhat doesn't come with an RDP daemon by default. Instead of dealing with that can of worms, I recommend using nomachine.

standard bridge, with proxy settings pointed to the deluge-vpn. OHHH. I need to use localhost. I think. I'll try it and report back. Yep, that was it. Thanks for the hint. However, that brings up another point, I'm gathering that prowlarr sends the tracker info directly to the arr's, which means what is working inside prowlarr isn't going to work in the 'arrs unless I move them inside the vpn. Hmm. This is getting complicated.

Nextcloud is a poor choice, the files are not synchronized between disk and display automatically, you must force a refresh to update the nextcloud database with the new content of the disk.

Ok, I set up prowlarr, added my private trackers no problem, but when I try to add bitmagnet using the address that is working in sonarr and radarr it says "Unable to connect to indexer, please check your DNS settings and ensure IPv6 is working or disabled. Connection timed out (192.168.x.x:3333)"

Since I don't use those, a quick trip to the support on the bitmagnet site provided me with what I needed for adding it directly to sonarr and radarr, but didn't mention RSS, so I left it checked, and just hoped. For anyone playing along at home, just add a torznab, put in your http://ip:3333/torznab and delete the api, and you are good.

The problem with this is people will assume it will work out of the box, when in reality the destination needs to be thought through based on the resources available. 1. it's a safe assumption that you won't want the backup on the same media that is being backed up, so using appdata is out 2. disk numbers aren't guaranteed to exist, and pools can be named almost anything you want except for system reserved names. If a default is used, people assume it should work for most people. Better to make people decide based on their system.

Does it provide an RSS feed? That may be a stupid question, but I didn't see any mention of it, so I suppose not?

No permissions granted.

How are you looking there? If you are connected via SMB, the data folder is hidden. Use mc at the Unraid console, the data folder is there and populated with all the normal postgres database folders.

I guess I should be just a bit more patient. 😁

Given the traffic this is generating, is a VPN advisable? If so, just follow normal redirection stuff?

format creates a blank file system The file system (even totally empty) takes up space on the drive. Think of the hard drive as a room that can hold paper files. If you just toss all the papers on the floor, it would be a bear to find any specific paper. The file system is all the filing cabinets, the folders inside, the card catalog with all the cross reference information to locate any specific piece of paper. Different file systems use different arrangements to keep track of the files, some file systems specialize in speed of access, others on file integrity, etc. When you format a drive, it sets up all the structures needed to manage and index the files. That takes up a non-insignificant amount of room on the drive, before any files are even written. Clearing removes ALL that information. Parity emulates raw bits, it has no idea what files are, what file system you formatted, or anything.

As long as NOTHING is changed on the disk, that is true. If you format the disk BEFORE you add it to the array, the clear status is gone, and Unraid will need to clear it again before adding it. Your question about file systems made me think I needed to clarify. Clearing removes all file system information. Formatting to add a filesystem must happen after the drive is fully added to the array, so the format can be included in parity.

Where's your company uniform? Suit jackets look so out of place here! 🤣

Have you done this? https://docs.unraid.net/unraid-os/manual/vm/vm-support/#enable-msi-for-interrupts-to-fix-hdmi-audio-support I know it's listed as a fix for HDMI audio, but maybe some of the principles apply. Wouldn't hurt to go through the rest of the page as well.

Depending on how much risk you want to expose yourself, you could do one parity at a time, that way you will always have valid parity if a data disk fails. Preclear is totally optional, it won't speed things up, but it will test the new drives for infant mortality. When you get to the point of adding old parity drives to data slots, be sure to make new backups and delete all your old flash drive backups, or mark them in some way so you never try to use them. If you accidentally use a backup that has your old layout, the first thing Unraid will do is overwrite your data drives that were parity.

Examine the syslinux section under main, flash and see what's different between gui and cli mode.

Have you tried safe mode?

I recommend testing all your gadgets for functionality without internet connectivity. Obviously the cloud based services won't function, but it would suck to set something up and not be able to manually control it if needed. Lighting, climate control and other critical stuff shouldn't need internet for basic functionality, if they do, you will find yourself in a bind at the worst possible time. If I can't make a gadget work the way I need on a VLAN with no internet, it's not going in my house.