JonathanM

Make sure the container mount point has RW /slave specified.

Yep. It will have to be repartitioned in the new environment.

It could be useful to have the current date next to the uptime in the information block. Admittedly it would probably seen by few, and nobody that really needed it would actually look at it, but if the effort is low it may be worth it for a quick sanity check. See below for one

Some enclosures mess with the drive geometry. Before doing anything destructive I'd put it back in the original enclosure and try to read it there.

Best option is recover from your backup. For family pictures, you do back up, right?

Not according to the screenshot.

This. These cards are meant to be in a server, where conditioned air is continuously forced over all the card slots. In a desktop machine the cards are left to fend for themselves, which is why practically all video cards have fans.

Not at the moment on the 2.5.X branch, possibly in the future. https://www.netgate.com/blog/pfsense-2-5-0-development-snapshots-now-available.html

Safe is a relative term. The biggest issue would be if they suddenly decided to enforce their TOS, in which case you would either abandon them, or pay the higher price. Like BRIT said, you can set it up so only you can see the content of the data, assuming you don't have the attention of a three letter agency. If you use them as the third tier of a sound backup strategy, you shouldn't have any issues, other than the massive amount of bandwidth needed to get the backup started.

Depends. Are you technically savvy enough to understand what I mean by fixed IP's, DHCP, assigning IP's, etc?

5.0.6 doesn't have diagnostics function, and the syslog isn't very helpful. The only thing that jumped out at me was the IP and gateway aren't in the same subnet. Can you get the IP and gateway from a computer that is currently up and running with internet?

Your symptoms sound like an IP conflict. Try powering off every device with an IP address. Not just shut down, remove power. Then bring your network back up 1 item at a time, starting with the ISP modem, then your router, then the Unraid server, then start with one computer and see if you can manage the server again. If so, start bringing the other devices back online one at a time, and verify things are still working. For wifi devices like phones and tablets, it should be sufficient to disable the wireless when you do the purge. When the wireless is reenabled they should get a new lease from the router.

There is no escaping the need to see the serial numbers on the physical drives at some point. My advice is to label / sharpie / paint pen the last 4 of the serial number on a portion of the drive that is exposed. You can memorialize that elsewhere if you like, the disk location plugin is handy, but at some point you will have to be able to point to the physical drive in question, and the less you have to disturb to get there, the better. Hot swap bays are ideal, because you can get to the drives without touching the cabling, but lacking that, you need a way to ID and replace a drive without tearing apart the whole rig.

I have it natively installed in linux, so not windows only. https://onvinetech.wordpress.com/2016/01/26/49/ Putty installation on mac, no clue if it includes plink, but it probably does since it looks like an adaptation of linux.

Pretty sure the shim is the result of enabling docker host access to custom networks, or something like that.

The putty program includes a command line "plink" that does all that in one line. plink -pw <unraid root password> root@<unraid IP> virsh start <Name of VM>

Unraid installs in RAM, the USB is only used at boot, and to save persistent configuration changes. Running from RAM is WAY faster than running from disk.

The single public share is probably causing windows to see a successful login with default credentials, which then precludes being asked for updated credentials, because windows is stupid. Try setting the public share to private and see how it goes.

What you are seeing is the result of Unraid being unable to mount the USB stick to /boot and continue the startup process correctly. Why that is happening is unclear, but the first thing I would try is to see if your USB will successfully boot in another computer. The array won't start, as none of the drives will be there, but you should be able to get to the web GUI. As long as you don't mess with the drive assignments in the GUI it won't alter anything on the test computer. Do you have a current backup of the USB stick /config folder?

Depends on the source and destination. If the files are just having their paths renamed to the new folder it will be nearly instant. If, however, the destination path is on a different disk, then you are copying and deleting instead of just renaming. Copying and deleting from one disk to another inside the array will be slow, as parity has to be updated for both the source and destination disk, effectively cutting the raw single disk speed by 1/4 or more.

Sure. That's what I do.

Because of the way Unraid is packaged and distributed, I STRONGLY advise against going through all this work to get a p410 running in Unraid. Every time a major update is released, you will have to go through the same work all over again, and hope it still works, otherwise your drives won't show up.

That's another way to accomplish it. Where did I lose you? What I'm proposing is the physical equivalent to temporarily pulling the hard drive out of the pfsense box, putting it into another computer and booting a utility cd to manipulate the partition, then putting the drive back in the pfsense box.

Probably. The easiest way I know to deal with it is set up a new VM with a gparted live iso as the install disk and specify the pfsense vdisk file as the primary drive.

It's worse than that, they actively discourage docker.