Custom Query (1384 matches)
Results (157 - 159 of 1384)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#250 | fixed | implement -g/-s wcache and lookahead for the SCSI drvies | ||
Description |
Most of SCSI/SAS drives are supporting cache control, so it is possible to implement this functionality. This should help a lot for SAS drives behind the RAID - some of them turning off write cache if drive is not "native". Tested on scsi, megaraid and cciss device types on Linux. It was found that cciss silently filtering MODE SELECT command, so actual values are not changed. On megaraid and direct connection everything works as expected. |
|||
#252 | fixed | add disks on megaraid sas controller to DEVICESCAN | ||
Description |
I decided to add autoscan functionality for drives on MegaSAS controllers. Main motivation for this was that devices on such controllers having random numbers, from 0 to ~250 and it is very annoying to write smartd configuration (i used shell + MegaCli in the past). There is no ioctl documentation provided, so i did patch based on MegaCli tool behavior (with strace and LD_PRELAOD for IOCTL) and FreeBSD driver sources which contain similar code. What this patch is doing:
Code changes:
Example: [root@p2986890 smartmontools]# ./smartctl --scan /dev/sda -d scsi # /dev/sda, SCSI device /dev/bus/0 -d megaraid,5 # /dev/bus/0 [megaraid_disk_05], SCSI device /dev/bus/0 -d megaraid,7 # /dev/bus/0 [megaraid_disk_07], SCSI device [root@p2986890 smartmontools]# ./smartctl --scan-open # /dev/sda -d scsi # /dev/sda, SCSI device open failed: DELL or MegaRaid controller, please try adding '-d megaraid,N' /dev/bus/0 -d sat+megaraid,5 # /dev/bus/0 [megaraid_disk_05] [SAT], ATA device /dev/bus/0 -d sat+megaraid,7 # /dev/bus/0 [megaraid_disk_07] [SAT], ATA device [root@p2986890 smartmontools]# ./smartd -d smartd 6.1 2012-12-14 r3732M [x86_64-linux-2.6.32-279.14.1.el6.x86_64] (local build) Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org No configuration file /usr/local/etc/smartd.conf found, scanning devices glob(3) found no matches for pattern /dev/hd[a-t] glob(3) found no matches for pattern /dev/sd[a-c][a-z] Device: /dev/sda, open() failed: DELL or MegaRaid controller, please try adding '-d megaraid,N' Device: /dev/bus/0 [megaraid_disk_05], type changed from 'megaraid,5' to 'sat+megaraid,5' Device: /dev/bus/0 [megaraid_disk_05] [SAT], opened Device: /dev/bus/0 [megaraid_disk_05] [SAT], WDC WD1003FBYX-01Y7B1, S/N:WD-XXXX, WWN:XXXX, FW:01.01V02, 1.00 TB Device: /dev/bus/0 [megaraid_disk_05] [SAT], found in smartd database: Western Digital RE4 Serial ATA Device: /dev/bus/0 [megaraid_disk_05] [SAT], not capable of SMART Health Status check Device: /dev/bus/0 [megaraid_disk_05] [SAT], is SMART capable. Adding to "monitor" list. Device: /dev/bus/0 [megaraid_disk_07], type changed from 'megaraid,7' to 'sat+megaraid,7' Device: /dev/bus/0 [megaraid_disk_07] [SAT], opened Device: /dev/bus/0 [megaraid_disk_07] [SAT], WDC WD1003FBYX-01Y7B1, S/N:WD-XXXX, WWN:XXXX, FW:01.01V02, 1.00 TB Device: /dev/bus/0 [megaraid_disk_07] [SAT], found in smartd database: Western Digital RE4 Serial ATA Device: /dev/bus/0 [megaraid_disk_07] [SAT], not capable of SMART Health Status check Device: /dev/bus/0 [megaraid_disk_07] [SAT], is SMART capable. Adding to "monitor" list. Monitoring 2 ATA and 0 SCSI devices Device: /dev/bus/0 [megaraid_disk_05] [SAT], opened ATA device Device: /dev/bus/0 [megaraid_disk_05] [SAT], previous self-test completed without error Device: /dev/bus/0 [megaraid_disk_07] [SAT], opened ATA device Device: /dev/bus/0 [megaraid_disk_07] [SAT], previous self-test completed without error |
|||
#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 |