Quantcast
Channel: VMware Communities : Popular Discussions - VI: VMware ESX® 3.0
Viewing all articles
Browse latest Browse all 60069

Problem with MSA1500, Luns (works under VMWare)

$
0
0

Hello,

My client have an great problem. Have an MSA1500 and that works under VMWare v. 3.x . The problem is with result that shows CLI. I dont know what he know to do, what option shall be used. They don't want to lost the data. The problem ist that, they have not the accessibility to contents of LUN's.

 

CLI-1> show unit 1

 

Unit 1:

In PDLA mode, Unit 1 is Lun 2; In VSA mode, Unit 1 is Lun 1.

Unit Identifier   :

Device Identifier : 600508B3-0092FE90-A9990461-904E000C

Preferred Path    : Controller 1 (this controller)

Cache Status      : Enabled

Max Boot Partition: Disabled

Volume Status     : VOLUME FAILED (Media_exchanged)

Parity Init Status: waiting for first write

 

5 Data Disk(s) used by lun 1:

   Disk101: Box 1, Bay 01, (B:T:L 0:03:01)   REPLACED MARKED OK

   Disk102: Box 1, Bay 02, (B:T:L 0:03:02)   REPLACED MARKED OK

   Disk103: Box 1, Bay 03, (B:T:L 0:03:03)   REPLACED MARKED OK

   Disk104: Box 1, Bay 04, (B:T:L 0:03:04)   REPLACED MARKED OK

   Disk105: Box 1, Bay 05, (B:T:L 0:03:05)   REPLACED MARKED OK

 

Spare Disk(s) used by lun 1:

   Disk106: Box 1, Bay 06, (B:T:L 0:03:06)

Logical Volume Raid Level: DISTRIBUTED PARITY FAULT TOLERANCE (RAID 5)

                          stripe_size=64kB

Logical Volume Capacity : 953,814MB

 

 

Usage: accept units

 

       accept unit <#>

  1. = {0-31}

 

Accept media exchange on the unit #.  If a failed unit has all the drives

 

in working order, you can use this command to change the state of

 

the unit to VOLUME_OK.

 

If unit # is not specified, it does it for all the units.

 

Thanks for help

Sylwia


Viewing all articles
Browse latest Browse all 60069

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>