Main Topics
Browse All Topics
This is a Dell 2650 with 2 SCSI drives (each 136 gb).. I have set it up as one container (one volume, no raid) so that the os should see it as 272 gb (which it does).. I am able to install centos 5.3 from the install cds (I chose server gui) but on reboot after installation is complete, it hangs.. It does seem to load grub.. but then I see 2 error message.. one seems to indicate something is wrong with a memory address and in the second it times out waiting to hear from the scsi adapter (waits for 22 s in an infinite loop).
would like to hear about possible ways to fix this; I read on another thread that one is supposed to give some startup parameters during install to let the OS talk to the adaptec controller correctly.
I did try initially to set it up as raid 1 using the Ctrl-A but it appears that the scrub process percentage indicator didnt seem to change (or maybe I just didnt wait long enough)
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Make sure that you have disabled the raid in the system bios if you are not going to use it. That could be the reason for the issue. If it is not disabled, you will need the raid driver to connect to the drives properly.
For my two cents, I like the hardware raid option better. I have seen a lot of reliability in these setups. If you don't want to lose any space to a raid configuration, the controller is capable of Raid 0 which will allow you to use all of the space.
The scrub is important to the process of creating the array. This is how the controller will align the sectors and build the metadata. The scrub can take up to two to five minutes per GB of array space. I would let the scrub continue until it has had that much time. If it is stuck trying to do the scrub, you may have a hardware issue in the raid/scsi or harddrives. Because you finished that install, I do not believe that is the most likely scenario.
More likely is that the controller was attempting a scrub while you were installing. If the install gets ahead of the scrub, the scrub may be wiping data right behind the install. That can lead to the situation you described. That is why I was concerned you may not have disabled the raid controller properly.
Turns out that I just had to wait for 20 minutes during the boot process for it to probe all the scsi devices and after that it proceeded as normal.. I turned off the cluster mode in the cmos setup but I dont think that was relevant..
so the problem turned out to be a non-problem.. (solution: wait for boot up to finish.. hopefully it doesnt do it on later boots)
Business Accounts
Answer for Membership
by: ComputerTechiePosted on 2009-04-20 at 14:25:11ID: 24188874
I would rebuild the Raid and reformat the drives than install OS.
CT