Programmers' Pain

No, I haven’t burned my 512 RGB LED coffee table (yet)..

The assembled coffee table doing it's main job in my living room: being a table :)

The assembled coffee table doing it's main job in my living room: being a table 🙂

No, I'm still alive and no, haven't turned my coffee table into a big camp fire (yet) 🙂 I was just busy with renovating my flat and some other projects that I'll show you in some future blog posts as well. Therefore I didn't had too much spare time left that I could invest into my 512 RGB LED coffee table project lately. Still I want to give you a brief update what has happened in the meanwhile: I closed my last blog post with basically having the table hardware-complete but still not finally assembled to be able to fix any hardware related bugs that might show up while continue testing it. For some weeks I've left the table in that state, did test various things and fixed some bugs before I put it together and moved it over to my living room where it just does it's job as a good looking coffee table. Since I can't use my notebook to connect to the Rainbowduino V3 controllers any more I had to spend some time on getting my Java software easily deployable to the tables PC and to add a hook into the Linux installation so that it starts up while the PC is booting. Feel free continue reading if you're interested in the details on how I did that and to get some additional insight in the current state of the tables Java software.


Howto setup an encrypted RAID1 array using external USB 3.0 disks

RAID1 setup using Linux software raid and LUKS encryption

RAID1 setup using Linux software raid and LUKS encryption

After one of my last blog posts dealt with modifying my two Sharkoon SATA Quickport XT USB3.0 docking stations I did spend some time figuring out how I can use them to set up multiple RAID1 volumes that should be encrypted using the LUKS environment of recent Linux distributions. Also I was searching for a mechanism to clearly map every involved disk to an unique raid volume so that I don't end up with a generic mount point like /mnt/raid1/ that would just show the content of the currently docked disks - instead every RAID1 volume should have it's own dedicated mount point. The solution I've came up with uses UDEV rules to identify the disks, mdadm to map two disks to a single software-RAID1 volume, cryptsetup to encrypt the raid volume and some smaller, self-written helper scripts that do simplify the usage of those external RAID1 volumes. How it all works and how you can set up such an environment on your own Linux machine: just click 'continue reading' 🙂

Tagged as:
Continue reading