JonathanM

Which server? Pick your favorite? Or the total across all Unraid boxes?

Please continue this discussion in the support thread relevant to your specific container, most likely but not necessarily, check your specific container for where to get support.

Running Unraid in a VM is not supported, but there are a few people who have made it work, there is a forum section for those folks to collaborate. https://forums.unraid.net/forum/46-virtualizing-unraid/

I understand the sentiment, but be aware that Unraid's parity array can only tolerate as many failures as there are parity disks, be that 1 or 2. Any failures on data drives beyond that will result in data loss on all dead drives. Unfortunately drives don't always give a lot of warning before they die, especially when they are rarely used, as can be the case with Unraid's independent disk strategy where often times a disk can stay spun down for weeks at a time. It really sucks to replace a dead drive and have one of the drives you didn't think had any issues die during the rebuild attempt. If you are planning to push the drives through failure... please make sure all important data is constantly backed up away from the server, so drive failures don't take you by surprise at the worst possible moment.

Apparently you have to intercept the switch's DNS to fool it into thinking it's connecting to an authorized server. https://www.howtogeek.com/875829/how-to-join-any-minecraft-server-on-the-nintendo-switch/

Containers are my preference because of better resource sharing, but use whatever you will be most comfortable administering. Either one is similar for security, the heavy lifting needs to be done by your external firewall to keep the smallest number of people possible access. If your friends have static IP's or dynamic within a manageable range, you could write firewall rules to only allow those IP's to pass through to the mc backend.

First, the trash setup doesn't use a rootshare, a term which is used to describe a single share that shows all the normal Unraid shares as folders. Trash recommends only using a single normal Unraid share for your media all the way through the import process, from acquisition to long term storage. That means having your downloads in the same share as your organized media. Unraid shares are simply identically named root folders on each disk, so to move the contents of /mnt/user/tv to /mnt/user/media/tv the most efficient way to do that is directly on each disk one at a time move /mnt/disk1/tv to /mnt/disk1/media/tv. That move would be almost instant, and you would just repeat this action on each disk that contained the root folder /mnt/diskX/tv. Using mc at the Unraid console would be the most efficient way. Just be sure never to mix /mnt/user paths with other paths. For the purposes of this example, stay out of /mnt/user entirely. The trash guides really only have value for someone wishing to utilize torrents to keep copies of what they acquire available for long term seeding, and they force you to give up any security and storage granularity for all those files. I wouldn't bother going through all the hassle just on a whim.

Enforce whitelist, and use your router firewall to block the known minecraft port scanner IP blocks. You could also opt for a nonstandard port, but that means explaining to your friends how to add a :port to the address.

Theoretically you should be able to add a path mapping with the container side pointed to a convenient folder like /backup and the host side pointed to /mnt/user/appdata/sql or something like that, then execute the backup inside the container pointed at /backup and the files should show up in /mnt/user/appdata/sql.

Do you have daily diagnostic emails? Each contains a current drive list, and if your emails aren't already purged you could look there, or any diagnostics zip files, or flash drive backups. (You do keep backups from each time you make major changes to the server, right?)

@scolcipitato? Want another project?🤣 You are doing such good work with folderview, maybe take a quick look and see if it's something you could fold into your view?

Not that I can think of.. Power on hours would be a good benchmark if the drive lived its entire life in the server.

The md part makes sure you keep parity valid, if you alter the sd device you would need to rebuild parity. The Xp1 part designates which disk and partition to target, if you scan sde it will miss the filesystem because it's inside the first partition.

Was the original physical machine UEFI? Maybe use standard BIOS (seaBIOS) in the template.

Not that I can think of, but you can certainly start a container from a script. Disable the auto start for that container on the docker page and script the startup separately. schedule at array start sleep however long you want to wait docker start containername run the rest of your commands.

memtest also checks the memory controller and the data path. It would still be a good test. If it fails you have a smoking gun to investigate, even if it turns out all your RAM sticks are good, the memtest could still fail. Memory timing or voltage in BIOS could be wrong, or just not stable at current values. If memtest passes 24 hours with no errors, then you have another data point to help you diagnose things.

New doesn't mean good. The first thing you need to do with new memory is a memtest.

Click on the folder icon, select edit, move the selected containers inside the edit screen. After you do that, you can drag the folder using the drag arrows.

Best bet would be to post in the support thread for that container.

Are you running VM's?

@ITKBI, stop posting new threads with this exact same content. Attach the diagnostics zip file to your next post in THIS thread if you want help.

Probably not, here are the versions available. https://hub.docker.com/r/linuxserver/unifi-controller/tags

Yep, The only downside is the need to manually manage the space, but it's not that difficult to remember to assign the proper pool to the task at hand. Not recommended. Preclear is really only useful to stress test regular hard drives.

Usually that's a symptom of a power supply issue.

Did you unlock the page?