Screenshot instructions:
Windows
Mac
Red Hat Linux
Ubuntu
Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(50) |
Nov
(161) |
Dec
(84) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(84) |
Feb
(103) |
Mar
(54) |
Apr
(63) |
May
(44) |
Jun
(45) |
Jul
(44) |
Aug
(55) |
Sep
(15) |
Oct
(99) |
Nov
(101) |
Dec
(104) |
| 2004 |
Jan
(76) |
Feb
(98) |
Mar
(99) |
Apr
(130) |
May
(107) |
Jun
(79) |
Jul
(94) |
Aug
(164) |
Sep
(115) |
Oct
(125) |
Nov
(160) |
Dec
(84) |
| 2005 |
Jan
(72) |
Feb
(85) |
Mar
(55) |
Apr
(109) |
May
(64) |
Jun
(33) |
Jul
(71) |
Aug
(77) |
Sep
(84) |
Oct
(102) |
Nov
(106) |
Dec
(51) |
| 2006 |
Jan
(47) |
Feb
(58) |
Mar
(60) |
Apr
(106) |
May
(73) |
Jun
(65) |
Jul
(109) |
Aug
(103) |
Sep
(73) |
Oct
(57) |
Nov
(94) |
Dec
(62) |
| 2007 |
Jan
(61) |
Feb
(67) |
Mar
(90) |
Apr
(90) |
May
(77) |
Jun
(82) |
Jul
(75) |
Aug
(74) |
Sep
(63) |
Oct
(70) |
Nov
(60) |
Dec
(59) |
| 2008 |
Jan
(68) |
Feb
(113) |
Mar
(128) |
Apr
(89) |
May
(57) |
Jun
(88) |
Jul
(74) |
Aug
(43) |
Sep
(77) |
Oct
(106) |
Nov
(99) |
Dec
(82) |
| 2009 |
Jan
(126) |
Feb
(49) |
Mar
(47) |
Apr
(26) |
May
(38) |
Jun
(75) |
Jul
(61) |
Aug
(45) |
Sep
(105) |
Oct
(77) |
Nov
(46) |
Dec
(47) |
| 2010 |
Jan
(58) |
Feb
(88) |
Mar
(54) |
Apr
(78) |
May
(30) |
Jun
(40) |
Jul
(46) |
Aug
(36) |
Sep
(30) |
Oct
(29) |
Nov
(80) |
Dec
(52) |
| 2011 |
Jan
(30) |
Feb
(27) |
Mar
(25) |
Apr
(77) |
May
(24) |
Jun
(45) |
Jul
(34) |
Aug
(24) |
Sep
(65) |
Oct
(55) |
Nov
(72) |
Dec
(19) |
| 2012 |
Jan
(58) |
Feb
(44) |
Mar
(90) |
Apr
(11) |
May
(27) |
Jun
(32) |
Jul
(61) |
Aug
(32) |
Sep
(39) |
Oct
(45) |
Nov
(50) |
Dec
(21) |
| 2013 |
Jan
(44) |
Feb
(26) |
Mar
(37) |
Apr
(46) |
May
(24) |
Jun
(44) |
Jul
(15) |
Aug
(16) |
Sep
(20) |
Oct
(36) |
Nov
(36) |
Dec
(41) |
| 2014 |
Jan
(21) |
Feb
(9) |
Mar
(14) |
Apr
(16) |
May
(32) |
Jun
(50) |
Jul
(71) |
Aug
(47) |
Sep
(17) |
Oct
(9) |
Nov
(40) |
Dec
(42) |
| 2015 |
Jan
(11) |
Feb
(25) |
Mar
(22) |
Apr
(21) |
May
(6) |
Jun
(3) |
Jul
(7) |
Aug
(42) |
Sep
(28) |
Oct
(33) |
Nov
(5) |
Dec
(7) |
| 2016 |
Jan
(12) |
Feb
(18) |
Mar
(19) |
Apr
(31) |
May
(27) |
Jun
(23) |
Jul
(12) |
Aug
(33) |
Sep
(5) |
Oct
(28) |
Nov
(19) |
Dec
(8) |
| 2017 |
Jan
(52) |
Feb
(36) |
Mar
(12) |
Apr
(17) |
May
(8) |
Jun
(12) |
Jul
(3) |
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
|
|
1
|
2
|
|
3
(1) |
4
(9) |
5
(17) |
6
(5) |
7
(2) |
8
|
9
(2) |
|
10
(1) |
11
(1) |
12
|
13
|
14
(2) |
15
(2) |
16
|
|
17
|
18
|
19
(3) |
20
(1) |
21
|
22
(1) |
23
(2) |
|
24
(4) |
25
(3) |
26
(1) |
27
(2) |
28
(3) |
29
|
30
|
|
31
|
|
|
|
|
|
|
|
From: Michael Madore <michael.madore@gm...> - 2006-12-04 23:29:38
|
Hi, I have 4 WDS WD5000YS-01MPB0 SATA drives. Two of the drives reports the following for attribute 195 (hardware_ecc_recovered): 194 Temperature_Celsius 0x0022 253 253 000 Old_age Always - 32 195 Hardware_ECC_Recovered 0x000e 001 001 000 Old_age Always - 45161944 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 The RAW value increases quickly when the data is being read from the drive. The other two drives do not report attribute 195 at all: 194 Temperature_Celsius 0x0022 253 253 000 Old_age Always - 26 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 I understand that the RAW value should not be directly interpreted. What should I make of a normalized value of 001 and a threshold of 000? Mike Madore |
|
From: Nicholas Piper <nick-smartmontools@ni...> - 2006-12-04 23:15:51
|
Dear list, I'm writing here because I'm using smartd, and I've read at http://linux-ata.org/software-status.html#smart that "There are also some lingering reports that using SMART commands while the disk is in heavy usage leads to timeouts and other failures. This needs to be investigated. Haven't seen any of these reports recently." and I wonder if this is related to my trouble. I'm not sure where to go for help as I'm sure I shouldn't bother the LKML with this, but also feel maybe I shouldn't write directly to the libata authors. I've been having this trouble recently with my two SATA disks. I've replaced one of the disks, yet the problems persist! It does not seem to be related to a kernel upgrade (acording to dpkg.log.) Dec 1 18:29:20 piamox7 kernel: ata1: command timeout Dec 1 18:29:20 piamox7 kernel: ata1: no sense translation for status: 0x40 Dec 1 18:29:20 piamox7 kernel: ata1: translated ATA stat/err 0x40/00 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 1 18:29:20 piamox7 kernel: ata1: status=0x40 { DriveReady } My disks are currently: Nov 30 15:52:38 piamox7 kernel: ata1: SATA max UDMA/133 cmd 0xF881A200 ctl 0xF881A238 bmdma 0x0 irq 16 Nov 30 15:52:38 piamox7 kernel: ata2: SATA max UDMA/133 cmd 0xF881A280 ctl 0xF881A2B8 bmdma 0x0 irq 16 Nov 30 15:52:38 piamox7 kernel: scsi0 : sata_promise Nov 30 15:52:38 piamox7 kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Nov 30 15:52:38 piamox7 kernel: ata1.00: ATA-7, max UDMA/133, 488397168 sectors: LBA48 Nov 30 15:52:38 piamox7 kernel: ata1.00: ata1: dev 0 multi count 0 Nov 30 15:52:38 piamox7 kernel: ata1.00: configured for UDMA/133 Nov 30 15:52:38 piamox7 kernel: scsi1 : sata_promise Nov 30 15:52:38 piamox7 kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Nov 30 15:52:38 piamox7 kernel: ata2.00: ATA-7, max UDMA/133, 488397168 sectors: LBA48 Nov 30 15:52:38 piamox7 kernel: ata2.00: ata2: dev 0 multi count 0 Nov 30 15:52:38 piamox7 kernel: ata2.00: configured for UDMA/133 Nov 30 15:52:38 piamox7 kernel: Vendor: ATA Model: WDC WD2500KS-00M Rev: 02.0 Nov 30 15:52:38 piamox7 kernel: Type: Direct-Access ANSI SCSI revision: 05 Nov 30 15:52:38 piamox7 kernel: Vendor: ATA Model: WDC WD2500KS-00M Rev: 02.0 Nov 30 15:52:38 piamox7 kernel: Type: Direct-Access ANSI SCSI revision: 05 I'm using Debian (mostly testing) and Linux 2.6.18 (compiled myself). That appears to contain libata 1.20. It's happened quite a few times: Nov 14 11:26:50 piamox7 kernel: ata2: command timeout Nov 17 02:15:35 piamox7 kernel: ata2: command timeout Nov 17 05:16:30 piamox7 kernel: ata1: command timeout Nov 18 05:07:45 piamox7 kernel: ata1: command timeout Nov 21 22:09:40 piamox7 kernel: ata2: command timeout Nov 22 21:02:50 piamox7 kernel: ata1: command timeout Nov 22 22:16:30 piamox7 kernel: ata1: command timeout Nov 23 06:13:10 piamox7 kernel: ata1: command timeout Nov 24 10:39:25 piamox7 kernel: ata1: command timeout Nov 30 04:37:15 piamox7 kernel: ata1: command timeout Dec 1 18:29:20 piamox7 kernel: ata1: command timeout Dec 3 04:29:40 piamox7 kernel: ata2: command timeout And some of those times it's really damaged the filesystem, even though I'm using a software RAID mirror: (note the 'sync done'; shouldn't that take much longer?) Dec 1 18:29:20 piamox7 kernel: ata1: command timeout Dec 1 18:29:20 piamox7 kernel: ata1: no sense translation for status: 0x40 Dec 1 18:29:20 piamox7 kernel: ata1: translated ATA stat/err 0x40/00 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 1 18:29:20 piamox7 kernel: ata1: status=0x40 { DriveReady } Dec 1 18:29:20 piamox7 kernel: sd 0:0:0:0: SCSI error: return code = 0x08000002 Dec 1 18:29:20 piamox7 kernel: sda: Current: sense key: Aborted Command Dec 1 18:29:20 piamox7 kernel: Additional sense: No additional sense information Dec 1 18:29:20 piamox7 kernel: end_request: I/O error, dev sda, sector 173202207 Dec 1 18:29:20 piamox7 kernel: raid1: Disk failure on sda3, disabling device. Dec 1 18:29:20 piamox7 kernel: ^IOperation continuing on 1 devices Dec 1 18:29:20 piamox7 kernel: RAID1 conf printout: Dec 1 18:29:20 piamox7 kernel: --- wd:1 rd:2 Dec 1 18:29:20 piamox7 kernel: disk 0, wo:1, o:0, dev:sda3 Dec 1 18:29:20 piamox7 kernel: disk 1, wo:0, o:1, dev:hda3 Dec 1 18:29:20 piamox7 kernel: RAID1 conf printout: Dec 1 18:29:20 piamox7 kernel: --- wd:1 rd:2 Dec 1 18:29:20 piamox7 kernel: disk 0, wo:1, o:0, dev:sda3 Dec 1 18:29:20 piamox7 kernel: disk 1, wo:0, o:1, dev:hda3 Dec 1 18:29:20 piamox7 kernel: RAID1 conf printout: Dec 1 18:29:20 piamox7 kernel: --- wd:1 rd:2 Dec 1 18:29:20 piamox7 kernel: disk 1, wo:0, o:1, dev:hda3 Dec 1 18:29:20 piamox7 kernel: RAID1 conf printout: Dec 1 18:29:20 piamox7 kernel: --- wd:1 rd:2 Dec 1 18:29:20 piamox7 kernel: disk 0, wo:1, o:1, dev:sdb3 Dec 1 18:29:20 piamox7 kernel: disk 1, wo:0, o:1, dev:hda3 Dec 1 18:29:23 piamox7 kernel: md: syncing RAID array md2 Dec 1 18:29:23 piamox7 kernel: md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc. Dec 1 18:29:23 piamox7 kernel: md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for reconstruction. Dec 1 18:29:23 piamox7 kernel: md: using 128k window, over a total of 117186048 blocks. Dec 1 18:29:23 piamox7 kernel: md: md2: sync done. Dec 1 18:29:23 piamox7 kernel: RAID1 conf printout: Dec 1 18:29:23 piamox7 kernel: --- wd:2 rd:2 Dec 1 18:29:23 piamox7 kernel: disk 0, wo:0, o:1, dev:sdb3 Dec 1 18:29:23 piamox7 kernel: disk 1, wo:0, o:1, dev:hda3 Dec 1 18:29:25 piamox7 kernel: EXT3-fs error (device md2): ext3_new_block: Allocating block in system zone - blocks from 6029312, length 2 Dec 1 18:29:25 piamox7 kernel: Remounting filesystem read-only In that case, I had to recreate the array after a reboot by mouting the apparently 'failed' disk and making a new filesytem on /dev/md2. fsck found so many problems on /dev/md2 that I gave up on it. I'm using smartmontools 5.36-8 from the Debian package. I get this each time I try to start smartd: Dec 3 13:06:08 piamox7 smartd[6772]: Device: /dev/sda, opened Dec 3 13:06:08 piamox7 smartd[6772]: Device: /dev/sda, not found in smartd database. Dec 3 13:06:08 piamox7 kernel: ata1: no sense translation for status: 0x50 Dec 3 13:06:08 piamox7 kernel: ata1: translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 3 13:06:08 piamox7 kernel: ata1: status=0x50 { DriveReady SeekComplete } Dec 3 13:06:08 piamox7 kernel: ata1: no sense translation for status: 0x50 Dec 3 13:06:08 piamox7 kernel: ata1: translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 3 13:06:08 piamox7 kernel: ata1: status=0x50 { DriveReady SeekComplete } Dec 3 13:06:08 piamox7 kernel: ata1: no sense translation for status: 0x50 Dec 3 13:06:08 piamox7 kernel: ata1: translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 3 13:06:08 piamox7 kernel: ata1: status=0x50 { DriveReady SeekComplete } Dec 3 13:06:08 piamox7 kernel: ata1: no sense translation for status: 0x50 Dec 3 13:06:08 piamox7 kernel: ata1: translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 3 13:06:08 piamox7 kernel: ata1: status=0x50 { DriveReady SeekComplete } Dec 3 13:06:08 piamox7 kernel: ata1: no sense translation for status: 0x50 Dec 3 13:06:08 piamox7 kernel: ata1: translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 3 13:06:08 piamox7 kernel: ata1: status=0x50 { DriveReady SeekComplete } Dec 3 13:06:08 piamox7 kernel: ata1: no sense translation for status: 0x50 Dec 3 13:06:08 piamox7 kernel: ata1: translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 3 13:06:08 piamox7 kernel: ata1: status=0x50 { DriveReady SeekComplete } Dec 3 13:06:08 piamox7 smartd[6772]: Device: /dev/sda, could not enable SMART Attribute Autosave. Dec 3 13:06:08 piamox7 kernel: ata1: no sense translation for status: 0x50 Dec 3 13:06:08 piamox7 kernel: ata1: translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 3 13:06:08 piamox7 kernel: ata1: status=0x50 { DriveReady SeekComplete } Dec 3 13:06:08 piamox7 kernel: ata1: no sense translation for status: 0x50 Dec 3 13:06:08 piamox7 kernel: ata1: translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 3 13:06:08 piamox7 kernel: ata1: status=0x50 { DriveReady SeekComplete } Dec 3 13:06:08 piamox7 kernel: ata1: no sense translation for status: 0x50 Dec 3 13:06:08 piamox7 kernel: ata1: translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 3 13:06:08 piamox7 kernel: ata1: status=0x50 { DriveReady SeekComplete } Dec 3 13:06:08 piamox7 kernel: ata1: no sense translation for status: 0x50 Dec 3 13:06:08 piamox7 kernel: ata1: translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 3 13:06:08 piamox7 kernel: ata1: status=0x50 { DriveReady SeekComplete } Dec 3 13:06:08 piamox7 kernel: ata1: no sense translation for status: 0x50 Dec 3 13:06:08 piamox7 kernel: ata1: translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 3 13:06:08 piamox7 kernel: ata1: status=0x50 { DriveReady SeekComplete } Dec 3 13:06:08 piamox7 kernel: ata1: no sense translation for status: 0x50 Dec 3 13:06:08 piamox7 kernel: ata1: translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 3 13:06:08 piamox7 kernel: ata1: status=0x50 { DriveReady SeekComplete } Dec 3 13:06:08 piamox7 smartd[6772]: Device: /dev/sda, enable SMART Automatic Offline Testing failed. Dec 3 13:06:08 piamox7 smartd[6772]: Device: /dev/sda, is SMART capable. Adding to "monitor" list. and have this line in /etc/smartd.conf: /dev/sda -a -d ata -o on -S on -s (S/../.././02|L/../../6/03) -m root -M exec /usr/share/smartmontools/smartd-runner I've just now realised I can improve that to remove -o on -S on, which caused those errors (which I expect to be not causing my further trouble.) /dev/sda -a -d ata -s (S/../.././02|L/../../6/03) -m root -M exec /usr/share/smartmontools/smartd-runner smartctl -d ata -a /dev/sda says: smartctl version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: WDC WD2500KS-00MJB0 Serial Number: WD-WCANK3521747 Firmware Version: 02.01C03 User Capacity: 250,059,350,016 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: Mon Dec 4 23:02:00 2006 GMT 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: (0x84) Offline data collection activity was suspended by an interrupting command from host. 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: (7080) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. 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: ( 83) minutes. Conveyance self-test routine recommended polling time: ( 6) minutes. SMART Attributes Data Structure revision number: 16 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 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0003 199 192 021 Pre-fail Always - 5033 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 25 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 200 200 051 Pre-fail Always - 0 9 Power_On_Hours 0x0032 096 096 000 Old_age Always - 3617 10 Spin_Retry_Count 0x0013 100 253 051 Pre-fail Always - 0 11 Calibration_Retry_Count 0x0012 100 253 051 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 19 190 Unknown_Attribute 0x0022 048 029 045 Old_age Always In_the_past 52 194 Temperature_Celsius 0x0022 098 079 000 Old_age Always - 52 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0009 200 200 051 Pre-fail 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% 3596 - # 2 Short offline Completed without error 00% 3572 - # 3 Extended offline Completed without error 00% 3551 - # 4 Short offline Completed without error 00% 3548 - # 5 Short offline Completed without error 00% 3525 - # 6 Short offline Completed without error 00% 3500 - # 7 Short offline Completed without error 00% 3476 - # 8 Conveyance offline Completed without error 00% 3463 - # 9 Short offline Completed without error 00% 3453 - #10 Short offline Completed without error 00% 3429 - #11 Short offline Completed without error 00% 3405 - #12 Extended offline Completed without error 00% 3383 - #13 Short offline Completed without error 00% 3381 - #14 Short offline Completed without error 00% 3357 - #15 Short offline Completed without error 00% 3333 - #16 Short offline Completed without error 00% 3309 - #17 Short offline Completed without error 00% 3285 - #18 Short offline Completed without error 00% 3261 - #19 Short offline Completed without error 00% 3237 - #20 Extended offline Completed without error 00% 3216 - #21 Short offline Completed without error 00% 3213 - 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. For now, I've reduced my RAID array to a single IDE disk as the SATA failures were causing me great trouble. I've used the Western Digital software ( http://support.wdc.com/download/index.asp?swid=1 ) to validate the disks. I used an extended test (1.5 hours) and the software says the disks are fine. I assume this also validates the SATA controller to some extent? I'd be grateful for any advice on what I can do? Much thanks, Nick -- Nick Piper, Developer, LogicaCMG http://www.nickpiper.co.uk/ GPG Encrypted mail welcome! 1024D/3ED8B27F Choose life. Be Vegan :-) Please reduce needless cruelty + suffering ! |
|
From: <martin@on...> - 2006-12-04 14:12:20
|
2006/12/4, Bernd Melchers <melchers@...>: > > > 0 > > >194 Temperature_Celsius 0x0032 253 253 000 Old_age > > >Always - > > > 55 > > It seems, your disk is very hot, 55 degree Celsius. This may be > one cause of failure, heat decreases the lifetime. Especially since the disk is only rated for 5=B0 to 55=B0C. Best Martin |
|
From: Simon Banton <simon-smartmontools@we...> - 2006-12-04 13:53:52
|
Hi Bruce, (tsk, sorry, forgot to reply to the list as well) As requested: ide-smart: >[/usr/local/sbin]# ./ide-smart -d /dev/hde >SMART_ENABLE: Input/output error smartsuite: >[/src/smartsuite-2.1]# ./smartctl -e /dev/hde >Smart Enable failed: Input/output error >Smartctl: Smart Enable Failed smartmontools smartctl with -r ioctl,3: >[/usr/sbin]# ./smartctl -s on -H --tolerance=verypermissive -r >ioctl,3 /dev/hde >smartctl version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen >Home page is http://smartmontools.sourceforge.net/ > > >REPORT-IOCTL: DeviceFD=3 Command=IDENTIFY DEVICE >REPORT-IOCTL: DeviceFD=3 Command=IDENTIFY DEVICE returned 0 > >===== [IDENTIFY DEVICE] DATA START (BASE-16) ===== >000-015: 40 00 ff 3f 37 c8 10 00 00 00 00 00 3f 00 00 00 >016-031: 00 00 00 00 33 59 4e 34 52 51 45 45 20 20 20 20 >032-047: 20 20 20 20 20 20 20 20 03 00 00 3e 39 00 41 59 >048-063: 34 52 42 31 30 57 61 4d 74 78 72 6f 36 20 31 59 >064-079: 30 32 30 50 20 20 20 20 20 20 20 20 20 20 20 20 >080-095: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 10 80 >096-111: 00 00 00 2f 00 40 00 02 00 00 07 00 ff ff 01 00 >112-127: 3f 00 c1 ff 3e 00 10 01 80 f7 4f 0e 00 00 07 00 >128-143: 03 00 78 00 78 00 78 00 78 00 00 00 00 00 00 00 >144-159: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >160-175: fe 00 1e 00 69 7c 09 7f 03 40 68 7c 01 3c 03 40 >176-191: 7f 40 00 00 00 00 00 00 00 00 0d 40 00 c0 00 00 >192-207: 00 00 00 00 00 00 00 00 80 f7 4f 0e 00 00 00 00 >208-223: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >224-239: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >240-255: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >256-271: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >272-287: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >288-303: 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 >304-319: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >320-335: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >336-351: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >352-367: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >368-383: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >384-399: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >400-415: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >416-431: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >432-447: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >448-463: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >464-479: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >480-495: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >496-511: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a5 df >===== [IDENTIFY DEVICE] DATA END (512 Bytes) ===== > >=== START OF ENABLE/DISABLE COMMANDS SECTION === > >REPORT-IOCTL: DeviceFD=3 Command=SMART ENABLE >REPORT-IOCTL: DeviceFD=3 Command=SMART ENABLE returned -1 errno=5 >[Input/output error] >Error SMART Enable failed: Input/output error >Smartctl: SMART Enable Failed. > > >REPORT-IOCTL: DeviceFD=3 Command=SMART STATUS >REPORT-IOCTL: DeviceFD=3 Command=SMART STATUS returned -1 errno=5 >[Input/output error] >SMART Disabled. Use option -s with argument 'on' to enable it. ... and from /var/log/messages: >Dec 4 13:21:46 khufu kernel: hde: drive_cmd: status=0x51 { >DriveReady SeekComplete Error } >Dec 4 13:21:46 khufu kernel: hde: drive_cmd: error=0x04 { DriveStatusError } >Dec 4 13:21:46 khufu kernel: ide: failed opcode was: 0xb0 Any light shed as a result? Cheers Simon |
|
From: Bernd Melchers <melchers@ze...> - 2006-12-04 13:26:03
|
> > 0 > >194 Temperature_Celsius 0x0032 253 253 000 Old_age > >Always - > > 55 It seems, your disk is very hot, 55 degree Celsius. This may be one cause of failure, heat decreases the lifetime. mit freundlichen Grüßen Bernd Melchers -- Archiv- und Backup-Service | fab-service@... Freie Universität Berlin | Tel. (030) 838-55905 und -56066 |
|
From: <Jimmy.H@mi...> - 2006-12-04 12:10:05
|
Dear SMARTMONTOOLS developers, When I use SMARTMONTOOLS to check my HD=A1=A6s S.M.A.R.T function, I = found some strange output as below. It seems SMARTMONTOOLS didn=A1=A6t support some SCSI commands in Marvell = chip. Do I need to modify driver or SMARTMONTOOLS source code to fix this issue?? =20 System information: CPU: BCM1250 MIPS 64 bit Sibyte CPU Chip set: Marvell 88SX-6081 Hard drive: Maxtor 500GB 7H500F0 GCC version: 3.4.1 Marvell SATA driver version: 3.6.3 beta version ---------------- output message ---------------------- Lynx_jimmy:/# smartctl -d scsi -a /dev/sda smartctl version 5.36 [mips64el-unknown-linux-gnu] Copyright (C) 2002-6 = Bruce Allen Home page is http://smartmontools.sourceforge.net/ Device: Maxtor 7H500F0 Version: HA43 Device type: disk Local Time is: Mon Dec 4 11:40:18 2006 UTC Device does not support SMART Error Counter logging not supported Device does not support Self Test logging =20 Lynx_jimmy:/# smartctl -d scsi -s on /dev/sda smartctl version 5.36 [mips64el-unknown-linux-gnu] Copyright (C) 2002-6 = Bruce Allen Home page is http://smartmontools.sourceforge.net/ unable to fetch IEC (SMART) mode page [unsupported field in scsi = command] A mandatory SMART command failed: exiting. To continue, add one or more = '-T permissive' options. =20 Lynx_jimmy:/# smartctl -d scsi -s on -T permissive /dev/sda smartctl version 5.36 [mips64el-unknown-linux-gnu] Copyright (C) 2002-6 = Bruce Allen Home page is http://smartmontools.sourceforge.net/ unable to fetch IEC (SMART) mode page [unsupported field in scsi = command]=20 =20 Lynx_jimmy:/# smartctl -d marvell -s on /dev/sda smartctl version program smartctl is using a deprecated SCSI ioctl, = please convert it to SG_IO 5.36 [mips64el-uprogram smartctl is using a deprecated SCSI ioctl, = please convert it to SG_IO nknown-linux-gnu] Copyright (C) 2002-6 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) A mandatory SMART command failed: exiting. To continue, add one or more = '-T permissive' options. ---------------- output message ---------------------- =20 Thanks & B.R Jimmy.h |
|
From: Bruce Allen <ballen@gr...> - 2006-12-04 11:58:16
|
Hi Simon, Weird -- I have no idea what this is due to!! It does sound like a sick disk. Just for fun try some other linux SMART utility such as ide-smart or smartsuite, and tell me what they say. PS: also try adding a -r ioctl,3 onto you command line, and send that output to the list. Cheers, Bruce About the only think I can think of is that the hardware disk c On Mon, 4 Dec 2006, Simon Banton wrote: > Hi, > > One of a pair of Maxtor 6Y120P0s got kicked out of an mdadm-managed > RAID 1 over the weekend, and it appears to have failed in such a way > that SMART monitoring can no longer be enabled for it. > > Here's what I get if I try to do so: > >> # smartctl -s on -a /dev/hde >> smartctl version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen >> Home page is http://smartmontools.sourceforge.net/ >> >> === START OF INFORMATION SECTION === >> Model Family: Maxtor DiamondMax Plus 9 family >> Device Model: Maxtor 6Y120P0 >> Serial Number: Y34NQREE >> Firmware Version: YAR41BW0 >> User Capacity: 122,942,324,736 bytes >> Device is: In smartctl database [for details use: -P show] >> ATA Version is: 7 >> ATA Standard is: ATA/ATAPI-7 T13 1532D revision 0 >> Local Time is: Mon Dec 4 11:28:20 2006 GMT >> SMART support is: Available - device has SMART capability. >> SMART support is: Disabled >> >> === START OF ENABLE/DISABLE COMMANDS SECTION === >> Error SMART Enable failed: Input/output error >> Smartctl: SMART Enable Failed. >> >> A mandatory SMART command failed: exiting. To continue, add one or >> more '-T permissive' options. > >> # smartctl -s on -H --tolerance=verypermissive /dev/hde >> smartctl version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen >> Home page is http://smartmontools.sourceforge.net/ >> >> === START OF ENABLE/DISABLE COMMANDS SECTION === >> Error SMART Enable failed: Input/output error >> Smartctl: SMART Enable Failed. > > > I've moved the disk to another machine and tried it on a number of > different IDE interfaces with different cables all to no avail. Its > ex-partner in the RAID still happily reports its SMART data just fine. > > Both the Maxtor and the Seagate disk utilities both report the drive > as 'OK', but both also fail to retrieve the SMART logs successfully - > the Seagate utility reporting 'Unsupported' for the SMART check. > > Here's an extract from /var/log/messages: > >> Dec 2 15:08:01 khufu smartd[3183]: Device: /dev/hde, not capable of >> SMART Health Status check >> Dec 2 15:08:06 khufu kernel: hde: drive_cmd: status=0x51 { >> DriveReady SeekComplete Error } >> Dec 2 15:08:06 khufu kernel: hde: drive_cmd: error=0x04 { DriveStatusError } >> Dec 2 15:08:06 khufu kernel: ide: failed opcode was: 0xb0 >> Dec 2 15:08:06 khufu smartd[3183]: Device: /dev/hde, Read SMART >> Values and/or Thresholds Failed >> Dec 2 15:08:06 khufu smartd[3183]: Device: /dev/hde, SMART >> Automatic Offline Testing unsupported... >> Dec 2 15:08:12 khufu kernel: hde: drive_cmd: status=0x51 { >> DriveReady SeekComplete Error } >> Dec 2 15:08:12 khufu kernel: hde: drive_cmd: error=0x04 { DriveStatusError } >> Dec 2 15:08:12 khufu kernel: ide: failed opcode was: 0xb0 >> Dec 2 15:08:12 khufu smartd[3183]: Device: /dev/hde, enable SMART >> Automatic Offline Testing failed. > > Is this failure mode well-known? Does it indicate an electrical > failure or corruption of the SMART firmware or area of the disk where > the data is stored? > > Anything else I should try before getting it RMAd (assuming > Seagate/Maxtor will replace a disk that their utilities pass as 'OK')? > > Many thanks for any advice. Incidentally, the system is Centos 4.3 > but with smartmontools updated to 5.36 from 5.33. > > Finally, I was able - but once only, immediately after the disk was > kicked from the array, to get the SMART data out of it. That report > is included below. > > Regards > Simon > > -- final SMART report - all subsequent attempts failed as detailed above -- > >> === START OF INFORMATION SECTION === >> Device Model: Maxtor 6Y120P0 >> Serial Number: Y34NQREE >> Firmware Version: YAR41BW0 >> User Capacity: 122,942,324,736 bytes >> Device is: In smartctl database [for details use: -P show] >> ATA Version is: 7 >> ATA Standard is: ATA/ATAPI-7 T13 1532D revision 0 >> Local Time is: Sat Dec 2 14:56:44 2006 GMT >> 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: ( 242) seconds. >> Offline data collection >> capabilities: (0x5b) SMART execute Offline immediate. >> Auto Offline data collection >> on/off supp >> ort. >> 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: ( 2) minutes. >> Extended self-test routine >> recommended polling time: ( 54) minutes. >> >> SMART Attributes Data Structure revision number: 16 >> Vendor Specific SMART Attributes with Thresholds: >> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE >> UPDATED WHEN_ >> FAILED RAW_VALUE >> 3 Spin_Up_Time 0x0027 207 204 063 Pre-fail >> Always - >> 15550 >> 4 Start_Stop_Count 0x0032 253 253 000 Old_age >> Always - >> 81 >> 5 Reallocated_Sector_Ct 0x0033 213 210 063 Pre-fail >> Always - >> 414 >> 6 Read_Channel_Margin 0x0001 253 253 100 Pre-fail >> Offline - >> 0 >> 7 Seek_Error_Rate 0x000a 253 252 000 Old_age >> Always - >> 0 >> 8 Seek_Time_Performance 0x0027 252 223 187 Pre-fail >> Always - >> 41870 >> 9 Power_On_Minutes 0x0032 197 197 000 Old_age >> Always - >> 1025h+07m >> 10 Spin_Retry_Count 0x002b 253 252 157 Pre-fail >> Always - >> 0 >> 11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail >> Always - >> 0 >> 12 Power_Cycle_Count 0x0032 253 253 000 Old_age >> Always - >> 119 >> 192 Power-Off_Retract_Count 0x0032 253 253 000 Old_age >> Always - >> 0 >> 193 Load_Cycle_Count 0x0032 253 253 000 Old_age >> Always - >> 0 >> 194 Temperature_Celsius 0x0032 253 253 000 Old_age >> Always - >> 55 >> 195 Hardware_ECC_Recovered 0x000a 253 252 000 Old_age >> Always - >> 4230 >> 196 Reallocated_Event_Count 0x0008 001 001 000 Old_age >> Offline - >> 438 >> 197 Current_Pending_Sector 0x0008 214 211 000 Old_age >> Offline - >> 400 >> 198 Offline_Uncorrectable 0x0008 001 001 000 Old_age >> Offline - >> 1272 >> 199 UDMA_CRC_Error_Count 0x0008 199 199 000 Old_age >> Offline - >> 0 >> 200 Multi_Zone_Error_Rate 0x000a 253 252 000 Old_age >> Always - >> 0 >> 201 Soft_Read_Error_Rate 0x000a 253 252 000 Old_age >> Always - >> 17 >> 202 TA_Increase_Count 0x000a 253 160 000 Old_age >> Always - >> 0 >> 203 Run_Out_Cancel 0x000b 253 252 180 Pre-fail >> Always - >> 4 >> 204 Shock_Count_Write_Opern 0x000a 253 252 000 Old_age >> Always - >> 0 >> 205 Shock_Rate_Write_Opern 0x000a 253 252 000 Old_age >> Always - >> 0 >> 207 Spin_High_Current 0x002a 253 252 000 Old_age >> Always - >> 0 >> 208 Spin_Buzz 0x002a 253 252 000 Old_age >> Always - >> 0 >> 209 Offline_Seek_Performnce 0x0024 196 178 000 Old_age >> Offline - >> 0 >> 99 Unknown_Attribute 0x0004 253 253 000 Old_age >> Offline - >> 0 >> 100 Unknown_Attribute 0x0004 253 253 000 Old_age >> Offline - >> 0 >> 101 Unknown_Attribute 0x0004 253 253 000 Old_age >> Offline - >> 0 >> >> SMART Error Log Version: 1 >> Warning: ATA error count 13 inconsistent with error log pointer 5 >> >> ATA Error Count: 13 (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 13 occurred at disk power-on lifetime: 17401 hours (725 days + 1 hours) >> When the command that caused the error occurred, the device was in >> an unknown >> state. >> >> After command completion occurred, registers were: >> ER ST SC SN CL CH DH >> -- -- -- -- -- -- -- >> 40 51 3f 97 00 74 e0 Error: UNC 63 sectors at LBA = 0x00740097 = 7602327 >> >> Commands leading to the command that caused the error were: >> CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name >> -- -- -- -- -- -- -- -- ---------------- -------------------- >> c8 00 40 97 00 74 e0 08 00:07:28.208 READ DMA >> c8 00 08 17 05 71 e0 08 00:07:28.192 READ DMA >> c8 00 08 2f e3 70 e0 08 00:07:28.192 READ DMA >> c8 00 08 27 e3 70 e0 08 00:07:28.192 READ DMA >> c8 00 08 87 a9 70 e0 08 00:07:28.176 READ DMA >> >> Error 12 occurred at disk power-on lifetime: 7952 hours (331 days + 8 hours) >> When the command that caused the error occurred, the device was in >> an unknown >> state. >> >> After command completion occurred, registers were: >> ER ST SC SN CL CH DH >> -- -- -- -- -- -- -- >> 40 51 28 97 03 44 e0 Error: UNC 40 sectors at LBA = 0x00440397 = 4457367 >> >> Commands leading to the command that caused the error were: >> CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name >> -- -- -- -- -- -- -- -- ---------------- -------------------- >> c8 00 28 97 03 44 e0 08 00:26:25.632 READ DMA >> c8 00 30 8f 03 44 e0 08 00:26:24.592 READ DMA >> c8 00 38 87 03 44 e0 08 00:26:23.568 READ DMA >> c8 00 40 7f 03 44 e0 08 00:26:22.528 READ DMA >> c8 00 48 77 03 44 e0 08 00:26:21.488 READ DMA >> >> Error 11 occurred at disk power-on lifetime: 7952 hours (331 days + 8 hours) >> When the command that caused the error occurred, the device was in >> an unknown >> state. >> >> After command completion occurred, registers were: >> ER ST SC SN CL CH DH >> -- -- -- -- -- -- -- >> 40 51 28 8f 03 44 e0 Error: UNC 40 sectors at LBA = 0x0044038f = 4457359 >> >> Commands leading to the command that caused the error were: >> CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name >> -- -- -- -- -- -- -- -- ---------------- -------------------- >> c8 00 30 8f 03 44 e0 08 00:26:24.592 READ DMA >> c8 00 38 87 03 44 e0 08 00:26:23.568 READ DMA >> c8 00 40 7f 03 44 e0 08 00:26:22.528 READ DMA >> c8 00 48 77 03 44 e0 08 00:26:21.488 READ DMA >> c8 00 50 6f 03 44 e0 08 00:26:20.448 READ DMA >> >> Error 10 occurred at disk power-on lifetime: 7952 hours (331 days + 8 hours) >> When the command that caused the error occurred, the device was in >> an unknown >> state. >> >> After command completion occurred, registers were: >> ER ST SC SN CL CH DH >> -- -- -- -- -- -- -- >> 40 51 28 87 03 44 e0 Error: UNC 40 sectors at LBA = 0x00440387 = 4457351 >> >> Commands leading to the command that caused the error were: >> CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name >> -- -- -- -- -- -- -- -- ---------------- -------------------- >> c8 00 38 87 03 44 e0 08 00:26:23.568 READ DMA >> c8 00 40 7f 03 44 e0 08 00:26:22.528 READ DMA >> c8 00 48 77 03 44 e0 08 00:26:21.488 READ DMA >> c8 00 50 6f 03 44 e0 08 00:26:20.448 READ DMA >> c8 00 58 67 03 44 e0 08 00:25:13.872 READ DMA >> >> Error 9 occurred at disk power-on lifetime: 7952 hours (331 days + 8 hours) >> When the command that caused the error occurred, the device was in >> an unknown >> state. >> >> After command completion occurred, registers were: >> ER ST SC SN CL CH DH >> -- -- -- -- -- -- -- >> 40 51 28 7f 03 44 e0 Error: UNC 40 sectors at LBA = 0x0044037f = 4457343 >> >> Commands leading to the command that caused the error were: >> CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name >> -- -- -- -- -- -- -- -- ---------------- -------------------- >> c8 00 40 7f 03 44 e0 08 00:26:22.528 READ DMA >> c8 00 48 77 03 44 e0 08 00:26:21.488 READ DMA >> c8 00 50 6f 03 44 e0 08 00:26:20.448 READ DMA >> c8 00 58 67 03 44 e0 08 00:25:13.872 READ DMA >> c8 00 60 5f 03 44 e0 08 00:25:12.832 READ DMA >> >> 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% 13356 - >> # 2 Short offline Completed without error 00% 13333 - >> # 3 Short offline Completed without error 00% 13312 - >> # 4 Short offline Completed without error 00% 13290 - >> # 5 Short offline Completed without error 00% 13267 - >> # 6 Extended offline Completed without error 00% 13247 - >> # 7 Short offline Completed without error 00% 13245 - >> # 8 Short offline Completed without error 00% 13222 - >> # 9 Short offline Completed without error 00% 13200 - >> #10 Short offline Completed without error 00% 13182 - >> #11 Short offline Completed without error 00% 13159 - >> #12 Short offline Completed without error 00% 13137 - >> #13 Short offline Completed without error 00% 13115 - >> #14 Extended offline Completed without error 00% 13094 - >> #15 Short offline Completed without error 00% 13092 - >> #16 Short offline Completed without error 00% 13003 - >> #17 Short offline Completed without error 00% 12980 - >> #18 Short offline Completed without error 00% 12958 - >> #19 Extended offline Completed without error 00% 12937 - >> #20 Short offline Completed without error 00% 12935 - >> #21 Short offline Completed without error 00% 12913 - >> >> 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. > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Smartmontools-support mailing list > Smartmontools-support@... > https://lists.sourceforge.net/lists/listinfo/smartmontools-support > |
|
From: Simon Banton <simon-smartmontools@we...> - 2006-12-04 11:52:40
|
Hi, One of a pair of Maxtor 6Y120P0s got kicked out of an mdadm-managed RAID 1 over the weekend, and it appears to have failed in such a way that SMART monitoring can no longer be enabled for it. Here's what I get if I try to do so: ># smartctl -s on -a /dev/hde >smartctl version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen >Home page is http://smartmontools.sourceforge.net/ > >=== START OF INFORMATION SECTION === >Model Family: Maxtor DiamondMax Plus 9 family >Device Model: Maxtor 6Y120P0 >Serial Number: Y34NQREE >Firmware Version: YAR41BW0 >User Capacity: 122,942,324,736 bytes >Device is: In smartctl database [for details use: -P show] >ATA Version is: 7 >ATA Standard is: ATA/ATAPI-7 T13 1532D revision 0 >Local Time is: Mon Dec 4 11:28:20 2006 GMT >SMART support is: Available - device has SMART capability. >SMART support is: Disabled > >=== START OF ENABLE/DISABLE COMMANDS SECTION === >Error SMART Enable failed: Input/output error >Smartctl: SMART Enable Failed. > >A mandatory SMART command failed: exiting. To continue, add one or >more '-T permissive' options. ># smartctl -s on -H --tolerance=verypermissive /dev/hde >smartctl version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen >Home page is http://smartmontools.sourceforge.net/ > >=== START OF ENABLE/DISABLE COMMANDS SECTION === >Error SMART Enable failed: Input/output error >Smartctl: SMART Enable Failed. I've moved the disk to another machine and tried it on a number of different IDE interfaces with different cables all to no avail. Its ex-partner in the RAID still happily reports its SMART data just fine. Both the Maxtor and the Seagate disk utilities both report the drive as 'OK', but both also fail to retrieve the SMART logs successfully - the Seagate utility reporting 'Unsupported' for the SMART check. Here's an extract from /var/log/messages: >Dec 2 15:08:01 khufu smartd[3183]: Device: /dev/hde, not capable of >SMART Health Status check >Dec 2 15:08:06 khufu kernel: hde: drive_cmd: status=0x51 { >DriveReady SeekComplete Error } >Dec 2 15:08:06 khufu kernel: hde: drive_cmd: error=0x04 { DriveStatusError } >Dec 2 15:08:06 khufu kernel: ide: failed opcode was: 0xb0 >Dec 2 15:08:06 khufu smartd[3183]: Device: /dev/hde, Read SMART >Values and/or Thresholds Failed >Dec 2 15:08:06 khufu smartd[3183]: Device: /dev/hde, SMART >Automatic Offline Testing unsupported... >Dec 2 15:08:12 khufu kernel: hde: drive_cmd: status=0x51 { >DriveReady SeekComplete Error } >Dec 2 15:08:12 khufu kernel: hde: drive_cmd: error=0x04 { DriveStatusError } >Dec 2 15:08:12 khufu kernel: ide: failed opcode was: 0xb0 >Dec 2 15:08:12 khufu smartd[3183]: Device: /dev/hde, enable SMART >Automatic Offline Testing failed. Is this failure mode well-known? Does it indicate an electrical failure or corruption of the SMART firmware or area of the disk where the data is stored? Anything else I should try before getting it RMAd (assuming Seagate/Maxtor will replace a disk that their utilities pass as 'OK')? Many thanks for any advice. Incidentally, the system is Centos 4.3 but with smartmontools updated to 5.36 from 5.33. Finally, I was able - but once only, immediately after the disk was kicked from the array, to get the SMART data out of it. That report is included below. Regards Simon -- final SMART report - all subsequent attempts failed as detailed above -- >=== START OF INFORMATION SECTION === >Device Model: Maxtor 6Y120P0 >Serial Number: Y34NQREE >Firmware Version: YAR41BW0 >User Capacity: 122,942,324,736 bytes >Device is: In smartctl database [for details use: -P show] >ATA Version is: 7 >ATA Standard is: ATA/ATAPI-7 T13 1532D revision 0 >Local Time is: Sat Dec 2 14:56:44 2006 GMT >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: ( 242) seconds. >Offline data collection >capabilities: (0x5b) SMART execute Offline immediate. > Auto Offline data collection >on/off supp >ort. > 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: ( 2) minutes. >Extended self-test routine >recommended polling time: ( 54) minutes. > >SMART Attributes Data Structure revision number: 16 >Vendor Specific SMART Attributes with Thresholds: >ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE >UPDATED WHEN_ >FAILED RAW_VALUE > 3 Spin_Up_Time 0x0027 207 204 063 Pre-fail >Always - > 15550 > 4 Start_Stop_Count 0x0032 253 253 000 Old_age >Always - > 81 > 5 Reallocated_Sector_Ct 0x0033 213 210 063 Pre-fail >Always - > 414 > 6 Read_Channel_Margin 0x0001 253 253 100 Pre-fail >Offline - > 0 > 7 Seek_Error_Rate 0x000a 253 252 000 Old_age >Always - > 0 > 8 Seek_Time_Performance 0x0027 252 223 187 Pre-fail >Always - > 41870 > 9 Power_On_Minutes 0x0032 197 197 000 Old_age >Always - > 1025h+07m > 10 Spin_Retry_Count 0x002b 253 252 157 Pre-fail >Always - > 0 > 11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail >Always - > 0 > 12 Power_Cycle_Count 0x0032 253 253 000 Old_age >Always - > 119 >192 Power-Off_Retract_Count 0x0032 253 253 000 Old_age >Always - > 0 >193 Load_Cycle_Count 0x0032 253 253 000 Old_age >Always - > 0 >194 Temperature_Celsius 0x0032 253 253 000 Old_age >Always - > 55 >195 Hardware_ECC_Recovered 0x000a 253 252 000 Old_age >Always - > 4230 >196 Reallocated_Event_Count 0x0008 001 001 000 Old_age >Offline - > 438 >197 Current_Pending_Sector 0x0008 214 211 000 Old_age >Offline - > 400 >198 Offline_Uncorrectable 0x0008 001 001 000 Old_age >Offline - > 1272 >199 UDMA_CRC_Error_Count 0x0008 199 199 000 Old_age >Offline - > 0 >200 Multi_Zone_Error_Rate 0x000a 253 252 000 Old_age >Always - > 0 >201 Soft_Read_Error_Rate 0x000a 253 252 000 Old_age >Always - > 17 >202 TA_Increase_Count 0x000a 253 160 000 Old_age >Always - > 0 >203 Run_Out_Cancel 0x000b 253 252 180 Pre-fail >Always - > 4 >204 Shock_Count_Write_Opern 0x000a 253 252 000 Old_age >Always - > 0 >205 Shock_Rate_Write_Opern 0x000a 253 252 000 Old_age >Always - > 0 >207 Spin_High_Current 0x002a 253 252 000 Old_age >Always - > 0 >208 Spin_Buzz 0x002a 253 252 000 Old_age >Always - > 0 >209 Offline_Seek_Performnce 0x0024 196 178 000 Old_age >Offline - > 0 > 99 Unknown_Attribute 0x0004 253 253 000 Old_age >Offline - > 0 >100 Unknown_Attribute 0x0004 253 253 000 Old_age >Offline - > 0 >101 Unknown_Attribute 0x0004 253 253 000 Old_age >Offline - > 0 > >SMART Error Log Version: 1 >Warning: ATA error count 13 inconsistent with error log pointer 5 > >ATA Error Count: 13 (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 13 occurred at disk power-on lifetime: 17401 hours (725 days + 1 hours) > When the command that caused the error occurred, the device was in >an unknown >state. > > After command completion occurred, registers were: > ER ST SC SN CL CH DH > -- -- -- -- -- -- -- > 40 51 3f 97 00 74 e0 Error: UNC 63 sectors at LBA = 0x00740097 = 7602327 > > Commands leading to the command that caused the error were: > CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name > -- -- -- -- -- -- -- -- ---------------- -------------------- > c8 00 40 97 00 74 e0 08 00:07:28.208 READ DMA > c8 00 08 17 05 71 e0 08 00:07:28.192 READ DMA > c8 00 08 2f e3 70 e0 08 00:07:28.192 READ DMA > c8 00 08 27 e3 70 e0 08 00:07:28.192 READ DMA > c8 00 08 87 a9 70 e0 08 00:07:28.176 READ DMA > >Error 12 occurred at disk power-on lifetime: 7952 hours (331 days + 8 hours) > When the command that caused the error occurred, the device was in >an unknown >state. > > After command completion occurred, registers were: > ER ST SC SN CL CH DH > -- -- -- -- -- -- -- > 40 51 28 97 03 44 e0 Error: UNC 40 sectors at LBA = 0x00440397 = 4457367 > > Commands leading to the command that caused the error were: > CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name > -- -- -- -- -- -- -- -- ---------------- -------------------- > c8 00 28 97 03 44 e0 08 00:26:25.632 READ DMA > c8 00 30 8f 03 44 e0 08 00:26:24.592 READ DMA > c8 00 38 87 03 44 e0 08 00:26:23.568 READ DMA > c8 00 40 7f 03 44 e0 08 00:26:22.528 READ DMA > c8 00 48 77 03 44 e0 08 00:26:21.488 READ DMA > >Error 11 occurred at disk power-on lifetime: 7952 hours (331 days + 8 hours) > When the command that caused the error occurred, the device was in >an unknown >state. > > After command completion occurred, registers were: > ER ST SC SN CL CH DH > -- -- -- -- -- -- -- > 40 51 28 8f 03 44 e0 Error: UNC 40 sectors at LBA = 0x0044038f = 4457359 > > Commands leading to the command that caused the error were: > CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name > -- -- -- -- -- -- -- -- ---------------- -------------------- > c8 00 30 8f 03 44 e0 08 00:26:24.592 READ DMA > c8 00 38 87 03 44 e0 08 00:26:23.568 READ DMA > c8 00 40 7f 03 44 e0 08 00:26:22.528 READ DMA > c8 00 48 77 03 44 e0 08 00:26:21.488 READ DMA > c8 00 50 6f 03 44 e0 08 00:26:20.448 READ DMA > >Error 10 occurred at disk power-on lifetime: 7952 hours (331 days + 8 hours) > When the command that caused the error occurred, the device was in >an unknown >state. > > After command completion occurred, registers were: > ER ST SC SN CL CH DH > -- -- -- -- -- -- -- > 40 51 28 87 03 44 e0 Error: UNC 40 sectors at LBA = 0x00440387 = 4457351 > > Commands leading to the command that caused the error were: > CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name > -- -- -- -- -- -- -- -- ---------------- -------------------- > c8 00 38 87 03 44 e0 08 00:26:23.568 READ DMA > c8 00 40 7f 03 44 e0 08 00:26:22.528 READ DMA > c8 00 48 77 03 44 e0 08 00:26:21.488 READ DMA > c8 00 50 6f 03 44 e0 08 00:26:20.448 READ DMA > c8 00 58 67 03 44 e0 08 00:25:13.872 READ DMA > >Error 9 occurred at disk power-on lifetime: 7952 hours (331 days + 8 hours) > When the command that caused the error occurred, the device was in >an unknown >state. > > After command completion occurred, registers were: > ER ST SC SN CL CH DH > -- -- -- -- -- -- -- > 40 51 28 7f 03 44 e0 Error: UNC 40 sectors at LBA = 0x0044037f = 4457343 > > Commands leading to the command that caused the error were: > CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name > -- -- -- -- -- -- -- -- ---------------- -------------------- > c8 00 40 7f 03 44 e0 08 00:26:22.528 READ DMA > c8 00 48 77 03 44 e0 08 00:26:21.488 READ DMA > c8 00 50 6f 03 44 e0 08 00:26:20.448 READ DMA > c8 00 58 67 03 44 e0 08 00:25:13.872 READ DMA > c8 00 60 5f 03 44 e0 08 00:25:12.832 READ DMA > >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% 13356 - ># 2 Short offline Completed without error 00% 13333 - ># 3 Short offline Completed without error 00% 13312 - ># 4 Short offline Completed without error 00% 13290 - ># 5 Short offline Completed without error 00% 13267 - ># 6 Extended offline Completed without error 00% 13247 - ># 7 Short offline Completed without error 00% 13245 - ># 8 Short offline Completed without error 00% 13222 - ># 9 Short offline Completed without error 00% 13200 - >#10 Short offline Completed without error 00% 13182 - >#11 Short offline Completed without error 00% 13159 - >#12 Short offline Completed without error 00% 13137 - >#13 Short offline Completed without error 00% 13115 - >#14 Extended offline Completed without error 00% 13094 - >#15 Short offline Completed without error 00% 13092 - >#16 Short offline Completed without error 00% 13003 - >#17 Short offline Completed without error 00% 12980 - >#18 Short offline Completed without error 00% 12958 - >#19 Extended offline Completed without error 00% 12937 - >#20 Short offline Completed without error 00% 12935 - >#21 Short offline Completed without error 00% 12913 - > >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. |
|
From: Bruce Allen <ballen@gr...> - 2006-12-04 09:19:28
|
Mark, thanks. This is (again) showing an error 2197 GB into a 500 GB disk. Not really possible, as Sergey has pointed out. Sergey, the actual LBA reported is 4292870155 = (hex) FFE0000B. I wonder if this is a code of some type, not refering to an actual LBA value. Mark, could you please run and extended self-test (-t long), wait for it to complete, then send the results? Cheers, Bruce On Sun, 3 Dec 2006, Mark Levitt wrote: >> On Tue, 28 Nov 2006, Mark Levitt wrote: >>> OK, I've bought a 2 port SATA PCI card. I'll try connecting one of the >>> drives to it and I'll let you know what smartctl says about it. > > OK, > > I installed a Belkin SATA PCI card and connected one of the drives to it. The card seems to be identified as "sata_sil" (Silicon Image, I guess). > > It seems to show the same error, even if connected to a different SATA controller: > > Here's the output of smartcrl -a -d ata /dev/sdb: > > smartctl version 5.36 [i686-redhat-linux-gnu] Copyright (C) 2002-6 Bruce Allen > Home page is http://smartmontools.sourceforge.net/ > > === START OF INFORMATION SECTION === > Device Model: WDC WD5000YS-01MPB0 > Serial Number: WD-WMANU1514231 > Firmware Version: 07.02E07 > User Capacity: 500,107,862,016 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: Sun Dec 3 17:22:52 2006 GMT > 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: (0x85) Offline data collection activity > was aborted by an interrupting command from host. > 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: (14400) seconds. > Offline data collection > capabilities: (0x7b) SMART execute Offline immediate. > Auto Offline data collection on/off support. > Suspend Offline collection upon new > command. > Offline surface scan supported. > Self-test supported. > 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: ( 179) minutes. > Conveyance self-test routine > recommended polling time: ( 6) minutes. > > SMART Attributes Data Structure revision number: 16 > 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 200 200 051 Pre-fail Always - 0 > 3 Spin_Up_Time 0x0003 223 221 021 Pre-fail Always - 5841 > 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 20 > 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 > 7 Seek_Error_Rate 0x000f 200 200 051 Pre-fail Always - 0 > 9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 1978 > 10 Spin_Retry_Count 0x0013 100 253 051 Pre-fail Always - 0 > 11 Calibration_Retry_Count 0x0012 100 253 051 Old_age Always - 0 > 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 20 > 194 Temperature_Celsius 0x0022 253 253 000 Old_age Always - 38 > 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 > 197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 0 > 198 Offline_Uncorrectable 0x0010 200 200 000 Old_age Offline - 0 > 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 > 200 Multi_Zone_Error_Rate 0x0009 200 200 051 Pre-fail 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% 1962 - > # 2 Short offline Completed without error 00% 1938 - > # 3 Short offline Completed without error 00% 1914 - > # 4 Short offline Completed without error 00% 1890 - > # 5 Short offline Completed without error 00% 1866 - > # 6 Short offline Completed without error 00% 1842 - > # 7 Short offline Completed without error 00% 1818 - > # 8 Short offline Completed without error 00% 1797 - > # 9 Short offline Completed without error 00% 1773 - > #10 Short offline Completed without error 00% 1749 - > #11 Short offline Completed: read failure 10% 1725 4292870155 > #12 Short offline Completed without error 00% 1717 - > #13 Short offline Completed without error 00% 1693 - > #14 Short offline Completed without error 00% 1669 - > #15 Short offline Completed without error 00% 1645 - > #16 Short offline Completed without error 00% 1621 - > #17 Short offline Completed without error 00% 1597 - > #18 Short offline Completed without error 00% 1573 - > #19 Short offline Completed without error 00% 1549 - > #20 Short offline Completed without error 00% 1525 - > #21 Short offline Completed without error 00% 1501 - > > 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. > > smartctl version 5.36 [i686-redhat-linux-gnu] Copyright (C) 2002-6 Bruce Allen > Home page is http://smartmontools.sourceforge.net/ > > === START OF INFORMATION SECTION === > Device Model: WDC WD5000YS-01MPB0 > Serial Number: WD-WMANU1514231 > Firmware Version: 07.02E07 > User Capacity: 500,107,862,016 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: Sun Dec 3 17:23:37 2006 GMT > SMART support is: Available - device has SMART capability. > SMART support is: Enabled > > smartctl version 5.36 [i686-redhat-linux-gnu] Copyright (C) 2002-6 Bruce Allen > Home page is http://smartmontools.sourceforge.net/ > > === START OF READ SMART DATA SECTION === > SMART Attributes Data Structure revision number: 16 > 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 200 200 051 Pre-fail Always - 0 > 3 Spin_Up_Time 0x0003 223 221 021 Pre-fail Always - 5841 > 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 20 > 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 > 7 Seek_Error_Rate 0x000f 200 200 051 Pre-fail Always - 0 > 9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 1978 > 10 Spin_Retry_Count 0x0013 100 253 051 Pre-fail Always - 0 > 11 Calibration_Retry_Count 0x0012 100 253 051 Old_age Always - 0 > 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 20 > 194 Temperature_Celsius 0x0022 253 253 000 Old_age Always - 38 > 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 > 197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 0 > 198 Offline_Uncorrectable 0x0010 200 200 000 Old_age Offline - 0 > 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 > 200 Multi_Zone_Error_Rate 0x0009 200 200 051 Pre-fail Offline - 0 > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Smartmontools-support mailing list > Smartmontools-support@... > https://lists.sourceforge.net/lists/listinfo/smartmontools-support > |