Leaderboard

Hi, guys, this is a three-part video series on building a 10 core server from start to finish. The server is based off an x-99 platform with a Xeon CPU. These videos follow what I did to make a complete server running unRAID. This includes building the hardware. Setting the bios. Creating the unRAID USB. Preclearing the disks, setting up the array, installing various plugins and tools. Installing media containers such as emby, sonarr radarr and some download clients then a couple of VMs. Hope some of you new guys to unRAID may find it interesting. Part 1 is hardware setup and build. Part 2 is unRAID instalation and configuration. Part 3 is Docker container and VM configuration and testing.

@jonp Here's the problem. Posts that work: ones that directly reference a particular message within a post: https://forums.lime-technology.com/topic/59916-in-post-links-that-refer-back-to-the-forum-dont-format-properly-or-even-work/?tab=comments#comment-589663 Posts that don't display correctly are ones that refer to the OP, without referencing a comment number (which should be perfectly correct, since the URL of the OP by default doesn't include the comment number https://forums.lime-technology.com/topic/59916-in-post-links-that-refer-back-to-the-forum-dont-format-properly-or-even-work/ @everyone If you want to refer to a particular thread, instead of grabbing the default URL, click the "Posted 7 hours ago" of the OP which will then give the full URL for the lead post. PITA IE: https://forums.lime-technology.com/topic/59916-in-post-links-that-refer-back-to-the-forum-dont-format-properly-or-even-work/?tab=comments#comment-588110

If for example your host machine has the following directory structure: / home/ downloads/ tmp/ other/ And the docker container has the following internal structure: / download/ tmp/ app/ When you map your directories during the creation process ("-v /home/downloads:/download"), you do this: / / home/ downloads/ <-------------------> download/ tmp/ tmp/ other/ app/ That link (or, mapping) effectively means your "/home/downloads" directory is the "/download" directory inside the container. They get overlaid, meaning they are effectively now the same directory. This is an important concept to understand because any files placed in the "/download" directory are immediately visible to the host, via "/home/downloads", and vice versa. In order to access the files (or in this case, download them) you must specify "/download" so the files are visible in your "/home/downloads" directory. If you specify root "/", all that will happen is files will be downloaded internally in the container (and will fail due to permission errors). What you are describing is a fundamental misunderstanding of how docker overlays its directories when you map them. By mapping these directories together, you are not saying that the internal root directory ("/") is now your "/home/downloads" folder. If you want, feel free to map root "/" and see what happens (I definitely do not recommend this though). In the case of Davos, no the download location does not imply "/download" because it was designed to be flexible when running outside of docker. The path is ABSOLUTE, meaning you must specify the whole path, from root. If you do not do this, it will attempt to find the path relative to where the application is running, which is the "/app" directory. TL;DR: Use "/download" when specifying the local directory for davos to download to. It will not work with any other directory when running inside a container. It is by design, and will not change.

Let's use our manners please. Offending posts moved to the Bilge.

Just an annoyance that I would like mdcmd to not by default log all the spindowns it does as a normal course of action. I fully expect in my system that drives spin up and down at any given point in time depending upon what is going on with the network, but I don't want to see in my syslog all the spindowns.

Once you remove the spare disk, and start the array, you should be able to see the content of the failed disk being emulated. If not, do not proceed with the rebuild. Something is wrong. Do no array writes! Fix the problem and start again. If it is emulated and there are critical files on that disk, I'd suggest copying the data off to a workstation while everything is working. You could actually copy the entire disk, file by file, over the network or to an unassigned devices in this manner and never need to rebuild. The advantage is that as each file is copied, it is safe. When doing a rebuild, the entire disk has to be rebuilt in order to recover all your files. If it fails half way through, you have a jumbled mess and no idea what is valid and what is not. I actually like this method better, especially if the diskr in the array are "fragile" (SMART errors, old, been through a flood , etc.) You are doing everything right including asking the right questions here. Too often people try to recover in the heat of a stressful situation and make things worse. Congrats for keeping a cool head. You're not home free yet though. Good luck!!

@Cursewords This is a community forum. None of us work for Limetech, except 3 people, and they are clearly identified. Not even the moderators like me work for the company nor are compensated. @Lev is just a member. I waa surprised by @Lev's post and one first read thought it was tongue in cheek, but maybe it is not. It is not a normal type of response. And he is a relatively new face here. I have deleted your second extremely inflammatory post. You can be upset with Lev but we won't allow wars to occur within the forums. We are a friendly and helpful forum, and such drama is not going to be tolerated. I will discuss with the other moderators and additional deletes or edits may occur. We typically do not intervene in minor tit for tat,, as there are so few cases of bad manners here. But clearly this is going well beyond. @Lev - please edit your post to remove offensive aspects. You start on a high note, complimentary of the post, and providing useful info, but it degrades. Whether tongue in cheek or not, it has offended another member. Thank you. Migrating from one NAS to another on the same server is risky, as myself and @tdallen tried to explain. But your approach of backing everything up for migration would work. You just might have some downtime. Often people have older computers they can leverage in such a migration. But just backing up your Freenas and bringing up unRaid would not be my first suggestion. And it had nothing to do with the power of your server. Your decision to migrate is your own. I would not let one post from one person affect your decision. It would be like going to Target, meeting an.offensive customer, and then never shopping there again. If you've monitored the forums for any time at all you realize that this is not the norm. please take the time to re-read and respond to the constructive posts, and let's continue the conversation. You'll be the bigger man.

@Cursewords Lev is only a volunteer trying to help, like we all are. We are mostly a drama free area. This post is not normal either from you or from @Lev But you might have to dig a little deeper to find the gold here.... All the best...

IOMMU related call traces: Sep 16 21:04:50 Tower2 kernel: WARNING: CPU: 4 PID: 1 at drivers/iommu/intel-iommu.c:2656 domain_prepare_identity_map+0xb9/0x15a Sep 16 21:04:50 Tower2 kernel: Your BIOS is broken; RMRR ends before it starts! Possibly harmless but look for a bios update or they might be issues with VT-d enable.

You need to format your disks first, next to the start array button.

Most of it goes automatic. When the Docker service is started it will scan all available network connections and build a list of custom networks for those connections which have valid IP settings. When creating/editing a Docker container the custom network(s) are automatically available in the dropdown list for network type. Choose here a custom network and optionally set a fixed IP address otherwise a dynamic address is assigned (you can set the range for dynamic assignments under Docker settings and avoid conflicts with the 'regular' DHCP server).

Just to be realistic, that's almost impossibly limiting. Two reasons - one, you really ought to play around with unRAID before you make the commitment to move over. Two, assuming you want to retain your existing data you'll need a transition strategy. unRAID won't allow you simply plug your ZFS formatted drive pool into the unRAID storage array, you need to plan a migration. With regard to almost everything else, unRAID sounds like it will meet your needs but I would recommend getting hands on with it before you start dismantling your FreeNAS server.

For information. What I've done: 1) I moved HP SC44Ge to another computer (there was an error "Failed to initialize PAL" on my PC, googled this error, there is problem with my MB) 2) Created DOS-USB key, added to key soft for rewriting version 1.26 and copies of old FW & BIOS 3) Boot from DOS 4) Erase FW and BIOS by "sasflash -o -e 6" 5) Rewrite with my FW & BIOS. Everything was well 6) Rewrite with more fresh FW & BIOS. No problem!