[Ivan Degtyarenko <imd@fy...>]

Douglas,

On Fri, 17 Oct 2003, Douglas Gilbert wrote:

> > smartctl -a /dev/sdf1
> > 
> > between others it gives 
> > 
> >     ...
> >     Manufactured in week 00 of year 2000
> >     ...
> > 
> > what it means? Where from smartctl takes this date info?
> > My problem is that harddrive which we bought is labeled by date:
> > 28 Apr 2003  and  'smartctl' gives year 2000.
> > Who is wrong?
> 
> Maxtor is wrong (or at least inconsistent)! During
> production they should put a valid production date
> in the disk firmware (about the same time as they
> give it a unique serial number).
Ok, thank you, I thought the same, Atlas 15k models are very new and it 
should be an inconsistent. At least it can't 3 years old. 


> > full output:
> > 
> > -------------------------------------------
> > # smartctl -a /dev/sdb1
> > 
> > smartctl version 5.20 Copyright (C) 2002-3 Bruce Allen
> > Home page is http://smartmontools.sourceforge.net/
> > 
> > Device: MAXTOR   ATLAS15K_73SCA   Version: DT60
> > Serial number: C80356MK
> > Device type: disk
> > Local Time is: Thu Oct  9 19:05:50 2003 EEST
> > Device supports SMART and is Enabled
> > Temperature Warning Enabled
> > SMART Health Status: OK
> > Current Drive Temperature:     36 C
> > Manufactured in week 00 of year 2000
> > Current start stop count:      182 times
> > Recommended start stop count:  4294967295 times
> 
> Perhaps I should change that to "Recommended maximum ...".
> Anyway the number is crazy and is 0xffffffff in hex. The
> standard gives them no latitude to do that.
> 
> > Error counter log:
> >           Errors Corrected    Total      Total   Correction     Gigabytes    
> > Total
> >               delay:       [rereads/    errors   algorithm      processed    
> > uncorrected
> >             minor | major  rewrites]  corrected  invocations   [10^9 
> > bytes]  errors
> > read:     349618        0         0         0          0        772.206           
> > 0
> > write:         0        0         0         0          0        668.155           
> > 0

By the way, what those 'delay minor errors' could mean? Is it harmless? 

> > Non-medium error count:        4
> > No self-tests have been logged
> > Long (extended) Self Test duration: 2056 seconds [34.3 minutes]
> 
> Perhaps you should do a self test (e.g. 'smartctl -t short /dev/sdf')
> to see if the result turns up after the second last line.
After 'smartctl -t short' results are still the same

> Anyway, how does the Atlas 15k perform?
Can't say too much, currently I am testing software RAID-5 by 6 Atlas 15k 
73Gb disks. All disks are Ultra320 but I have Adaptec 39160D and disks are 
running Ultra160 mode. As well testing PC is pretty poor (old Intel 
Celeron 433MHz with 256Mb of memory). Later I will connect RAID to 
server station with Adaptec 39320D and could tell more.


now hdparm gives
# hdparm -t /dev/sdg

/dev/sdg:
 Timing buffered disk reads:  64 MB in  2.04 seconds = 31.37 MB/sec


for short comparison on the other channel old IBM DDRS-34560 gives 
# hdparm -t /dev/sda

/dev/sda:
 Timing buffered disk reads:  64 MB in  5.10 seconds = 12.55 MB/sec


Later, if need, I could say more test info about Ultra320 mode.

But behind this we had problems, two new Atlas 15k disks just crushed with 
many bad blocks after some weeks of hard using. It was this summer, then 
we lost our RAID. Now we got by warranty two new and I am testing it.   

# badblocks -b 4096 -s -w -c 512 /dev/sd?1

gave no error :) 

Ivan


--------- Ivan Degtyarenko ----------- imd@... ----------

  Laboratory of Physics        Helsinki University of Technology
  tel +358-9-451 3103          P.O.Box 1100
  fax +358-9-451 3116          02015 Espoo, Finland

---------------------------------- http://www.fyslab.hut.fi/ ------