- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: Bad disk .
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-14-2005 05:26 AM
тАО09-14-2005 05:26 AM
Thanks.
Veri.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-14-2005 05:32 AM
тАО09-14-2005 05:32 AM
Re: Bad disk .
vgdisplay -v | grep -e "PV Name" -e "PV Status"
(Look for 'unavailable')
and
ioscan -fnCdisk | grep NO_HW
both commands should report the failed disk.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-14-2005 05:38 AM
тАО09-14-2005 05:38 AM
Re: Bad disk .
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!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-14-2005 05:42 AM
тАО09-14-2005 05:42 AM
Re: Bad disk .
Hence HP will have been informed, and would log a call for the disc inside the XP to be replaced.
You generally will not know there is any issue until you get informed by HP that they need to replace a part in the XP.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-14-2005 07:36 AM
тАО09-14-2005 07:36 AM
Re: Bad disk .
This could be maped to , one of the Superdome partition ,in the superdome ( Total 10 Partition )
As a sysadmin , what information should I need to know , as I have to raise a internal change ticket or helpdesk ticket for that.
Many Thanks,
Veri.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-14-2005 09:19 AM
тАО09-14-2005 09:19 AM
Re: Bad disk .
The disk exchange doesn't impact your server, because the array rebuild the data from the bad disk to a spare disk and if the disk is replaced, it copies the data back. It takes a while, but there is no impact to your applications.
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!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-14-2005 05:39 PM
тАО09-14-2005 05:39 PM
Re: Bad disk .
A disk in a XP array is not directly visible to host. It is part of a raid group which consists of 4 or 7 disks. Also one raid group may be giving you more that 10-15 LUNs to various hosts which will be available even after failed disk. In such case it will not be possible for any of the host to know that disk has failed.
You can infact refer to XP- SVP to get s detailed information regarding the location of the disk. The replacement has to be carried out by a XP trainned engineer only. If SVP is not accesible you can use command view XP to find out the location of failed disk.
HTH,
Devender
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-15-2005 06:23 AM
тАО09-15-2005 06:23 AM
Re: Bad disk .
what is xpinfo is used for. !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-15-2005 03:51 PM
тАО09-15-2005 03:51 PM
Re: Bad disk .
xpinfo is the command which should be installed on the hosts which access a XP array. The use of xpinfo is to give a detailed information of the various LUNs a host is accessing from one or more XP arrays.
HTH,
Devender
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-16-2005 02:41 AM
тАО09-16-2005 02:41 AM
SolutionOn a given host it gives all important information. It looks like
#xpinfo
Scanning disk devices...
Device File : /dev/rdsk/c4t0d0 Model : XP512
Port : CL1C Serial # : 00032380
Host Target : 00 Code Rev : 0118
Array LUN : 00 Subsystem : 0004
CU:LDev : 00:98 CT Group : ---
Type : OPEN-E CA Volume : SMPL
Size : 13893 MB BC0 (MU#0) : SMPL
ALPA : e4 BC1 (MU#1) : SMPL
Loop Id : 02 BC2 (MU#2) : SMPL
SCSI Id : --- RAID Level : RAID5
FC-LUN : 4000000000000000 RAID Group : 1-10
Port WWN : 500060e8027e7c02 ACP Pair : 1
Disk Mechs : R109 R119 R129 R139
Device File : /dev/rdsk/c4t0d1 Model : XP512
Port : CL1C Serial # : 00032380
Host Target : 00 Code Rev : 0118
Array LUN : 01 Subsystem : 0005
CU:LDev : 01:98 CT Group : ---
Type : OPEN-E CA Volume : SMPL
Size : 13893 MB BC0 (MU#0) : SMPL
ALPA : e4 BC1 (MU#1) : SMPL
Loop Id : 02 BC2 (MU#2) : SMPL
SCSI Id : --- RAID Level : RAID5
FC-LUN : 4001000000000000 RAID Group : 2-10
Port WWN : 500060e8027e7c02 ACP Pair : 2
Disk Mechs : R149 R159 R169 R179
Device File : /dev/rdsk/c4t0d2 Model : XP512
Port : CL1C Serial # : 00032380
Host Target : 00 Code Rev : 0118
Array LUN : 02 Subsystem : 0006
CU:LDev : 02:98 CT Group : ---
Type : OPEN-E CA Volume : SMPL
Size : 13893 MB BC0 (MU#0) : SMPL
ALPA : e4 BC1 (MU#1) : SMPL
Loop Id : 02 BC2 (MU#2) : SMPL
SCSI Id : --- RAID Level : RAID5
FC-LUN : 4002000000000000 RAID Group : 5-10
Port WWN : 500060e8027e7c02 ACP Pair : 1
Disk Mechs : R209 R219 R229 R239
Or something like this-
#xpinfo -i
Scanning disk devices...
Device File ALPA Tgt Lun Port CU:LDev Type Serial#
===================================================
/dev/rdsk/c4t0d0 e4 00 00 CL1C 00:98 OPEN-E 00032380
/dev/rdsk/c4t0d1 e4 00 01 CL1C 01:98 OPEN-E 00032380
/dev/rdsk/c4t0d2 e4 00 02 CL1C 02:98 OPEN-E 00032380
/dev/rdsk/c4t0d3 e4 00 03 CL1C 03:98 OPEN-E 00032380
/dev/rdsk/c4t0d4 e4 00 04 CL1C 00:99 OPEN-E 00032380
/dev/rdsk/c4t0d5 e4 00 05 CL1C 01:99 OPEN-E 00032380
/dev/rdsk/c4t0d6 e4 00 06 CL1C 02:99 OPEN-E 00032380
/dev/rdsk/c4t0d7 e4 00 07 CL1C 03:99 OPEN-E 00032380
/dev/rdsk/c4t1d0 e4 01 08 CL1C 00:9a OPEN-E 00032380
/dev/rdsk/c4t1d1 e4 01 09 CL1C 01:9a OPEN-E 00032380
HTH,
Devender