summaryrefslogtreecommitdiff
path: root/content/blog/2022
diff options
context:
space:
mode:
authormms <michal@sapka.me>2023-12-29 23:39:26 +0100
committermms <michal@sapka.me>2023-12-29 23:39:26 +0100
commit339ba0bf872a672fea7d611343df4a6f0e14d585 (patch)
treea76e605040f987947ddf5fe31ca9806fd7f7e61a /content/blog/2022
parent4c6ed817fb1ac3f1585f8fe19376e722a3f994c7 (diff)
feat: move most of 2022 into new locations
Diffstat (limited to 'content/blog/2022')
-rw-r--r--content/blog/2022/repartitioning.md81
1 files changed, 81 insertions, 0 deletions
diff --git a/content/blog/2022/repartitioning.md b/content/blog/2022/repartitioning.md
new file mode 100644
index 0000000..e3e9dc5
--- /dev/null
+++ b/content/blog/2022/repartitioning.md
@@ -0,0 +1,81 @@
+---
+date: 2022-05-07T10:15:00+02:00
+draft: false
+category: blog
+year: 2022
+title: Repartitioning the home server
+abstract: How I rethought and repartitioned my server.
+---
+I have owned Synology 920+ for some two years. Unfortunately, when I first got it, I made some assumptions that are no longer true and therefore this NAS is basically a glorofied Plex machine. A bad one, as the CPU is not powerful for any modern codec transcoding. Time to fix it!
+
+## Durandal
+
+The server (named Durandal) had all drives in Synology Hybrid Raid (SHR) configuration until recenly. When I first bought the device, I got three WD-RED 4 TB drives, which left one bay empty. Soon, the occupied space filled the three drives, and I expanded it with 6 TB - as SHR allows for mixing drive size. In adition, SHR1 allows for one drive failure.
+The configuration looked like:
+
+```
+ HDD1 HDD2 HDD3 HDD4
+ -------- -------- -------- ------------
+ | | | | | | | |
+ | WD-RED | | WD-RED | | WD-RED | | WD-RED |
+ | 4 TB | | 4 TB | | 4 TB | | 6 TB |
+ | | | | | | | |
+ -------- -------- -------- ------------
+| |
+ ---------------------------------------------------
+ Volume 1 (SHR1)
+ 9.6 TB
+```
+
+This setup has the drawback of not allowing as much storage as required, and storing movie backups on volume with redundancy is an overkill.
+
+
+## Vulcan
+
+A few days ago, I rethought the current assumption, and the new ones are:
+
+- I want to host application on the NAS
+- I want to host my photographs (no more iCloud subscription)
+- I want to store multimedia, but I don't care if I lose it.
+
+This led to a new architecture based on two volumes:
+
+
+```
+ HDD1 HDD2 HDD3 HDD4
+ -------- -------- -------- ------------
+ | | | | | | | |
+ | WD-RED | | WD-RED | | WD-RED | | WD-RED |
+ | 4 TB | | 4 TB | | 4 TB | | 6 TB |
+ | | | | | | | |
+ -------- -------- -------- ------------
+
+ CACHE1 CACHE2
+ -------- --------
+ | Samsung| | Samsung|
+ | 256 GB | | 256 GB |
+ -------- --------
+| | | |
+ ------------------------ ---------------------------
+ Volume 1 (SHR1) Volume 2 (RAID0)
+ 3.5 TB 8.7 TB
+
+```
+
+Now I have a clear distinction between space for important stuff and for stuff I can recreate with ease. Having 3.5 TB is overkill here, as the drives will sooner fail than I will be able to fill them - currently, I store 520 GB in iCloud... and I pay for 2 TB as there is nothing in between. Having two 2 TB drives there would be much more economical
+
+The total capacity is also significantly higher now. There will be things I'll want to secure that are on Volume 2, but since it won't be anything mission-critical, I can just use a USB Drive for this.
+
+## The future
+
+Since the server is ready, I think I'll strive for:
+
+- adding new offsite backup (or 2) for Volume 1,
+- leaving Plex (temporarily I use Samba shares),
+- adding proper photo storage,
+- adding a music server,
+- adding DNS server,
+- moving this site,
+- moving my XMPP server,
+- adding a VPN server,
+- adding backup power for the NAS, modem, and router.