Custom Query (1552 matches)

Are the two phrases synonymous?

Or do ATA Error Count and Device Error Count have different meanings?

I'm comparing what's above:

• a device error under the heading of ATA Error Count

– with, for example, ​https://superuser.com/q/746720/84988 where there is:

• an ATA error but no device error.

I assume that the phrase ATA Error Count is somehow deprecated. If so, this is a request for enhancement to the GUI, for wording to be consistent.

Thanks

uname -a Linux xforce 2.6.26-2-686 #1 SMP Fri Oct 23 23:43:53 UTC 2009 i686 GNU/Linux

smartctl -V smartctl 5.39 2009-12-09 r2995 [i686-pc-linux-gnu] (local build) Copyright (C) 2002-9 by Bruce Allen, ​http://smartmontools.sourceforge.net

smartctl 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.

smartmontools release 5.39 dated 2009-12-09 at 21:00:32 UTC smartmontools SVN rev 2995 dated 2009-12-09 at 21:01:43 smartmontools build host: i686-pc-linux-gnu smartmontools build configured: 2010-01-11 23:51:52 UTC smartctl compile dated Jan 11 2010 at 23:52:24 smartmontools configure arguments: '--prefix=/usr' '--sysconfdir=/etc' '--mandir=/usr/share/man' '--with-initscriptdir=/etc/init.d' '--with-docdir=/usr/share/doc/smartmontools' '--with-selinux' 'CXXFLAGS=-g -O2' 'LDFLAGS=' 'CPPFLAGS=' 'CFLAGS=-g -O2 -fsigned-char -Wall -O2'

02:0e.0 RAID bus controller [0104]: Dell PowerEdge Expandable RAID controller 4 [1028:0013] (rev 06)

Subsystem: Dell PowerEdge Expandable RAID Controller 4e/Di [1028:016d] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping+ SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 64 (32000ns min), Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 46 Region 0: Memory at f80f0000 (32-bit, prefetchable) [size=64K] Region 2: Memory at fe9c0000 (32-bit, non-prefetchable) [size=256K] Expansion ROM at fea00000 [disabled] [size=128K] Capabilities: [c0] Power Management version 2

Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME-

Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/1 Enable-

Address: 0000000000000000 Data: 0000

Capabilities: [e0] PCI-X non-bridge device

Command: DPERE- ERO- RBC=512 OST=4 Status: Dev=02:0e.0 64bit+ 133MHz+ SCD- USC- DC=bridge DMMRBC=1024 DMOST=4 DMCRS=16 RSCEM- 266MHz- 533MHz-

Kernel driver in use: megaraid Kernel modules: megaraid_mbox

/usr/sbin/smartctl -a -d megaraid,0 -H /dev/sda : Disk Serial number: 3HW2DAL6 /usr/sbin/smartctl -a -d megaraid,1 -H /dev/sda : Disk Serial number: 3HW2DAP9 /usr/sbin/smartctl -a -d megaraid,0 -H /dev/sdb : Disk Serial number: 3HW2DAL6 /usr/sbin/smartctl -a -d megaraid,1 -H /dev/sdb : Disk Serial number: 3HW2DAP9

/usr/sbin/megactl -v a0 PERC 4e/Di bios:H418 fw:513O chan:2 ldrv:2 rbld:30% batt:good a0d0 68GiB RAID 1 1x2 optimal

row 0: a0c0t0 a0c0t1

a0d1 136GiB RAID 5 1x3 optimal

row 0: a0c1t2 a0c1t3 a0c1t4

a0c0t0 SEAGATE ST373453LC 68GiB a0d0 online a0c0t1 SEAGATE ST373453LC 68GiB a0d0 online a0c1t2 SEAGATE ST373453LC 68GiB a0d1 online a0c1t3 SEAGATE ST373453LC 68GiB a0d1 online a0c1t4 SEAGATE ST373453LC 68GiB a0d1 online

/usr/sbin/smartctl -d megaraid,2 -H /dev/sdb smartctl 5.39 2009-12-09 r2995 [i686-pc-linux-gnu] (local build) Copyright (C) 2002-9 by Bruce Allen, ​http://smartmontools.sourceforge.net

Smartctl open device: /dev/sdb [megaraid_disk_02] failed: INQUIRY failed

I observed that when smartd is polling for SMART data, Windows sometimes spins up a disk that is powered down even when “-n standby” is used in smartd.conf. The log will report that the disk is in standby mode and checks are suspended. Still you can hear that the disk is starting.

I found that this behavior is caused by smartd when opening the (physical) disk device. Smartd opens the disk asking for full read and write permissions by default. (Only when it does not have admin rights, it opens the disk with ‘0’ permissions.) But opening with full read and write permissions sometimes results in Windows spinning up the disk, most likely to consolidate Windows’ internal state with the disk. However, to query the disk’s power state, you only need a handle to query the drive’s metadata, without any read or write permissions.

The attached patch adds a new function to the base class ‘smart_device’: ‘check_os_powermode()’. The generic default implementation returns true to indicate power up or undetermined. The Win32 implementation uses Windows’ GetDevicePowerState API, and returns false when the OS indicates that the device is in low-power state. However, the point is when the ‘smart_device’ is not already opened, ‘check_os_powermode()’ opens the device temporarily using ‘0’ permissions to open only a handle for querying device metadata, and so prevents the disk from spinning up. (Even when admin rights would be available.)