Is "pediags" useless for PE840's storage?
Bryan
bryan.madhatter at gmail.com
Thu Apr 16 22:05:26 CDT 2009
OMSA 5.5 live also has SAS raid storage manager built in to query the SAS
5/6. That may give you more information as well.
On Wed, Apr 15, 2009 at 7:45 AM, Giulio Orsero <giulioo at gmail.com> wrote:
> This is what it shows on my system:
>
> ===============================
> # ./pediags sasdevdiag --show
>
> Device Index : 1
> Device Name : Dell SAS 5/iR Adapter Controller 1
> Description : Dell SAS 5/iR Adapter Controller 1, Serial Number:
> 5002219
> 1bb8cc000
> Device Class : RAID Controller
> Device Status : Device is working properly.
> Device Location : PCI Bus 2, Device 8, Function 0
> Additional H/W Info : Firmware: 00.10.51.00.06.12.05.00, Driver Version:
> 4.00.38.02
>
> Device Index : 2
> Device Name : Connector(SAS Port) 0
> Description : Connector(SAS Port) 0
> Device Class : Controller Channel
> Device Status : Device is working properly.
> Device Location : Connector 0
>
> Device Index : 3
> Device Name : SAS/SATA backplane 1:0
> Description : SAS/SATA backplane 1:0
> Device Class : Internal Enclosure
> Device Status : Device is working properly.
> Device Location : Enclosure 1:0
> Additional H/W Info : Firmware: 1.05
>
> Test Index : 1
> Test Name : SAS Phy Integrity Test
> Description : Gets Enclosure and HDD Phy Error Log Information.
>
> Device Index : 4
> Device Name : Array Disk 1:0:0
> Description : SSD ATA WDC WD2502ABYS-1
> Device Class : RAID Array Disk
> Device Status : Device is working properly.
> Device Location : Slot 0
> Additional H/W Info : 237464 MB, Firmware: 3B04, Serial Number:
> WD-WCAT19434291
>
> Device Index : 5
> Device Name : Array Disk 1:0:1
> Description : SSD ATA WDC WD2502ABYS-1
> Device Class : RAID Array Disk
> Device Status : Device is working properly.
> Device Location : Slot 1
> Additional H/W Info : 237464 MB, Firmware: 3B04, Serial Number:
> WD-WCAT19433947
>
> Device Index : 6
> Device Name : Logical Connector
> Description : Logical Connector
> Device Class : Controller Channel
> Device Status : Device is working properly.
> Device Location : Logical Connector
>
> ============
>
> You can see only 1 test is available, and when I run that test I get the
> error I wrote about in my initial post. It seems it will work only if you
> have SAS disks, while I have SATA.
>
> I think this is kind of a bug, that having SATA disks disable even the
> controller log tests, controller self tests, ...
>
> Thanks.
>
>
>
>
> On Wed, Apr 15, 2009 at 11:19 AM, <Patrick_Fischer at dell.com> wrote:
>
>> > Am I right that pediags cannot do any test on the PE840 RAID
>> controller/hard
>>
>> > disks?
>>
>> PEDIAGS is working properly and well on PE840 / 860 with SAS 5/6.
>>
>> I will try to give a short explanation. For this I used OMSA 5.5 Live CD
>> on a
>>
>> PE2900 I with PERC5i but the behaviour is similar on SAS 5/6 (yes, I have
>>
>> tested this). There is only one harddisk in SLOT 7 configured as RAID0 /
>> VD0.
>>
>> [root at anubis bin]# pwd
>>
>> /opt/dell/onlinediags/oldiags/bin
>>
>> [root at anubis bin]# ./pediags sasdevdiag --show
>>
>> This command will give you a table like
>>
>> Device Index : 1
>>
>> Device Name : Dell PERC 5/i Integrated RAID Controller 1
>>
>> Description : Dell PERC 5/i Integrated RAID Controller 1, Serial
>> Number: <snip>
>>
>> Device Class : RAID Controller
>>
>> Device Status : Device is working properly.
>>
>> Device Location : PCI Bus 2, Device 14, Function 0
>>
>> Additional H/W Info : Firmware: 5.2.2-0072, Driver Version: 00.00.03.21,
>> Cluster inactive
>>
>> Test Index : 1
>>
>> Test Name : SAS Controller Log Test
>>
>> Description : Gets the Controller Events Log.
>>
>> Test Alert : <snip>
>>
>> Test Index : 2
>>
>> Test Name : Controller Self Test
>>
>> Description : Runs Self Diagnostics on the controller.
>>
>> Test Alert : <snip>
>>
>> Test Index : 3
>>
>> Test Name : Controller TTY Log Test
>>
>> Description : Gets the Controller TTY Log.
>>
>> Test Alert : <snip>
>>
>> <snip>
>>
>> Device Index : 6
>>
>> Device Name : Array Disk 1:0:7
>>
>> Description : SAS FUJITSU MAX3147RC
>>
>> Device Class : RAID Array Disk
>>
>> Device Status : Device is working properly.
>>
>> Device Location : Slot 7
>>
>> Additional H/W Info : 139392 MB, Firmware: D207, Serial Number: <snip>
>>
>> Test Index : 1
>>
>> Test Name : Disk Self Test
>>
>> Description : Tests the hard drive.
>>
>> Test Alert : <snip>
>>
>> Test Index : 2
>>
>> Test Name : Disk Blink Test
>>
>> Description : Blinks the hard drive.
>>
>> In this table you can see the device which you could test and which kind
>> of test is available.
>>
>> [root at anubis bin]# ./pediags sasdevdiag --run test-index=all
>> quicktest=true
>>
>> >> /root/Desktop/results.txt
>>
>> This would perform all tests but this is mostly not necessary. If you want
>> to test one
>>
>> of your harddisks pick the correct device number from list and perform
>> only disk self
>>
>> test.
>>
>> [root at anubis bin]# ./pediags sasdevdiag --run device-index=6 test-index=1
>> quicktest=true
>>
>> ................
>>
>> Device Name : Array Disk 1:0:7
>>
>> Description : SAS FUJITSU MAX3147RC
>>
>> Device Location : Slot 7
>>
>> Test Name : Disk Self Test
>>
>> Description : Tests the hard drive.
>>
>> Passes : 1
>>
>> Result : passed
>>
>> Start Time : Wed Apr 15 02:30:46 2009
>>
>> Completion Time : Wed Apr 15 02:31:27 2009
>>
>> Result Event : The test operation completed successfully. No errors
>> found.
>>
>> To extract the controller log from PERC5i you run
>>
>> [root at anubis bin]# ./pediags sasdevdiag --run device-index=1 test-index=3
>>
>> ...
>>
>> Device Name : Dell PERC 5/i Integrated RAID Controller 1
>>
>> Description : Dell PERC 5/i Integrated RAID Controller 1, Serial
>> Number: 12345
>>
>> Device Location : PCI Bus 2, Device 14, Function 0
>>
>> Test Name : Controller TTY Log Test
>>
>> Description : Gets the Controller TTY Log.
>>
>> Passes : 1
>>
>> Result : passed
>>
>> Start Time : Wed Apr 15 02:34:19 2009
>>
>> Completion Time : Wed Apr 15 02:34:19 2009
>>
>> Result Event : The test operation completed successfully. No errors
>> found.
>>
>> [root at anubis bin]# cat /var/log/TTY_00000000.log
>>
>> PERC 5/i Integrated 0:
>>
>> T0: LSI Logic MegaRAID firmware loaded
>>
>> T0: Firmware version 1.03.50-0461 built ...
>>
>> <snip>
>>
>> Please take note that you cannot perform this on a SAS HBA as there is no
>>
>> controller log.
>>
>> Other steps will work on SAS HBA. Back to your question.
>>
>> > Device Name : SAS/SATA backplane 1:0
>>
>> > Description : SAS/SATA backplane 1:0
>>
>> > Device Location : Enclosure 1:0
>>
>> > Test Name : SAS Phy Integrity Test
>>
>> > Description : Gets Enclosure and HDD Phy Error Log Information.
>>
>> > Passes : 1
>>
>> > Result : warning
>>
>> > <snip>
>>
>> > Result Event : The Test is not supported on this configuration.
>>
>> > Run the test on a backplane with an expander or a backplane with SAS
>> disks.
>>
>> The result is onlya warning (informational) that he couldnt get infos from
>> this
>>
>> device in your configuration. This means not that all tests failed.
>>
>> Please try with your harddisks only (where X is the disk device number
>> from table).
>>
>> [root at anubis bin]# ./pediags sasdevdiag --run device-index=<X>
>> test-index=1 quicktest=true
>>
>> Regards,
>>
>>
>> _______________________________________________
>> Linux-PowerEdge mailing list
>> Linux-PowerEdge at dell.com
>> http://lists.us.dell.com/mailman/listinfo/linux-poweredge
>> Please read the FAQ at http://lists.us.dell.com/faq
>>
>
>
>
> --
> giulioo at pobox.com
>
> _______________________________________________
> Linux-PowerEdge mailing list
> Linux-PowerEdge at dell.com
> http://lists.us.dell.com/mailman/listinfo/linux-poweredge
> Please read the FAQ at http://lists.us.dell.com/faq
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20090416/1badf39d/attachment-0001.htm
More information about the Linux-PowerEdge
mailing list