Building Zion [ 56k warning ]

catsay · October 8, 2017, 8:17pm

Most likely a issue with that DIMM. At least it was a correctable error CE rather than uncorrectable UE,
It’s a good thing you switched the DIMM and narrowed it down to that, if it was the Memory controller channel that would have been a lot worse.

SudoSaibot · October 9, 2017, 12:09am

@oO.o I used the zfs-dkms 0.6.5.9 repo package and it does not have encryption. ZFS Encryption was added to 0.7.1 in August but debian is behind until a “stable” release.

github.com/Conan-Kudo/zfs

Native Encryption for ZFS on Linux

This change incorporates three major pieces:

The first change is a keystore that manages wrapping
and encryption keys for encrypted datasets. These
commands mostly involve manipulating the new
DSL Crypto Key ZAP Objects that live in the MOS. Each
encrypted dataset has its own DSL Crypto Key that is
protected with a user's key. This level of indirection
allows users to change their keys without re-encrypting
their entire datasets. The change implements the new
subcommands "zfs load-key", "zfs unload-key" and
"zfs change-key" which allow the user to manage their
encryption keys and settings. In addition, several new
flags and properties have been added to allow dataset
creation and to make mounting and unmounting more
convenient.

The second piece of this patch provides the ability to
encrypt, decyrpt, and authenticate protected datasets.
Each object set maintains a Merkel tree of Message
Authentication Codes that protect the lower layers,
similarly to how checksums are maintained. This part
impacts the zio layer, which handles the actual
encryption and generation of MACs, as well as the ARC
and DMU, which need to be able to handle encrypted
buffers and protected data.

The last addition is the ability to do raw, encrypted
sends and receives. The idea here is to send raw
encrypted and compressed data and receive it exactly
as is on a backup system. This means that the dataset
on the receiving system is protected using the same
user key that is in use on the sending side. By doing
so, datasets can be efficiently backed up to an
untrusted system without fear of data being
compromised.

Reviewed by: Matthew Ahrens <[email protected]>
Reviewed-by: Brian Behlendorf <[email protected]>
Reviewed-by: Jorgen Lundman <[email protected]>
Signed-off-by: Tom Caputi <[email protected]>
Closes #494
Closes #5769

by tcaputi on 05:36PM - 14 Aug 17

changed 162 files with 16105 additions and 1200 deletions.

@PhaseLockedLoop After using Emby for a while I decided to switch to Plex. Emby is written in C# for windows, but cross compiles with mono which makes it a heavy application imo. Emby seemed more customizable and seeking shows was much faster and responsive. Seeking in Plex seems sluggish or non existent, but that may be my config.

The emby developers also implemented some horrendous nagware which can be circumvented with some help from an AUR package.

https://aur.archlinux.org/packages/emby-server-unlocked/

SudoSaibot · December 23, 2017, 11:56pm

Months later…

Been too busy to finish the server. Finally have a bit of time to wrap it up. Wanted to buy a hotswap cage but I’m too cheap so I used some extra internal drive bays and made some janky brackets to hold it in place. Job done.

SudoSaibot · March 25, 2018, 9:57pm

Something to keep the dust out. Built a filter box and cut apart a $2 furnace filter. Sealed the case except the front and rear, Then only put fans up top behind the filter pressurizing the case. Working well after 3 months.

Also giving Syncthing a shot, for synchronizing our phones photos to the server for local access and backup.