HP Surestore Disk Array 12h Storage Manager 60-NT User’s Guide - Page 119

Access Volume disabled with NVSRAM

Page 119 highlights

Operating on Microsoft Windows Restriction Workaround After installing the Host-Agent software, you see an error message with "Service Error 100" on the host. Causes include: The Host-Agent software does not find any controllers with firmware version 4.x. Controllers with firmware version 4.x have the Access Volume disabled with NVSRAM configuration settings. The NVSRAM on controllers in a Storage Array you are attempting to manage contains an Access Volume logical unit number that is already in use by another volume. A possibility of file system corruption exists when resources are moved back and forth multiple times between cluster nodes using Microsoft Cluster Server running under Windows 2000 Advanced Server. When the cluster resource is moved, the owning node flushes cache and then releases the reservation to the volume(s). The other node then reserves the volume(s). In some instances, file system reads and writes do not finish before the release. This results in a reservation conflict and file system corruption. Trying to recover using the chkdsk command causes the file system information to be corrected in such a way that some files are no longer accessible. The NVSRAM on controllers in a Storage Array you are attempting to manage contains an Access Volume logical unit number that is not supported by the operating system and installed patches. For example, the Access Volume is configured at LUN 32, but the operating system and service packs only support 8 LUNs. None. The problem is highly unlikely to occur during normal failover situations. 119

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141

2SHUDWLQJ±/LPLWDWLRQV±±±±±±
119
Operating on Microsoft
Windows
After installing the Host-Agent software, you
see an error message with
Service Error 100
on the host.
Causes include:
The Host-Agent software does not find any
controllers with firmware version 4.x.
Controllers with firmware version 4.x have the
Access Volume disabled with NVSRAM
configuration settings.
The NVSRAM on controllers in a Storage Array
you are attempting to manage contains an
Access Volume logical unit number that is
already in use by another volume.
The NVSRAM on controllers in a Storage Array
you are attempting to manage contains an
Access Volume logical unit number that is not
supported by the operating system and
installed patches. For example, the Access
Volume is configured at LUN 32, but the
operating system and service packs only
support 8 LUNs.
A possibility of file system corruption exists
when resources are moved back and forth
multiple times between cluster nodes using
Microsoft Cluster Server running under
Windows 2000 Advanced Server.
When the cluster resource is moved, the
owning node flushes cache and then releases
the reservation to the volume(s). The other
node then reserves the volume(s). In some
instances, file system reads and writes do not
finish before the release. This results in a
reservation conflict and file system corruption.
Trying to recover using the chkdsk command
causes the file system information to be
corrected in such a way that some files are no
longer accessible.
None. The problem is highly unlikely to occur
during normal failover situations.
7DEOH±¹¹ ±
2SHUDWLQJ±/LPLWDWLRQV±IRU±:LQGRZV±·²²²±±Â6KHHW±Ä±RI±µÃ
Restriction
Workaround