Most computer new computer hardware that will fail quickly, will fail within the first month of usage, if not sooner.

Given that, it's recommended to do a burn-in test for any new computer hardware, including hard drives.

I've been using a disk burn-in test to stress test hard drives as I've been replacing them in my …

I was looking at drive utilization, and thought that my /mnt/docker/ directory was a bit bigger than I thought it should have been, so I started doing some some digging.

I found that I had a rather large log file from my Gitlab Docker container.

ls -lh *-json.log
-rw-r----- 1 root root 13G Jan 22 13:42 …

I run some Docker containers on my NAS, but ran into a hard drive space issue because of Docker:

sudo du -sh /var/lib/docker
30G	/var/lib/docker

My NAS has a 110Gb SSD for the OS (Ubuntu Server) and 4 drives in a ZFS array for storage.

By default, Docker runs everything from /var/lib/docker, but without doing some …

I was having some lockup issues with my NAS, and wanted to run Memtest86+.

Thankfully, I have Supermicro motherboard that has IPMI (Intelligent Platform Management Interface), which is an out of band way of remotely administering a server.

Supermicro provides a way of mounting a remote image/ISO via a Samba share, so …

I had wanted to enable hardware transcoding in Plex for a while, but was under the (incorrect) impression that the CPU in the Docker host didn't support Intel Quick Sync.

Enabling hardware transcoding in Plex

Requirements for using hardware transcoding in Plex:

1. A CPU and/or GPU that supports hardware transcoding.
2. A …

Sooner or later, every system will have a drive failure.

ZFS was designed with this in mind.

I noticed in my /var/log/kern.log file error messages about one of the drives in my ZFS pool.

Dec  8 07:11:17 nas kernel: [738110.398391] ata8.00: exception Emask 0x0 SAct 0x80000004 SErr 0x0 action 0x0
Dec  8 07:11:17 nas …