From: Luciano <lu...@jo...> - 2010-01-02 13:50:51
Attachments:
smartctl-a.txt
|
Hi, I would like to ask to have the following SSD added to the DB. I've tested with the SVN build (reports smartctl 5.40 2010-01-01 r3025). I followed the wiki guide for getting information for the drive. After running the short self-test, and 'smartcl -c' showing that there is 0% of the test remaining, the selftest log is showing: smartctl 5.40 2010-01-01 r3025 [x86_64-pc-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF READ SMART DATA SECTION === Warning! SMART Self-Test Log Structure error: invalid SMART checksum. SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] So I don't know if something is wrong... This is an SSD drive btw. I've attached smartctl -a output. Thanks in advance! |
From: Christian F. <Chr...@t-...> - 2010-01-03 13:22:17
Attachments:
smart_drivedb.h
|
Luciano wrote: > I would like to ask to have the following SSD added to the DB. I've > tested with the SVN build (reports smartctl 5.40 2010-01-01 r3025). I > followed the wiki guide for getting information for the drive. After > running the short self-test, and 'smartcl -c' showing that there is 0% > of the test remaining, the selftest log is showing: > > smartctl 5.40 2010-01-01 r3025 [x86_64-pc-linux-gnu] (local build) > Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net > > === START OF READ SMART DATA SECTION === > Warning! SMART Self-Test Log Structure error: invalid SMART checksum. > SMART Self-test log structure revision number 1 > No self-tests have been logged. [To run self-tests, use: smartctl -t] > > > So I don't know if something is wrong... This is an SSD drive btw. > Self-tests are probably unsupported or buggy. > I've attached smartctl -a output. > The attributes of this drive look very similar to the attributes from OZC SSD drives: 64-bit raw values, no normalized values. Could you please test the attached database entry. The file can be read with the -B option of smartctl. If the path is SYSCONFDIR/smart_drivedb.h (usually /etc/smart_drivedb.h or /usr/local/etc/smart_drivedb.h), no option is needed. See man page. Are the raw values and their description reasonable? What is the output of 'smartctl -l directory /dev/ice' ? Thanks, Christian |
From: Luciano <lu...@jo...> - 2010-01-03 23:50:17
Attachments:
newsmartctl.txt
|
> The attributes of this drive look very similar to the attributes from OZC > SSD drives: 64-bit raw values, no normalized values. Yes I think it uses the same controller .. I think I read on overclockers.co.uk. > > Could you please test the attached database entry. > > The file can be read with the -B option of smartctl. If the path is > SYSCONFDIR/smart_drivedb.h (usually /etc/smart_drivedb.h or > /usr/local/etc/smart_drivedb.h), no option is needed. See man page. > smartctl -a -B .. It's attached > Are the raw values and their description reasonable? > I'm afraid I'm not entirely sure how to interpret these values. The last two attributes are still showing 'unknown', so I guess those are wrong: 210 Unknown_Attribute 0x0000 --- --- --- Old_age Offline - 237 211 Unknown_Attribute 0x0000 --- --- --- Old_age Offline - 0 Also, VALUE/WORST/THRESH are all blank. I would have thought these should have something in them. > What is the output of 'smartctl -l directory /dev/ice' ? tulum ~ # smartctl -l directory /dev/sda smartctl 5.40 2010-01-01 r3025 [x86_64-pc-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net General Purpose Logging (GPL) feature set supported General Purpose Log Directory Version 1 SMART Log Directory Version 1 [multi-sector log support] GP/S Log at address 0x00 has 1 sectors [Log Directory] GP/S Log at address 0x01 has 1 sectors [Summary SMART error log] GP/S Log at address 0x02 has 51 sectors [Comprehensive SMART error log] GP/S Log at address 0x03 has 77 sectors [Ext. Comprehensive SMART error log] GP/S Log at address 0x06 has 1 sectors [SMART self-test log] GP/S Log at address 0x07 has 1 sectors [Extended self-test log] GP/S Log at address 0x09 has 1 sectors [Selective self-test log] GP/S Log at address 0x10 has 1 sectors [NCQ Command Error] GP/S Log at address 0x11 has 1 sectors [SATA Phy Event Counters] GP Log at address 0xa0 has 4096 sectors [Device vendor specific log] I also tried the extended error log, but got gibberish again: tulum ~ # smartctl -l xerror -B ~luciano/Downloads/smart_drivedb.h /dev/sda smartctl 5.40 2010-01-01 r3025 [x86_64-pc-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF READ SMART DATA SECTION === General Purpose Logging (GPL) feature set supported Warning! SMART Extended Comprehensive Error Log Structure (77/77) error: invalid SMART checksum. SMART Extended Comprehensive Error Log Version: 49 (77 sectors) No Errors Logged Any ideas? Cheers. > > Thanks, > Christian > > |
From: Christian F. <Chr...@t-...> - 2010-01-04 20:56:21
|
Luciano wrote: >> Could you please test the attached database entry. >> >> The file can be read with the -B option of smartctl. If the path is >> SYSCONFDIR/smart_drivedb.h (usually /etc/smart_drivedb.h or >> /usr/local/etc/smart_drivedb.h), no option is needed. See man page. >> >> > smartctl -a -B .. It's attached > > The output makes sense. DB entry is now included in drivedb.h >> Are the raw values and their description reasonable? >> >> > I'm afraid I'm not entirely sure how to interpret these values. The > last two attributes are still showing 'unknown', so I guess those are > wrong: > > 210 Unknown_Attribute 0x0000 --- --- --- Old_age > Offline - 237 > 211 Unknown_Attribute 0x0000 --- --- --- Old_age > Offline - 0 > > These names are not wrong, we actually don't know the meaning of these attributes :-) > Also, VALUE/WORST/THRESH are all blank. I would have thought these > should have something in them. > > Traditional SMART provides 48-bit raw values. This firmware uses the VALUE and WORST bytes for a 64-bit raw value. Therefore, smartctl prints '---' for VALUE, WORST and THRESH. The FLAG value seams to be useless also. > I also tried the extended error log, but got gibberish again: > > tulum ~ # smartctl -l xerror -B ~luciano/Downloads/smart_drivedb.h /dev/sda > smartctl 5.40 2010-01-01 r3025 [x86_64-pc-linux-gnu] (local build) > Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net > > === START OF READ SMART DATA SECTION === > General Purpose Logging (GPL) feature set supported > Warning! SMART Extended Comprehensive Error Log Structure (77/77) > error: invalid SMART checksum. > SMART Extended Comprehensive Error Log Version: 49 (77 sectors) > No Errors Logged > > Any ideas? > > This is not unusual: If a log is still clean, the checksums might be not valid. Thanks, Christian |