Review: OCZ Vertex 3 120G SSD

I’m not entirely certain which event triggered my gear lust for a solid state drive (SSD), it was probably a mix of Jeff Atwood’s post, TechReport’s storage section, and the falling prices resulting in smaller SSDs down below the $100 price point. Whatever it was, I couldn’t really shake the idea of having a SSD in my work laptop – so I decided to get one.

Initially I had thought that a 60G-64G drive would fit the bill, being under the $100 price point and just big enough to hold the OS plus my Lotus Notes mail installation. After reviewing benchmarks, and reviews I decided to focus on the 120G size – in part due to a general recommendation that the 60G size is a bit small for most, and the benchmark numbers on the 120G are a bit better. The price was higher, but still within a very reasonable budget as SSDs are approaching $1 a Gig. The TechReport comparison of 120G-128G size helped me narrow my choice down to the OCZ Vertex 3.

While the Vertex 3 has been on the market a year, it still ranks as one of the fastest drives available. There were some issues with the SandForce SF-2881 controller, but firmware 2.15 is reported to be solid.

My laptop was running a 500G SATA2 Toshiba drive, configured as a single large partition running Windows 7. I had no interest in re-installing from scratch so my approach was to clone the working system onto the smaller drive. There are likely plenty of ways to do this, I was able to easily find a blog post describing how to do it – I roughly followed those steps but will document exactly what I did here.

Step 1) Reduce the partition on the big hard drive to be a bit less than the formatted capacity of the SSD. Initially after reading a bit I was hesitant to use GParted to do this as it seemed some folks had had problems with Windows 7 and GParted. Windows 7 also has a built in partition resize capability.

I ran into several issues trying to use the built in Windows 7 functionality. First up was some unmovable files causing issues. Even after turning off virtual memory and system restore, I still had issues. The Event Viewer was a help in identifying Chrome as holding onto some unmovable files, then I hit what I believe was an issue with NTFS Metafiles being unmovable and blocking my ability to shrink the partition smaller than 245G. At this point I threw my hands in the air and ran GParted from an Ubuntu Live USB key.

GParted ran to completion, but oddly gave me an error indicating something was wrong – but I couldn’t spot anything actually wrong. [Normally GParted should not give an error] The damage was done so I just rebooted and let Windows perform the necessary chkdsk activity. Things were fine, so either I mis-read that there was an error or it was something that was recoverable. Either way I was now happily running with a 100G partition.

Step 2) Use Clonezilla‘s “savepart” option to capture an image of the partition. Since I had a 500G drive which now had lots of empty space after the 100G system partition, I created a 2nd volume to store the captured image to. You can use a second USB mounted drive, or any number of other options including ssh with Clonezilla to store your image.

I will comment that Clonezilla is not for the timid, the user interface appear very complex and requires some careful reading to make sure you’re doing what you think you’re doing. Youtube has a number of walk throughs. For the 100G partition it took about 1:35 to backup.

Above you see the SSD attached to the ultra slim sled that the laptop hard disk was in, this is a very slim metal sleeve with a pull tab and some rubber bumpers. It fit nicely into my W520.

Step 3) Swap the drives. If you have a password on the drive, it’s a good idea to disable before removing it as USB enclosures and passworded drives don’t mix well. Install the new SSD, and place the existing drive into a USB enclosure. Boot the laptop into Ubuntu Live again and partition the new SSD drive, make sure to tag the new partition as with the ‘boot’ flag.

Step 4) Restore the image you saved with Clonezilla’s “restore part” option. In this case I was restoring from the 2nd partition on the original hard drive that is now mounted as a USB volume. Clonezilla warns you twice when restoring a partition to validate you’ve got the correct destination, a nice paranoid touch.

The restore ran nearly 3x faster taking about 37 minutes.

Step 5) Boot into windows, chkdsk may have run again but with the SSD it seemed to take no time at all. You might want to visit the OCZ site and grab the toolbox utility to validate you’ve got the latest firmware, I did this to verify I had 2.15.

Performance

After I did the clone, I ran some boot time tests on the hard drive. I tested immediately after I had completed step 5 with the SSD. For work I need Lotus Notes up and running to access my calendar etc, so that was a logical pattern to benchmark – how long to get back to key information? I used a stop watch, and the times include the time I spent typing in the two passwords and navigating to the icon to launch Notes. It’s not terribly scientific, but I think the results still speak for themselves.

Disk test 1 Disk test 2 Disk test 3 SSD test 1 SSD test 2 SSD test 3
Cold boot to Windows login 1:22 1:24 55 23 23 23
Login to launch of Notes 1:42 1:13 1:44 10 10 10
Lotus Notes ready 40 44 40 10 10 11
Total time 3:45 3:22 3:19 43 43 44

This is crazy hot – more than 3x faster, under a minute from a cold boot.

Now certain operations don’t seem any faster. Resuming from hibernation feels to be about the same speed. This makes sense as the performance difference for sequential reads isn’t much different. It seems in normal usage, lots of little things are more immediate too. Some of this is likely simply moving from a SATA2 to a SATA3 drive, but I’m convinced no spinning platter could keep up with the SSD.

Review: Filtrete 3M-50 Wifi Thermostat

I came across this particular wifi enabled thermostat a year or so ago, unfortunately they are not available in Canada. I’d guess this is simply the additional headache of bringing an electronic device to market in Canada (yes, different hoops than what is needed in the USA) and the market size. On my last trip to the states I took the opportunity to drop into a HomeDepot and pick one up. There was only 1 unit in the entire city I was in (I had to go to both HomeDepot stores!) – so you may have trouble getting one even if you live in the US, I suggest you call ahead.

The sales pitch on having your home thermostat wifi enabled is to make it simpler to program, and easier to adjust from anywhere in the house or out of the house. When we leave on vacation, turning down the heat and reprogramming the 7 day schedule is pretty low on the priority list. Being able to do so from the hotel over the internet would be handy. I’m looking forward to the ability to pull out more statistics from the device and surface them in graphs, for example yesterday my furnace was on for 4hrs 47mins and today it ran 2hrs 46mins (it was much warmer today).

Most of this post will discuss the installation process, as this is primarily my experience with it so far. Some of this will be specific to my particular install but I’ll try to walk you through the process I used to arrive at a successful result. If you want to stop reading here the short version is that it’s pretty cool, you probably want one.

The first step is to read (or at least flip quickly) through the manuals included. The packaging strongly indicates you need a C wire, the manual lists it as optional. The C wire is required, don’t get confused by the manual. Next take a look the wiring for your existing thermostat.

The good news is that the wire coming out of the wall has more than enough conductors to carry a C wire if I need to add one. The bad news is that I’m standing there scratching my head because I don’t really understand the current wiring.  My existing thermostat is a Honeywell MagicStat CT 3300 for which I was able to easily find a manual online. This helped me identify the wiring that was connected.

Next stop is to go take a look at the furnace, to map the other end of the wires. Unfortunately between the furnace and the thermostat I found this, something I’ll call the mess-o-wires.

The mess-o-wires ties in my A/C unit to the furnace and the thermostat. Opening up the furnace I get to the control board where the wiring starts.

So basically I have my furnace, connected to a wire A, this in turn heads to the mess-o-wires, then connects to wire B, this runs upstairs to the thermostat. Mapping the wire colors and connections results in the following table. The last column is the CT3300 hook ups. I also found a helpful reference to understand what the wiring names were.

Color Wire A Wire B CT 3300
Y orange yellow Y
R red red + black Rh + Rc
W1 white white W
G green green G
C black

This lead to an ah-hah moment. So I’m basically running in a 4 wire mode at the thermostat W Y RH G. The RH and RC are bridged back in that mess-o-wires. Knowing this helped me map to the 3M-50 manual for how to properly hook things up. The solution is that I need to fix the mess-o-wires to allow the C wire to run up to the thermostat using the black wire. Let me stress that this is unlikely to be your solution, but the process of wire tracing and mapping should help you understand your current setup and how to perform the install. If this is over your head, call your furnace service folks to do this part.

Once I was past this part, the actual installation went very smoothly – just follow the manual. The wifi unit ships along with the unit, but is not installed and the manuals don’t seem to reference it beyond providing a URL: www.radiothermostat.com/wifi. I inserted the wifi module while the thermostat was on and running, it seemed to handle that just fine. When you do visit www.radiothermostat.com/wifi you’ll find a friendly 3 step process:

  1. Register for an account on the web
  2. Verify Thermostat Installation
  3. Use laptop to connect your thermostat to your local wifi, and then to the internet

It’s not really three steps since step three contains more sub steps. My notes are a bit sketchy here, but it didn’t seem to provide much in the way of hand holding – they assume you know what you’re doing when it comes to wireless setup. At this point I’ll deviate from how I did the setup and talk about the iOS app. If you have an iDevice, then you should do step 3 above entirely using it. I’m not sure how smoothly a second iOS device will work out as it seemed that I was forced to re-setup the wifi connection (step 3) on the iPad even though it seemed to be working fine over a web browser. (again my notes are a bit rough as to what happened) I’m certain you can have multiple iOS devices, you just might have to go through the setup phase more than once.

There is also an Android app. This seems to be poorly advertised as I only found it while writing this post, they should really add it to the website. Adding the app to my phone and logging in, I’m able to view my thermostat without any network re-setup required. So my iOS app experience above of needing to re-setup the wifi must have been due to some other issue I was having.

I will say that I really like the wireless configuration approach. Much better than the Logitech HarmonyLink mess with a USB cable and browser plugins. The HarmonyLink could easily adopt this style of setup – creating an ad-hoc network to do the wireless configuration. The thermostat generates a 5 digit verification code to ensure that it’s really you, the HarmonyLink could simply flash the led to give you a verification pattern.

For some reason Chrome didn’t seem to work to create an account. Switching to Firefox solved this. After I had created the account, Chrome worked just fine. In fact, the website has a reasonable mobile layout as well. So a strike against them for doing something odd with account sign ups, but kudos for getting it mostly right no matter what device you visit the website with.

The iOS app is very simple, it lets you control the basic functions: temperature up/down; home/away; fan on/off/auto; heat/cool. You cannot set a schedule with the app it seems. The schedule can be set on the device (but who would do that?) and via a full web browser. The mobile version of the website is limited in a similar manner as the iOS app. The Android app appears to offer the same functions as the iOS app.

Configuration of Celcius vs. Fahrenheit is supported by the web/iOS/Android app in a single setting. The physical display on the thermostat requires you configure this as is shown on this youtube video. This had me puzzled for a bit until I found the video link, it is also mentioned in the FAQ.

There is a developer API available and folks who’ve created impressive private versions of a web UI. Interesting that temperatures are all Fahrenheit in the developer API, so I assume that’s how it is stored internally. I’ll certainly be experimenting in this direction when I have some time. The forums seems to be fairly active and have some good content in them from the quick browsing I’ve done.

Review: Harmony Link

When it was announced back in September 2011 I was quite excited about the HarmonyLink. I got one as a gift this Christmas and after some initial efforts with it, my enthusiasm is a little dampened, but I still think the device has a lot of promise. There are some serious flaws that need to be addressed by Logitech before it can replace my Pronto TSU 2000.

I was surprised that it didn’t use the same Harmony Desktop software that worked with the 659, then I got excited because it appeared to be web based. The model is log into website, configure your Devices and Activities on the web and sync to your device – nice. Sadly if you try to log into your account on myharmony.com from a non supported platform you get this message:

The following platforms are supported:

Microsoft® Windows XP or Vista with Internet Explorer 7+, or Firefox 3+

Microsoft® Windows 7 with Internet Explorer 8+ or Firefox 3+

Intel Mac OS® 10.4.8+ with Firefox 3+ or Safari 4+

The reason for this is they use a custom browser plug-in to do the initial setup of the device. This sort of makes sense, as the HarmonyLink is a wifi device that needs to be told how to connect to your wireless network. The initial setup seems to be the only time you’ll need the USB cable provided. I also found it a bit uncomfortable being asked by a website to enter my WPA2 password.

Logitech could have made things much simpler. Provided a very simple utility on Windows and Mac OSX to do the device initialization. Of course you need to program the device to enable it for your wireless network, they have all the code they need to do this in a reasonable manner so it seems like just a dumb design decision to include it as part of the browser plugin.

Security fail: The website myharmony.com also wasn’t able to accept a < character in my password. It gets better, the Android app (and apparently the iOS app too) doesn’t remember your password. So you need to type it in from time to time. Strike two for password security. They do require at least 4 characters, I can think of some great four letter words that might fit. So the user is torn between using a strong password or a convenient one. Everyone who might want to use the remote may need to know the password, that’d be strike three on their security story.

Setting up the devices was pretty reasonable, it does require that you know the model numbers of your equipment but will provide suggestions if you’re close to the right name. I had trouble locating the IR4PS3 device (for control of the PS3) in the device database, I ended up succeeding by entering Sony as the manufacturer and IR4PS3 as the model – then the correction offered by the website (IR4PS3/IR4PS3) worked.

The remote is setup around the idea of Activities, such as “Watch TV”. This is a bit different than the flow I have setup with my Pronto so it’ll take some getting used to. They have three basic activities: Watch TV, Watch Movie, Listen to Music. You can have multiples of one type of activity and give them unique names, but they provide only 4 icons – which is very silly given how easy it should be to have many different icons.

They very first time you connect to the HarmonyLink using your Android or iOS device running the remote control app, you’ll likely have a firmware update and a sync of your data from the web. The Android app hung on me during the firmware update leaving me waiting and waiting. It required a reboot of my Android tablet and I was back in business.

I haven’t warmed up to the Android version of the app yet. The power off path wasn’t immediately obvious to me, I’ll have to see how others that get a chance to use the remote once I shake out all the major issues react to it. Responsiveness to button presses is pretty good, there doesn’t feel like there is any appreciable lag. You can edit the button layout, with the exception of the 4 way navigation pad which seems fixed (this is unfortunate as the IR4PS3 mapping for ‘ok’ doesn’t map to X).

I was disappointed to discover that there wasn’t a web UI on the HarmonyLink itself. You must use a supported device (Android, iOS) and run the app. I’ll need to break out Wireshark and take a look at what needs to be done to fix that.

As I started with, I’m still optimistic this is going to be a nice addition to my home theatre – but only once they address some of the shortcomings. Engadget gathered a long list of great comments which felt pretty much on target. There is also a suggestion thread in the Logitech forums. I hope Logitech is listening.