System freezes after intel rapid storage technology

Hi.

I have a system on a Intel BOXDH67GD Sandy Bridge mainboard, with 5 Seagate 500 GB 7200.12 16 MB disk. 4 of them configured in a RAID 10 and one as the system disk.

After a reboot, the system wont boot, this is what happens when i try to boot:

1. Shows the Intel Raid Storage Technology screen with the raid configuration. In the RAID 10 configuration the status is Verify. I can access the menu by pressing CTRL+ I.

2. If none is pressed (or i exit the raid config menu), the only thing i see is the cursor blinking. And nothing is happening (I have attached a photo of the error).

I cannot access the BIOS by pressing F2, the only option i have is CTRL+I in the startup.

Eny suggestions on what the problem might be?
IMAG0104.jpg
Rybicki-IbsenAsked:
Who is Participating?
 
Rybicki-IbsenAuthor Commented:
We just tried to delete the RAID and create it again. That helped.

But after just two days - It makes the same error and freezes on startup. The controller must be broken.
0
 
jeff_01Commented:
It appears as though the raid manager is busy verifying the array before it will boot  (STATUS: Verify). There was obviously an issue and it has now forced a check. Try give it some time to complete. Perhaps you are rebooting before it gets a chance to finish.

Regards
0
 
Rybicki-IbsenAuthor Commented:
Hi Jeff 01.

It was my first idea as well, but it has been running about 10 hours. Should it take that much time?
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
DaeltCommented:
depending on what kind of HDD (Sata, SaS, IDE, SCSI), raid opérations can take hours and hours.

For instance last time i rebuild a SCSI 36Gb HDD on an old raid 5 server took 4 hours.

Not very used about raid 10 setups, but i guess that with 1TB virtual disk it can take a lot of time to make an operation. Maybe you have a status display on the verify operation in the raid controller menu, have a check, but i wont be surprised that it take more than 10 hours depending on your hardware.
0
 
Rybicki-IbsenAuthor Commented:
Daelt:

No progress bar or other indication of progress :/ But i can hear the disks are working.

Ill have to wait and see
0
 
noxchoGlobal Support CoordinatorCommented:
I've seen the cases when it run 24 hours. So wait.
0
 
coredatarecoveryCommented:
you could check the smart status of the drives with ubuntu, to identify the downed array memeber if waiting does not do it.

Verifying could take up to 2 days depending on drive size and speed of the motherboard.
0
 
coredatarecoveryCommented:
especially if there is a failing drive in the mix.
0
 
Rybicki-IbsenAuthor Commented:
All: Thanks for your input.

coredatarecovery: The systems looks before i even get to be apple to boot. Its stock on the screenshot i posted. Cant access bios, or do other than entering the Raid controller menu the 10 seconds or so of the boot process.

Or do you mean that I should i take the drives out of the machine and test them in another machine??


Ill give it some more time, and hope its gonna help, i suppose this operations should not take longer than 48 hours?
0
 
coredatarecoveryCommented:
It should not take longer than 48. Yes I advocate taking them out, however you must mark their order.
In ubuntu you are not mounting them, just checking disk manager, smart status.
0
 
Rybicki-IbsenAuthor Commented:
We did wait 50 hours - nothing happened!!

We tried to take off the harddrives in raid and boot only on the exteded System disk. Not possible!

We took of all the disk - in order to enter bios - not possible.

We tried a lot of different things. Did also check system states, by entering BIOS (There was a jumper on the motherboard allowing access to the BIOS on startup. Everything looked fine.

We reattached the harddrives. The system, was still hanging after displaying the RAID (as seen above)

We decided that this HAD to be an error in the raid controller. Unfortunately the controller is onboard, som the board has to be replaced.
 
0
 
Rybicki-IbsenAuthor Commented:
We have identified the RAID controller on the board to be broken.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.