JonathanM

Yes, and those can cause issues as well. The bent spring to pad connection is just a very poor design, it's usually fine when first inserted, but doesn't hold up in the long term. The issue is that current flowing through a tiny contact patch causes heat, heat changes the metal and makes it brittle and rigid instead of springy, heat also promotes corrosion, which means that even a tiny shift caused by vibration or disturbance can cause the resistance to go up, making even more heat when current flows. Even with the best materials possible it's not a great design, add cheap manufacturing and substitution of inferior metals to the mix, and it's terrible. There is a reason so many drives start having issues out of the blue when their internal media smart reports are perfectly fine, SATA connections are just junk. The fewer of that type of connection you have, the better. Ideally there is only one SATA connection per drive, the one directly connected. 4 pin molex style aren't perfect, but they are MUCH better than SATA style for transmitting power and staying connected under stress. SATA connectors are adequate for single drive current, splitters are just asking for trouble.

The problem is the SATA power connector is so poorly designed that any such adapter is likely to cause as many issues as it solves.

What path did you point radarr to?

@SpencerJ should be able to help.

Have you tried typing in the path instead of trying to browse there?

Yes. Run the xfs repair on Unraid, which is what you should have done in the first place. Yes, it is. The filesystem is corrupt and needs to be repaired. Parity emulates the entire drive, no matter what filesystem or corruption is there. Parity has no concept of files or filesystems, just the raw bits. That's correct, it's emulating the filesystem exactly as it was on the drive, in need of repair. Trurl & Squid already tried to tell you all this, so I don't know if my attempt at saying the same thing in different words is going to get through or not. Now that you have removed the drive, the emulated filesystem doesn't match the physical drive, so you need to do the filesystem repair on the emulated drive, and when the emulated drive is mountable, then you can rebuild the physical drive to match the emulated one in Unraid. I'll try restating all this again more succinctly. Unmountable means the filesystem is corrupt or missing, and requires XFS or whichever filesystem is in use to be repaired. Disabled means a write to the physical drive failed, which means the parity emulated drive is no longer in sync with the physical drive. That requires rebuilding parity or the drive to get the two back in sync. Normally when a drive is disabled you need to figure out why the write failed, sometimes it's a connection, sometimes the drive is actually dying, in your case you disabled the drive on purpose by removing it and then starting the array with it missing. Unmountable and Disabled are two distinct problems with different solutions. In your first post you described an unmountable disk which needed a file system repair. The drive was not disabled until you disabled it. The file system corruption was likely the result of a bad connection or bad cable, which will need to be addressed or the resynchronization of the emulated drive to the physical drive will probably fail.

Totally optional, no need to enable this if you don't want the added functionality. It is if you want it to be. The core functions for sharing files have no reliance on an internet connection when using a paid license. It's only when you want to add third party applications that you need internet.

Unraid doesn't write its own virtual machine implementation, it uses the KVM engine. So, when it's available there, you can be reasonably sure that Unraid will support it.

Sure, you can add, remove, rearrange, whatever. If the drive hasn't previously been formatted as an Unraid data drive you will be prompted to format it after you start the array. Just be very sure the format list only includes drives you intend to format, unfortunately Unraid will format ALL unmountable drives at once, so if for some reason a previously good data drive happens to be unmountable for whatever reason, it will get formatted as well, instead of offering you the correct option to fix the filesystem.

That assumes a single user only unless I missed something. How would you go about it if you have many friends and family members each with their own vault?

No limit.

Probably BIOS setting is wrong.

Respectfully, where are you getting this from? Everything I've read says you can continue to manually upgrade your Unraid with your existing key by extracting the files from the installation and overwriting the bz archives on the flash drive. No need to have internet access on your server or link it to your forum account.

How would you recommend subdividing them?

You forgot 1.a. Stop VM's. 1.b. Close SSH sessions if any All of these items are theoretically handled by the stock Unraid shutdown, but it's not always foolproof, and it's much easier to work through an orderly shutdown than to deal with a hang and possible unclean shutdown.

The terms to google are nat reflection hairpinning nat loopback along with your specific router.

Why not? With the proper settings in your router it should work just fine.

Maybe, but I only remember seeing one person attempt it. With 3 ports, IF you can pass the hardware for 2 of the ports through cleanly, IF the hardware is supported by pfSense, then it's doable with a full Unraid license. I personally run a pfSense VM with my 2 motherboard 1Gb ports passed through, and Unraid has exclusive use of a 10Gb PCIe card. The 10GB and the LAN 1GB for pfSense are plugged in to the same switch, and the 1GB WAN goes to the modem. It's definitely NOT possible with a trial version of Unraid, because the trial version requires internet access to start the array and VM's. IIRC @Ford Prefect was trying to help someone with the 2 nic setup, but I don't know if it ever got running. I'm not familiar enough with other hypervisors to comment on the feasibility of doing it with other software.

Trust me, we know exactly how you feel. Thank you for taking the time to deal with this.

What you are asking to do is VERY advanced, and not easy to implement and troubleshoot.

This thread is about wireless, not ethernet.

You may now hold the record for oldest thread necro. I suggest creating a new post in the current general support section with more detail about what you have tried and any errors you are seeing, this thread is not a good place to discuss current issues since virtually everything has changed in 10 years.

You can still download the zip file and copy it to your Unraid boot USB with another machine. https://unraid.net/download

One at a time is safer, since they operate totally independent of each other. Takes twice as long, but definitely safer.

If the container has its own ip address, all ports on that address are open, no need to map ports, just change the port in the application itself. In bridge, the container shares the hosts IP, so only mapped ports are available, and you can map container ports to any port that's available on the host IP. Mapping doesn't apply to anything but bridge modes.