Sign in with
Sign up | Sign in
Your question

RAID 0 Error

Last response: in Storage
Share
April 25, 2006 11:28:56 PM

The following shows that on boot-up, something is wrong with the RAID operation on my PC. How do I determine the reason for the "Error Occurrd" messages next to each drive? Is this a RAID controller issue or a drive issue? Windows fails to load after this screen:

Intel(R) RAID for Serial ATA - RAID BIOS v3.0.0.2344
Copyright(C) 2003 Intel Corporation. All Rights Reserved.

RAID Volumes:
[Maxtor 6Y200M0 Port0 189.9GB Error Occurrd
[Maxtor 6Y200M0 Port1 189.9GB Error Occurrd

Non-RAID Disks:
None defined.

More about : raid error

April 26, 2006 12:03:55 AM

Quote:
The following shows that on boot-up, something is wrong with the RAID operation on my PC. How do I determine the reason for the "Error Occurrd" messages next to each drive? Is this a RAID controller issue or a drive issue? Windows fails to load after this screen:

Intel(R) RAID for Serial ATA - RAID BIOS v3.0.0.2344
Copyright(C) 2003 Intel Corporation. All Rights Reserved.

RAID Volumes:
[Maxtor 6Y200M0 Port0 189.9GB Error Occurrd
[Maxtor 6Y200M0 Port1 189.9GB Error Occurrd

Non-RAID Disks:
None defined.


i believe that you need to install appropriate raid drivers.
April 26, 2006 12:31:23 AM

hmmmm i think you must enter raid utility menu and create a raid array of any kind... or disable raid at all if you dont want to use
Related resources
April 26, 2006 2:41:32 AM

Is this a new array you are trying to set up or one that was working fine and now has gone wrong somehow?
April 26, 2006 3:44:59 AM

this is an old array that just started acting up.
April 26, 2006 5:59:28 PM

I'm w/ Wusy on this one. I think you're screwed bud. Try googling the error messages- that might shed some light on to what's fu*cked up.

-mpjesse
April 26, 2006 6:50:24 PM

This also happened to me on my MSI MB. I had two 80GB, Raid 1 running just the OS. The Raid lasted about 2 months, and then one day during a boot the RAID failed.

Untill the firmware is updated on my MB, I am not going to try it again on that controller.
April 26, 2006 7:01:08 PM

do you have smart enabled for your disks? does it report any error?
April 26, 2006 7:28:10 PM

Quote:
The following shows that on boot-up, something is wrong with the RAID operation on my PC. How do I determine the reason for the "Error Occurrd" messages next to each drive? Is this a RAID controller issue or a drive issue? Windows fails to load after this screen:

Intel(R) RAID for Serial ATA - RAID BIOS v3.0.0.2344
Copyright(C) 2003 Intel Corporation. All Rights Reserved.

RAID Volumes:
[Maxtor 6Y200M0 Port0 189.9GB Error Occurrd
[Maxtor 6Y200M0 Port1 189.9GB Error Occurrd

Non-RAID Disks:
None defined.


What about clearing the BIOS?
April 26, 2006 7:41:21 PM

It may be possible to recreate the array, but don't initilize the array (or what ever the term the controller uses) and it won't wipe out the data. If that works, get your data off immediately and then rebuild the array. I've been able to do this before.

Go into the raid setup menu and you'll probably see that the disks are off line, or aren't allocated, or what ever term that particular controller uses. It will allow you to force the disks back on line, or to allocate them, and then it may give you the option to create the array, or create and initialize the array and may tell you that if you initialize the array you will lose the data...obviously you don't want to do that. :wink:
April 26, 2006 8:32:56 PM

Is this an onboard RAID, intel southbridge? Did you recently update your BIOS ?
April 26, 2006 9:13:49 PM

I laugh at your RAID 0 error, and laugh even louder at the time, and hassle you'll experience trying to resurrect it.

Repeat after me: RAID 0 sucks donkey testicles.

The only exception is where it runs in tandem with RAID 1 - but that is so expensive it's just plain dumb, unless you have more money than brains...

And Wusy - learn to spell for god's sake: the word is "LOSE".

"LOOSE" is what your brain is. :p 
April 26, 2006 9:36:59 PM

Quote:
I laugh at your RAID 0 error, and laugh even louder at the time, and hassle you'll experience trying to resurrect it.

Repeat after me: RAID 0 sucks donkey testicles.

The only exception is where it runs in tandem with RAID 1 - but that is so expensive it's just plain dumb, unless you have more money than brains...

And Wusy - learn to spell for god's sake: the word is "LOSE".

"LOOSE" is what your brain is. :p 


There is so many time to laugh about failure..

Overclocking.. fried CPU, RAM, motherboard or video card ... But still, most people here just advice 90% of the time to do it.

Virus, spyware,.. and all the like that make system unstable and can cause data loss..

RAID is another thing that may go wrong.. or may not.. just like OC. So what the point to advise against RAID? It is his data, his life and if he want to have RAID, or OC, or visit porn or hacking website and get lot of viruses.. it is his fucking business.

And you said that RAID 1 is good.. so what about...

Quote:
This also happened to me on my MSI MB. I had two 80GB, Raid 1 running just the OS. The Raid lasted about 2 months, and then one day during a boot the RAID failed.

Untill the firmware is updated on my MB, I am not going to try it again on that controller.


Yes.. RAID 1 can fails too. When a controller fail, it is not HDDs fault. It can happen with any hardware.. The PSU might blow and kills your HDD, be it a RAID array or single drive. Maybe the entire system.

If one would stop doing and trying things with his computer because something may fail, then having a computer is just not an option to him.

I'm running OCed.. yes, I did corrupt windows installation . I fix it and i'm still running OCed.. simply slightly less.

Yes I'm running a RAID0 array. I still have to fail. I started using RAID in 2001, and so far, I'm at my third array, updated to get increased storage, not because one fails.

MAybe one day, the array will fail. So what. I still have a backup of my important stuff on a drive that's not part of the array. And if that single drive fails, I have the same folder on my array. if both fails at the same time.. my digital picture are saved one a couple of dvd.

But the fun part is that I enjoy trying something new on my computer. I'm not slave to it.

By the way, next time you go outside, watch out the next time you get outside (if you actually have a life..) because you may fell of the porch and break your neck. Don't take your car, you may have a fatal accident and die. Don't ride bicycle.. don't swim, don't go on a boat. Don't take the plane. Don't eat too, you may suffocate and die. Stop breathing, you may get some viruses..
April 26, 2006 9:38:56 PM

Quote:
The following shows that on boot-up, something is wrong with the RAID operation on my PC. How do I determine the reason for the "Error Occurrd" messages next to each drive? Is this a RAID controller issue or a drive issue? Windows fails to load after this screen:

Intel(R) RAID for Serial ATA - RAID BIOS v3.0.0.2344
Copyright(C) 2003 Intel Corporation. All Rights Reserved.

RAID Volumes:
[Maxtor 6Y200M0 Port0 189.9GB Error Occurrd
[Maxtor 6Y200M0 Port1 189.9GB Error Occurrd

Non-RAID Disks:
None defined.


I'm thinking more that it is a controller failure rather than a drive failure. Unless you did something to kill both drive, it is likely not to happen.

If you have acces to a similar board with same controller, you may try it to see if your drive are still accessible
April 26, 2006 9:40:14 PM

Quote:
By the way, next time you go outside, watch out the next time you get outside (if you actually have a life..) because you may fell of the porch and break your neck. Don't take your car, you may have a fatal accident and die. Don't ride bicycle.. don't swim, don't go on a boat. Don't take the plane. Don't eat too, you may suffocate and die. Stop breathing, you may get some viruses..

i think.... i think i'm gonna cry man
April 26, 2006 9:45:45 PM

Quote:
By the way, next time you go outside, watch out the next time you get outside (if you actually have a life..) because you may fell of the porch and break your neck. Don't take your car, you may have a fatal accident and die. Don't ride bicycle.. don't swim, don't go on a boat. Don't take the plane. Don't eat too, you may suffocate and die. Stop breathing, you may get some viruses..

i think.... i think i'm gonna cry man

big boys don't cry
April 26, 2006 10:47:10 PM

Not that I can say for certain it isnt the controler....

But I vote degraded PSU. What else do you have hooked up to what watt/brand/model PSU?


*I had a supposedly top notch PSU that started dropping drives with a similar error.
April 26, 2006 11:18:05 PM

I agree with Pat. I think it's a controller issue myself, and more correctly I think it is probably firmware and/or drivers that caused the drives to go off-line, and I am almost willing to bet the array [the data itself] is not dead and can be resurrected enough to get the data.

As for laughing at someones hardware issues, that's just juvenile. Having a single disk, or a raid array, or whatever else is risky and that is why you should always have a backup plan. It sucks when you have to learn these lessons for the first time, but that's life. Hopefully there wasn't any critical data that gets lost, but this is how we all learn, from using stuff and learning from errors, failures, etc. This is also how we gain experience and are able to help others, if we so choose. Laughing at that experience, well, you'll grow up eventually....maybe.

Blankj, I'm not replying to you, I just hit the reply button....but, I don't agree it's a PSU issue. :wink:
April 27, 2006 1:52:17 AM

If it makes a difference, the status of the logical RAID 0 drive is "Normal". The status "Error Occurrd" is on the physical drives.
April 27, 2006 1:57:38 AM

Quote:
do you have smart enabled for your disks? does it report any error?
yes, smart is enabled. where are the errors reported?
April 27, 2006 2:15:05 AM

I would do a full test of both drives using the manufactures utility (the test doesn't alter your data in any way) to see if they are in working order.

You could also run memtest86 and prime95 to see if you system is otherwise stable.

All of the above available via ultimate boot cd.

My onboard RAID controller lets me recreate arrays without initializing them. As long as I use the same settings I my data is ok.

If both drives are healthy that would be your best bet.

---

I used have similar problems every few months with my RAID 1 array until I switched to Western Digital Raid Edition 2 Drives. Perhaps the Time Limitted Error Recovery feature really does help! Or maybe I have just been very unlucky prior to the swith and very luck afterwards?

BTW I never lost data when my RAID 1 array crashed. I was just left with 2 identical non-RAID drives. I could then rebuild the array just by recreating the array without initializing or by removing one of the drives from the arra, adding it again as a hot spare and then rebuilding it using NVidia's RAID utility.

Obviously the 2nd method won't work with RAID 0.
April 27, 2006 2:43:24 AM

Quote:
Is this an onboard RAID, intel southbridge? Did you recently update your BIOS ?
the RAID in onboard, the southbridge is ICH5R and the BIOS has not been updated for at least the last few months.
April 27, 2006 2:50:02 AM

Quote:
I agree with Pat. I think it's a controller issue myself, and more correctly I think it is probably firmware and/or drivers that caused the drives to go off-line, and I am almost willing to bet the array [the data itself] is not dead and can be resurrected enough to get the data.

As for laughing at someones hardware issues, that's just juvenile. Having a single disk, or a raid array, or whatever else is risky and that is why you should always have a backup plan. It sucks when you have to learn these lessons for the first time, but that's life. Hopefully there wasn't any critical data that gets lost, but this is how we all learn, from using stuff and learning from errors, failures, etc. This is also how we gain experience and are able to help others, if we so choose. Laughing at that experience, well, you'll grow up eventually....maybe.

Blankj, I'm not replying to you, I just hit the reply button....but, I don't agree it's a PSU issue. :wink:


thank to you and everyone else who is keeping this in perspective.
April 27, 2006 2:54:58 AM

Quote:

Then why didn't you update it in the first place? (That's just silly)


because there wasn't an update?
April 27, 2006 11:33:30 AM

if there's an error the system stops before booting warning you about errors... if it didnt, there's no errors with your disk.. at least none smart could detect. smart cant detect media error for example, that could destroy your array but cant be detected via smart
May 21, 2006 10:59:51 PM

The error turned out to be from a bad drive, not from the raid controller or BIOS. The drive, a maxtor, is about 2.5 years old but only has a 1-year warranty. If I would have know the warranty was only for 1 year, I doubt I would have bought them. I bought them from Dell and they were a good deal, or so I thought. I'm using enterprise drives now. They're not quite as fast but they have a very good mean time to failure.

Thanks to everyone for all of your help.
!