Wierd temperatures reported from new Seagate

[bill..]

I just got a new 160G Seagate Barracuda which is operating just fine
- I think.

I cloned my Barracuda 80G and set up the new one as the boot drive
( the 80 will eventually go to another machine)

I run Motherboard Monitor and was interested just how hot the drives
would run. Added the new drive to a MBM monitor slot and it was within
1 deg of the old drive at about 37deg C.

The problem:

Every 30 - 60 minutes the high temp alarm goes off on the new drive.
the actual value is bogus - sometimes it is as high 260 - 264 deg. The
next reading is typically normal - ie back to 37 or so. This had never
ever happened with the old drive.

Suspecting a problem with MBM, I tried HDtemp and a couple of other
utilities too - all occasionally reported a bad temp - but only on
the new drive.

So, is there a newer version of SMART that is confusing the sw or is
my new drive defective?

Any suggestions?


Bill

 

[Rod Speed]

I just got a new 160G Seagate Barracuda which is operating just fine
- I think.

I cloned my Barracuda 80G and set up the new one as the boot drive
( the 80 will eventually go to another machine)

I run Motherboard Monitor and was interested just how hot the drives
would run. Added the new drive to a MBM monitor slot and it was within
1 deg of the old drive at about 37deg C.

The problem:

Every 30 - 60 minutes the high temp alarm goes off on the new drive.
the actual value is bogus - sometimes it is as high 260 - 264 deg. The
next reading is typically normal - ie back to 37 or so. This had never
ever happened with the old drive.

Suspecting a problem with MBM, I tried HDtemp and a couple of other
utilities too - all occasionally reported a bad temp - but only on
the new drive.

So, is there a newer version of SMART that is confusing the sw
Nope.

or is my new drive defective?

Very unlikely that the actual temperature is spiking occasionally.

More likely some quirk with the SMART temp in that
particular drive, its not being reported properly all the time.

 

[Arno Wagner]

I just got a new 160G Seagate Barracuda which is operating just fine
- I think.

I cloned my Barracuda 80G and set up the new one as the boot drive
( the 80 will eventually go to another machine)

I run Motherboard Monitor and was interested just how hot the drives
would run. Added the new drive to a MBM monitor slot and it was within
1 deg of the old drive at about 37deg C.

The problem:

Every 30 - 60 minutes the high temp alarm goes off on the new drive.
the actual value is bogus - sometimes it is as high 260 - 264 deg. The
next reading is typically normal - ie back to 37 or so. This had never
ever happened with the old drive.

Suspecting a problem with MBM, I tried HDtemp and a couple of other
utilities too - all occasionally reported a bad temp - but only on
the new drive.

So, is there a newer version of SMART that is confusing the sw or is
my new drive defective?

Any suggestions?

I have seen something like this with the 120GB version.
Sometimes it delivers a bogus measurement. My guess is that
this is a bug in its firmware, so best learn to live with it.

Arno

 

[Svend Olaf Mikkelsen]

I just got a new 160G Seagate Barracuda which is operating just fine
- I think.

I cloned my Barracuda 80G and set up the new one as the boot drive
( the 80 will eventually go to another machine)

I run Motherboard Monitor and was interested just how hot the drives
would run. Added the new drive to a MBM monitor slot and it was within
1 deg of the old drive at about 37deg C.

The problem:

Every 30 - 60 minutes the high temp alarm goes off on the new drive.
the actual value is bogus - sometimes it is as high 260 - 264 deg. The
next reading is typically normal - ie back to 37 or so. This had never
ever happened with the old drive.

Suspecting a problem with MBM, I tried HDtemp and a couple of other
utilities too - all occasionally reported a bad temp - but only on
the new drive.

So, is there a newer version of SMART that is confusing the sw or is
my new drive defective?

Any suggestions?


Bill

The smart value is one byte, so it cannot be 260 or 264. The bytes
from the vendor specific values are vendor specific, and not
documented I guess.

A Seagate of mine reports the temperature in the value field with
threshold 0, although a similar vendor specific byte is shown.

The numbers 260 or 264 would not match the temperature in the low
byte, so that does not explain it.