Custom Query (1561 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (397 - 399 of 1561)

Ticket Resolution Summary Owner Reporter
#1170 fixed Windows builds: No effect of ASLR due to missing relocation information Christian Franke Christian Franke
Description

The exe files from recent smartmontools builds for Windows indicate ASLR compatibility but do not provide the required relocation information:

$ x86_64-w64-mingw32-objdump -p smartctl.exe
...
        relocations stripped

The default LDFLAGS set by the configure script do not work as expected with some recent versions of MinGW-w64 toolchain:

  • 7.3.0-11ubuntu1+20.2build1 on Ubuntu 18.04.1 (used for CircleCI and 7.0-1 release builds)
  • 7.4.0-1 on Cygwin

It worked in the past with:

  • 4.9.1-19+14.3 on Debian 8.9 (used for 6.6-1 release build)
#172 wontfix Windows XP x64 smartctl support for 3ware Christian Franke dmarty
Description

Are there any plans to add 3ware support to smartctl for the windows version? Specifically, I'm hoping to be able to send the smartctl -l scterc,70,70 to drives behind my 3ware controller, so they behave more like enterprise drives as regards error recovery. I know the drives I'm using support this as I've tried them when connected to the MB, but I can't address them behind my new 3ware controller, at least, not under the windows version of smartctl.

Many thanks!

#256 fixed Windows Event log missing log source somebody edwardk
Description

The Windows Event log service does not have a message file registered when the smartd service is installed. This results in Event log messages similar to:

The description for Event ID ( 2 ) in Source ( smartd ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: smartd, 3648, Info, Device:
.\scsi1: [areca_disk#08_enc#01], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 69 to 68, Device:
.\scsi1: [areca_disk#08_enc#01], SMART Usage Attribute: 194 Temperature_Celsius changed from 31 to 32.

Registry entry keys can be added to fix this issue at

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\smartd

For my system:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\smartd]
"EventMessageFile"=hex(2):43,00,3a,00,5c,00,50,00,72,00,6f,00,67,00,72,00,61,\
  00,6d,00,20,00,46,00,69,00,6c,00,65,00,73,00,20,00,28,00,78,00,38,00,36,00,\
  29,00,5c,00,47,00,53,00,6d,00,61,00,72,00,74,00,43,00,6f,00,6e,00,74,00,72,\
  00,6f,00,6c,00,5c,00,62,00,69,00,6e,00,5c,00,73,00,79,00,73,00,6c,00,6f,00,\
  67,00,65,00,76,00,74,00,2e,00,65,00,78,00,65,00,00,00
"TypesSupported"=dword:00000007

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.