Abbe

I currently have 256TB in a supermicro 4u. 18x16TB with 2 drives for parity. The empty "bottom" six slots are covered with foil to create better airflow. They will soon be filled with more 16TB refurbished ebay drives Edit: Oh, yeah, I have a few of the stickers you see available if you're interested. They're really high quality vinyl. Hit me up :)

Hello one and all. I ordered some vinyl stickers to pimp my server. I realized I got a way better price by ordering quite a few of them, and I thought I could pass on the savings to you guys! I have stickers that read Unraid, Plex, and Tailscale. They're approximately 5 x 1.5 inches. Pack of all three for 10 dollars? Or something? Send me a message on here and we'll set something up. (See image. USB plug for scale)

Thanks for that, worked like a charm! Can't help you with that, I'm afraid :)

Doesn't seem like it's resolved :( I started moving a few thousand files (appr 10TB) to a new location using unraid's own file manager. I remember the dialogue window said "Running" or something, but absolutely nothing was happening. I checked the destination folder, and nothing was appearing. I tried minimizing the dialogue window, and it just disappeared. Now, whenever I try to select a file or groups of files in the file manager, it says "Job running", and won't let me do anything. I have no idea if the process is actually doing anything, or if it has crashed. Do I dare reboot the system in this state? I guess I'm going to let it do it's thing over night and see if there's any change tomorrow. Edit: Oh, yes, the Jobs-button is greyed out for me too Edit 2: I tried a file manager called Krusader, by recommendation from a fellow data hoarder. It moved all the files I wished to move in a matter of a minute or two! Absolutely unbelievable! Highly recommended! :)

My plan is to have the two 2.5" bays in one redundant ssd-pool for containers/system files, and ill add a nvme pcie-card for the cache. But just growing the array without worrying about additional stuff seems absolutely awesome :)

Thanks a lot, stuff like that helps to get a fundamental understanding of the system. So, there is only THE array, and you can make it as big as you like. And there is a advantage og having a cache, as big and fast as possible. My next question is, is two parity drives simply a question of adding security/integrity? Are there performance issues with having 20 data drives and 1 or 2 parity drives? My initial thought was to add drives in chunks of eight, making 6+2 arrays as I going along. But I could instead create a 22 data disk array plus 2 measly parity drives? That would be awesome, as I would get way more data available.

Probably plenty of n00bish questions incoming. I'm hoping some pedagogical person can take his/her time to read this :) I am a complete unraid virgin. I just installed the trial version on my newly acquired server yesterday. It is currently creating an array of my first eight disks. (6+2) I have 24 total slots to fill up eventually, and ten more drives waiting (although eight of those have valuable data on them already from my old NAS. I have only had experiences with customer level NAS in the past.) I took for granted that an "array" was simply like a raid array. You could create one array, select the drives and the redundancy, and then create another. Have several of these arrays, or "volumes". But I am learning that this is not the case. An array, or should I say "THE array" is simply all the drives you want to store long term data, correct? And then, what is a "pool"? I have understood people use it mainly as fast access cache using fast SSD's. Does a pool need to consist of disks NOT in the array, or is it created from disks IN the array? Does a pool have to contain a certain number of whole disks, or can it even be just a small part of a single disk? And what about vdevs..? My foundational question might be "If I want to store a file, I select a [what] to put it in?" If the answer to questions like this is "rtfm", then I apologize. I just feel I need more of a visual mental image of how it's all connected. And I have a feeling that if I just let the build of the array finish, and started tinkering on my own, I would get the hang of it after a while. But, call me anxious... I would like to get a birds eye view early on.