Carlos E. R. wrote:
The Thursday 2008-04-03 at 03:10 +0200, Joachim Schrod wrote:
Just make sure that you really rip out the broken disk. Just last month, I was called to a customer's site because some sleep-deprived sysadmin ripped out the working disk, and not the broken disk. Usually, I recommend my technicians to just let the RAID degrade and repair it with calm, when they are well rested -- after all, they just lost the failover possibility... ;-)
I wonder why they don't put a LED on them, so that you can light it up from some software and see "that one".
Well, if the hdd is broken the led probably won't get the signal anyway. (^-^) Normally, a server with a hardware raidcontroller and hotplug enclosure is SAF-TE aware, each hdd slot has an activity and a failure led, so the raid controller that monitors the disks will activate the failure led if the drive does not work correctly. This presumes that the drive enclosure is SAF-TE compliant and the raidcontroller is connected to the enclosure with the necessary signal cable. That means you stand in front of the server because the beeper of the raid controller is screaming so loud you can't ignore it. Then you take a look at the hotplug enclosure and see the drive slot with the constantly gleaming red led. You grumble a bit, rip out the drive and search for a compatible hdd. Plug in the new drive and watch the activity leds when the rebuild starts. Our systems usually have both the fault and activity led of the replacement slot blinking as long as the rebuild runs. All the while you get mails with the alerts and the status of the raid system. Since all of this doesn't require stopping or logging in to the system even a NOC technician is able to do this. Even your boss will (probably) be able to switch the broken drive. -- Sandy List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org