Custom Query (1386 matches)
Results (241 - 243 of 1386)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #254 | wontfix | Smartctl 5.38 testing SAS HDD issue | ||
| Description |
Server+ LSI RAID card 1064E+ Seagate new Gen of 10K HDD:ST 900MM0006 RAID 1 seeting on 2 x SAS HDD; Use smartctlv5.43 to do test DST, skip; report error: not supported But for centos/federo, no such issue; |
|||
| #255 | wontfix | Smartctl 5.43 testing issue in Suse 10 (LSI 1064E) | ||
| Description |
Server+ LSI RAID card 1064E+ Seagate new Gen of 10K HDD:ST 900MM0006 RAID 1 seeting on 2 x SAS HDD; Use smartctlv5.43 to do test DST, skip; report error: not supported But for centos/federo, no such issue; |
|||
| #256 | fixed | Windows Event log missing log source | ||
| 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: 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 |
|||
