Green is Bad – at least where WD disks are concerned

I don’t have much luck choosing hard disks – see The Seagate fiasco

Having replaced all the dodgy Seagate disks in my RAID array with new Western Digital Caviar Green (WD6400AADS) drives in February, I have already stumbled upon a big new problem.

It would appear that these Caviar Green disks achieve some of their stated green-ness by using a ‘clever’ energy saving system which automatically parks the hard disk heads (moving them off the platters) if the disk has been idle for over 8 seconds. This apparently reduces aerodynamic drag while the platters are spinning and achieves some microscopic power savings.


According to the published WD Caviar Green spec sheet, the disks are rated for 300,000 of these head load/unload cycles during the warranted lifetime of the disk. I checked how many load/unload cycles my new disks had performed so far in their short 1,840 hours (76 days) of life and gasped at what I saw – 234,000 !

My disks had consumed 78% of their rated load/unload cycles in just over two months of usage! Why was this happening?

Some quick investigation revealed that this is due in some part to my using the disks in a Linux system and has been exacerbated by including them in a RAID array. I calculated that on average the disk heads have been loading and unloading every 30 seconds since I first started using them. That would mean an expected life span of just over 100 days 😯

I needed a solution – and quick. WD are not oblivious to this issue, but have not exactly been forthcoming in their marketing material to bring this to your attention. They have however published a knowledge base article – In Linux the S.M.A.R.T Attribute 193 Load/Unload counter keeps increasing on a SATA 2 hard drive – which states the following:

WD drives are designed to reduce power consumption, in part by positioning the heads in a park position (unloading the heads) and turning off unnecessary electronics, resulting in substantial power savings. WD defines this mode as Idle 3.

Some utilities, operating systems, and applications, such as some implementations of Linux, for example, are not optimized for low power storage devices and can cause our drives to wake up at a higher rate than normal. This effectively negates the power-saving advantages of low-power drives, such as WD GreenPower™ models, and artificially increases the number of load-unload cycles. Although the increase in load/unload cycles is within design margins (drive has been validated to 1 million load/unload cycles without issue) a balance between life of product, logging requirements, and low power consumption can be achieved depending on what is critical to the system. Present SMART normalized values have not been re-normalized to 1 million cycles so advisory reporting on this attribute does not mean failure of product.

WD also released a MS-DOS software tool called WDIDLE3.EXE which can be used to disable the idle mode feature altogether – RE2GP Idle Mode Update Utility (backup mirror site)

This firmware modifies the behavior of the drive to wait longer before positioning the heads in their park position and turning off unnecessary electronics.

It’s not exactly plain sailing to use this tool, particularly if you are running Linux. I found the simplest route was to copy the utility to the DOSAPPS directory of an Ultimate Boot CD, rebuild the ISO image, boot off it into FreeDOS and run it from there. After executing wdidle3.exe /d I saw the good news that “Idle3 Timer is disabled” on all disks and the Load_Cycle_Count counter has been permanently halted *phew*

I have hopefully saved my disks from an early demise but I fear that the amount of overuse they have suffered already may have caused permanent wear damage. I guess only time will tell.

The Seagate fiasco

In July 2008 I purchased two Seagate Barracuda ST3500320AS 500GB hard disks. One started reporting a high (and growing) number of unreadable/unrecoverable sectors and so I returned it for a warranty replacement. A couple of weeks later the second drive started doing the same.

A few months after that I started to see forum posts and reports from other Seagate customers reporting defective and dead drives, all of the same type and age. This soon turned into a flood of complaints on the Seagate community support forum and the IT press picked up the story.

» Seagate Forum: Official st31000340as 1TB barracuda epic fail thread

» TheRegister: Seagate customers swamped by Barracuda drive failures

» Engadget: Seagate Barracuda 7200.11 drives said to be failing at an alarming rate

On 18th January 2009 Seagate responded officially and acknowledged that there were firmware issues with some drives.

Smokin' Seagate

A number of Seagate hard drives from the following families may become inaccessible when the host system is powered on:

Barracuda 7200.11
DiamondMax 22
Barracuda ES.2 SATA

Once a drive has become affected the data becomes inaccessible to users but the data is not deleted.  Seagate has isolated this issue to a firmware bug affecting drives from these families manufactured in December 2008.

Please use the following tools and instructions to determine if you have one of the affected products.  If your drive is affected, we recommend that you update the firmware on the disk drive to prevent this condition.

(Note the incorrect “firmware bug affecting drives … manufactured in December 2008”, when they should have said “through to December 2008”).

Seagate released firmware update ‘SD1A’  for the affected drives. This first version of their updater software failed to recognise some of the affected drives and would not update them.

In response to customer complaints Seagate then released an updated-update the next day, with the same SD1A version number.

Note: This file has been updated as of Jan 19, 2008 4:15PM CST. Please re-download this if you have an earlier version.

This update caused the BIOS of some PCs to stop detecting the 500GB capacity drives, rendering them unusable. Well done Seagate!

» Seagate Forum: Does the SD1A break 500GB cudas?

Seagate removed the download link and then finally on 21st January 2009 released an updated-updated-update, yet again with the same version number SD1A.

Could they possibly be any more incompetent in dealing with an already bad situation?

I gather the final version of the SD1A update is safe to use, I haven’t tried it for myself as I opted to purchase new Western Digital Caviar drives and migrate all my data to them instead.

Seagate later decided to close all the forum threads about this issue and “consolidate” them into a new thread:

Hello:

To consolidate the discussion regarding the Seagate Barracuda 7200.11 Firmware issues, please post all related messages in the new thread that we have begun for the purpose of centering all the discussion in one place. Please do not post firmware-related content in another thread. We are closing this thread to redirect.

Thank you for your understanding!

-The Moderator Team

Try clicking on the link and see what you get!

The message you are trying to access has been deleted. Please update your bookmarks.

Great customer support Seagate!

Prevent SSH session timeout

When using mobile broadband I found that a SSH shell session to a remote server would terminate unless I used it every few minutes. To overcome this use the ServerAliveInterval option to send a regular keepalive message to the remote server, which should be enough for the ISP firewalls to maintain the TCP session indefinitely.

Either add the SSH option via the command line, e.g.

$ ssh -o ServerAliveInterval=60 user@host

Or add the following line to ~/.ssh/config:

ServerAliveInterval 60  # Send a keepalive every 60 seconds

Configure HomePlug devices from Mac OS and Linux

If like me you have a need to configure HomePlug Powerline devices but don’t have a Windoze PC, I found a simple tool written by Manuel Kasper that compiles on most BSDs and Mac OS X and allows you to set the network encryption key without running any Windoze software.

The program is called plconfig and it communicates with most Intellon chipset based PowerPacket bridges.

Downloads: plconfig version 0.2 for BSD or Linux

QED-uk.com and Mallplace.com spam

Well here’s an interesting thing. I registered with QED-uk.com (Miller Brothers Retail Ltd t/a Quality Electrical Direct) in July 2006 using an email address unique to that site.

Two years later I have been receiving spam emails from mallplace.com all sent to this same unique address.

Originating IP: 213.171.196.167
from: information@mallplace.com
subject: Best new website award goes to mallplace.com
Date: Tue, 23 Dec 2008 17:20:35 +0000

Originating IP: 213.171.196.167
from: information@mallplace.com
subject: Mallplace, January Sales!
Date: Fri, 26 Dec 2008 14:48:41 +0000

Originating IP: 213.171.196.167
from: information@mallplace.com
subject: mallplace.com given 5 star review by webuser magazine!
Date: Sun, 28 Dec 2008 21:26:51 +0000

So how did the mallplace.com spammers obtain my address I wonder?

The address of QED-uk.com is Miller House, Ogden Road, Doncaster, DN2 4SQ and the whois record for mallplace.com shows that the registrant is “pollock new media” of Miller House, Ogden Road, DN2 4SQ.

QED-uk.com’s web site makes this claim regarding privacy: “As a UK based company we abide by the rules and regulations of the Data Protection Acts of 1984 and 1998, and as such no information supplied to us will be given to or used by any third parties.”

Perhaps someone from Pollock New Media / Mallplace.com would care to comment on their association with Miller Brothers Retail Ltd / QED-uk.com?

UPDATE 17/12/2009

I am now receiving spam mail from ‘liGo Electronics <ichoose@ligo-electronics.com>’ to the same unique address that I used with QED-uk.com. This time they claim “You have received this email as a special customer of liGo.”

Oh really?