[Bug 877685] New: smartmontools can not read information from MegaRaid controller
https://bugzilla.novell.com/show_bug.cgi?id=877685 https://bugzilla.novell.com/show_bug.cgi?id=877685#c0 Summary: smartmontools can not read information from MegaRaid controller Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: svalx@svalx.net QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:29.0) Gecko/20100101 Firefox/29.0 smartmontools-6.2-2.1.2.x86_64 I have a single MegaRaid 9240-8i controller with 8 disks on 2 RAID's. and want to get info about this disks. Reproducible: Always Steps to Reproduce: ---------- # smartctl -i /dev/sdd smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.14.3-26.g2a280a3-desktop] (SUSE RPM) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org Smartctl open device: /dev/sdd failed: DELL or MegaRaid controller, please try adding '-d megaraid,N' --------- # smartctl -i -d megaraid,0 /dev/sdd smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.14.3-26.g2a280a3-desktop] (SUSE RPM) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org Smartctl open device: /dev/sdd [megaraid_disk_00] failed: INQUIRY failed --------- $ man smartctl ... megaraid,N - [Linux only] the device consists of one or more SCSI/SAS disks connected to a MegaRAID controller. The non-negative integer N (in the range of 0 to 127 inclusive) denotes which disk on the controller is monitored. Use syntax such as: smartctl -a -d megaraid,2 /dev/sda smartctl -a -d megaraid,0 /dev/sdb smartctl -a -d megaraid,0 /dev/bus/0 The following entry in /proc/devices must exist: For PERC2/3/4 controllers: megadevN For PERC5/6 controllers: megaraid_sas_ioctlN ... --------- $ grep mega /proc/devices 250 megaraid_sas_ioctl --------- So I have megaraid_sas_ioctl instead megaraid_sas_ioctl0 and probably it case of failed inquiry. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=877685 https://bugzilla.novell.com/show_bug.cgi?id=877685#c zhang jiajun <jzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jzhang@suse.com AssignedTo|bnc-team-screening@forge.pr |sbrabec@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=877685 http://bugzilla.novell.com/show_bug.cgi?id=877685#c1 Tomáš Chvátal <tchvatal@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from Tomáš Chvátal <tchvatal@suse.com> --- The product for which this bug is reported is no longer supported. Sorry we didn't manage to find out the solution for the problem during the lifetime. If the problem still occurs on current releases feel free to report a new ticket and/or if the problem is in upstream software itself to report it to the upstream developers. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com