-
New setup: pools, shares and SSD
no one else?
-
New setup: pools, shares and SSD
I thought that leaving "media" out of the parity will : 1- preserve (mechanically) the other two disks 2- reduce CPU usage of calculating parity for all "media" data Still, I don't know who to use as cache and how...
-
jorgemarmo started following New setup: pools, shares and SSD
-
New setup: pools, shares and SSD
This is my first time, so please be gentle. I'm setting up a homelab server, I have 3x18Tb HDD, 1x1Tb NVMe, 1x500Gb SATA SSD My plan is to have 2xHDD for photos docs and sensitive data in an array (1 parity, 1 data) Then, 1xHDD for stored media (movies, music, TV shows... *arr + jellyfin) I asked advice for the LLM friends but they gave me different approaches, one told me to put downloaded cache and apps data (dockers, and 1VM for HomeAssistant, and jellyfin data) on the NVMe and use the SSD for caching backups that mover should later put into array... The other one told me to use NVMe for cache and SSD for apps, and then I question it about it and it inverted them, NVMe for apps and SSD for cache... And eventually they hallucinated, I believe, at least partially, due to the change on the mover options settings change from version >6.12? ... here is a scheme: here is a scheme: PARITY └── 18 TB HDD └── parity protection ARRAY (XFS) └── 18 TB HDD [protected sensitive data] ├── photos │ ├── Primary Storage: array │ ├── Secondary Storage: backuppool │ └── Mover Behaviour: Array → Cache │ ├── documents │ ├── Primary Storage: array │ ├── Secondary Storage: backuppool │ └── Mover Behaviour: Array → Cache │ ├── personal_backups │ ├── Primary Storage: array │ ├── Secondary Storage: backuppool │ └── Mover Behaviour: Array → Cache │ └── phone_uploads ├── Primary Storage: array ├── Secondary Storage: backuppool └── Mover Behaviour: Array → Cache MEDIA POOL (XFS) └── 18 TB HDD [unprotected media] ├── movies │ ├── Primary Storage: media │ ├── Secondary Storage: none │ └── Mover Behaviour: no mover │ ├── series │ ├── Primary Storage: media │ ├── Secondary Storage: none │ └── Mover Behaviour: no mover │ ├── music │ ├── Primary Storage: media │ ├── Secondary Storage: none │ └── Mover Behaviour: no mover │ └── downloads_archive ├── Primary Storage: media ├── Secondary Storage: none └── Mover Behaviour: no mover FASTPOOL (ZFS on NVMe 1 TB) └── Samsung 950 EVO NVMe ├── appdata │ ├── Primary Storage: fastpool │ ├── Secondary Storage: backuppool │ └── Mover Behaviour: Cache → Array DISABLED │ ├── system │ ├── Primary Storage: fastpool │ ├── Secondary Storage: none │ └── Mover Behaviour: no mover │ ├── domains │ ├── Primary Storage: fastpool │ ├── Secondary Storage: backuppool │ └── Mover Behaviour: Cache → Array DISABLED │ ├── downloads │ ├── Primary Storage: fastpool │ ├── Secondary Storage: media │ └── Mover Behaviour: Cache → Array │ ├── jellyfin_metadata │ ├── Primary Storage: fastpool │ ├── Secondary Storage: none │ └── Mover Behaviour: no mover │ ├── jellyfin_cache │ ├── Primary Storage: fastpool │ ├── Secondary Storage: none │ └── Mover Behaviour: no mover │ ├── transcodes │ ├── Primary Storage: fastpool │ ├── Secondary Storage: none │ └── Mover Behaviour: cache only │ └── unpacking_temp ├── Primary Storage: fastpool ├── Secondary Storage: none └── Mover Behaviour: cache only BACKUPPOOL (BTRFS on SATA SSD 500 GB) └── Samsung 850 EVO SATA SSD ├── appdata_backup │ ├── Primary Storage: backuppool │ ├── Secondary Storage: array │ └── Mover Behaviour: Cache → Array │ ├── HA_backup │ ├── Primary Storage: backuppool │ ├── Secondary Storage: array │ └── Mover Behaviour: Cache → Array │ ├── VM_backup │ ├── Primary Storage: backuppool │ ├── Secondary Storage: array │ └── Mover Behaviour: Cache → Array │ ├── snapshots │ ├── Primary Storage: backuppool │ ├── Secondary Storage: none │ └── Mover Behaviour: no mover │ └── emergency_restore ├── Primary Storage: backuppool ├── Secondary Storage: none └── Mover Behaviour: no mover could you please advise on the best way to set things up, poolwise, sharewise, filesystemwise. Thank you
-
newbie: 2 drives parity-vs-mirroring ; XFS-vs-ZFS ; apps drive
yes, I'm trying to implement a 3-2-1 including a NAS in the family-in-law's house. does this means that, in this case, the parity disk can be unplugged-plugged somewhere else and read ?
-
newbie: 2 drives parity-vs-mirroring ; XFS-vs-ZFS ; apps drive
Hi, I just assembled and installed unRAID on my home lab server -- Hardware wise I have 5 drives : 1Tb NVMe that I plan to use as cache and mover will move dayly / weekly 500Gb SSD that I plan to use as apps/vm/docker --> plex, Home Assistant, adguardHome, one flavor of homer-heimdall-homepage-homarr, and sonarr 3x 18Tb HDD that I wanted to configure 2x HDD to data sensitive to be protected 1x HDD to store media, mainly my transcoded music and films, also the sonarr downloads that will be read and streamed by the plex srvr -- The use (the way I imagine) : the cache will handle the sonarr downloads and then the downloads should be moved to the media HDD similar to an automated daily backup of the family phone's pics and vids using SMBSync or something similar to specific shares (it's a shame this app is no longer maintained)... these should be moved to the protected drives Home Assistant will run all the time from apps drive the protected data won't be use intensive. and today, I have like 1.2Tb of data to protect so I really believe that 18Tb should get me several years of peace of mind *and I know that "big enough is what she said" also what every person expanding their array/pool once said. . .. I might install a VM or two to play around... probably to run android studio; fusion360.... now, the questions : 1) how do I set up docker and the VM manager to use the apps-SSD for apps data / yet to use the cache to write ? (I guess this will be clearer down the road) 2) about the "protected array" in my vast understanding (joking) is that for only 2 drives, calculate parity makes no sense and that just mirroring (which if I got right might be achieved by a pool instead of the array) gives the same protection, using less resources... so I dig a bit on the wise internet and I found a couple of posts, like this one basically saying that with only 2 drives on the array, unraid will set-up a RAID1 like array, not calculating parity... the posts I found (google found) are "old" so, could someone confirm this and eventually telle me if would it be better to set up an array OR a mirrored pool ? 3) I let the file systems all in "auto" which I believe will use XFS, and this is fine by me, but just for the protected array/pool I wonder if ZFS would be a better pick ? Thank you all in advance for your time, patience and wisdom sharing replies.
jorgemarmo
Members
-
Joined
-
Last visited