NetBSD Problem Report #42552

From leo@slug.localdomain  Thu Dec 31 09:21:23 2009
Return-Path: <leo@slug.localdomain>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by www.NetBSD.org (Postfix) with ESMTP id A610963C37E
	for <gnats-bugs@gnats.NetBSD.org>; Thu, 31 Dec 2009 09:21:23 +0000 (UTC)
Message-Id: <20091231092121.C57E868843@slug.localdomain>
Date: Thu, 31 Dec 2009 10:21:21 +0100 (CET)
From: leo@marco.de
Reply-To: leo@marco.de
To: gnats-bugs@gnats.NetBSD.org
Subject: smartd reports "not capable of SMART self-check"
X-Send-Pr-Version: 3.95

>Number:         42552
>Category:       kern
>Synopsis:       smartd reports "not capable of SMART self-check"
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Dec 31 09:25:00 +0000 2009
>Last-Modified:  Mon Jan 11 00:15:03 +0000 2010
>Originator:     leo@marco.de
>Release:        NetBSD 5.0_STABLE
>Organization:
Matthias Pfaller                            Software Entwicklung
marco Systemanalyse und Entwicklung GmbH    Tel   +49 8131 5161 41
Hans-Böckler-Str. 2, D 85221 Dachau         Fax   +49 8131 5161 66
http://www.marco.de/                        Email leo@marco.de
>Environment:


System: NetBSD zork 5.0_STABLE NetBSD 5.0_STABLE (ZORK) #3: Wed Dec 23 17:10:41 CET 2009 leo@slug:/usr/src-5.0/sys/arch/amd64/compile/ZORK amd64
Architecture: x86_64
Machine: amd64
>Description:
	Two days ago I installed smartmontools on my system. Now I'm getting
		Dec 31 08:26:24 zork smartd[5883]: Device: /dev/wd2d, not capable of SMART self-check 
		Dec 31 08:26:25 zork smartd[5883]: Device: /dev/wd2d, failed to read SMART Attribute Data 
		Dec 31 08:26:26 zork smartd[5883]: Device: /dev/wd2d, Read SMART Self Test Log Failed 
	reports from smartd, while smartctl doesn't show any problems.
	Using google I found, that linux users had a similar problem two years
	ago. It was caused by a kernel bug. Maybe we have a similar problem.
	See
		http://article.gmane.org/gmane.linux.ide/20799/raw
>How-To-Repeat:
	run smartd for a couple of hours (maybe you need two drives).
>Fix:
	unknown.
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
    2006, 2007, 2008, 2009
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights reserved.

NetBSD 5.0_STABLE (ZORK) #3: Wed Dec 23 17:10:41 CET 2009
	leo@slug:/usr/src-5/sys/arch/amd64/compile/ZORK
total memory = 2000 MB
avail memory = 1930 MB
timecounter: Timecounters tick every 10.000 msec
RTC BIOS diagnostic error 11<memory_size>
timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100
SMBIOS rev. 2.5 @ 0xf0450 (80 entries)
Dell Inc. OptiPlex 755                 
mainbus0 (root)
cpu0 at mainbus0 apid 0: Intel 686-class, 2327MHz, id 0x6fb
cpu1 at mainbus0 apid 1: Intel 686-class, 2327MHz, id 0x6fb
ioapic0 at mainbus0 apid 8: pa 0xfec00000, version 20, 24 pins
acpi0 at mainbus0: Intel ACPICA 20080321
acpi0: X/RSDT: OemId <DELL  , B9K    ,00000015>, AslId <ASL ,00000061>
acpi0: SCI interrupting at int 9
acpi0: fixed-feature power button present
timecounter: Timecounter "ACPI-Fast" frequency 3579545 Hz quality 1000
ACPI-Fast 24-bit timer
acpibut0 at acpi0 (VBTN, PNP0C0C): ACPI Power Button
pcppi0 at acpi0 (SPK, PNP0800): io 0x61
midi0 at pcppi0: PC speaker (CPU-intensive output)
sysbeep0 at pcppi0
attimer0 at acpi0 (TMR, PNP0100): io 0x40-0x5f irq 0
lpt0 at acpi0 (PRT, PNP0401): io 0x378-0x37f,0x778-0x77f irq 7
com0 at acpi0 (COMA, PNP0501-1): io 0x3f8-0x3ff irq 4
com0: ns16550a, working fifo
TPM (SMO1200) at acpi0 not configured
hpet0 at acpi0 (HPET, PNP0103): mem 0xfed00000-0xfed003ff
timecounter: Timecounter "hpet0" frequency 14318179 Hz quality 2000
attimer0: attached to pcppi0
pci0 at mainbus0 bus 0: configuration mode 1
pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
pchb0 at pci0 dev 0 function 0
pchb0: vendor 0x8086 product 0x29b0 (rev. 0x02)
agp0 at pchb0: detected 6140k stolen memory
agp0: aperture at 0xd0000000, size 0x10000000
ppb0 at pci0 dev 1 function 0: vendor 0x8086 product 0x29b1 (rev. 0x02)
pci1 at ppb0 bus 1
pci1: i/o space, memory space enabled, rd/line, wr/inv ok
vga0 at pci0 dev 2 function 0: vendor 0x8086 product 0x29b2 (rev. 0x02)
wsdisplay0 at vga0 kbdmux 1: console (80x25, vt100 emulation)
wsmux1: connecting to wsdisplay0
drm at vga0 not configured
vendor 0x8086 product 0x29b3 (miscellaneous display, revision 0x02) at pci0 dev 2 function 1 not configured
vendor 0x8086 product 0x29b4 (miscellaneous communications, revision 0x02) at pci0 dev 3 function 0 not configured
pciide0 at pci0 dev 3 function 2
pciide0: vendor 0x8086 product 0x29b6 (rev. 0x02)
pciide0: bus-master DMA support present, but unused (no driver support)
pciide0: primary channel wired to native-PCI mode
pciide0: using ioapic0 pin 18 for native-PCI interrupt
atabus6 at pciide0 channel 0
pciide0: secondary channel wired to native-PCI mode
atabus7 at pciide0 channel 1
vendor 0x8086 product 0x29b7 (serial communications, interface 0x02, revision 0x02) at pci0 dev 3 function 3 not configured
wm0 at pci0 dev 25 function 0: 82801I (AMT) LAN Controller, rev. 2
wm0: interrupting at ioapic0 pin 21
wm0: PCI-Express bus
wm0: FLASH
wm0: Ethernet address 00:1a:a0:e8:43:9b
igphy0 at wm0 phy 1: i82566 10/100/1000 media interface, rev. 0
igphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
uhci0 at pci0 dev 26 function 0: vendor 0x8086 product 0x2937 (rev. 0x02)
uhci0: interrupting at ioapic0 pin 16
usb0 at uhci0: USB revision 1.0
uhci1 at pci0 dev 26 function 1: vendor 0x8086 product 0x2938 (rev. 0x02)
uhci1: interrupting at ioapic0 pin 17
usb1 at uhci1: USB revision 1.0
ehci0 at pci0 dev 26 function 7: vendor 0x8086 product 0x293c (rev. 0x02)
ehci0: interrupting at ioapic0 pin 22
ehci0: EHCI version 1.0
ehci0: wrong number of companions (3 != 2)
ehci0: companion controllers, 2 ports each: uhci0 uhci1
usb2 at ehci0: USB revision 2.0
hdaudio0 at pci0 dev 27 function 0: HD Audio Controller
hdaudio0: interrupting at ioapic0 pin 16
hdafg0 at hdaudio0 vendor 0x11D4 product 0x1984 nid 0x01 (firmware configuration)
hdafg0: DAC0:04, Analog Speaker: Jack (Green, 12)
hdafg0: ADC1:08, Analog Mic In: Jack (Pink, 14)
hdafg0: ADC2:09, Analog Line In: Jack (Blue, 15)
hdafg0: DAC3:03, Analog HP Out: Jack (Green, 11)
hdafg0: 2ch/2ch 8000Hz-192000Hz 16/16 20/32 24/32
audio0 at hdafg0: full duplex, playback, capture, independent
ppb1 at pci0 dev 28 function 0: vendor 0x8086 product 0x2940 (rev. 0x02)
pci2 at ppb1 bus 2
pci2: i/o space, memory space enabled, rd/line, wr/inv ok
uhci2 at pci0 dev 29 function 0: vendor 0x8086 product 0x2934 (rev. 0x02)
uhci2: interrupting at ioapic0 pin 23
usb3 at uhci2: USB revision 1.0
uhci3 at pci0 dev 29 function 1: vendor 0x8086 product 0x2935 (rev. 0x02)
uhci3: interrupting at ioapic0 pin 17
usb4 at uhci3: USB revision 1.0
uhci4 at pci0 dev 29 function 2: vendor 0x8086 product 0x2936 (rev. 0x02)
uhci4: interrupting at ioapic0 pin 18
usb5 at uhci4: USB revision 1.0
ehci1 at pci0 dev 29 function 7: vendor 0x8086 product 0x293a (rev. 0x02)
ehci1: interrupting at ioapic0 pin 23
ehci1: EHCI version 1.0
ehci1: companion controllers, 2 ports each: uhci2 uhci3 uhci4
usb6 at ehci1: USB revision 2.0
ppb2 at pci0 dev 30 function 0: vendor 0x8086 product 0x244e (rev. 0x92)
pci3 at ppb2 bus 3
pci3: i/o space, memory space enabled
wm1 at pci3 dev 0 function 0: Intel i82541PI 1000BASE-T Ethernet, rev. 5
wm1: interrupting at ioapic0 pin 16
wm1: 32-bit 33MHz PCI bus
wm1: 64 word (6 address bits) MicroWire EEPROM
wm1: Ethernet address 00:0e:0c:c4:46:73
igphy1 at wm1 phy 1: Intel IGP01E1000 Gigabit PHY, rev. 0
igphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
wm2 at pci3 dev 2 function 0: Intel i82541PI 1000BASE-T Ethernet, rev. 5
wm2: interrupting at ioapic0 pin 18
wm2: 32-bit 33MHz PCI bus
wm2: 64 word (6 address bits) MicroWire EEPROM
wm2: Ethernet address 00:0e:0c:c4:43:51
igphy2 at wm2 phy 1: Intel IGP01E1000 Gigabit PHY, rev. 0
igphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
ichlpcib0 at pci0 dev 31 function 0
ichlpcib0: vendor 0x8086 product 0x2914 (rev. 0x02)
timecounter: Timecounter "ichlpcib0" frequency 3579545 Hz quality 1000
ichlpcib0: 24-bit timer
ichlpcib0: TCO timer reboot disabled by hardware; hope SMBIOS properly handles it.
ichlpcib0: TCO (watchdog) timer configured.
ahcisata0 at pci0 dev 31 function 2: vendor 0x8086 product 0x2922
ahcisata0: interrupting at ioapic0 pin 18
ahcisata0: AHCI revision 1.2, 6 ports, 32 command slots, features 0xe722e0e0
atabus0 at ahcisata0 channel 0
atabus1 at ahcisata0 channel 1
atabus2 at ahcisata0 channel 2
atabus3 at ahcisata0 channel 3
atabus5 at ahcisata0 channel 5
ichsmb0 at pci0 dev 31 function 3: vendor 0x8086 product 0x2930 (rev. 0x02)
ichsmb0: interrupting at ioapic0 pin 18
iic0 at ichsmb0: I2C bus
spdmem0 at iic0 addr 0x50
spdmem0: DDR2 SDRAM memory, no parity or ECC, 1024MB, 667MHz (PC2-5300)
spdmem0: 14 rows, 10 cols, 2 ranks, 4 banks/chip, 3.00ns cycle time
spdmem0: tAA-tRCD-tRP-tRAS: 5-5-5-15
spdmem0: voltage SSTL 1.8V, refresh time 7.8us (self-refreshing)
spdmem1 at iic0 addr 0x52
spdmem1: DDR2 SDRAM memory, no parity or ECC, 1024MB, 667MHz (PC2-5300)
spdmem1: 14 rows, 10 cols, 2 ranks, 4 banks/chip, 3.00ns cycle time
spdmem1: tAA-tRCD-tRP-tRAS: 5-5-5-15
spdmem1: voltage SSTL 1.8V, refresh time 7.8us (self-refreshing)
isa0 at ichlpcib0
timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
timecounter: Timecounter "TSC" frequency 2327628380 Hz quality 3000
uhub0 at usb0: vendor 0x8086 UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhub1 at usb1: vendor 0x8086 UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhub2 at usb2: vendor 0x8086 EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub2: 6 ports with 6 removable, self powered
uhub3 at usb3: vendor 0x8086 UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered
uhub4 at usb4: vendor 0x8086 UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub4: 2 ports with 2 removable, self powered
uhub5 at usb5: vendor 0x8086 UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub5: 2 ports with 2 removable, self powered
uhub6 at usb6: vendor 0x8086 EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub6: 6 ports with 6 removable, self powered
ahcisata0 port 2: device present, speed: 3.0Gb/s
ahcisata0 port 3: device present, speed: 3.0Gb/s
ahcisata0 port 0: PHY offline
ahcisata0 port 1: PHY offline
ahcisata0 port 5: PHY offline
wd2 at atabus2 drive 0: <ST31500541AS>
wd2: quirks 2<FORCE_LBA48>
wd2: drive supports 16-sector PIO transfers, LBA48 addressing
wd2: 1397 GB, 2907021 cyl, 16 head, 63 sec, 512 bytes/sect x 2930277168 sectors
wd2: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
wd2(ahcisata0:2:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) (using DMA)
wd3 at atabus3 drive 0: <ST31500541AS>
wd3: quirks 2<FORCE_LBA48>
wd3: drive supports 16-sector PIO transfers, LBA48 addressing
wd3: 1397 GB, 2907021 cyl, 16 head, 63 sec, 512 bytes/sect x 2930277168 sectors
wd3: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
wd3(ahcisata0:3:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) (using DMA)
umass0 at uhub2 port 1 configuration 1 interface 0
umass0: USB Flash Disk, rev 2.00/11.00, addr 2
umass0: using SCSI over Bulk-Only
scsibus0 at umass0: 2 targets, 1 lun per target
sd0 at scsibus0 target 0 lun 0: <USB, Flash Disk, 1100> disk fixed
sd0: 1912 MB, 3936 cyl, 16 head, 63 sec, 512 bytes/sect x 3915776 sectors
Kernelized RAIDframe activated
raid0: RAID Level 1
raid0: Components: /dev/wd2e /dev/wd3e
raid0: Total Sectors: 2923986176 (1427727 MB)
boot device: sd0
root on sd0a dumps on sd0b
root file system type: ffs
uhidev0 at uhub1 port 2 configuration 1 interface 0
uhidev0: Dell Dell USB Keyboard, rev 1.10/3.52, addr 2, iclass 3/1
ukbd0 at uhidev0
wskbd0 at ukbd0 mux 1
wskbd0: connecting to wsdisplay0
pppoe0: connected to ac2.muc1
wsdisplay0: screen 1 added (80x25, vt100 emulation)
wsdisplay0: screen 2 added (80x25, vt100 emulation)
wsdisplay0: screen 3 added (80x25, vt100 emulation)
wsdisplay0: screen 4 added (80x25, vt100 emulation)

>Audit-Trail:
From: Manuel Bouyer <bouyer@antioche.eu.org>
To: gnats-bugs@NetBSD.org
Cc: kern-bug-people@NetBSD.org, gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
Subject: Re: kern/42552: smartd reports "not capable of SMART self-check"
Date: Mon, 4 Jan 2010 17:32:39 +0100

 On Thu, Dec 31, 2009 at 09:25:01AM +0000, leo@marco.de wrote:
 > 	Two days ago I installed smartmontools on my system. Now I'm getting
 > 		Dec 31 08:26:24 zork smartd[5883]: Device: /dev/wd2d, not capable of SMART self-check 
 > 		Dec 31 08:26:25 zork smartd[5883]: Device: /dev/wd2d, failed to read SMART Attribute Data 
 > 		Dec 31 08:26:26 zork smartd[5883]: Device: /dev/wd2d, Read SMART Self Test Log Failed 
 > 	reports from smartd, while smartctl doesn't show any problems.
 > 	Using google I found, that linux users had a similar problem two years
 > 	ago. It was caused by a kernel bug. Maybe we have a similar problem.
 > 	See
 > 		http://article.gmane.org/gmane.linux.ide/20799/raw


 Are you seeing it only for wd2, or for all drives in the system ?

 -- 
 Manuel Bouyer <bouyer@antioche.eu.org>
      NetBSD: 26 ans d'experience feront toujours la difference
 --

From: Manuel Bouyer <bouyer@antioche.eu.org>
To: gnats-bugs@NetBSD.org
Cc: kern-bug-people@NetBSD.org, gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
Subject: Re: kern/42552: smartd reports "not capable of SMART self-check"
Date: Mon, 4 Jan 2010 17:59:43 +0100

 --cNdxnHkX5QqsyA0e
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline

 On Thu, Dec 31, 2009 at 09:25:01AM +0000, leo@marco.de wrote:
 > >Description:
 > 	Two days ago I installed smartmontools on my system. Now I'm getting
 > 		Dec 31 08:26:24 zork smartd[5883]: Device: /dev/wd2d, not capable of SMART self-check 
 > 		Dec 31 08:26:25 zork smartd[5883]: Device: /dev/wd2d, failed to read SMART Attribute Data 
 > 		Dec 31 08:26:26 zork smartd[5883]: Device: /dev/wd2d, Read SMART Self Test Log Failed 
 > 	reports from smartd, while smartctl doesn't show any problems.
 > 	Using google I found, that linux users had a similar problem two years
 > 	ago. It was caused by a kernel bug. Maybe we have a similar problem.
 > 	See
 > 		http://article.gmane.org/gmane.linux.ide/20799/raw

 Maybe we need to set r_error to 0 in all cases. Can you try the attached
 patch ?

 -- 
 Manuel Bouyer <bouyer@antioche.eu.org>
      NetBSD: 26 ans d'experience feront toujours la difference
 --

 --cNdxnHkX5QqsyA0e
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: attachment; filename=diff

 Index: ahcisata_core.c
 ===================================================================
 RCS file: /cvsroot/src/sys/dev/ic/ahcisata_core.c,v
 retrieving revision 1.18.4.1
 diff -u -p -u -r1.18.4.1 ahcisata_core.c
 --- ahcisata_core.c	19 Feb 2009 20:30:15 -0000	1.18.4.1
 +++ ahcisata_core.c	4 Jan 2010 16:58:14 -0000
 @@ -825,6 +825,7 @@ ahci_cmd_complete(struct ata_channel *ch
  		ata_c->r_count = 0;
  		ata_c->r_sector = 0;
  		ata_c->r_cyl = 0;
 +		ata_c->r_error = 0;
  		if (chp->ch_status & WDCS_BSY) {
  			ata_c->flags |= AT_TIMEOU;
  		} else if (chp->ch_status & WDCS_ERR) {

 --cNdxnHkX5QqsyA0e--

From: Matthias Pfaller <leo@marco.de>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/42552: smartd reports "not capable of SMART self-check"
Date: Mon, 04 Jan 2010 20:07:50 +0100

 This is a multi-part message in MIME format.
 --------------020708050409060500090803
 Content-Type: text/plain; charset=ISO-8859-1; format=flowed
 Content-Transfer-Encoding: 7bit

 Manuel Bouyer wrote:
 > The following reply was made to PR kern/42552; it has been noted by GNATS.
 >
 > From: Manuel Bouyer <bouyer@antioche.eu.org>
 > To: gnats-bugs@NetBSD.org
 > Cc: kern-bug-people@NetBSD.org, gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
 > Subject: Re: kern/42552: smartd reports "not capable of SMART self-check"
 > Date: Mon, 4 Jan 2010 17:59:43 +0100
 >
 >  --cNdxnHkX5QqsyA0e
 >  Content-Type: text/plain; charset=us-ascii
 >  Content-Disposition: inline
 >  
 >  On Thu, Dec 31, 2009 at 09:25:01AM +0000, leo@marco.de wrote:
 >  > >Description:
 >  > 	Two days ago I installed smartmontools on my system. Now I'm getting
 >  > 		Dec 31 08:26:24 zork smartd[5883]: Device: /dev/wd2d, not capable of SMART self-check 
 >  > 		Dec 31 08:26:25 zork smartd[5883]: Device: /dev/wd2d, failed to read SMART Attribute Data 
 >  > 		Dec 31 08:26:26 zork smartd[5883]: Device: /dev/wd2d, Read SMART Self Test Log Failed 
 >  > 	reports from smartd, while smartctl doesn't show any problems.
 >  > 	Using google I found, that linux users had a similar problem two years
 >  > 	ago. It was caused by a kernel bug. Maybe we have a similar problem.
 >  > 	See
 >  > 		http://article.gmane.org/gmane.linux.ide/20799/raw
 >  
 >  Maybe we need to set r_error to 0 in all cases. Can you try the attached
 >  patch ?
 >  
 >  -- 
 >  Manuel Bouyer <bouyer@antioche.eu.org>
 >       NetBSD: 26 ans d'experience feront toujours la difference
 >  --
 >  
 >  --cNdxnHkX5QqsyA0e
 >  Content-Type: text/plain; charset=us-ascii
 >  Content-Disposition: attachment; filename=diff
 >  
 >  Index: ahcisata_core.c
 >  ===================================================================
 >  RCS file: /cvsroot/src/sys/dev/ic/ahcisata_core.c,v
 >  retrieving revision 1.18.4.1
 >  diff -u -p -u -r1.18.4.1 ahcisata_core.c
 >  --- ahcisata_core.c	19 Feb 2009 20:30:15 -0000	1.18.4.1
 >  +++ ahcisata_core.c	4 Jan 2010 16:58:14 -0000
 >  @@ -825,6 +825,7 @@ ahci_cmd_complete(struct ata_channel *ch
 >   		ata_c->r_count = 0;
 >   		ata_c->r_sector = 0;
 >   		ata_c->r_cyl = 0;
 >  +		ata_c->r_error = 0;
 >   		if (chp->ch_status & WDCS_BSY) {
 >   			ata_c->flags |= AT_TIMEOU;
 >   		} else if (chp->ch_status & WDCS_ERR) {
 >  
 >  --cNdxnHkX5QqsyA0e--
 >  
 >   
 I have installed a kernel with this patch, but I can't reboot at the 
 moment. I have an "atactl setstandby 3600" in my /etc/rc.local, so maybe 
 the drives are in standby, when the error occurs.

 regards, Matthias


 --------------020708050409060500090803
 Content-Type: text/plain;
  name="smartd.txt"
 Content-Transfer-Encoding: 7bit
 Content-Disposition: inline;
  filename="smartd.txt"

 Jan  4 06:26:25 zork smartd[5883]: Device: /dev/wd2d, not capable of SMART self-check 
 Jan  4 06:26:26 zork smartd[5883]: Device: /dev/wd2d, failed to read SMART Attribute Data 
 Jan  4 06:26:27 zork smartd[5883]: Device: /dev/wd2d, Read SMART Self Test Log Failed 
 Jan  4 06:26:28 zork smartd[5883]: Device: /dev/wd2d, Read SMART Error Log Failed 
 Jan  4 06:26:34 zork smartd[5883]: Device: /dev/wd3d, not capable of SMART self-check 
 Jan  4 06:26:35 zork smartd[5883]: Device: /dev/wd3d, failed to read SMART Attribute Data 
 Jan  4 06:26:36 zork smartd[5883]: Device: /dev/wd3d, Read SMART Self Test Log Failed 
 Jan  4 06:26:37 zork smartd[5883]: Device: /dev/wd3d, Read SMART Error Log Failed 
 Jan  4 08:26:23 zork smartd[5883]: Device: /dev/wd2d, not capable of SMART self-check 
 Jan  4 08:26:24 zork smartd[5883]: Device: /dev/wd2d, failed to read SMART Attribute Data 
 Jan  4 08:26:25 zork smartd[5883]: Device: /dev/wd2d, Read SMART Self Test Log Failed 
 Jan  4 08:26:26 zork smartd[5883]: Device: /dev/wd2d, Read SMART Error Log Failed 
 Jan  4 08:26:32 zork smartd[5883]: Device: /dev/wd3d, not capable of SMART self-check 
 Jan  4 08:26:33 zork smartd[5883]: Device: /dev/wd3d, failed to read SMART Attribute Data 
 Jan  4 08:26:34 zork smartd[5883]: Device: /dev/wd3d, Read SMART Self Test Log Failed 
 Jan  4 08:26:35 zork smartd[5883]: Device: /dev/wd3d, Read SMART Error Log Failed 

 --------------020708050409060500090803--

From: Manuel Bouyer <bouyer@antioche.eu.org>
To: gnats-bugs@NetBSD.org
Cc: kern-bug-people@NetBSD.org, gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org,
        leo@marco.de
Subject: Re: kern/42552: smartd reports "not capable of SMART self-check"
Date: Mon, 4 Jan 2010 20:33:43 +0100

 On Mon, Jan 04, 2010 at 07:10:06PM +0000, Matthias Pfaller wrote:
 >  I have installed a kernel with this patch, but I can't reboot at the 
 >  moment. I have an "atactl setstandby 3600" in my /etc/rc.local, so maybe 
 >  the drives are in standby, when the error occurs.

 Yes, that could explain it. Not sure if the self test can be run
 when the drive is in standby mode. If the patch doesn't help, can you
 see if disabling the standby timer solves the problem ?

 -- 
 Manuel Bouyer <bouyer@antioche.eu.org>
      NetBSD: 26 ans d'experience feront toujours la difference
 --

From: Matthias Pfaller <leo@marco.de>
To: Manuel Bouyer <bouyer@antioche.eu.org>
Cc: gnats-bugs@NetBSD.org
Subject: Re: kern/42552: smartd reports "not capable of SMART self-check"
Date: Wed, 06 Jan 2010 17:14:36 +0100

 Manuel Bouyer wrote:
 > On Mon, Jan 04, 2010 at 07:10:06PM +0000, Matthias Pfaller wrote:
 >   
 >>  I have installed a kernel with this patch, but I can't reboot at the 
 >>  moment. I have an "atactl setstandby 3600" in my /etc/rc.local, so maybe 
 >>  the drives are in standby, when the error occurs.
 >>     
 >
 > Yes, that could explain it. Not sure if the self test can be run
 > when the drive is in standby mode. If the patch doesn't help, can you
 > see if disabling the standby timer solves the problem ?
 >
 >   
 Sorry, your patch didn't help. Now I'll try for a couple of days without 
 standby.

 Regards, Matthias

From: Matthias Pfaller <leo@marco.de>
To: gnats-bugs@NetBSD.org
Cc: netbsd-bugs@NetBSD.org
Subject: Re: kern/42552: smartd reports "not capable of SMART self-check"
Date: Sat, 09 Jan 2010 16:49:14 +0100

 Manuel Bouyer wrote:
 > On Mon, Jan 04, 2010 at 07:10:06PM +0000, Matthias Pfaller wrote:
 >   
 >>  I have installed a kernel with this patch, but I can't reboot at the 
 >>  moment. I have an "atactl setstandby 3600" in my /etc/rc.local, so maybe 
 >>  the drives are in standby, when the error occurs.
 >>     
 >
 > Yes, that could explain it. Not sure if the self test can be run
 > when the drive is in standby mode. If the patch doesn't help, can you
 > see if disabling the standby timer solves the problem ?
 >
 >   
 Disabling the standby timer "solves" the problem. But the documentation 
 of smartd states, that it should be able to work with drives in standby. 
 So either this doesn't work with netbsd or it just doesn't work with 
 ahcisata.
 Another thing: My previous system had drives on a piixide and when the 
 drives woke up from standby, the kernel did not log a error message. Now 
 I get errors like these from time to time:

 Jan 2 02:03:02 zork /netbsd: wd3e: device timeout reading fsbn 597712576 
 of 59$
 Jan 2 02:03:02 zork /netbsd: ahcisata0 port 3: device present, speed: 
 3.0Gb/s
 Jan 2 02:03:02 zork /netbsd: wd3: soft error (corrected)


 Is this something to be fixed or is piixide just more tolerant?

 Regards, Matthias

From: Manuel Bouyer <bouyer@antioche.eu.org>
To: gnats-bugs@netbsd.org
Cc: kern-bug-people@netbsd.org, gnats-admin@netbsd.org, netbsd-bugs@netbsd.org,
        leo@marco.de
Subject: Re: kern/42552: smartd reports "not capable of SMART self-check"
Date: Sun, 10 Jan 2010 21:52:07 +0100

 On Sat, Jan 09, 2010 at 03:50:05PM +0000, Matthias Pfaller wrote:
 >  Manuel Bouyer wrote:
 >  > On Mon, Jan 04, 2010 at 07:10:06PM +0000, Matthias Pfaller wrote:
 >  >   
 >  >>  I have installed a kernel with this patch, but I can't reboot at the 
 >  >>  moment. I have an "atactl setstandby 3600" in my /etc/rc.local, so maybe 
 >  >>  the drives are in standby, when the error occurs.
 >  >>     
 >  >
 >  > Yes, that could explain it. Not sure if the self test can be run
 >  > when the drive is in standby mode. If the patch doesn't help, can you
 >  > see if disabling the standby timer solves the problem ?
 >  >
 >  >   
 >  Disabling the standby timer "solves" the problem. But the documentation 
 >  of smartd states, that it should be able to work with drives in standby. 
 >  So either this doesn't work with netbsd or it just doesn't work with 
 >  ahcisata.
 >  Another thing: My previous system had drives on a piixide and when the 
 >  drives woke up from standby, the kernel did not log a error message. Now 
 >  I get errors like these from time to time:
 >  
 >  Jan 2 02:03:02 zork /netbsd: wd3e: device timeout reading fsbn 597712576 
 >  of 59$
 >  Jan 2 02:03:02 zork /netbsd: ahcisata0 port 3: device present, speed: 
 >  3.0Gb/s
 >  Jan 2 02:03:02 zork /netbsd: wd3: soft error (corrected)
 >  
 >  
 >  Is this something to be fixed or is piixide just more tolerant?

 It's possible this requires SATA power management support in ahcisata.
 But I didn't read this part of the spec yet :)

 -- 
 Manuel Bouyer <bouyer@antioche.eu.org>
      NetBSD: 26 ans d'experience feront toujours la difference
 --

>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.