I’ve been using command-line commands or the Clover Configurator to mount Clover’s EFI partition to edit Clover’s main configuration file.
However, I find it easiest to mount the hidden EFI volume in Disk Utility:
The hidden partitions will only be shown if Disk Utility’s debug mode has been enabled. In a shell, type:
defaults write com.apple.DiskUtility DUDebugMenuEnabled 1
Start Disk Utility and enable the option to show all partitions:
Ever since I fusioned a SSD and a HDD into an OS X Fusion Drive, Clover has been unable to auto-boot the new logical Fusion Drive volume. Clover was just sitting on its startup volume selection screen and was waiting for me to select the volume to boot. I’ve found some hints that using an UUID should make Clover autoboot the Fusion drive but I’ve been unable to make it work with any of the UUIDs of the logical/physical volume.
What finally worked was using the system ID (or whatever this is called) of the volume. Here’s an excerpt from my Clover configuration:
With this ID, Clover auto-boots my Fusion Drive volume just fine after waiting for 5 seconds for user input.
The full IDs can be found in Clover’s log file in
/Library/Logs/CloverEFI/ and look like this:
system.log:0:837 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(3,GPT,17337FC1-A0F7-4C73-DEA1-363BA11AB811,0x3A346008,0x40000)
You have to strip the PciRoot/Sata part for Clover.
Since OS X Yosemite, the CoreStorage service allows you to rename the logical volume name of a Fusion Drive if you wish to do so.
sudo diskutil cs rename "Macintosh HD" "Fusion Drive"
The Fusion Drive now shows up as “Fusion Drive” instead of “Macintosh HD” which was the name I’ve chosen initially. The OS X main volume is still named “Macintosh HD”.
Sep 29 19:19:41 wopr sshd: error: Could not load host key: /etc/ssh/ssh_host_ed25519_key
If you’re getting this error message in the log file, you most likely have the ed25519 HostKey enabled in your sshd_config file but for some reason, no host key was generated for it.
Since openssh-6.4 you can run the ssh-keygen command to generate any missing host keys:
$ ssh-keygen -A
ssh-keygen: generating new host keys: ED25519
Usually, my first step after setting up a new Ubuntu guest is to enable console access in order gain shell access on the newly created VM.
Step 1 – Activate the serial console in the guest
Change the GRUB_CMDLINE_LINUX_DEFAULT to:
Don’t forget to update Grub
Step 2 – Create the serial console in the guest
cp /etc/init/tty1.conf /etc/init/ttyS0.conf
Edit ttyS0.conf and replace the tty1 with ttyS0 in the last line so it will read something like “exec /sbin/getty -8 38400 ttyS0″.
Reboot the VM.
Step 3 – Log in from the host
virsh console myvm
This is it! You just gained console access to your VM.
Tip: To exit the console, hit CTRL-]. It doesn’t matter where the ] is located on your keyboard, you have to press the key below the <BACKSPACE> key and on the left side of the <ENTER> key.
Wouldn’t it be cool to build a bare-metal high availability cluster using CoreOS and a handful of DDoS-protected, €5/month Kimsufi servers from OVH? Here’s how to install CoreOS on a Kimsufi server.
At the time of this writing, OVH is not providing a CoreOS installation template for the Kimsufi servers. Since there is no virtual KVM console available for the entry level servers, I tried to use OVH’s iPXE API. This approach would have worked well weren’t it for the CoreOS installer which tries to load binaries in the installation script after overwriting the same partition – which always results in a segfault. Also, the API is only available for the older Kimsufi 2G servers on OVH’s V6 control panel, not for the current Kimsufi servers for which OVH doesn’t provide an API at this time. Fortunately, OVH provides a “rescue mode” which lets us boot from an USB stick which is permanentely plugged in on all Kimsufi servers. Continue reading
Here’s an overview of natively supported PCI-e (64-bit) network interface controllers (NIC) for OS X. I’ve had the chance to test some of them in my current Hackintosh build.
HP NC360T PCI-Express PRO/1000
The HP NC360T dual port PCI-e network adapter works out of the box in OS X. However, since OS X 10.8.2 Apple changed something in the driver resulting in a link loss whenever the network is under considerable load. If this happens, the network can be brought back to life by deactivating/reactivating the network in OS X’s control panel. Do not buy this network card if you intend to use it in a recent OS X version.
A cap burst on my ASUS P6T Hackintosh so I had to decide wether to buy an Apple desktop computer or to build a new Hackintosh. I would have bought an (internally) expandable Mac Pro but the current trash bin just doesn’t appeal to me.
I had three goals for the new build:
- Since kernel extension signing is mandatory in OS X Yosemite (at least in the dev previews/public beta versions), it has to be as vanilla as possible.
So, without further ado, here’s the new build:
The Z97X-UD5H uses Intel’s latest 9 Series chipset which to this date is not being used in any Apple computer. There’s a good chance Apple will use this chipset in the next iMac refresh in Q3/Q4 ’14. Even though the chipset is not officially supported in OS X, it runs just fine, even without a custom DSDT/SSDT! Continue reading
I prefer strongSwan over Openswan because it’s still in active development, easier to setup and doesn’t require a L2TP daemon. I prefer a simple IKEv1 setup using PSK and XAUTH over certificates. If you plan to share your VPN server with your friends it’s also a lot easier to setup for them without certificates. I haven’t tried the VPN configuration below with non-Apple clients but it works well with iOS and OS X clients. Make sure to use the Cisco IPSec VPN profile, not the L2TP over IPSec profile you need for Openswan. While strongSwan works well with KVM and Xen containers, it probably won’t work with non-virtualised containers like OpenVZ or LXC. Continue reading
LXC is awesome! You can create and start your own virtual container with just 3 commands in Ubuntu 14.04.
apt-get install lxc debootstrap lxc-templates
lxc-create -t ubuntu -n demo
lxc-start -n demo -d
It doesn’t get any easier than this. There’s even a Boostrap-based fronted available: LXC Web Panel.
Unfortunately, LXC Web Panel doesn’t work with LXC 1.0 which is part of Ubuntu 14.04. Fortunately though, there’s a fork available on GitHub which adds support for LXC 1.0:
I re-forked claudyus’ LXC Web Panel fork and added support for Ubuntu 14.04 and a few other things. My forked fork is available here: https://github.com/trick77/LXC-Web-Panel Claudyus has already updated his repository with my changes.
By the way, the original author of LXC Web Panel said he’s currently working on a Bootstrap 3 based version for LXC 1.0 which will include a RESTful API and other new features. Make sure to follow this guy on GitHub: https://github.com/googley
This may help setting up your own DNS unblocking solution:
Once everything has been set up properly, all ticks should be green like in this screenshot:
I just pushed another update to GitHub, please make sure to use a configuration generated with the latest generator version or the tester will fail. My main motivation to create this tester was to reduce the amount of support requests I’m receiving. Let’s see how well this goes :-)
I just pushed an update for the DNS-unblocking generator to GitHub. From now on, there is just one configuration file for the non-SNI and the pure-SNI approach. Please see the updated README.md on Github for more information.
After upgrading one of my KVMs to Ubuntu Server 14.04 LTS, Tomcat 7 started to freeze while starting up with:
INFO: Deploying configuration descriptor /etc/tomcat7/Catalina/localhost/ROOT.xml
Only after several minutes, Tomcat generates the following message and starts accepting requests:
INFO: Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [295,490] milliseconds.
INFO: Server startup in 296882 ms
If you don’t have a requirement for strong cryptography in Tomcat, you might as well switch to the less secure non-blocking /dev/urandom source instead of /dev/random.
Create a file named setenv.sh in /var/lib/tomcat7/bin make it executable:
..and restart Tomcat.
It will now restart within seconds thanks to the non-blocking random source.
I received a notification that one of my dedicated servers was taking part in a NTP based DDoS reflection attack. At first I was like “No way!” since I don’t use NTP on any servers. Closer inspection of the source IP address revealed that the attack was coming from my Supermicro server’s built in IPMI controller. And indeed, Supermicro is using a vulnerable NTP version on its IPMI controllers:
ntpdc -n -c monlist ipmi.mysupermicroserver.com
remote address port local address count m ver rstr avgint lstint
186.2.161.nnn 53842 76.20.120.nn 51127 7 2 0 0 0
217.147.208.n 123 76.20.120.nn 1 4 4 0 0 7
130.60.204.nn 123 76.20.120.nn 1 4 4 0 0 8
The quickest fix is to turn NTP sync off in IPMI as described here. If for some reason you have a requirement for NTP, here’s how to fix the Supermicro firmware on your own (not for the faint-hearted!).
Since Supermicro has a spotty track record when it comes to IPMI controller security, it’s highly recommended to define a set of jump hosts in the IP Access Control menu. Here’s a gotcha: the default policy is set to ACCEPT which means you have to add a DROP rule at the end with 0.0.0.0/0. Obviously, a private VLAN would be the preferred way, but if no VLAN is available, IP access control comes in handy. The IP access control list will filter any traffic to the IPMI controller except for the defined IP ranges. It will block access to NTP as well.
Still waiting for Supermicro to finally fix the issue in a new firmware revision though…
I love watching the Late Late Show with Craig Ferguson. Here’s what’s needed to watch CBS content on iPad outside the U.S. using my DNS-unblocking config generator.
Add this to config.json, regenerate the configuration files and make sure to upload them to the right places. As with NBC’s iOS app, the video stream itself is geo-fenced which may lead to considerable bandwidth consumption on your VPS server.
By the way, is it just me or does audio quality suck badly in CBS’s iOS app?