HP P4000 HP Smart Array SAS controllers for Integrity servers support guide - Page 82

Physical disk state definitions, WRONG PHYSICAL DISK WAS - unrecoverable i o

Get HP P4000 PDF manuals and user guides View all HP P4000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 82 highlights

USING INTERIM RECOVERY MODE READY FOR RECOVERY OPERATION RECOVERING WRONG PHYSICAL DISK WAS REPLACED PHYSICAL DISK(S) NOT PROPERLY CONNECTED EXPANDING NOT YET AVAILABLE QUEUED FOR EXPANSION • An array expansion was aborted. • The logical drive is temporarily disabled because another logical drive on the controller had a missing disk at power on. Also known as a "degraded" state. A physical disk in a fault tolerant logical drive has failed. For RAID 1, 1+0 or 5, data loss can result if a second disk fails. For RAID ADG, data loss can result if two additional disks fail. A replacement disk is present, but the rebuild has not started yet; for example, because another logical drive might be rebuilding. The logical drive also returns to this state if the rebuild is aborted due to unrecoverable read errors from another disk. Physical disks in this logical drive are being rebuilt. When the logical drive was in a degraded state, the system was powered off and a disk other than the failed disk was replaced. When the system was powered off, disks were removed. Any other logical drives are held in a temporary FAILED state when this occurs. The data in the logical drive is being reorganized because: • Physical disks have been added to the array (capacity expansion). • The stripe size is being changed (stripe size migration). • The RAID level is being changed (RAID level migration). A capacity expansion operation is in progress (or is queued up) that will make room on the disks for this new logical drive. Until room is made on the physical disks, the newly configured logical drive cannot be read or written. The logical drive is waiting to undergo data reorganization (see EXPANDING). Possible causes for the delay are a rebuild or expansion operation that might be in progress. Physical disk state definitions The Status column of the SCSI Device Summary in the sautil command output example also provides useful troubleshooting information. To interpret the status of physical disks, use the following physical disk state definitions. The physical disk state definitions are also included in the sautil manpage. OK The physical disk is configured in one or more logical drives and is operational. SPARE The physical disk is configured as a spare disk. UNASSIGNED The physical disk has not been configured in any logical drives. FAILED The configured physical disk has failed. 82 Troubleshooting

  • 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
  • 142
•
An array expansion was aborted.
•
The logical drive is temporarily disabled because
another logical drive on the controller had a missing
disk at power on.
USING INTERIM RECOVERY
MODE
Also known as a “degraded” state. A physical disk in a
fault tolerant logical drive has failed. For RAID 1, 1+0 or
5, data loss can result if a second disk fails. For RAID ADG,
data loss can result if two additional disks fail.
READY FOR RECOVERY
OPERATION
A replacement disk is present, but the rebuild has not
started yet; for example, because another logical drive
might be rebuilding. The logical drive also returns to this
state if the rebuild is aborted due to unrecoverable read
errors from another disk.
RECOVERING
Physical disks in this logical drive are being rebuilt.
WRONG PHYSICAL DISK WAS
REPLACED
When the logical drive was in a degraded state, the system
was powered off and a disk other than the failed disk was
replaced.
PHYSICAL DISK(S) NOT
PROPERLY CONNECTED
When the system was powered off, disks were removed.
Any other logical drives are held in a temporary
FAILED
state when this occurs.
EXPANDING
The data in the logical drive is being reorganized because:
•
Physical disks have been added to the array (capacity
expansion).
•
The stripe size is being changed (stripe size migration).
•
The RAID level is being changed (RAID level
migration).
NOT YET AVAILABLE
A capacity expansion operation is in progress (or is queued
up) that will make room on the disks for this new logical
drive. Until room is made on the physical disks, the newly
configured logical drive cannot be read or written.
QUEUED FOR EXPANSION
The logical drive is waiting to undergo data reorganization
(see
EXPANDING
). Possible causes for the delay are a
rebuild or expansion operation that might be in progress.
Physical disk state definitions
The Status column of the SCSI Device Summary in the
sautil
<device_file>
command
output example also provides useful troubleshooting information. To interpret the status of
physical disks, use the following physical disk state definitions. The physical disk state definitions
are also included in the
sautil
manpage.
OK
The physical disk is configured in one or more logical drives and is operational.
SPARE
The physical disk is configured as a spare disk.
UNASSIGNED
The physical disk has not been configured in any logical drives.
FAILED
The configured physical disk has failed.
82
Troubleshooting