I've been taking Fridays off from work this summer, and by Friday August 21 I had thought I had everything figured out.
- I realized the problem I had getting Windows 7 to install on my RAID was that I had not set a system disk - and the Windows installer is too stupid to let you sent one from the UI. But this was something I could set in the S5520SC BIOS.
- I had heard from DriverHeaven that other people had the same CPU spiking problem with Windows 7 and that I should use Visa in the meantime.
- I confirmed that one of my disk drives was defective.
I really took my time and wanted everything to go well for once. I got everything ready and then went into the BIOS to set up the RAID. For some reason the BIOS setup was not working properly this time, it would not let me finished configuring my second virtual disk - it kept freezing and forcing me to reboot the computer - grumble grumble grumble.
Next I thought I would try using the Intel RAID Web Console 2 from the utility CD. I booted the CD, and then upgraded to the latest version of the utility from the network, but I could not get the Web Console 2 to work - nothing would happen. Next I rebooted the CD again, but this time I did not do the network upgrade. Finally I was able to get into the RAID Web Console 2 user interface. This application was pretty crummy too, confusing to use, and buggy in some places. Eventually I managed to define the two RAID 5 virtual disks I wanted and started to initialize them. After 30 minutes I was wondering what was taking so long and then a progress bar finally popped up to show that it was only 10% done. I wish I had selected the fast initialization instead of the full initialization. I was getting tired of waiting so I went off to do some reading for a while.
I came back 15 or 20 minutes later to see how things were and found the screen blank, and the graphics card fan was on full (something that never happened before). I tried power the system off and on, but nothing happened. In fact, when powering the system on the Power On Self Test (POST) LEDs would not even light up at all. That was a very bad sign.
Eventually I found a phone number for Intel technical support and someone talked me through some tests. Mostly it was removing stuff from the motherboard and powering the system back on. Nothing helped and nothing changed so the support person conceded that the board was dead and sent me instructions for returning the board for a replacement.
By this time I felt pretty crushed - the morning had started off so well, and by mid afternoon it looked like I was finally going to get everything working - when BAM - the worst happens. I suppose this it what someone feels like after a terrible child birth and they discover that their child is not only retarded, but blind and deaf too. Of course this was just a computer and could never be the same as a child, but I just felt really depressed and angry. Why me?
The next day I set out to return the motherboard. First of all Intel required that there be some sort of commercial invoice for customs purposes so it took me an hour or so to fabricate something that looked official. Next was the process of removing all the connectors from the motherboard. Taking the water blocks off of the CPUs was interesting - but it was good to see that the thermal compound I had used had spread out nice and evenly across the CPU heat spreader. Of course I had to clean everything off and put the CPUs away safely, then prepare the motherboard for shipping. I took me almost 45 minutes at the UPS store to get all the information right because I was shipping across the boarder. I selected the least expensive shipping method, and that took over a week and cost me $85.00.
Anyway, I've had two weeks waiting for a replacement and today I'm supposed to get my replacement motherboard...
No comments:
Post a Comment