*sigh* More work woes.
Jun. 18th, 2004 10:11 amYou know how the Chinese give names to their years. Like, the Year of the Dragon, and the Year of the Monkey, and so forth?
This is the week of the Raid Failure.
Got a page this morning, waking me from what had been a fairly restless night, so I was none to happy at being dragged out of bed half an hour before I was due to get up. It was one of the network engineers, who wanted me to know that the server on my workbench was beeping loudly and was there anyway to make it stop. I had him log in on the console and shut the box down, as it's not in production and could stand to be switched off until I got to the office.
After my morning meeting, I came back to my desk and fired it up to see what was up. As soon as it got to the SCSI initialization phase, it started wailing. I had a sinking feeling I know what that meant, so I escaped into the RAID controller's config screen to see. Yep, there's a bad disk. This box only has three drives, so it actually has no spare to pull in in case of disk failure; when you lose one, it is automatically in degraded mode.
I started a rebuild, and will now have to see about getting a replacement drive before I can wrap this project up. My only consolation is that at least it failed today, rather than this time next week after I had shipped it to the customer's site in Kentucky.
Apologies for all the work stuff this week, but it's what's consuming most of my attention the last few days. (Well, there's some non-work stuff, but I'm not ready to talk about that yet. <G>)
This is the week of the Raid Failure.
Got a page this morning, waking me from what had been a fairly restless night, so I was none to happy at being dragged out of bed half an hour before I was due to get up. It was one of the network engineers, who wanted me to know that the server on my workbench was beeping loudly and was there anyway to make it stop. I had him log in on the console and shut the box down, as it's not in production and could stand to be switched off until I got to the office.
After my morning meeting, I came back to my desk and fired it up to see what was up. As soon as it got to the SCSI initialization phase, it started wailing. I had a sinking feeling I know what that meant, so I escaped into the RAID controller's config screen to see. Yep, there's a bad disk. This box only has three drives, so it actually has no spare to pull in in case of disk failure; when you lose one, it is automatically in degraded mode.
I started a rebuild, and will now have to see about getting a replacement drive before I can wrap this project up. My only consolation is that at least it failed today, rather than this time next week after I had shipped it to the customer's site in Kentucky.
Apologies for all the work stuff this week, but it's what's consuming most of my attention the last few days. (Well, there's some non-work stuff, but I'm not ready to talk about that yet. <G>)