Custom Query (1249 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (58 - 60 of 1249)

Ticket Resolution Summary Owner Reporter
#88 fixed Store last selective self-test span in smartd state file Christian Franke Christian Franke
Description

For scheduled selective self-tests, smartd reads the last test span from the selective self-test log of the drive. At least some WDC drives reportedly do not preserve the self-test log accross power cycles, see smartmontools-support list.

To support such drives, smartd should store the last test span in its state file instead.

#89 fixed Use log directory to check for old error/self-test log support Christian Franke Christian Franke
Description

Smartctl and smartd assume that the old SMART error log (log address 0x01) is supported if an error-logging capability bit in IDENTIFY or SMART data is set. Same applies to old SMART self-test log (log address 0x06). These logs were introduced in ATA-5 and are now outdated because 48-bit LBA addresses are not supported. Recent devices may only support the newer 48-bit capable logs (extended comprehensive error-log, extended self-test log) introduced in ATA-6.

smartctl -a ... prints misleading messages then:

Error SMART Error Log Read failed: Input/output error
Smartctl: SMART Error Log Read Failed
Error SMART Error Self-Test Log Read failed: Input/output error
Smartctl: SMART Self Test Log Read Failed

Misleading kernel messages may appear during smartd startup:

... kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
... kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
... kernel: ide: failed opcode was: 0xb0
... smartd[...]: Device: /dev/hda, Read SMART Self Test Log Failed
... smartd[...]: Device: /dev/hda, no SMART Self-Test log; remove -l selftest Directive from smartd.conf

(smartctl -x ... is not affected)

Smartctl and smartd should read the log directory (log address 0x00) to check whether the old logs are still supported and print an "unsupported" message if not.

#91 fixed smartctl, standby mode not detected properly on FreeBSD Dan Lukes drsweety
Description

Hi!

I've enabled the standby timer on all my harddisks with "camcontrol standby adaX -t 900" (=which sends the STANDBY ATA cmd to the drive (=idle now, arm standby timer to 900s)). This works fine and "smartctl" recognises that the drive is in standby mode:

# smartctl -A -n standby /dev/ada3
smartctl 5.39.1 2010-01-28 r3054 [FreeBSD 8.1-RELEASE amd64] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

Device is in STANDBY mode, exit(2)
# camcontrol cmd ada3 -a "E5 00 00 00 00 00 00 00 00 00 00 00" -r -
50 00 00 00 00 40 00 00 00 00 00

However, if a drive is currently active it still thinks that the drive is in standby mode even though it clearly is not:

# dd if=/dev/ada0 of=/dev/null count=1
1+0 records in
1+0 records out
512 bytes transferred in 0.034235 secs (14955 bytes/sec)
# ./smartctl -A -n standby /dev/ada0
smartctl 5.39.1 2010-01-28 r3054 [FreeBSD 8.1-RELEASE amd64] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

Power mode: 00
Device is in STANDBY mode, exit(2)
# camcontrol cmd ada0 -a "E5 00 00 00 00 00 00 00 00 00 00 00" -r -
50 00 00 00 00 00 00 00 00 FF 00
#

Note that the "Power mode: 00" output was added by me to atacmds.cpp for debugging purposes. It outputs the value of "result" from within "ataCheckPowerMode". As you can see from the "camcontrol" output the device is active (sector count=FF). I'm not sure why the output for sector count from "camcontrol" and "smartctl" differ... Is this working as designed?

Note: See TracQuery for help on using queries.