From 695614902ba24f14e06a42982c62132d3b5015d4 Mon Sep 17 00:00:00 2001 From: Jan Tuomi Date: Fri, 2 Jan 2026 15:33:34 +0200 Subject: Use figures instead of plain images --- content/posts/home-server-part-3.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'content/posts/home-server-part-3.md') diff --git a/content/posts/home-server-part-3.md b/content/posts/home-server-part-3.md index cad17a6..b650d0f 100644 --- a/content/posts/home-server-part-3.md +++ b/content/posts/home-server-part-3.md @@ -31,13 +31,13 @@ The initial idea is this: Using the install wizard, I set up the system following my rough plan. And here we go, all up and running: -![Fastfetch output showing the machine specs. Disregard the uptime (I took the screenshot way later)](/files/pursotin_fastfetch.png) +{{ fig(src="/files/pursotin_fastfetch.png", alt="Fastfetch output showing the machine specs. Disregard the uptime (I took the screenshot way later)") }} ### RAIDZ You might notice that I bought 4 x 1 TB of NVMe disks, but `fastfetch` is only showing ~2TB. That's because I set up the disks into a "RAID 1+0" configuration: -![A "RAID 1+0" configuration](/files/pursotin_raidz.svg) +{{ fig(src="/files/pursotin_raidz.svg", alt="A "RAID 1+0" configuration") }} RAID 1+0 is a combination of two RAID levels. RAID 1, or _mirror_, consumes two disks to produce one virtual disk that has the capacity of only one physical disk but can withstand the loss of either one. ZFS can automatically heal missing data in a member of a mirror by copying it over from the healthy member. RAID 0, or _stripe_, consumes two disks to produce a disk that has the capacity of the sum of its member capacities as well as double I/O speed, but fails if either member disk fails. The combination of these is a useful way to get increased speed and increased durability at the price of half your raw capacity. -- cgit v1.3