1755036 Members
2846 Online
108828 Solutions
New Discussion

rx2660 bad disk

 
itrc55
Regular Advisor

rx2660 bad disk

Hi,

 

I have rx2660 server with 2 physical disk, but when I try to scan the disk's only

I find 1 disk I using insf -e command and I rebooted the server but the same on disk only available.

the light of the two disk is green one only blinking.

please your support to resolve this issue.

 

OS version 11.31

 

Thanks

 

10 REPLIES 10
Torsten.
Acclaimed Contributor

Re: rx2660 bad disk

I'm sure you have a hardware RAID in use - please post

 

# ioscan -fn


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Bill Hassell
Honored Contributor

Re: rx2660 bad disk

The rx2660 has a built-in SAS array controller or may have an optional P400 or similar array controller. That means that ioscan may not see actual disks, but instead will see LUNs created by the array controller. It all depends on how the box was originally setup. Try these commands:

 

sasmgr get_info -D /dev/sasd1 -q target=all
sasmgr get_info -D /dev/sasd1 -q raid
sasmgr get_info -D /dev/sasd1 -q lun=all

 



Bill Hassell, sysadmin
Nighwish
Frequent Advisor

Re: rx2660 bad disk

Hi

I think Bill is right, you should see two disk like the above:

disk 1 0/4/1/0.0.0.0.0 sdisk CLAIMED DEVICE HP DG072A9BB7
/dev/dsk/c2t0d0 /dev/dsk/c2t0d0s2 /dev/rdsk/c2t0d0 /dev/rdsk/c2t0d0s2
/dev/dsk/c2t0d0s1 /dev/dsk/c2t0d0s3 /dev/rdsk/c2t0d0s1 /dev/rdsk/c2t0d0s3
disk 0 0/4/1/0.0.0.1.0 sdisk CLAIMED DEVICE HP DG072A9BB7
/dev/dsk/c2t1d0 /dev/dsk/c2t1d0s2 /dev/rdsk/c2t1d0 /dev/rdsk/c2t1d0s2
/dev/dsk/c2t1d0s1 /dev/dsk/c2t1d0s3 /dev/rdsk/c2t1d0s1 /dev/rdsk/c2t1d0s3


You have a raid by hardware. Use sasmgr commands to find out the state of your raid.
Torsten.
Acclaimed Contributor

Re: rx2660 bad disk

In case of the default SAS chip a hardware RAID looks like this:

disk 0 0/1/1/0.0.0.0.0 sdisk CLAIMED DEVICE HP IR Volume
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
/dev/dsk/c0t0d0s1 /dev/rdsk/c0t0d0s1
/dev/dsk/c0t0d0s2 /dev/rdsk/c0t0d0s2
/dev/dsk/c0t0d0s3 /dev/rdsk/c0t0d0s3


In case of a P400 smartarray controller:

disk 0 0/5/0/0/0/0.0.0 sdisk CLAIMED DEVICE HP LOGICAL VOLUME
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
/dev/dsk/c0t0d0s1 /dev/rdsk/c0t0d0s1
/dev/dsk/c0t0d0s2 /dev/rdsk/c0t0d0s2
/dev/dsk/c0t0d0s3 /dev/rdsk/c0t0d0s3


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
itrc55
Regular Advisor

Re: rx2660 bad disk

Hi,

 

please check the output of each command

 

 #ioscan -funC disk
Class     I  H/W Path     Driver S/W State   H/W Type     Description
=====================================================================
disk     12  0/1/1/0.0.0.0.0      sdisk   CLAIMED     DEVICE       HP      DG146ABAB4
                         /dev/dsk/c8t0d0     /dev/dsk/c8t0d0s1   /dev/dsk/c8t0d0s2   /dev/dsk/c8t0d0s3   /dev/rdsk/c8t0d0    /dev/rdsk/c8t0d0s1  /dev/rdsk/c8t0d0s2  /dev/rdsk/c8t0d0s3
disk     20  0/1/1/0.0.0.1.0      sdisk   CLAIMED     DEVICE       HP      DG146ABAB4
                         /dev/dsk/c8t1d0   /dev/rdsk/c8t1d0
disk      3  0/2/1/0.2.5.0.0.0.0  sdisk   CLAIMED     DEVICE       DGC     CX4-480WDR5
                         /dev/dsk/c3t0d0   /dev/rdsk/c3t0d0
disk      4  0/2/1/0.2.5.0.0.0.1  sdisk   CLAIMED     DEVICE       DGC     CX4-480WDR5
                         /dev/dsk/c3t0d1   /dev/rdsk/c3t0d1
disk      5  0/2/1/0.2.5.0.0.0.2  sdisk   CLAIMED     DEVICE       DGC     CX4-480WDR5
                         /dev/dsk/c3t0d2   /dev/rdsk/c3t0d2
disk      0  0/2/1/0.2.6.0.0.0.0  sdisk   CLAIMED     DEVICE       DGC     CX4-480WDR5
                         /dev/dsk/c1t0d0   /dev/rdsk/c1t0d0
disk      1  0/2/1/0.2.6.0.0.0.1  sdisk   CLAIMED     DEVICE       DGC     CX4-480WDR5
                         /dev/dsk/c1t0d1   /dev/rdsk/c1t0d1
disk      2  0/2/1/0.2.6.0.0.0.2  sdisk   CLAIMED     DEVICE       DGC     CX4-480WDR5
                         /dev/dsk/c1t0d2   /dev/rdsk/c1t0d2
disk      9  0/4/1/0.2.5.0.0.0.0  sdisk   CLAIMED     DEVICE       DGC     CX4-480WDR5
                         /dev/dsk/c7t0d0   /dev/rdsk/c7t0d0
disk     10  0/4/1/0.2.5.0.0.0.1  sdisk   CLAIMED     DEVICE       DGC     CX4-480WDR5
                         /dev/dsk/c7t0d1   /dev/rdsk/c7t0d1
disk     11  0/4/1/0.2.5.0.0.0.2  sdisk   CLAIMED     DEVICE       DGC     CX4-480WDR5
                         /dev/dsk/c7t0d2   /dev/rdsk/c7t0d2
disk      6  0/4/1/0.2.6.0.0.0.0  sdisk   CLAIMED     DEVICE       DGC     CX4-480WDR5
                         /dev/dsk/c5t0d0   /dev/rdsk/c5t0d0
disk      7  0/4/1/0.2.6.0.0.0.1  sdisk   CLAIMED     DEVICE       DGC     CX4-480WDR5
                         /dev/dsk/c5t0d1   /dev/rdsk/c5t0d1
disk      8  0/4/1/0.2.6.0.0.0.2  sdisk   CLAIMED     DEVICE       DGC     CX4-480WDR5
                         /dev/dsk/c5t0d2   /dev/rdsk/c5t0d2
disk     17  255/1/0.0.0  sdisk   CLAIMED     DEVICE       TEAC    DV-28E-N
                         /dev/dsk/c9t0d0   /dev/rdsk/c9t0d0

 

 

 #sasmgr get_info -D /dev/sasd1 -q target=all

Tue Feb 21 07:13:34 2012

Target SAS Address                                 : 0x5000c5000519a5c5
Target Health                                      : ONLINE
IPort SAS Address                                  : 0x50060b0000be7048
Previous IPort SAS Address                         : 0x0
Target Type                                        : SCSI Device
Target Topology                                    : DIRECT
Protocol Capability of Target                      : UNKNOWN
Target Slot                                        : 0x8
Target Enclosure ID                                : 0x1
Target Enclosure Type                              : Direct Attached SGPIO

Target SAS Address                                 : 0x5000c5000519a625
Target Health                                      : ONLINE
IPort SAS Address                                  : 0x50060b0000be7049
Previous IPort SAS Address                         : 0x0
Target Type                                        : SCSI Device
Target Topology                                    : DIRECT
Protocol Capability of Target                      : UNKNOWN
Target Slot                                        : 0x7
Target Enclosure ID                                : 0x1
Target Enclosure Type                              : Direct Attached SGPIO

*********************************************************************
*****              HBA Specific information                     *****
*********************************************************************
Information for target (0x5000c5000519a5c5)
Target State                                       : READY

Information for target (0x5000c5000519a625)
Target State                                       : READY

 

#sasmgr get_info -D /dev/sasd1 -q raid

Tue Feb 21 07:14:02 2012

---------- PHYSICAL DRIVES ----------
LUN dsf              SAS Address          Enclosure    Bay      Size(MB)

/dev/rdsk/c8t0d0     0x5000c5000519a5c5     1            8      140014
/dev/rdsk/c8t1d0     0x5000c5000519a625     1            7      0

 

 

 #sasmgr get_info -D /dev/sasd1 -q lun=all
LUN dsf              Hardware Path                  SAS Address
------------------------------------------------------------------
/dev/rdsk/c8t0d0     0/1/1/0.0.0.0.0                0x5000c5000519a5c5
/dev/rdsk/c8t1d0     0/1/1/0.0.0.1.0                0x5000c5000519a625

 

Thanks for your support

Torsten.
Acclaimed Contributor

Re: rx2660 bad disk

But there are 2 disks (unmirrored):

 

dev/rdsk/c8t0d0 0/1/1/0.0.0.0.0 0x5000c5000519a5c5
/dev/rdsk/c8t1d0 0/1/1/0.0.0.1.0 0x5000c5000519a625

 

both are listed in ioscan too.


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
itrc55
Regular Advisor

Re: rx2660 bad disk

Hi,

 

yes now i can see the second disk, but is there hardware mirroring option on rx2660 server as available on blade server (BL8xx i2), when i reboot the server and go to shell and execute the following command.

 

Shell> drivers

 

i don't see any Smart Array SAS Driver, i see the below.

 

Shell> drivers


T D
D Y C I
R P F A
V VERSION E G G #D #C DRIVER NAME IMAGE NAME
== ======== = = = == == =================================== ===================
15 00000020 B - - 5 12 PCI Bus Driver PciBus
20 02010400 B X X 1 2 LSI Logic Fusion MPT SAS Driver PciROM:01:01:00:001
24 00000109 D X X 1 - HP 4 Gb Fibre Channel Driver PciROM:02:01:00:002
26 00000109 D X X 1 - HP 4 Gb Fibre Channel Driver PciROM:04:01:00:002
2A 00000020 D X - 1 - Usb Keyboard Driver UsbKb
2B 00000020 ? - - - - Usb Mouse Driver UsbMouse
2C 00000020 ? - - - - Usb Cbi0 Mass Storage Driver UsbCbi0
2D 00000020 ? - - - - Usb Cbi1 Mass Storage Driver UsbCbi1
2E 00000010 ? - - - - UGA Console Driver GraphicsConsole
2F 00000000 D - - 1 - PCI VGA Mini Port Driver PciVgaMiniPort
30 00000010 D - - 1 - VGA Class Driver VgaClassDriver
31 00000013 B - - 1 1 Serial 16550 UART Driver Serial16550
32 00000010 B - - 1 1 Serial Terminal Driver Terminal
33 00000010 D - - 2 - Platform Console Management Driver ConPlatform
34 00000010 D - - 2 - Platform Console Management Driver ConPlatform
35 00000010 B - - 2 2 Console Splitter Driver ConSplitter
36 00000010 ? - - - - Console Splitter Driver ConSplitter
37 00000011 B - - 2 2 Console Splitter Driver ConSplitter
38 00000011 B - - 2 2 Console Splitter Driver ConSplitter
3C 00000040 D - - 2 - Usb Ohci Driver SysROM:Usb Ohci Dri
3D 00000020 B - - 2 3 USB Bus Driver SysROM:USB Bus Driv
3E 00000020 D - - 1 - Usb Bot Mass Storage Driver SysROM:USB Bot Mass
3F 00000020 D - - 1 - Generic USB Mass Storage Driver SysROM:Generic USB
48 00090404 B X X 2 2 Broadcom Gigabit Ethernet Driver SysROM:Broadcom Gig
49 00000010 D - - 6 - Generic Disk I/O Driver DiskIo
4A 00000011 B - - 1 3 Partition Driver(MBR/GPT/El Torito) Partition
4B 00000010 D - - 2 - FAT File System Driver Fat
4C 00000011 ? X X - - PCI IDE/ATAPI Bus Driver Ide
4D 00000010 ? - - - - Intel(R) PRO 100 UNDI Driver Undi
4F 00000021 D - - 2 - Simple Network Protocol Driver Snp3264
51 00000020 D - - 2 - PXE Base Code Driver PxeBc
53 00000020 D - - 2 - PXE DHCPv4 Driver PxeDhcp4
54 00000010 ? - - - - ARP Network Service Driver Arp
55 00000010 ? - - - - DHCP Protocol Driver Dhcp4
56 00000010 ? - - - - IP4 Network Service Driver Ip4
57 00000010 ? - - - - IP4 CONFIG Network Service Driver Ip4Config
58 00000010 ? - - - - MNP Network Service Driver Mnp
59 00000010 ? - - - - MTFTP4 Network Service Mtftp4
5A 00000010 ? - - - - Tcp Network Service Driver Tcp4
5B 00000010 ? - - - - UDP Network Service Driver Udp4
5D 00000031 D - - 2 - SCSI Bus Driver SysROM:SCSI Bus Dri
5E 00000020 ? - - - - Scsi Disk Driver SysROM:SCSI Disk Dr
5F 00000030 ? - - - - SCSI Tape Driver SysROM:SCSI Tape Dr

 

or i need to soft mirroring only.

 

Thanks

 

Matti_Kurkela
Honored Contributor

Re: rx2660 bad disk

Your "sasmgr get_info -D /dev/sasd1 -q raid" indicates the size of /dev/rdsk/c8t1d0 (= slot 7) is 0, so the disk has probably failed its internal hardware diagnostic and is now effectively dead. Replace it.

 

You can light up a locator LED to confirm you are replacing the right disk:

sasmgr set_attr -D /dev/sasd1 -q lun=/dev/rdsk/c8t1d0 -q locate_led=on

 

I guess the EFI shell is smart enough to not display broken disks.

 

This is the EFI driver for your disk controller:

20 02010400 B X X 1 2 LSI Logic Fusion MPT SAS Driver PciROM:01:01:00:001

 

The X's indicate the driver supports EFI configuration and diagnostics commands.

The "drivers" listing indicates its driver handle is 20; use "devices" or "devtree" to find the device handle for it.

Then you can use "drvcfg -s 20 <device_handle>" to access the configuration menu of the disk controller while in EFI mode.

MK
itrc55
Regular Advisor

Re: rx2660 bad disk

Hi,

Thanks, you are correct the disk has probably failed,

but I have last question before give you the point.

How I can light up a locator LED on lan or fiber card to confirm the correct lan, if I want to change it. on rx2660 , rx6600 or on all rx servers

Thanks