Author: b t
-
One board failed. Nothing went down — everything got a hundred times slower.
Part numbers: 00Y5860 / 00RY384 (IBM Storwize V5000 node canister) An afternoon in early August, a data centre called it in, and the description was vague: “Nothing is down, but it’s very slow.” The array was online, the volumes were all there, hosts could read and write, and there was no outage alarm at all.…
-
A cache battery that sat in the warehouse for three years reported low charge on day one
Part numbers: 078-000-079 (EMC VPLEX) · 81Y2432 (IBM DS5020) · 5541807-A (HDS VSP 9500) Start with something most people have never thought about. A battery is the only spare that degrades while doing nothing. A controller, a mainboard, a network card — keep them dry and static-safe and they will sit on a shelf for…
-
The same 300GB 15K SAS drive — so why will the VMAX not accept it?
Part numbers: 005050266 (EMC VMAX40K 300GB 15K 2.5″) · 005052957 (EMC Unity 450F 600GB 10K 2.5″) This is the trap the buying side falls into most often, and it is fallen into with complete confidence. The array reports a failed drive. Operations writes down the specification: 2.5-inch, SAS, 300GB, 15K RPM. They take those parameters…
-
The controller is in, the lights are green, and the disks will not claim it
Part number: FAS8200 (NetApp controller) This is where a NetApp controller replacement most often stalls, and the symptom when it does is alarming: the part is in, the machine came up, the indicators are normal, but the new controller cannot see its half of the disks. The spare is not faulty. A step was missed.…
-
-
-
-
-
-
