Thoughts and Ramblings

General things I find of interest.

FreeNAS Internal Backups

I’ve changed my media storage system from the Linux setup I outlined earlier to FreeNAS. In the process of the transition, I built an entirely new server using a Norco 4224 as the case and a Xeon processor with ECC. Since FreeNAS makes ZFS so easy and doesn’t suffer from several of the problems of ZFS on Linux, I elected to use this OS for my storage going forth. The only issue I had to resolve was how I would handle backups.


Yosemite Install Can't Be Verified

This weekend, I noticed that the spinning hard drive in my MacBook Pro was dying. I ordered a replacement, installed it, then proceeded to install Yosemite. After counting the numerous Yosemite installer bugs, I noticed an unusual one:

This copy of the Install OS X Yosemite application can’t be verified. It may have been corrupted or tampered with during downloading.

My searches for this didn’t yield a useful solution so I figured out what the problem really was: Since I disconnected the battery as part of my install process, the computer was completely without power for a moment and loss the date/time. So, I set the date in the terminal using the date command, and then the above mentioned error went away.


Not All Packets Are Equal

The term Net Neutrality covers a lot of hotly debated topics but at its core is whether ISPs should be allowed to treat some traffic differently. In the midst of the discussion, one minor fact seems to have been lost: Not all packets are truly equal.

Around 10 years ago, I had DSL with 768kbps down and 128kbps up. I quickly learned that if I did any upload at all, the download speeds suffered greatly. Upon investigation, I discovered that the outgoing control packets, such as ACK packets, were being stuffed in the same queue as outgoing data packets. One of the solutions was to employ egress traffic shaping. This was simply prioritizing control packets such as ACK, SYN, and RST, followed by small packets all ahead of the large data packets. The result: uploading data no longer slowed downloads. Today, with much higher speeds, this shaping has less benefit, but it is not gone.


My Media Setup - Part 3

In my previous post I outlined the issues with using the GoogleTV for playback and I promised to outline my new client.

The Hardware

Since a list makes this easier, I’ll present the hardware that way:

Not mentioned above is the requirement of an HDMI receiver between the TV and NUC. The NUC can be configured to use analog audio output or passing audio directly to a TV over the HDMI, but a receiver provides the best audio experience.


My Media Setup - Part 2

Since my last post on the topic, my client and server software have changed. In the interest of full disclosure, I should mention that I now work part time for Plex, though all of my decisions outlined in this post were made before that time.

Necessity for the change

I started to get frustrated with some of the limitations of the GoogleTV:

  • The platform seemed to become stagnate (and the pending AndroidTV hadn’t been announced yet). It became clear that some of the limitations were never going to be resolved.
  • The device is supposed to passthrough DTS, but it will occasionally fail for a second during playback. It does this both on optical and HDMI. I tended to resolved this by transcoding the DTS to AC3 with the more problematic movies.
  • The device is supposed to play VC-1, but it would stutter during playback if the content was in an MKV file. It did not if the content was in a MPEG-TS. This problem does not exist during disk playback. I resorted to transcoding VC-1 content to AVC.
  • The device is supposed to passthrough HD-audio such as DTS-HD and TrueHD. It does this with playback of a disk, but not from MKV files nor MPEG-TS.

Clearly the best solution is a computer since it has no problem with all of these.