Go Back   Wireless and Wifi Forums > News > Newsgroups > alt.comp.hardware
Register FAQ Forum Rules Members List Calendar Search Today's Posts Advertise Mark Forums Read

 
Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 01-07-2007, 02:11 PM
John
Guest
 
Posts: n/a
Default "Error Occurred(0)" with RAID 0. What does it mean?

During boot up, one of my two week old hard disks in my RAID 0 is now
reporting this error:

"Error Occurred(0)"

I googled for this error message and found only one other person that
reported this error and his screen snapshot is nearly identical to my
problem.

http://www.hardforum.com/showthread.php?t=1132761

None of the responses that I read in that thread were helpful to me.

Using Western Digital diagnostic tools, I tested each drive and no
errors in either drive were discovered. Chkdsk also reported no errors.

From the time I first observed this error message some days ago, the
computer has been working without any apparent problems (boots up and
runs just fine) but the error message is driving me nuts.

I have two of these disks:

Western Digital Caviar SE16 WD3200KS 320GB 7200 RPM 16MB Cache SATA

RAID 0 with Intel Matrix Storage Manager

Motherboard: ASUS P5B-E (latest BIOS installed).

Intel ICH86/DO/DH SATA RAID Controller:
Driver date: 5/11/06
Driver version: 6.0.0.1022

JMicron JMB36X Controller:
Device type: SCSI and RAID controllers
Manufacturer: JMicron Technology
Driver date: 12/5/2006
Driver version: 1.17.8.1

Device manager reports no errors for either of the above controllers.

XP Professional. All service packs and updates installed.

Intel Core 2 Duo E6600 Conroe 2.4GHz 4M shared L2 Cache LGA 775 Processor


Does anyone have any suggestions on how I can resolve this error message?





Reply With Quote
  #2 (permalink)  
Old 01-07-2007, 03:11 PM
HDRDTD
Guest
 
Posts: n/a
Default Re: "Error Occurred(0)" with RAID 0. What does it mean?

It 'might' be that one of the drives has developed a SMART error.

Years ago when the WD 36gig Raptors first came out, I had two iof them
running in a RAID 0 array.

My symtoms were slightly differenrt than your, mine would randomly lock up.
Usually re-booting the system got it going again but I could never find the
problem.

One of the thing I did notice, was that none of the programs I tried could
read the SMART status of either drive.

After a while, I finally decided to change to a single Raptor 74gig in part
becauise I wanted to replace the RAID array drives with some other drive for
troubleshooting.

Once I got the system running on the new drive, I installed the old drives
as seperate drives, and lo and behold, one of the drives started reporting a
SMART error.!

I downloaded the WD diagnostics, it found a bad spot that SMART had been
trying to report. I got an rma from WD, they replaced the drive and the
replacement drive is still running in another system years later.


My point is, One of the drives may have developed a SMART error, but because
they are in a RAID 0 array, nothing can report the SMART error in detail,
and you may not see the actual error until the RAID array is broken into two
ordinary drives.


"John" <John@nospam.net> wrote in message
news:45a10df8$0$27099$4c368faf@roadrunner.com...
> During boot up, one of my two week old hard disks in my RAID 0 is now
> reporting this error:
>
> "Error Occurred(0)"
>
> I googled for this error message and found only one other person that
> reported this error and his screen snapshot is nearly identical to my
> problem.
>
> http://www.hardforum.com/showthread.php?t=1132761
>
> None of the responses that I read in that thread were helpful to me.
>
> Using Western Digital diagnostic tools, I tested each drive and no errors
> in either drive were discovered. Chkdsk also reported no errors.
>
> From the time I first observed this error message some days ago, the
> computer has been working without any apparent problems (boots up and runs
> just fine) but the error message is driving me nuts.
>
> I have two of these disks:
>
> Western Digital Caviar SE16 WD3200KS 320GB 7200 RPM 16MB Cache SATA
>
> RAID 0 with Intel Matrix Storage Manager
>
> Motherboard: ASUS P5B-E (latest BIOS installed).
>
> Intel ICH86/DO/DH SATA RAID Controller:
> Driver date: 5/11/06
> Driver version: 6.0.0.1022
>
> JMicron JMB36X Controller:
> Device type: SCSI and RAID controllers
> Manufacturer: JMicron Technology
> Driver date: 12/5/2006
> Driver version: 1.17.8.1
>
> Device manager reports no errors for either of the above controllers.
>
> XP Professional. All service packs and updates installed.
>
> Intel Core 2 Duo E6600 Conroe 2.4GHz 4M shared L2 Cache LGA 775 Processor
>
>
> Does anyone have any suggestions on how I can resolve this error message?
>
>
>
>




Reply With Quote
  #3 (permalink)  
Old 01-07-2007, 04:19 PM
old man
Guest
 
Posts: n/a
Default Re: "Error Occurred(0)" with RAID 0. What does it mean?

I agree hd's in a raid array do not allways show SMART errors
The hd manu checking utilities do not allways work perfectly when they are
on an array

"John" <John@nospam.net> wrote in message
news:45a10df8$0$27099$4c368faf@roadrunner.com...
> During boot up, one of my two week old hard disks in my RAID 0 is now
> reporting this error:
>
> "Error Occurred(0)"
>
> I googled for this error message and found only one other person that
> reported this error and his screen snapshot is nearly identical to my
> problem.
>
> http://www.hardforum.com/showthread.php?t=1132761
>
> None of the responses that I read in that thread were helpful to me.
>
> Using Western Digital diagnostic tools, I tested each drive and no
> errors in either drive were discovered. Chkdsk also reported no errors.
>
> From the time I first observed this error message some days ago, the
> computer has been working without any apparent problems (boots up and
> runs just fine) but the error message is driving me nuts.
>
> I have two of these disks:
>
> Western Digital Caviar SE16 WD3200KS 320GB 7200 RPM 16MB Cache SATA
>
> RAID 0 with Intel Matrix Storage Manager
>
> Motherboard: ASUS P5B-E (latest BIOS installed).
>
> Intel ICH86/DO/DH SATA RAID Controller:
> Driver date: 5/11/06
> Driver version: 6.0.0.1022
>
> JMicron JMB36X Controller:
> Device type: SCSI and RAID controllers
> Manufacturer: JMicron Technology
> Driver date: 12/5/2006
> Driver version: 1.17.8.1
>
> Device manager reports no errors for either of the above controllers.
>
> XP Professional. All service packs and updates installed.
>
> Intel Core 2 Duo E6600 Conroe 2.4GHz 4M shared L2 Cache LGA 775 Processor
>
>
> Does anyone have any suggestions on how I can resolve this error message?
>
>
>
>




Reply With Quote
  #4 (permalink)  
Old 01-07-2007, 05:40 PM
John
Guest
 
Posts: n/a
Default Re: "Error Occurred(0)" with RAID 0. What does it mean?

HDRDTD wrote:
> It 'might' be that one of the drives has developed a SMART error.
>


[snip]

>
> My point is, One of the drives may have developed a SMART error, but because
> they are in a RAID 0 array, nothing can report the SMART error in detail,
> and you may not see the actual error until the RAID array is broken into two
> ordinary drives.
>
>


I went into BIOS and deselected the RAID option so that I had two
separate drives. The computer, of course, couldn't boot but I was able
to run the WD diagnostics from a bootable floppy for each separate HD.
No problems were detected. I used DLGIDIAG5.EXE

01/06/2007, 11:09:33
SELECTED OPTION - "QUICK TEST"
SELECTED DRIVE -
Model : WDC WD3200KS-00PFB0
S/N : WD-WCAPD2868494
Firmware : 21.00M21
C H S : 620181 16 63
Capacity : 320G
Drive : 0 Port: 0xEC00
RESULTS - "NO ERRORS FOUND"
ERROR/STATUS CODE = 0000


01/06/2007, 11:11:40
SELECTED OPTION - "SMART STATUS"
SELECTED DRIVE -
Model : WDC WD3200KS-00PFB0
S/N : WD-WCAPD2437481
Firmware : 21.00M21
C H S : 620181 16 63
Capacity : 320G
Drive : 0 Port: 0xE800
RESULTS - "NO ERRORS FOUND"
ERROR/STATUS CODE = 0000

Reply With Quote
  #5 (permalink)  
Old 01-07-2007, 06:07 PM
Arno Wagner
Guest
 
Posts: n/a
Default Re: "Error Occurred(0)" with RAID 0. What does it mean?

In comp.sys.ibm.pc.hardware.storage John <John@nospam.net> wrote:
> During boot up, one of my two week old hard disks in my RAID 0 is now
> reporting this error:


> "Error Occurred(0)"


> I googled for this error message and found only one other person that
> reported this error and his screen snapshot is nearly identical to my
> problem.


> http://www.hardforum.com/showthread.php?t=1132761


> None of the responses that I read in that thread were helpful to me.


> Using Western Digital diagnostic tools, I tested each drive and no
> errors in either drive were discovered. Chkdsk also reported no errors.


> From the time I first observed this error message some days ago, the
> computer has been working without any apparent problems (boots up and
> runs just fine) but the error message is driving me nuts.


> I have two of these disks:


> Western Digital Caviar SE16 WD3200KS 320GB 7200 RPM 16MB Cache SATA


> RAID 0 with Intel Matrix Storage Manager


> Motherboard: ASUS P5B-E (latest BIOS installed).


> Intel ICH86/DO/DH SATA RAID Controller:
> Driver date: 5/11/06
> Driver version: 6.0.0.1022


> JMicron JMB36X Controller:
> Device type: SCSI and RAID controllers
> Manufacturer: JMicron Technology
> Driver date: 12/5/2006
> Driver version: 1.17.8.1


> Device manager reports no errors for either of the above controllers.


> XP Professional. All service packs and updates installed.


> Intel Core 2 Duo E6600 Conroe 2.4GHz 4M shared L2 Cache LGA 775 Processor



> Does anyone have any suggestions on how I can resolve this error message?



Ok, it seems to be something transitional. It may be a drive in the
process of dying (so a SMART check to find that out) or an interface
problem. Maybe one of the (S)ATA connectors does not sit quite right?

Side note: I would not depend on a controller that gives this
type of obscure and entirely unhelpful error messages. Hints
at an overal unclean design....

Arno


Reply With Quote
  #6 (permalink)  
Old 01-07-2007, 06:38 PM
Michael Daly
Guest
 
Posts: n/a
Default Re: "Error Occurred(0)" with RAID 0. What does it mean?

John wrote:

> Intel ICH86/DO/DH SATA RAID Controller:
> Driver date: 5/11/06
> Driver version: 6.0.0.1022
>
> JMicron JMB36X Controller:
> Device type: SCSI and RAID controllers
> Manufacturer: JMicron Technology
> Driver date: 12/5/2006
> Driver version: 1.17.8.1


You might narrow it down if you knew which of these two controllers the drives
were connected to. Is it possible to switch between these two or is the
existing RAID setup exclusive to one of them?

Mike

Reply With Quote
  #7 (permalink)  
Old 01-07-2007, 08:57 PM
John
Guest
 
Posts: n/a
Default Re: "Error Occurred(0)" with RAID 0. What does it mean?

Michael Daly wrote:
> John wrote:
>
>> Intel ICH86/DO/DH SATA RAID Controller:
>> Driver date: 5/11/06
>> Driver version: 6.0.0.1022
>>
>> JMicron JMB36X Controller:
>> Device type: SCSI and RAID controllers
>> Manufacturer: JMicron Technology
>> Driver date: 12/5/2006
>> Driver version: 1.17.8.1

>
> You might narrow it down if you knew which of these two controllers the
> drives were connected to. Is it possible to switch between these two
> or is the existing RAID setup exclusive to one of them?
>
> Mike


That's an excellent question.

I wonder what the consequences will be by disabling a RAID controller?
Will the operating system start? I do have a full OS partition backup,
but still....

Reply With Quote
  #8 (permalink)  
Old 01-07-2007, 09:43 PM
Michael Daly
Guest
 
Posts: n/a
Default Re: "Error Occurred(0)" with RAID 0. What does it mean?

John wrote:

> I wonder what the consequences will be by disabling a RAID controller?


Since it's a RAID0 config, your drives will look like gibberish to the OS if you
turn off RAID. Disabling one controller in BIOS will result in a boot error if
you disable the one with the disks attached (no drives found or some such
error). You'll always be able to boot to BIOS to reset.

If you have the motherboard manual (you can usually find one online at the
manufacturer's website) you can determine which sockets are for which
controller. Then just look at which one the cables are plugged into.

Mike

Reply With Quote
  #9 (permalink)  
Old 01-07-2007, 10:18 PM
John
Guest
 
Posts: n/a
Default Re: "Error Occurred(0)" with RAID 0. What does it mean?

Michael Daly wrote:
> John wrote:
>
>> I wonder what the consequences will be by disabling a RAID controller?

>
> Since it's a RAID0 config, your drives will look like gibberish to the
> OS if you turn off RAID. Disabling one controller in BIOS will result
> in a boot error if you disable the one with the disks attached (no
> drives found or some such error). You'll always be able to boot to BIOS
> to reset.


I found that out the hard way. I had accidentally set the BIOS settings
to default and I "lost" my drives. Once I reset the BIOS settings I was
good to go.

What I had meant was what would happen if I had go into 'Computer
management console'->'Device Manager'->'SCSI and RAID controllers' and
disabled one of the controllers then restarted the computer?

I'm a little squeamish about doing this at this point until my large
hard disk arrives so that I can first backup the entire hard disk.

>
> If you have the motherboard manual (you can usually find one online at
> the manufacturer's website) you can determine which sockets are for
> which controller. Then just look at which one the cables are plugged into.


I have the manual but I'm not sure what you mean. I plug the cable into
the left-most socket for drive 0 and I plug in drive 1 to the socket to
the right. Like so: http://i10.tinypic.com/2qvgtpt.jpg
> Mike


To answer someone else's question: Yes, I replaced the cable on drive 0.

Reply With Quote
  #10 (permalink)  
Old 01-07-2007, 11:01 PM
Michael Daly
Guest
 
Posts: n/a
Default Re: "Error Occurred(0)" with RAID 0. What does it mean?

John wrote:

> I have the manual but I'm not sure what you mean. I plug the cable into
> the left-most socket for drive 0 and I plug in drive 1 to the socket to
> the right. Like so: http://i10.tinypic.com/2qvgtpt.jpg


There are four SATA sockets there and you are using two of them. There should
be some other sockets someplace else. One set is controlled by the Intel
chipset and the other by the second controller. I'm guessing the four we see in
the picture are for the Intel chipset and the others are elsewhere - possible
for eSATA and are exposed outside the box. If this is the case, the Intel RAID
controller is kicking out the error message.

Mike

Reply With Quote
  #11 (permalink)  
Old 01-08-2007, 03:59 PM
John
Guest
 
Posts: n/a
Default Re: "Error Occurred(0)" with RAID 0. Dying disk.

I installed 'Intel Matrix Storage Console' version 6.2.

It's stating 'Error Occurred' on 'Device Port 0'

'A drive in a RAID 0 volume is failing. Try to back up data immediately.'

The '(0)' (I believe) refers to the device number and is not an error
code. This is what threw me off.

I backed everything up and I'll clone the dying drive to an identical
replacement.

I ran the Western Digital diagnostics again and it says that everything
is peachy.

Reply With Quote
  #12 (permalink)  
Old 01-08-2007, 04:22 PM
Arno Wagner
Guest
 
Posts: n/a
Default Re: "Error Occurred(0)" with RAID 0. Dying disk.

In comp.sys.ibm.pc.hardware.storage John <John@nospam.net> wrote:
> I installed 'Intel Matrix Storage Console' version 6.2.


> It's stating 'Error Occurred' on 'Device Port 0'


> 'A drive in a RAID 0 volume is failing. Try to back up data immediately.'


> The '(0)' (I believe) refers to the device number and is not an error
> code. This is what threw me off.


> I backed everything up and I'll clone the dying drive to an identical
> replacement.


> I ran the Western Digital diagnostics again and it says that everything
> is peachy.


After you have backed up, maybe connect the drive directly and
post its SMART attributes here. Maybe we can spot some problem.
I don't know the WD usilities, but for Maxtor both the disks and
the diag-software are over-optimistic in their thresholds. The
attributes themselves tell the true story, however.

Arno

Reply With Quote
  #13 (permalink)  
Old 02-17-2008, 12:56 PM
Junior Member
 
Join Date: Feb 2008
Posts: 1
Default

I have figured out how to resolve this issue:

First you should check your hard drives (run a diagnostic utility) to make sure in fact there is no problem (not required). This utility was built into the BIOS of my machine which was from 2004, so you should probably have the same. Anyway:

I installed the Intel Matrix Storage Manager which IS compatible with my hardware (even though my hardware was very old - from 2004). Then follow these steps to resolve the issue: Launch the Intel Matrix Storage Console software that you now have from the installation and open up the tree view to examine my drives. In here the drives show the reported error as well. Right-click on each drive and select the popup menu option "Mark as Normal". Upon the next reboot the problem has gone away - and has not come back since.
Reply With Quote
  #14 (permalink)  
Old 03-18-2010, 02:01 AM
Junior Member
 
Join Date: Mar 2010
Posts: 1
Default

I had the same issue. This fixed the issue for me. Western Digital tools just told me I had an error but the tools did not find any issues when set to IDE and tested.

This took the bit flip error setting of the drive and reset it to off.

Thanks

Quote:
Originally Posted by KruseLudington View Post
I have figured out how to resolve this issue:

First you should check your hard drives (run a diagnostic utility) to make sure in fact there is no problem (not required). This utility was built into the BIOS of my machine which was from 2004, so you should probably have the same. Anyway:

I installed the Intel Matrix Storage Manager which IS compatible with my hardware (even though my hardware was very old - from 2004). Then follow these steps to resolve the issue: Launch the Intel Matrix Storage Console software that you now have from the installation and open up the tree view to examine my drives. In here the drives show the reported error as well. Right-click on each drive and select the popup menu option "Mark as Normal". Upon the next reboot the problem has gone away - and has not come back since.

Reply With Quote
  #15 (permalink)  
Old 09-01-2010, 10:50 PM
Junior Member
 
Join Date: Sep 2010
Posts: 1
Default

Quote:
Originally Posted by KruseLudington View Post
I have figured out how to resolve this issue:

First you should check your hard drives (run a diagnostic utility) to make sure in fact there is no problem (not required). This utility was built into the BIOS of my machine which was from 2004, so you should probably have the same. Anyway:

I installed the Intel Matrix Storage Manager which IS compatible with my hardware (even though my hardware was very old - from 2004). Then follow these steps to resolve the issue: Launch the Intel Matrix Storage Console software that you now have from the installation and open up the tree view to examine my drives. In here the drives show the reported error as well. Right-click on each drive and select the popup menu option "Mark as Normal". Upon the next reboot the problem has gone away - and has not come back since.
I didnt like the look of this error when i first saw it but doing this seems to have fixed the problem completely thanks alot
Reply With Quote
  #16 (permalink)  
Old 11-02-2011, 11:34 AM
Junior Member
 
Join Date: Nov 2011
Posts: 1
Default On Target Thread

Quote:
Originally Posted by KruseLudington View Post
I have figured out how to resolve this issue:

First you should check your hard drives (run a diagnostic utility) to make sure in fact there is no problem (not required). This utility was built into the BIOS of my machine which was from 2004, so you should probably have the same. Anyway:

I installed the Intel Matrix Storage Manager which IS compatible with my hardware (even though my hardware was very old - from 2004). Then follow these steps to resolve the issue: Launch the Intel Matrix Storage Console software that you now have from the installation and open up the tree view to examine my drives. In here the drives show the reported error as well. Right-click on each drive and select the popup menu option "Mark as Normal". Upon the next reboot the problem has gone away - and has not come back since.
KruseLudington kept this thread alive and posted a fast, easy to understand solution in this final paragraph. He helped me solve a nagging problem (that really wasn't a problem) on a PC build for someone else, i.e., the boot screen kept flagging that HDD "error" that happened one time and just needed to be cleared. Thanks posters, and thanks Google Search for meaningful hits.
Reply With Quote
  #17 (permalink)  
Old 05-26-2012, 04:26 PM
Junior Member
 
Join Date: May 2012
Posts: 1
Default 3 of 4 HDDs failed in RAID10

Hi
I believe it is highly unlikely that 3 of 4 HDDs in a RAID 10 System fail at the same time! may be one of you can help.
I have an ASUS 6PTSE Motherboard with 4 1TByte HDDs in a single RAID10 with W7 64 Ultimate. The system has been working with no problems reported at all, until suddenly I had a blue screen. Restarting the System no OS was found and the RAID system reported 3 of the 4 HDDs to have failed at the same time! The OS was on that single partition 4 TByte HDD RAID 10! No special weather, so no external reason for the HW to fail.

I did first verify that all connections, SATA and power supply to the HDDS were OK. Than I replaced the power supply, a 800W XIGMATEK MRP MC802, with an identical one in my daughters PC. Both PC showed no change: Mine showed the same BIOS error message, hers did work perfectly as before with my power supply.

What else can I do? The programs and data on the RAID are mission critical and I need my RAID up and working again. I must say that setting up a second PC to backup an image of a 4TByte HDD seemed a bit overkill backup strategy! may be I was wrong! But I could not believe that more than ob HDD would fail at the same time, now 3 failed!
Reply With Quote
  #18 (permalink)  
Old 08-18-2013, 03:32 AM
Junior Member
 
Join Date: Aug 2013
Posts: 2
Default

I want to thank everyone for this post. It helped me resolve the error message which I've been wondering about for a while. KruseLudington's post (below) led me to download a newer version for my OS (Win7) Intel Rapid Storage Technology 12.8.0.1016 (Intel® Rapid Storage Technology (Intel® RST) RAID Driver) from downloadcenter dot intel dot com.

After installing this and rebooting, I just went in and marked the volumes as normal.

I have had on of my drives with this error message for well over a year. Obviously the error is erroneous because the drive has been functioning with no problems at all. Recently I did get some chkdsk errors on my RAID 0 array which caused the second drive to also display the Error Occurred (0) message. I fixed the errors, but the message didn't go away.

Indeed the 0 is the SATA device number which doesn't provide any good information unless you have multiple arrays. The error (in the Intel application) turned out to be a read error. As far as I can figure out, an error reading data from any disk in the array one time at boot seems to cause this error message, and the message persists even after the problem is resolved. The solution is simply to fix the problem with a disk utility (I used chkdsk /F) then mark the volume as Normal in the Intel application (as suggested below).

Thanks!

Quote:
Originally Posted by KruseLudington View Post
I have figured out how to resolve this issue:

First you should check your hard drives (run a diagnostic utility) to make sure in fact there is no problem (not required). This utility was built into the BIOS of my machine which was from 2004, so you should probably have the same. Anyway:

I installed the Intel Matrix Storage Manager which IS compatible with my hardware (even though my hardware was very old - from 2004). Then follow these steps to resolve the issue: Launch the Intel Matrix Storage Console software that you now have from the installation and open up the tree view to examine my drives. In here the drives show the reported error as well. Right-click on each drive and select the popup menu option "Mark as Normal". Upon the next reboot the problem has gone away - and has not come back since.

Reply With Quote
Reply


« Epson scanner front buttons | DNS Resolution »
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Increase partition size on RAID mirrored disk volume woods.81@googlemail.com alt.comp.hardware 5 01-19-2007 11:05 AM
Trying to change SATA disk to RAID mirrored disks woods.81@googlemail.com alt.comp.hardware 4 12-27-2006 04:00 AM
RAID Settings Chris Rennert alt.comp.hardware 1 10-22-2005 06:14 PM
HELP: FAILED RAID 0 winux alt.comp.hardware 2 09-09-2005 04:32 PM
Re: Does WinME support RAID? Mike Walsh alt.comp.hardware 1 07-27-2005 04:58 PM


All times are GMT. The time now is 11:15 PM.



Powered by vBulletin® Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.6.0 PL2

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45