Finicky buttons on Vortex SPARC

A quick tip for anyone experiencing somewhat finicky buttons on a Vortex Sparc (Gen. 1): Chances are your unit isn’t defective, it’s just time to replace your CR2354 battery.

Apparently the red-dot will continue working until the very last moment, when your cell is completely out of juice – but the controls won’t. Sometimes they work, sometime they won’t. Turning the red dot on and off seemingly takes forever and occasionally won’t work at all. Even though the dot itself was as bright as it gets, turns out my battery was almost out of power. Replaced it with a new one – everything is back to working again like it’s supposed to.

KVM too fast for plymouth-upstart-bridge

Kind of a hilarious bug, really… I recently installed another Ubuntu 14.04 server running inside a KVM with a rather fast storage backend, therefore the system apparently boots just a tiny bit faster than my other images have in the past. Problem is, apparently that slows down the boot process as init thinks something must be crashing and decides to respawn it for good measure…

Yep, that’s right – 47 seconds waiting and idling, doing nothing when the image could have booted in a fraction of that time.

To fix it, simply add a sleep 2 to your /etc/init/plymouth-upstart-bridge.conf

Init won’t freak out anymore and starts the image as it’s supposed to:

Way better….

Updating SmartArray controllers on 64-bit Ubuntu 14.04

Want to install a firmware update on one of your HP SmartArray controllers while running a 64-bit OS? Turns out, the binaries distributed by HP seem to be 32-bit only – running for example Ubuntu 14.04, here’s what you gotta do…

 

But libstdtc++6 seems already installed, hmpf… 32-bit maybe?

 

Let’s try that again…

Well, that was rather easy…

Fix check_hpasm for 3.x kernels

After upgrading one of my HP ProLiant servers to Ubuntu 12.04 LTS (better late than never) the check_hpasm Nagios plugin broke, resulting in no regular checks of the internal arrays being performed.

Apparently that’s a known bug with the hpacucli utility doing the actual checks, which can’t uname returning a 3.x kernel version. You can manually fix this by running it like this:

Therefore a quick and dirty fix for check_hpasm would be to open up /usr/lib/nagios/plugins/check_hpasm and go to the part that reads:

and replace the line (553 in my case) calling hpacucli with:

Worked just fine for me.

Grant Williams ASFA 2013 presentation

While this isn’t an economics or investment blog by any means, here’s a nice 30 minute presentation by Grant Williams recently given during the 2013 ASFA conference. Humorous as always and IMHO spot-on, outlining the current state of international financial markets, the current government bond bubble and equity rally of 2013… and how it’s all inevitably going to go down in flames. Very well worth watching, even if you aren’t a investor, trader or otherwise closely associated with the financial markets.

[youtube https://www.youtube.com/watch?v=5A3CoFyi2U8]

Fix for bad write performance with LUKS + RAID5

After setting up a new fileserver with an LUKS encrypted dataset on top of Linux software RAID5 I did some benchmarks and reliability testing before filling it up with “real” data… but it turns out write performance was quite horrible. Only a fraction of what the “raw” RAID5 could do, all while having the CPU mostly idle. So what’s going on?

Apparently only small blocks of data get written to the disks when using LUKS encrypted volumes (mostly default settings) therefore dramatically reducing write performance (figured it out thanks to this) on my RAID 5 volume. Setting the stripe_cache_size from 256 to 8192 increased throughput from roughly 50-70 MB/sec to well above 200 MB/sec.

To permanently set it, so you don’t have to manually adjust it after every reboot, consider setting up a udev rule like this:

Fix for Google Play Error [RPC:S-5:AEC-0]

After re-installing the Google apps package (gapps-jb-20130301-signed.zip) on my CM10.1 phone, Google Play stopped working and didn’t let my install any new apps or update existing ones. To fix the Error[RPC:S-5:AEC-0] you’ll have to:

Go to the system settings -> delete your Google account -> add it again and let your Android sync

Don’t worry, you won’t lose any of your data by doing that.