JonathanM

Currently custom networks are only kept in the image, so yes, you will need to redo the custom networks BEFORE you restore the Previous Apps that are looking for them. Custom variables should be in the templates, and so should container specific changes. If, however, you don't have the apps set up properly so all their appdata is stored external to the image, you will lose those settings. Docker containers are supposed to be set up so all customization is done to mapped paths outside the image.

The little rubber band drive belt is getting old and hard. When not used, it takes a set, and forcing it to a slightly different position with the manual open lets it get a grip on a different piece of rubber, then after a few cycles, the same hard curved bit settles around the drive pulley and it just slips again.

Do you have a recent backup of your boot USB? I'm not seeing anything except a failure to read the USB, suggesting it may be failing.

As the message says, "Post your diagnostics in the forum for help"

What does it show if you plug it back directly to a sata port? Some USB docks don't pass the drive through properly.

If you are ok with losing the data on it you could use the diskspeed container.

AFAIK yes, as soon as you mount one, the rest will mount along with it.

That's a very old SSD, are you sure it's healthy?

Try cutting back the memory to 8GB and the CPU to a single core and see how it performs.

Yes, but the drive doesn't have to be precleared, that's only useful to determine if the drive is healthy, and it doesn't have to be in the same slot on the same controller. Unraid tracks drives by serial number regardless of port or controller. You will need to select the new drive in the parity slot dropdown where it will show the removed drive as missing.

Except for this part, sounds fine. I'm not parsing what you are trying to say here. In general, new config allows you to assign any drive to any logical slot, and drives assigned to parity slots will be totally overwritten, drives assigned to data slots will mount and be usable if they are recognized as having a valid formatted partition. Unrecognized drives in data slots will have the option to format them, regardless of content. Sometimes previously valid drives will not be recognized until you manually set the desired format type in the disk slot settings. So bottom line, as long as you don't put a drive with data you want to keep in a parity slot, you should be fine. No need to rebuild the removed drive if you don't need the data in that slot.

cache : no means mover doesn't move anything. Click on the question mark at the top right of the GUI to toggle the help text, it explains what the different settings do. stopping the containers and the VM's isn't enough, you need to disable the docker and vm services in settings, you will know you got it right when the GUI tabs for docker and vm's are completely gone from the GUI page. Theoretically if your current cache pool is a healthy BTRFS redundant array you could swap the drives out one at a time, but I've seen people lose data trying it. @JorgeB could tell you if that should work in your situation if you attach diagnostics to your next post in this thread.

I threw together a little script that if run at array start should fire a GUI notification when a ping to 1.1.1.1 fails. YMMV, no warranties, this is worth exactly what you paid for it. If someone sees something wrong with this, please say something. I can't really test it right now. If run at array start using user scripts plugin, it should ping that address every minute, until the ping fails, then it fires a warning and exits, waiting for you to stop and start the array.

If it doesn't have internet access how could it notify you?

I don't believe the motherboard in that unit would run Unraid, it came with 1GB, and I don't believe it's officially upgradeable, and even unofficially it seems the max is 2GB. Unraid needs minimum 4GB, it's happier with 8 or more.

This is not an Unraid question, so I moved it to the lounge. If you can connect when you are inside the LAN, but not when you are outside, that means the port forwarding is NOT correct.

Think of disk format like a filing cabinet system with card catalog. Even when it's totally empty, all the organizational structures still take up space, and the more features supported by the file system, the more space it occupies even when empty of file contents.

You can do the parity drives one at a time to maintain redundancy.

Could be multiple issues. How is the enclosure communicating with the motherboard? If it's not SAS, that's an issue. Writing to the array while parity is being built will slow things down considerably as well. Does the parity build speed up if you pause the writes? Diagnostics could hold some clues.

What IP address does the Unraid box get from the shared port? Can you successfully use the shared connection with a different computer?

It works on some hardware combinations.

Why? Those settings are rather hard on the battery. Much better for the equipment to start the shutdown as soon as it's obvious the power isn't returning, in my area if the power is out more than a minute or so, it's probably going to be out for much longer. I'd recommend starting the shutdown 5 to 10 minutes after power is gone at most. That way if power does come back on relatively soon, you have enough battery left for another shutdown if the returning power wasn't stable. Keep in mind that recharge rates are rather slow, typically about 10 to 20 times the time on battery. So if you run 20 minutes on battery, it's probably going to be several hours before the battery is full again. SLA batteries don't like to be discharged below 50%, it reduces their usable life dramatically. I'm betting your battery(s) are end of life. To properly test your UPS system, you need a way to cut the power to the UPS without breaking the ground connection, so switching the power without unplugging it, a load comparable to the server, like 140W of heat or incandescent lightbulbs, and a steady power source for the server. Leave the communication from the UPS to the server connected, turn off the power to the UPS, and observe the UPS connected dummy load and the shutdown behaviour of the server. Hopefully the server shuts down properly before the UPS dies. Obviously the server needs power from a steady source not associated with the UPS or it's switched circuit.

Attach diagnostics zip file to your next post in this thread. Sounds like a power delivery problem. Either PSU too small, or wiring / connections.

Probably not new, RMA replacements are typically inspected and reprogrammed returns, so you very well may have inherited someone else's issues. I'd RMA again and see if you get a better result.

Check again in a day or so, sometimes it takes a bit.