gmane.linux.utilities.smartmontools

help needed

american eagle — 2008-12-02T17:20:06

------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________ Smartmontools-support mailing list Smartmontools-support< at >lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/smartmontools-support

Question for smartmontool users (OFFLINEtesting)..

Justin Piszcz — 2008-11-19T18:27:29

How often do you run offline tests and how much time do you allocate for them? Total time to complete Offline data collection: (4800) seconds How do you fit offline schedules into your short/long schedules, is it best to run them directly after a long test? Does anyone have a link to in-depth documentation on offline testing? Justin. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

state persistence mode

Florian Effenberger — 2008-11-18T15:31:41

Hello, I'm running smartd with the setting of DEVICESCAN -a -d sat -m root -n standby,q -M daily \ -W 0,0,40 -S on -o on -I 194 -I 231 -I 9 -s \ (S/../../(1|2|3|4|5|6)/05|C/../../7/05|L/../../7/10|O/../../7/15) so long-time scans are run on Sunday. Unfortunately, this machine isn't online 24x7, so sometimes it doesn't run at the planned test time. The manpage of smartd talks about a "state persistence mode" I could use for this case. I searched for more information, but to no avail. What can I do to get my scans done if the machine isn't online at the specified test time? Something like anacron, but only for smartmontools? :-) Thanks, Florian ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

a temperature conversion question

Alfred Ganz — 2008-11-16T02:27:16

Ladies and Gentlemen, I am using smartd amd smartctl (from smartmontools-5.38-4.1 under Linux 2.6.18-92.1.10.el5) on a Maxtor OneTouch USB disk (Model Family: Seagate Barracuda 7200.10 family) on which I have reported a problem with SMART STATUS reporting (which is due to a problem with the handling of the status return length in usb-storage). Except for this, things work just fine. Note that I use the disk as backup, so it is only spun up while the backup is done. However, I have observed strange reporting of the RAW VALUE for "190 Airflow_Temperature_Cel". When I use smartctl, the RAW VALUE is the same as the one for "Temperature_Celsius", with a value around 40, but the log from smartd reports the 190 values significantly higher (somewhere around 60), and the 194 values the same as smartctl. I will append an example. It looks to me like the 190 RAW VALUES reported by smartctl may not be the VALUE field of the 190 line, whereas the 190 value reported by smartd seems to match that VALUE field. Question: what is the reason for these differences. What other info should I provide that might help to clarify this? Thanks for your help, AG --------------------------------------------------------------------------- [root< at >network config]# smartctl -a -T permissive -d sat,12 /dev/sdb smartctl version 5.38 [i686-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.10 family Device Model: ST3250410AS Serial Number: 6RY3WRG6 Firmware Version: 3.AAC User Capacity: 250,059,350,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sat Nov 15 20:28:00 2008 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled ...... 190 Airflow_Temperature_Cel 0x0022 055 048 045 Old_age Always - 45 (Lifetime Min/Max 34/45) 194 Temperature_Celsius 0x0022 045 052 000 Old_age Always - 45 (0 20 0 0) ...... ------------------- from /etc/smartd.conf --------------------------------- # the backup disk /dev/sdb -d sat,12 -n standby,q -s (S/../.././03) -a -m root ------------------- from the log files ------------------------------------ Nov 15 20:30:20 network smartd[3028]: Device: /dev/sdb, SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 63 to 55 Nov 15 20:30:20 network smartd[3028]: Device: /dev/sdb, SMART Usage Attribute: 194 Temperature_Celsius changed from 37 to 45 --------------------------------------------------------------------------- [root< at >network config]# smartctl -a -T permissive -d sat,12 /dev/sdb smartctl version 5.38 [i686-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.10 family Device Model: ST3250410AS Serial Number: 6RY3WRG6 Firmware Version: 3.AAC User Capacity: 250,059,350,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sat Nov 15 20:30:42 2008 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled ...... 190 Airflow_Temperature_Cel 0x0022 055 048 045 Old_age Always - 45 (Lifetime Min/Max 34/45) 194 Temperature_Celsius 0x0022 045 052 000 Old_age Always - 45 (0 20 0 0) ...... ---------------------------------------------------------------------------

Usb stick and SMART

Michal Hlavinka — 2008-11-15T11:34:26

Hi, I've got interesting report about usb stick SanDisk Cruzer 8GB which *seems* to support smart. Is it possible at all? AFAIK I've read something about usb sticks are forbidden to support this? For more information see https://bugzilla.redhat.com/show_bug.cgi?id=471235 Cheers, Michal ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

Short Test Never Completes

Kevin Colbert — 2008-11-13T15:25:31

smartmontools offline test aborts,other tools work

Ken Witherow — 2008-11-12T21:56:43

Linux 2.6.27, smartmontools 5.38 on AMD64 with MCP55 controller (sata_nv) It takes about 16 hours to do a short test with smartmontools, the long test aborts sometime after starting it. The last time it completed successfully with smartmontools was July 28 under 2.6.26 (I haven't had a chance to go back and test to see if older kernels fix it). However, the drive passes both types of tests with the seagate diagnostic tools in the expected time, both under DOS and in Linux. My other drives (IDE) successfully complete their tests with smartmontools still. hdparm -Tt /dev/sdb /dev/sdb: Timing cached reads: 1060 MB in 2.00 seconds = 530.06 MB/sec Timing buffered disk reads: 238 MB in 3.00 seconds = 79.31 MB/sec Seagate Seatools Enterprise version 2.54 (sg driver version = ) 1-800-SEAGATE www.seagate.com Copyright (c)2001, Peripheral Test Instruments, LLC (303)763-7488 www.scsitools.com Wed Nov 5 20:36:59 2008 Starting 10 % Generic Short Test on drive /dev/sg2 Wed Nov 5 20:36:59 2008 -Starting 30 second sequential reads from block 0 on drive /dev/sg2 Wed Nov 5 20:37:12 2008 Generic Short Test PASSED on drive /dev/sg2 ------------------------------------------------------------- Wed Nov 5 20:37:31 2008 Entering Generic Long Test on drive /dev/sg2 Wed Nov 5 21:30:47 2008 Generic Long Test PASSED on drive /dev/sg2 smartctl -a /dev/sdb smartctl version 5.38 [x86_64-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.10 family Device Model: ST3250410AS Serial Number: 9RY0BPS2 Firmware Version: 3.AAC User Capacity: 250,059,350,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Fri Nov 7 20:32:11 2008 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 430) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 64) minutes. SCT capabilities: (0x0001) SCT Status supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 114 100 006 Pre-fail Always - 0 3 Spin_Up_Time 0x0003 098 097 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 28 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 081 060 030 Pre-fail Always - 144511060 9 Power_On_Hours 0x0032 090 090 000 Old_age Always - 8783 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 28 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 061 056 045 Old_age Always - 39 (Lifetime Min/Max 33/44) 194 Temperature_Celsius 0x0022 039 044 000 Old_age Always - 39 (0 23 0 0) 195 Hardware_ECC_Recovered 0x001a 063 053 000 Old_age Always - 69806628 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0 202 TA_Increase_Count 0x0032 100 253 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 8754 - # 2 Short offline Aborted by host 90% 8736 - # 3 Short offline Aborted by host 80% 8736 - # 4 Short offline Completed without error 00% 8735 - # 5 Extended offline Aborted by host 90% 8724 - # 6 Extended offline Aborted by host 90% 8717 - # 7 Extended offline Aborted by host 90% 8673 - # 8 Extended offline Aborted by host 90% 8504 - # 9 Extended offline Aborted by host 90% 8337 - #10 Extended offline Interrupted (host reset) 80% 8164 - #11 Extended offline Interrupted (host reset) 90% 7872 - #12 Extended offline Aborted by host 80% 7835 - #13 Extended offline Aborted by host 90% 7521 - #14 Extended offline Aborted by host 90% 7514 - #15 Extended offline Aborted by host 90% 7352 - #16 Extended offline Aborted by host 90% 7184 - #17 Extended offline Aborted by host 90% 7017 - #18 Extended offline Aborted by host 90% 6849 - #19 Extended offline Aborted by host 90% 6522 - #20 Extended offline Completed without error 00% 6350 - #21 Extended offline Completed without error 00% 6182 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

Anyone tell me..

Jon Hardcastle — 2008-11-12T15:43:57

What is wrong with this: DEVICESCAN -d sat -s (S/../.././06|L/../.././15) -m my< at >emailaddy.co.uk -W 2,40,45 -M test -o on -f -H -l selftest -l error -C 197 -U 198 the short test works ok, but the Long test never seeems to run.. originally i wanted this to run only on sunday but changed it to daily to test it... ----------------------- N: Jon Hardcastle E: Jon< at >eHardcastle.com '..Be fearful when others are greedy, and be greedy when others are fearful.' ----------------------- ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

Compilling smartmontools on FreeBSD

Сергей Казуров — 2008-11-12T14:57:25

Good day! I`m FreeBSD user (version - 6.2 release) and when i run command "make" i get following error: os_freebsd.o os_freebsd.cpp os_freebsd.cpp: In function `int highpoint_command_interface(int, smart_command_set, int, char*)': os_freebsd.cpp:279: error: a function-definition is not allowed here before '{' token os_freebsd.cpp:461: error: a function-definition is not allowed here before '{' token os_freebsd.cpp:564: error: a function-definition is not allowed here before '{' token os_freebsd.cpp:601: error: a function-definition is not allowed here before '{' token os_freebsd.cpp:851: error: a function-definition is not allowed here before '{' token os_freebsd.cpp:934: error: a function-definition is not allowed here before '{' token os_freebsd.cpp:1028: error: a function-definition is not allowed here before '{' token os_freebsd.cpp:1046: error: a function-definition is not allowed here before '{' token os_freebsd.cpp:1122: error: a function-definition is not allowed here before '{' token os_freebsd.cpp:924: warning: unused variable 'fbsd_dev_prefix' os_freebsd.cpp:925: warning: unused variable 'fbsd_dev_ata_disk_prefix' os_freebsd.cpp:926: warning: unused variable 'fbsd_dev_scsi_disk_plus' os_freebsd.cpp:927: warning: unused variable 'fbsd_dev_scsi_tape1' os_freebsd.cpp:928: warning: unused variable 'fbsd_dev_scsi_tape2' os_freebsd.cpp:929: warning: unused variable 'fbsd_dev_scsi_tape3' os_freebsd.cpp:930: warning: unused variable 'fbsd_dev_twe_ctrl' os_freebsd.cpp:931: warning: unused variable 'fbsd_dev_twa_ctrl' os_freebsd.cpp:932: warning: unused variable 'fbsd_dev_cciss' os_freebsd.cpp:1033: warning: unused variable 'bytes' os_freebsd.cpp:1129: error: expected `}' at end of input os_freebsd.cpp: At global scope: os_freebsd.cpp:47: warning: 'filenameandversion' defined but not used os_freebsd.cpp:62: warning: 'int parse_ata_chan_dev(const char*, freebsd_dev_channel*)' declared `static' but never defined *** Error code 1 What i do wrong? Best regards, Sergey Kazurov. mailto:kazurovsg< at >yandex.ru ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

Head_Flying_Hours FAILING_NOW

Marcelo Aguila — 2008-11-11T19:59:27

Hi, guys. Today I've got a window indicating a problem with Head_Flying_Hours. I'm running Suse 10.3 in a Dell Latitude D830. Searching in internet I found a page that sais this is a critical problem, but I'm not sure if this is true and if this problem has solution or maybe I should ask for replacement of my disk because I bought the laptop this year in april. Additionally the test shows problems with IDs 241 and 242. Any hint? Regards, Rm. Here is my smartctl -a /dev/sda output ----------------------- CUT HERE ------------------------------ smartctl version 5.37 [i686-suse-linux-gnu] Copyright (C) 2002-6 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: ST9120823ASG Serial Number: 5NJ0TSTD Firmware Version: 3.ADD User Capacity: 120,034,123,776 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 7 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Tue Nov 11 14:43:43 2008 CLST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED See vendor-specific Attribute list for marginal Attributes. General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 426) seconds. Offline data collection capabilities: (0x53) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 111) minutes. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 100 253 006 Pre-fail Always - 0 3 Spin_Up_Time 0x0003 098 098 085 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 543 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 063 060 030 Pre-fail Always - 60168660320 9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 2117 10 Spin_Retry_Count 0x0013 100 100 034 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 554 187 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 189 Unknown_Attribute 0x003a 100 100 000 Old_age Always - 0 190 Temperature_Celsius 0x0022 058 052 045 Old_age Always - 707264554 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 553 193 Load_Cycle_Count 0x0022 053 053 000 Old_age Always - 94481 194 Temperature_Celsius 0x001a 042 048 000 Old_age Always - 42 (Lifetime Min/Max 0/13) 195 Hardware_ECC_Recovered 0x0012 087 063 000 Old_age Always - 155561650 197 Current_Pending_Sector 0x0010 100 100 000 Old_age Offline - 0 198 Offline_Uncorrectable 0x003e 100 100 000 Old_age Always - 0 199 UDMA_CRC_Error_Count 0x0000 200 200 000 Old_age Offline - 0 200 Multi_Zone_Error_Rate 0x0032 100 253 000 Old_age Always - 0 202 TA_Increase_Count 0x0000 100 253 000 Old_age Offline - 0 240 Head_Flying_Hours 0x0000 000 000 000 Old_age Offline FAILING_NOW 154335354816590 241 Unknown_Attribute 0x0000 000 000 000 Old_age Offline FAILING_NOW 1073185442 242 Unknown_Attribute 0x0000 000 000 000 Old_age Offline FAILING_NOW 754224 254 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 2117 - # 2 Short offline Completed without error 00% 1 - # 3 Short offline Completed without error 00% 0 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

Finding bad sector in a software RAID

Bruce Allen — 2008-11-11T07:16:48

Here is a nice description of tracking down an UNC sector on a Linux software RAID device. Apparently it was subsequently corrected by the RAID driver. http://www.roeckx.be/journal/Finding_which_sector_belongs_to_which_file_on_a_RAID_device_.html ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

Question with --offlineauto=on.

Justin Piszcz — 2008-11-10T23:40:09

There are only 13 results on the mailing list for information about offlineauto in reference to smartctl. Searching mail lists gives 13 results.. Do most people on this list utilize offlineauto on traditional SATA, whether it be non-enterprise OR enterprise disks? Do you find more frequent failures with offlineauto enabled or disabled? There is some various discussion but I do not see the pros/cons of enabling it vs. disabling it. I can tell when it is doing its scans, once every four hours, the disks are quite noisy :) But it does appear when system or user I/O takes hold, it appears to take priority over the 'background' offline scan. Does anyone have any metrics on having it off vs. on for SATA drives? I know more expensive 10k-15k RPM UltraSCSI/SAS disks will have automatic backround media scans etc but specifically for SATA, do most people on this list use this option, or? Justin. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

ST650211CF Broken SMART?

Weedy — 2008-11-08T16:08:00

If I'm reading this right this drive should have burst into flames or something. So far I've had no trouble at all with it. So do I ignore SMART or junk it? # smartctl -d ata --all -T permissive /dev/sda smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: ST650211CF Serial Number: 3ME15JQ1 Firmware Version: 3.04 User Capacity: 5,000,970,240 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 1 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sat Nov 8 10:54:08 2008 EST SMART is only available in ATA Version 3 Revision 3 or greater. We will try to proceed in spite of this. SMART support is: Unavailable - Packet Interface Devices [this device: Write-once (optical disk)] don't support ATA SMART SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: FAILED! Drive failure expected in less than 24 hours. SAVE ALL DATA. See vendor-specific Attribute list for failed Attributes. General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 420) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. No General Purpose Logging support. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 28) minutes. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 056 050 025 Pre-fail Always - 59402560 3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 091 091 020 Old_age Always - 9686 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 1 7 Seek_Error_Rate 0x000f 024 019 030 Pre-fail Always FAILING_NOW 72039490298986 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 41 10 Spin_Retry_Count 0x0012 100 081 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 091 091 020 Old_age Always - 9696 192 Power-Off_Retract_Count 0x0032 001 001 000 Old_age Always - 4294961235 193 Load_Cycle_Count 0x0032 092 092 000 Old_age Always - 17639 194 Temperature_Celsius 0x0022 024 046 000 Old_age Always - 24 (Lifetime Min/Max 8/46) 195 Hardware_ECC_Recovered 0x001a 100 253 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 2 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0 202 TA_Increase_Count 0x0032 100 253 000 Old_age Always - 0 SMART Error Log Version: 1 ATA Error Count: 31 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 31 occurred at disk power-on lifetime: 24 hours (1 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 0f f0 a2 00 e0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- e0 00 10 00 10 a1 00 00 00:00:00.009 STANDBY IMMEDIATE e0 00 10 00 e0 a0 00 00 00:00:00.016 STANDBY IMMEDIATE e0 00 01 00 89 00 00 00 00:00:00.000 STANDBY IMMEDIATE e0 00 01 00 89 00 00 00 00:00:00.033 STANDBY IMMEDIATE e0 00 0b 00 7e 00 00 00 00:00:00.000 STANDBY IMMEDIATE Error 30 occurred at disk power-on lifetime: 24 hours (1 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 0f f0 a2 00 e0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- e0 00 10 00 10 a1 00 00 00:00:00.009 STANDBY IMMEDIATE e0 00 10 00 e0 a0 00 00 00:00:00.016 STANDBY IMMEDIATE e0 00 01 00 89 00 00 00 00:00:00.000 STANDBY IMMEDIATE e0 00 01 00 89 00 00 00 00:00:00.033 STANDBY IMMEDIATE e0 00 0b 00 7e 00 00 00 00:00:00.000 STANDBY IMMEDIATE Error 29 occurred at disk power-on lifetime: 24 hours (1 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 0f f0 a2 00 e0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- e0 00 10 00 10 a1 00 00 00:00:00.009 STANDBY IMMEDIATE e0 00 10 00 e0 a0 00 00 00:00:00.016 STANDBY IMMEDIATE e0 00 01 00 89 00 00 00 00:00:00.000 STANDBY IMMEDIATE e0 00 01 00 89 00 00 00 00:00:00.033 STANDBY IMMEDIATE e0 00 0b 00 7e 00 00 00 00:00:00.000 STANDBY IMMEDIATE Error 28 occurred at disk power-on lifetime: 24 hours (1 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 0f f0 a2 00 e0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- e0 00 10 00 10 a1 00 00 00:00:00.008 STANDBY IMMEDIATE e0 00 10 00 e0 a0 00 00 00:00:00.016 STANDBY IMMEDIATE e0 00 01 00 89 00 00 00 00:00:00.000 STANDBY IMMEDIATE e0 00 01 00 89 00 00 00 00:00:00.033 STANDBY IMMEDIATE e0 00 0b 00 7e 00 00 00 00:00:00.000 STANDBY IMMEDIATE Error 27 occurred at disk power-on lifetime: 24 hours (1 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 0f f0 a2 00 e0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- e0 00 10 00 10 a1 00 00 00:00:00.009 STANDBY IMMEDIATE e0 00 10 00 e0 a0 00 00 00:00:00.016 STANDBY IMMEDIATE e0 00 01 00 89 00 00 00 00:00:00.000 STANDBY IMMEDIATE e0 00 01 00 89 00 00 00 00:00:00.033 STANDBY IMMEDIATE e0 00 0b 00 7e 00 00 00 00:00:00.000 STANDBY IMMEDIATE SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 40 - Warning! SMART Selective Self-Test Log Structure error: invalid SMART checksum. SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

Interpretation of the S.M.A.R.T. error log(smartctl -l error)

Jens Wolter — 2008-11-07T09:09:17

Hello list, when im downloading a big File (~700MB) to my only HD (/dev/sda, SATA2), or sometimes for no apparent reason at all, my system freezs. After i reboot i have those 2 Errors in my S.M.A.R.T. error log (with: smartctl -d ata -l error /dev/sda ): --------schnipp-------- Error 692 occurred at disk power-on lifetime: 3624 hours (151 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 10 51 01 6e e2 42 e5 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 37 00 01 6e e2 42 e5 00 00:14:02.472 SET MAX ADDRESS EXT 27 00 00 6e e2 42 e0 00 00:14:02.472 READ NATIVE MAX ADDRESS EXT 37 00 00 6e e2 42 e5 00 00:14:08.279 SET MAX ADDRESS EXT 27 00 01 6e e2 42 e0 00 00:14:08.220 READ NATIVE MAX ADDRESS EXT 37 00 01 6e e2 42 e5 00 00:14:08.004 SET MAX ADDRESS EXT Error 691 occurred at disk power-on lifetime: 3624 hours (151 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 10 51 01 6e e2 42 e5 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 37 00 01 6e e2 42 e5 00 00:14:02.472 SET MAX ADDRESS EXT 27 00 00 6e e2 42 e0 00 00:14:02.472 READ NATIVE MAX ADDRESS EXT 37 00 00 6e e2 42 e5 00 00:14:02.472 SET MAX ADDRESS EXT 27 00 01 af ea 42 e0 00 00:14:02.471 READ NATIVE MAX ADDRESS EXT 29 00 01 af ea 42 e0 00 00:14:02.471 READ MULTIPLE EXT --------schnapp-------- You can see the complete Output of "smartctl -d ata -a /dev/sda" at http://debian.pastebin.com/m3f3aabc5 The Disk seems to be sane, it passed all Tests!? Can somebody tell me, what S.M.A.R.T. tries to tell me or whats wrong with my HD respectively? MfG Jens Wolter PS: Is this the right use of the Word "respectively"?

unstable arc1261 + smartmontools

Artem Bokhan — 2008-10-31T13:42:56

Smartd rarely reports errors on different disks Oct 31 14:32:40 smartd[10038]: Device: /dev/sg1 [areca_01], failed to read SMART Attribute Data Oct 31 15:32:41 smartd[10038]: Device: /dev/sg1 [areca_01], failed to read SMART Attribute Data Oct 31 16:32:40 smartd[10038]: Device: /dev/sg1 [areca_01], failed to read SMART Attribute Data Oct 31 16:32:41 smartd[10038]: Device: /dev/sg1 [areca_02], failed to read SMART Attribute Data Oct 31 17:32:40 smartd[10038]: Device: /dev/sg1 [areca_01], failed to read SMART Attribute Data Oct 31 17:32:41 smartd[10038]: Device: /dev/sg1 [areca_05], failed to read SMART Attribute Data Oct 31 18:02:41 smartd[10038]: Device: /dev/sg1 [areca_07], failed to read SMART Attribute Data Oct 31 18:32:40 smartd[10038]: Device: /dev/sg1 [areca_01], failed to read SMART Attribute Data __________ The following warning/error was logged by the smartd daemon: Device: /dev/sg1 [areca_06], Read SMART Self-Test Log Failed For details see host's SYSLOG (default: /var/log/messages). You can also use the smartctl utility for further investigation. No additional email messages about this problem will be sent. __________ The following warning/error was logged by the smartd daemon: Device: /dev/sg1 [areca_05], not capable of SMART self-check For details see host's SYSLOG (default: /var/log/messages). You can also use the smartctl utility for further investigation. No additional email messages about this problem will be sent. __________ The following warning/error was logged by the smartd daemon: Device: /dev/sg1 [areca_04], Read SMART Error Log Failed For details see host's SYSLOG (default: /var/log/messages). You can also use the smartctl utility for further investigation. No additional email messages about this problem will be sent. Linux: Ubuntu server LTS 8.x smartd.conf: /dev/sg1 -d areca,1 -a -m postmaster< at >ngs.ru /dev/sg1 -d areca,2 -a -m postmaster< at >ngs.ru /dev/sg1 -d areca,3 -a -m postmaster< at >ngs.ru /dev/sg1 -d areca,4 -a -m postmaster< at >ngs.ru /dev/sg1 -d areca,5 -a -m postmaster< at >ngs.ru /dev/sg1 -d areca,6 -a -m postmaster< at >ngs.ru /dev/sg1 -d areca,7 -a -m postmaster< at >ngs.ru /dev/sg1 -d areca,8 -a -m postmaster< at >ngs.ru /dev/sg1 -d areca,9 -a -m postmaster< at >ngs.ru /dev/sg1 -d areca,10 -a -m postmaster< at >ngs.ru /dev/sg1 -d areca,11 -a -m postmaster< at >ngs.ru /dev/sg1 -d areca,12 -a -m postmaster< at >ngs.ru /dev/sg1 -d areca,13 -a -m postmaster< at >ngs.ru /dev/sg1 -d areca,14 -a -m postmaster< at >ngs.ru arc: Controller Name ARC-1261 Firmware Version V1.46 2008-08-06 BOOT ROM Version V1.45 2008-3-14 Serial Number Y826CAAYAR601248 Unit Serial # Main Processor 800MHz IOP341 C1 CPU ICache Size 32KBytes CPU DCache Size 32KBytes/Write Back CPU SCache Size 512KBytes/Write Back System Memory 256MB/533MHz/ECC Current IP Address 172.16.1.21 smartd: smartd 5.39 2008-10-20 21:15 [x86_64-unknown-linux-gnu] (local build) Copyright (C) 2002-8 by Bruce Allen, http://smartmontools.sourceforge.net smartd comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under the terms of the GNU General Public License Version 2. See http://www.gnu.org for further details. CVS version IDs of files used to build this code are: Module: atacmdnames.cpp revision: 1.17 date: 2008/03/29 uses: atacmdnames.h revision: 1.6 date: 2008/03/04 Module: atacmds.cpp revision: 1.208 date: 2008/10/11 uses: atacmds.h revision: 1.102 date: 2008/10/11 uses: configure.in revision: 1.145 date: 2008/10/13 uses: extern.h revision: 1.59 date: 2008/08/23 uses: int64.h revision: 1.17 date: 2008/03/04 uses: scsiata.h revision: 1.6 date: 2008/07/25 uses: utility.h revision: 1.65 date: 2008/09/17 Module: knowndrives.cpp revision: 1.184 date: 2008/10/20 uses: atacmds.h revision: 1.102 date: 2008/10/11 uses: configure.in revision: 1.145 date: 2008/10/13 uses: extern.h revision: 1.59 date: 2008/08/23 uses: int64.h revision: 1.17 date: 2008/03/04 uses: knowndrives.h revision: 1.22 date: 2008/10/08 uses: utility.h revision: 1.65 date: 2008/09/17 Module: os_linux.cpp revision: 1.122 date: 2008/10/03 uses: atacmds.h revision: 1.102 date: 2008/10/11 uses: configure.in revision: 1.145 date: 2008/10/13 uses: int64.h revision: 1.17 date: 2008/03/04 uses: os_linux.h revision: 1.27 date: 2008/03/04 uses: scsicmds.h revision: 1.67 date: 2008/07/25 uses: utility.h revision: 1.65 date: 2008/09/17 Module: scsicmds.cpp revision: 1.97 date: 2008/07/25 uses: configure.in revision: 1.145 date: 2008/10/13 uses: extern.h revision: 1.59 date: 2008/08/23 uses: int64.h revision: 1.17 date: 2008/03/04 uses: scsicmds.h revision: 1.67 date: 2008/07/25 uses: utility.h revision: 1.65 date: 2008/09/17 Module: smartd.cpp revision: 1.430 date: 2008/10/13 uses: atacmds.h revision: 1.102 date: 2008/10/11 uses: configure.in revision: 1.145 date: 2008/10/13 uses: extern.h revision: 1.59 date: 2008/08/23 uses: int64.h revision: 1.17 date: 2008/03/04 uses: knowndrives.h revision: 1.22 date: 2008/10/08 uses: scsicmds.h revision: 1.67 date: 2008/07/25 uses: utility.h revision: 1.65 date: 2008/09/17 Module: utility.cpp revision: 1.74 date: 2008/09/13 uses: configure.in revision: 1.145 date: 2008/10/13 uses: int64.h revision: 1.17 date: 2008/03/04 uses: utility.h revision: 1.65 date: 2008/09/17 smartmontools release 5.39 dated 2008/03/10 at 10:44:07 GMT smartmontools build host: x86_64-unknown-linux-gnu smartmontools build configured: 2008/10/21 10:38:24 UTC smartd compile dated Oct 21 2008 at 17:38:32 smartmontools configure arguments: [no arguments given] ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

DEVICESCAN with wildcards

Jon Hardcastle — 2008-10-30T13:05:06

Hey, I have a raid5 array with 5 active and 1 spare hard drives. I have noticed since I increased to this from 4 actives only that when a long test is happening on all the drives at once i get degradation when streaming.. I wonder if i can use wildcards in the DEVICESCAN to specify alternate days for long health tests etc? Thanks. ----------------------- N: Jon Hardcastle E: Jon< at >eHardcastle.com '..Be fearful when others are greedy, and be greedy when others are fearful.' ----------------------- ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

How to fix bad blocks on software RAID?

Kai Schaetzl — 2008-10-28T19:31:19

I have two Samsung HD502IJ disks in a software RAID 1 array on CentOS 5. There are two mirrored partitions (/dev/md0, /dev/md1) on each, a small one for the xen hypervisor system and a large one with the remainder of the disk that is managed by LVM to get a bunch of smaller partitions for xen guests. Both disks show one Offline_Uncorrectable error at different offsets. Earlier this month I started to get errors from md in the logs about attempts for reallocation which seemed to fail for the first tries and then succeed (I can make the logs available if somebody thinks it would help). Since then it happened three or four more times. RAID has been fine all the time and shows as clean. I checked with smartctl -a -d ata, output can be found here: http://winware.org/smart/raid-error.sda.txt http://winware.org/smart/raid-error.sdb.txt The short offline tests then found the Offline_Uncorrectable errors and I also started getting two pending sectors in sda in the smartd messages. However, these disappeared after some time and only the two Offline_Uncorrectable errors remain. It looks to me that I have a bunch of closely related bad blocks (after offset 208645048) on sda that keep upping my Raw_Read_Error_Rate each time a reading attempt is made on them. (which happens somewhat frequently because of backups each day). (Forget about the error on sdb for now.) How can I trigger a reallocation so that these are not getting used anymore? If I understand correctly I cannot follow the bad block how-to exactly, or only partly? I read this thread http://sourceforge.net/mailarchive/message.php? msg_id=Pine.LNX.4.64.0806270653350.5844%40gc.phys.uwm.edu which suggests I could copy over good data from the other disk, but it's not clear to me at all how I find out where exactly the problem is and how I copy the correct data over. For identifying I followed the badblock how-to section concerning LVM and I think I have identified the correct bad block number for that LVM partition. However, I can't prove that there is a problem with the two methods from the how-to. 1. Using dd to read from that block and around it is always fine. This might be due to the RAID? As I'm reading from the LVM device on the RAID partition I might always get readable data. Would I need to destroy the RAID before I can get any errors? But if I remove RAID I also break the LVM that sits on it. How would I then access a specific LVM partition on a specific disk? 2. And when I try debugfs on it I always get debugfs: icheck 1000 Block Inode number 1000 even on a low number like 1000. Thanks for any hints. Kai ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

Inquiry: How to reliably get a SMART harddisk failure warning in a GUI system like MacOSX

Stefan Nowak — 2008-10-27T21:01:01

Hello SmartMonTool People! TARGET AUDIENCE: Those with Macintosh/Darwin knowledge. PREWORD: First I'd like to mention, that I extensively looked through the FAQ, searched through the mailinglist archive, and did not find anything related to my inquiry. Hence I decided to ask here. Please CC me in your answers, as I am not subscribed, and possibly integrate the answer to the inquiry to the manpage and respectively the online documentation, so that other MacOSX users also benefit from this. I offer to summarize that information, and possibly also put it to Mac-relevant pages (i.e macosxhints.com). Thanks for help already in advance! QUESTION: How do I have to setup my computer-environment, that I reliably get a warning, as soon as SMART detects a problem? Assumed that I am working in an OS which directly boots into a GUI, not showing me any CLI warnings while booting, and later on also works in a GUI. What's necessary that the warning _reliably_ comes to me as the MacOSX GUI user? Please also tell me the optimal polling, testing, etc settings, and why the default logpath is /var/run/smartd.pid rather than /var/log/ smartd.pid ENVIRONMENT: I have installed smartmontools via the MacPorts.org paket manager, and I am using version 5.38 on MacOSX 10.4.11 ASSUMPTIONS / IDEAS: I saw that the installation routine created: /Library/StartupItems/SMART I read the manpage for smartd, and saw that it either can send a message to SYSLOG or to the system MAIL daemon, but no option to simply execute a command, i.e. a GUI-based notification service. My idea on OSX would be to pass the message over to growl (a notification service) or an applescript, and that this really causes a floating window, which I reliable get to see, so that I cannot miss that information. ## Growl Notification smartd message output | growlnotify --sticky --priority 10 --message - ## Apple Script Notification smartd message output | osascript ~/bin/warning.scpt ## Content of warning.scpt ... Code which display a floating window with the error message ... Or shall I simply use something like: http://www.corecode.at/smartreporter/ which I guess is similar like: smartctl -H disk0 Shall I use both smartd and smartreporter, how do I correctly set them up to co-operate, or better only one? Pros/cons? Regards, Stefan Nowak, Vienna/Austria ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

smartd/smartctl offlining drives

Richard Scobie — 2008-10-28T03:37:19

I have 2 similarly specced machines with Fedora 9 installed using kernel 2.6.26.5-45.fc9.x86_64 and a 16 x SATA md RAID6 behind an LSISAS1068E SAS controller. Both are running a locally compiled version of Samba 3.0.29. If they are configured to start samba and smartd on boot, these two services are the last to start - samba directly followed by smartd. This results in the SAS controller progressively offlining each of the 16 drives in turn, as the SMART commands cause the controller to repeatedly reset each drive: Oct 25 12:39:13 storage smartd[3147]: Device: /dev/sdc, opened Oct 25 12:39:13 storage smartd[3147]: Device: /dev/sdc, not found in smartd database. Oct 25 12:39:19 storage kernel: mptscsih: ioc0: attempting task abort! (sc=ffff81022d0597c0) Oct 25 12:39:19 storage kernel: sd 8:0:0:0: [sdc] CDB: ATA command pass through(16): 85 08 0e 00 d5 00 01 00 01 00 4f 00 c2 00 b0 00 Oct 25 12:39:20 storage kernel: mptbase: ioc0: LogInfo(0x31140000): Originator={PL}, Code={IO Executed}, SubCode(0x0000) Oct 25 12:39:21 storage kernel: mptscsih: ioc0: task abort: SUCCESS (sc=ffff81022d0597c0) Oct 25 12:39:31 storage kernel: mptscsih: ioc0: attempting task abort! (sc=ffff81022d0597c0) Oct 25 12:39:31 storage kernel: sd 8:0:0:0: [sdc] CDB: Test Unit Ready: 00 00 00 00 00 00 Oct 25 12:39:32 storage kernel: mptbase: ioc0: LogInfo(0x31140000): Originator={PL}, Code={IO Executed}, SubCode(0x0000) Oct 25 12:39:32 storage kernel: mptscsih: ioc0: task abort: SUCCESS (sc=ffff81022d0597c0) Oct 25 12:39:32 storage kernel: mptscsih: ioc0: attempting target reset! (sc=ffff81022d0597c0) Oct 25 12:39:32 storage kernel: sd 8:0:0:0: [sdc] CDB: ATA command pass through(16): 85 08 0e 00 d5 00 01 00 01 00 4f 00 c2 00 b0 00 Oct 25 12:39:34 storage kernel: mptscsih: ioc0: Issue of TaskMgmt failed! Oct 25 12:39:34 storage kernel: mptscsih: ioc0: target reset: FAILED (sc=ffff81022d0597c0) Oct 25 12:39:34 storage kernel: mptscsih: ioc0: attempting bus reset! (sc=ffff81022d0597c0) Oct 25 12:39:34 storage kernel: sd 8:0:0:0: [sdc] CDB: ATA command pass through(16): 85 08 0e 00 d5 00 01 00 01 00 4f 00 c2 00 b0 00 Oct 25 12:39:43 storage kernel: mptscsih: ioc0: bus reset: SUCCESS (sc=ffff81022d0597c0) Oct 25 12:40:03 storage kernel: mptscsih: ioc0: attempting task abort! (sc=ffff81022d0597c0) Oct 25 12:40:03 storage kernel: sd 8:0:0:0: [sdc] CDB: Test Unit Ready: 00 00 00 00 00 00 Oct 25 12:40:04 storage kernel: mptbase: ioc0: LogInfo(0x31140000): Originator={PL}, Code={IO Executed}, SubCode(0x0000) Oct 25 12:40:04 storage kernel: mptscsih: ioc0: task abort: SUCCESS (sc=ffff81022d0597c0) Oct 25 12:40:04 storage kernel: mptscsih: ioc0: attempting host reset! (sc=ffff81022d0597c0) Oct 25 12:40:04 storage kernel: mptbase: ioc0: Initiating recovery Oct 25 12:40:19 storage kernel: mptscsih: ioc0: host reset: SUCCESS (sc=ffff81022d0597c0) Oct 25 12:40:19 storage kernel: sd 8:0:0:0: Device offlined - not ready after error recovery Oct 25 12:40:19 storage smartd[3147]: Device: /dev/sdc, Read SMART Error Log Failed Oct 25 12:40:19 storage smartd[3147]: Device: /dev/sdc, no SMART Error log; remove -l error Directive from smartd.conf Oct 25 12:40:19 storage smartd[3147]: Device: /dev/sdc, is SMART capable. Adding to "monitor" list. Oct 25 12:40:19 storage smartd[3147]: Device: /dev/sdd, opened Oct 25 12:40:19 storage smartd[3147]: Device: /dev/sdd, not found in smartd database. Oct 25 12:40:26 storage kernel: mptscsih: ioc0: attempting task abort! (sc=ffff81022d207b80) Oct 25 12:40:26 storage kernel: sd 8:0:1:0: [sdd] CDB: ATA command pass through(16): 85 08 0e 00 d5 00 01 00 01 00 4f 00 c2 00 b0 00 and so on until all 16 drives are down. If samba is disabled on boot, with smartd enabled and samba is then manually started later or smartd is disabled on boot, with samba enabled and smartd started manually, everything works perfectly - smartd and smartctl work perfectly. I am unsure exactly which component - samba, smartd or mpt driver is at fault here. A while back I posted a similar problem on the Redhat Bugzilla #452389, but at that stage I had not made the connection that starting samba and smartd simultaneously is causing the problem. Regards, Richard ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

Sata drive complains on schedules test.

Jon Hardcastle — 2008-10-28T08:53:01

I have noticed that it does appear (at least in the log entry) say that the test has run, but it will my dmesg buffer, messages log and emails me to say it has failed and cant run. Can someone please offer some advise? Thanks ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

Looking for a direct contact at Smartmontools

Christian Mueller — 2008-10-24T22:05:14