- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- EVA6000
Disk Enclosures
1752567
Members
5138
Online
108788
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
12-15-2009 04:42 AM
12-15-2009 04:42 AM
EVA6000
Hi, I have an array 6.220 CV 9.1 and I have what appear to be orphaned drives in Command View.
Would anyone have any idea how this happened? If I un-present the drive it does have an effect on the server its allegedly presented to.
allocatedcapacity = unknown
allocatedcapacityblocks = unknown
comments =
creationdatetime = 01-Apr-2009 17:01:13
diskgroupid = 00010710B408056005EC06000090000000000400
diskgroupname = \Disk Groups\Default Disk Group
familyname = Test-CA2
mirrorcache = mirrored
objecthexuid = 6005-08b4-0006-ec05-0000-9000-01a4-0000
objectid = 20200710B408056005EC0600009000000000A401
objectname = \Virtual Disks\VMware Disks\Test-CA2\ACTIVE
objectparenthexuid = 6005-08b4-0006-ec05-0000-9000-01a3-0000
objectparentid = 00000710B408056005EC0600009000000000A301
objectparentuid = 00000710B408056005EC0600009000000000A301
objecttype = virtualdisk
objectwwn =
osunitid = 0
partitionname = ACTIVE
preferredpath = a_failover_failback
presentations
presentation
hostid = 11800710B408056005EC06000090000000005C01
lunnumber = 1
hostname = \Hosts\SQLFarm\UIWDBTST04
readcache = enable
redundancy = vraid1
requestedcapacity = unknown
requestedcapacityblocks = unknown
restoreprogress = n/a
scvdenable = enable
uid = 20200710B408056005EC0600009000000000A401
virtualdiskpresented = yes
virtualdisktype = original
writeprotect = disable
wwlunid = 6005-08b4-0006-ec05-0000-9000-01a4-0000
Would anyone have any idea how this happened? If I un-present the drive it does have an effect on the server its allegedly presented to.
allocatedcapacity = unknown
allocatedcapacityblocks = unknown
comments =
creationdatetime = 01-Apr-2009 17:01:13
diskgroupid = 00010710B408056005EC06000090000000000400
diskgroupname = \Disk Groups\Default Disk Group
familyname = Test-CA2
mirrorcache = mirrored
objecthexuid = 6005-08b4-0006-ec05-0000-9000-01a4-0000
objectid = 20200710B408056005EC0600009000000000A401
objectname = \Virtual Disks\VMware Disks\Test-CA2\ACTIVE
objectparenthexuid = 6005-08b4-0006-ec05-0000-9000-01a3-0000
objectparentid = 00000710B408056005EC0600009000000000A301
objectparentuid = 00000710B408056005EC0600009000000000A301
objecttype = virtualdisk
objectwwn =
osunitid = 0
partitionname = ACTIVE
preferredpath = a_failover_failback
presentations
presentation
hostid = 11800710B408056005EC06000090000000005C01
lunnumber = 1
hostname = \Hosts\SQLFarm\UIWDBTST04
readcache = enable
redundancy = vraid1
requestedcapacity = unknown
requestedcapacityblocks = unknown
restoreprogress = n/a
scvdenable = enable
uid = 20200710B408056005EC0600009000000000A401
virtualdiskpresented = yes
virtualdisktype = original
writeprotect = disable
wwlunid = 6005-08b4-0006-ec05-0000-9000-01a4-0000
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-15-2009 07:12 PM
12-15-2009 07:12 PM
Re: EVA6000
Hi DwainDibbly,
Looks like some issue with this Vdisk. Complete log from EVA would give better idea on what happed, however, if you do not have data on it, you may delete and create another Vdisk.
Regards
Susanta
Looks like some issue with this Vdisk. Complete log from EVA would give better idea on what happed, however, if you do not have data on it, you may delete and create another Vdisk.
Regards
Susanta
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP