smartd self test never completes (Seagate 7200.12 ST31000528AS CC34)

[Wolfgang S. Rupprecht]

I just got a Seagate 7200.12 ST31000528AS with CC34 firmware and I
noticed that the smart self-tests never complete.  24 hours after
starting the long test still shows "90%" remaining.  This system has 3
other seagate disks of various vintages and the smart tests all run at
the rate the drive says they will (randing from 1-5 hours depending on
the drive).  This is the only drive that seems to get stuck.  Does this
drive need to be initialized in some funny way to get it to act like a
drive of old?  I've also tried the short test and the new "Conveyance
Test" and after 10 -20 minutes both tests still showed 90% remaining, so
it isn't just the long test that hangs.  It is all of them.

$ smartd -a /dev/sda
Device Model:     ST31000528AS
Firmware Version: CC34
User Capacity:    1,000,204,886,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Sun May 31 05:51:15 2009 PDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
...
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Conveyance offline  Aborted by host               90%       277         -
# 2  Short offline       Aborted by host               90%       273         -
# 3  Extended offline    Aborted by host               90%       273         -
# 4  Extended offline    Interrupted (host reset)      90%       252         -
# 5  Extended offline    Interrupted (host reset)      90%       219         -
# 6  Extended offline    Interrupted (host reset)      90%       164         -
# 7  Extended offline    Interrupted (host reset)      90%        48         -
	
The "aborted by host" was me stopping the tests after the one or two
minute tests ran for > 10 minutes.  The extended offline was in several
of the cases the computer being rebooted after over 24 hours of the test
running.

Anyone else have one of these yet?  Did you figure out how to get the
test to run?

-wolfgang
-- 
Wolfgang S. Rupprecht              Android 1.5 (Cupcake) and Fedora-11