MSA Storage

P2000 G3 two vdisk with same name

 
Technical_guy
Advisor

P2000 G3 two vdisk with same name

Hi

I have HP MSA P2000, recently i have two disk Failed from Enclosure 2 : Slot 5 & 8.

i have assigned the GLOBAL Spare it took both the disk and SAN was working fine.

Now when i inserted a new disk to replace with ENC2: Slot 5. 1. the new HDD name shown in enclosure COnsole as VDISK.

it dint show me "avail". which normally it does.

2.it automatically created a vd01_0100000 Volume & under tha LUN with 2999.95GB

3. and this created lUN get quarantine. attached is the snapshot.P2000 Vdisk Offline.PNG

4. it created a dupliated LUN automatically once i inserted a New disk. now i want to remove that LUN & Disk which is showing error. currently i SAN is in prooduction and working fine. how can i remove this LUN, what could be the issue, why it created lunP2000 Vdisk Offline.PNG

3 REPLIES 3
SahanaR
HPE Pro

Re: P2000 G3 two vdisk with same name

Hello,

Good day!

1>Yes,you are right new disks should come up as avail by default.

2>Sometimes few drives very rarely do hold some old configuration and once they are inserted the ghost entries are seen.


3>I saw the picture and usually the ghost vidisk come up as quarantined.

4>We can delete this ghost vdisk through CLI.

 

NOTE:Please have a data backup of the production vdisk vd01 which was originally present.Just in case of emergency.


>>SSH into any one of the controller.
>>Run # show vdisks

This command provides unique serial number for each vdisk.Please check if both the vd01 vdisk has different serial number.
If so proceed to next step

>>We can delete the vdisk using the unique serial number.Select the serial number of the ghost vd01 vdisk(make sure its unique from the production vd01).
Then run this command for example # delete vdisks 00c0ff288f2400004171af5800000000

This should delete the ghost vdisk.


>>If the previous step was successful,check if the drive in encl 2 slot 5 now shows as leftover drive.
If so we can clear metadata and reuse this drive as spare.

# clear disk-metadata 2.5


>>if the drive comes up as failed or in any other state I would recommend you to replace this drive 2.5 with a new one or
You could also avoid this entire process and get a new drive exchanged for 2.5.So once you remove this drive,the ghost vdisk will be removed and you can insert a new drive.

 

I hope this is helpful!

Thanks 

 

I am a HPE employee

 

Sahana@R

Accept or Kudo

Technical_guy
Advisor

Re: P2000 G3 two vdisk with same name

Hi

Thanks for your prompt response,  below is the output once is run the command #show vdisk.

HP StorageWorks MSA Storage P2000 G3 FC
System Name: SAN01
System Location:
Version: TS240P004-02
# show vdisks
Name Size Free Own Pref RAID Disks Spr Chk Status Jobs
Job% Serial Number Drive Spin Down
Spin Down Delay Health
Health Reason
Health Recommendation
-------------------------------------------------------------------------------
vd01 5995.1GB 0B A A RAID5 11 0 64k FTOL
00c0ff1532b70000b645015100000000 Disabled
0 OK

vd01 2997.5GB 551.8MB A A RAID5 6 0 64k OFFL
00c0ff1b18060000990af95200000000 Disabled
0 Fault
The vdisk is offline. One disk failed for RAID 0 or NRAID, three disks failed for RAID 6, or two disks failed for other RAID levels. The vdisk cannot be recon structed.
- The CLI 'trust' command may be able to recover some or all of the data on th e vdisk. - Replace the failed disk or disks. (Look for event 8 in the event log to determine which disks failed.)
- To prevent this problem in the future, use a fault-tolerant RAID level and configure one or more disks as spare disks.
vd02 5995.1GB 196.1GB B B RAID5 11 0 64k FTOL VRSC
47% 00c0ff15341b000096a3f65300000000 Disabled
0 OK

Question : is it safe to delete the offline Vdisk in production. ordoest it need any restart.

thank you.

SahanaR
HPE Pro

Re: P2000 G3 two vdisk with same name

Hi,

You are very welcome!

I see that both the vd01 are having unique serial numbers.

So it is safe to delete the offline vdisk with its serial number,also this step has not caused any issues as far as I have seen.

If needed you can perform this action during a maintaience window or off business hours.

Also as stated earlier you can go with the below option,

>>if the drive comes up as failed or in any other state I would recommend you to replace this drive 2.5 with a new one or
You could also avoid this entire process and get a new drive exchanged for 2.5.So once you remove this drive,the ghost vdisk will be removed and you can insert a new drive.

 

NOTE:Please have a data backup of the production vdisk vd01 which was originally present.Just in case of emergency.

 

Thanks

 

 

 

 

Sahana@R

Accept or Kudo