Click to See Complete Forum and Search --> : Server SCSI/Raid Confusion.


Phleace
12-20-2004, 07:53 PM
Hello,

I'm having problems getting a NetServer LPr PIII/500 up and running. It is to mainly be used on our LAN for storage and hosting for our website. Upon examining the system, it would appear one of the hard drives is dead. It makes a loud clicking noise and the system hangs when it tries to read from it or identify it. I am still trying to work up to getting an OS installed on it. I took out the faulty hard drive and kept in the single other drive (P1166A 18.2GB ULTRA3 10K) but I cannot seem to be able to do anything with it. I've spent close to nine hours playing around in the BIOS and in the NetRaid Express Tools configuration program, but all I can accomplish is getting the NetRaid card to beep loud and long at me when I try boot with the settings. I'm afraid I dont know a whole lot about SCSI/Raid configurations, as I'm new with working with servers of these kinds. I have tried moving around the cables to get the drive to show up on Channel-1, 2, and 3, and the ID is always shown as 0. When I Array the drive (not sure I really undertstand the process) the HDD is shown as "ONLIN A0-O". Upon save and reboot, the NetRaid card beeps constantly and I have to clear the configuration to get it to stop. I can boot Linux and Windows installation CD's just fine, but when it comes time to partition, the beeping starts back up again and the system stops. I am at a loss as to how to deal with this issue, though I'm afraid it's probably something incredibly simple I'm just not doing right. I am extremely new to SCSI hard drives and cables and the settings they use, and my understanding of the terms is a little on the weak side.

Any and all help is greatly appreciated.

Thanks!

~Jason

techwise
12-20-2004, 10:55 PM
Well I dont know too much either but I do believe that if you are attempting to set up hardware raid you are going to need more than one hard drive. Depending on the level raid you choose you need at least 2.

This could be the problem.

Try using that drive in a non raid configuration.

Mike