Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: Stephen Waters <heb@lu...> - 2004-01-15 15:35:56
how do I get my drive's data into the database?
smartmontools 5.26 (Debian 'unstable')
Device Model: Maxtor 94098H6
Serial Number: N60DL4AC
Firmware Version: BAC51KJ0
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 6
ATA Standard is: ATA/ATAPI-6 T13 1410D revision 0
Local Time is: Thu Jan 15 09:24:52 2004 CST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
On Fri, 2004-01-16 at 21:36, Bruce Allen wrote:
> This output looks a bit strange. Could you tell me, what OS and (if
> relevant) distribution are you using? What's the hardware platform?
MSI K8T Master2-FAR Motherboard (VIA K8T800 chipset)
Dual AMD Opteron 240
2GB DDR RAM
Maxtor 40GB Hard drive from a couple years ago
32-bit kernel, 32-bit apps
$ uname -a
Linux arrakeen 2.6.0-1-k7-smp #2 SMP Sun Jan 11 17:10:11 EST 2004 i686
Anything else I should include?
From: Phil Williams <phil@su...> - 2004-01-16 22:13:57
On Thu, Jan 15, 2004 at 09:35:46AM -0600, Stephen Waters wrote:
> how do I get my drive's data into the database?
There's an FAQ on the smartmontools homepage (http://smartmontools.sourceforge.net/)
Here's the answer to that question:
If your drive is not in the database, then the names of the Attributes
(displayed in the ID# column of smartctl -A /dev/hd?) and the format of the
the raw Attribute values shown in the RAW_VALUE column may be incorrect.
This is mostly cosmetic: the essential drive health monitoring/testing
functionality of smartmontools does not depend upon the database.
To have your drive added to the database, first use the command:
smartctl -t short /dev/hd?
to run a short self-test on the drive, and wait a few minutes for the test
to complete. Then email the output from:
smartctl -a /dev/hd?
to smartmontools-database as an email attachment. The timestamp in the
self-test log will help us to determine whether Attribute 9 is being used
to store the lifetime in hours, minutes, or seconds.
If you need to use any of the vendor-specific display options (-v options)
with the drive, or if any of the Attributes are behaving strangely, please
include that information as well.