Custom Query (1386 matches)
Results (238 - 240 of 1386)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#251 | worksforme | smartctl segfaults on OpenBSD-powerpc | ||
Description |
On OpenBSD-current @powerpc smartctl 6.0 segfaults, here there are some info: $ sudo smartctl -i /dev/wd0c smartctl 6.0 2012-10-10 r3643 [powerpc-unknown-openbsd5.2] (local build) Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org Segmentation fault (core dumped) Program received signal SIGSEGV, Segmentation fault. strcmp (s1=0xfffd5403 "ec2hour", s2=0x20436f6d <Address 0x20436f6d out of bounds>) at /usr/src/lib/libc/string/strcmp.c:47 47 while (*s1 == *s2++) Current language: auto; currently c (gdb) bt #0 strcmp (s1=0xfffd5403 "ec2hour", s2=0x20436f6d <Address 0x20436f6d out of bounds>) at /usr/src/lib/libc/string/strcmp.c:47 #1 0x0180bd54 in parse_attribute_def (opt=Variable "opt" is not available. ) at /usr/obj/ports/smartmontools-6.0/smartmontools-6.0/atacmds.cpp:213 #2 0x0181bf7c in parse_db_presets (presets=0x18588c4 "-v 9,seconds", defs=0xfffd5620, firmwarebugs=0xfffd7858, type=0x0)
/usr/obj/ports/smartmontools-6.0/smartmontools-6.0/knowndrives.cpp:221 #3 0x0181bf7c in parse_db_presets (presets=0xfffd7858 "", defs=0x0, firmwarebugs=0x0, type=0xfffd8269)
/usr/obj/ports/smartmontools-6.0/smartmontools-6.0/knowndrives.cpp:221 #4 0x0181bf7c in parse_db_presets (presets=0xffffffff <Address 0xffffffff out of bounds>, defs=0x30303800, firmwarebugs=0xf8c69177, type=0x1c00)
/usr/obj/ports/smartmontools-6.0/smartmontools-6.0/knowndrives.cpp:221
#5 0x0181bf7c in parse_db_presets (presets=0x0, defs=0x0,
firmwarebugs=0x17, type=0xfffda354) at
/usr/obj/ports/smartmontools-6.0/smartmontools-6.0/knowndrives.cpp:221
#6 0x0181bf7c in parse_db_presets (presets=0x1890e1c "\001\210\r
/usr/obj/ports/smartmontools-6.0/smartmontools-6.0/knowndrives.cpp:221 #7 0x0181bf7c in parse_db_presets (presets=0x20 <Address 0x20 out of bounds>, defs=0x1890e1c, firmwarebugs=0xfffda404, type=0xfffda3b0)
/usr/obj/ports/smartmontools-6.0/smartmontools-6.0/knowndrives.cpp:221 #8 0x0181bf7c in parse_db_presets (presets=0x0, defs=0x20, firmwarebugs=0x1801eb0, type=0x1890e18)
/usr/obj/ports/smartmontools-6.0/smartmontools-6.0/knowndrives.cpp:221 Previous frame inner to this frame (corrupt stack?) |
|||
#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 |
|||
#253 | wontfix | Add Highpoint RocketRAID support (hptiop) | ||
Description |
I mainly work with FreeNAS systems, but I found an issue that I think can be resolved here. I have a RocketRAID 4520 controller(latest generation from Highpoint). When I use the command smartctl -a -d hpt,1/1/1 /dev/hptiop0 I get the error "Smartctl: Device Read Identity Failed: Bad address'. It appears that this issue was previously documented in ticket:71. That ticket was closed since nobody had this controller. I have a controller from each of the 35xx, 43xx, and 45xx family of controllers. AFAIK the only way to get any SMART data and run any tests is via the Highpoint CLI available as a binary only. My guess is that all 3 families of controller mentioned above and the 44xx will all work with the same appropriate fix. I have a system that I can give SSH and FTP access to on request. I only have the 45xx until the end of the year however(on loan to help facilitate support for FreeNAS). You can read additional information on this issue provided by me at the FreeNAS ticket https://support.freenas.org/ticket/1932. I listed the priority as major since so many generations of cards are included with this ticket. |