UNSOLVED

bluemonday

updated

20 years ago

0

36946

February 6th, 2007 22:00

RAID volume errors on a new 9200 with Vista

I have a one-day old Dimension 9200 with Vista Home Premium on it.

When transferring over some of my photos, the transfer virtually stopped and a corrupt data (or something, I can't remember) error message appeared. Now when I reboot, the text screens say 'Error occurred' in red for the drive on Port 0 (the drive on Port 1 says 'Member' in green).

A balloon also appears when the desktop has loaded saying: RAID volume errors Some data requests to RAID volume 0 failed...etc

I have found some references to this in the forums, but would like to know:

1) Does this mean my hard/drives is broken/corrupt forever? If so, I will obviously get back in touch with Dell to sort a replacement.

2) If not, could a drive reformat and clean re-install of Vista cure it?

My computer seems to be running ok apart from this error message, but I'd rather get it sorted now than leave it. I have got all my data backed up so am not worried about losing that.
  • shesagordie

    12 Elder

    •

    46017 Posts

    404

    0

    Posted February 6th, 2007 22:00

    bluemonday  
     
    As this is a one day old system, you should contact Dell ASAP about this. 
     
    Have you tried running Dell diagnostic's extended [not the express], read, write, verify test on the hard drives.
     
    Bev.
     
     
     
     
    ===================================================
    Please don't send me questions about your system by DCF Messenger.
    Post the issue in the appropriate Board, where they will be answered.
  • 404

    0

    Posted February 8th, 2007 22:00

    thanks Bev.

    Dell called me back this morning and took control of my PC to fix this. If anyone else has this same problem then from what I remember, some of the steps that the guy did to fix it were to click the Start button (although obviously this isn't labelled 'Start' in Vista), click All Programs, then Intel Matrix Storage Manager. When this menu opens up, right-click the Intel Matrix Storage Console and select Run as Administrator.

    I missed what he did at this point, but it was a very quick fix and only involved a couple of clicks.

    Sorry if this is only partially useful but someone with more technical knowledge may be able to suggest what the exact fix was should anyone else need it.

    What it did prove was that this error was not an actual hardware one and is fixable without sending your PC back.
  • shesagordie

    12 Elder

    •

    46017 Posts

    404

    0

    Posted February 8th, 2007 22:00

    bluemonday
     
    Pleased to hear that problem is resolved and appreciate the feedback.   :)
     
    Bev.
     
     
     
     
    ===================================================
    Please don't send me questions about your system by DCF Messenger.
    Post the issue in the appropriate Board, where they will be answered.
  • thetrikster

    37 Posts

    404

    0

    Posted February 13th, 2007 14:00

    I think I have the same problem with my day-old system as well! I suspect that you have your drives set up as a RAID-1 array and that all the Dell tech support person did was to re-sync the drives (ie. to copy the data back from the drive-1 to drive-0).

    I'd be interested to hear how your system is working now as I've had the same experience and I'm still having problems. If you look in the Windows event log then you may see messages about timeouts to the iaStor0 device - which is the disk array. Too many of those and the disk is marked as failed.

    I ran the extensive tests on the allegedly failed disk and they reported everything is OK. Browsing the internet I get the impression that the fault may be with Intel's Matrix RAID drivers (although it could of course be a fault that the diagnostics don't find).

    Anyway, how does it look for you now?
  • 404

    0

    Posted February 13th, 2007 16:00

    My system is working fine now without any problems. During booting, both Ports appear with a green 'Member' next to them as opposed to one of them having a red 'Error occurred'.

    I don't know how quick re-syncing the drives is, but the fix that the Dell support person did literally only took a matter of seconds (just time for me to look away from the screen and then back).

    Good luck fixing your PC, I hope you manage to resolve the problem.
  • thetrikster

    37 Posts

    406

    0

    Posted February 13th, 2007 17:00

    Well, strictly speaking, syncing the disk takes ages. However, that happens in the background and just starting that takes no time at all. If you get the chance I'd be grateful if you could look in your System log and see if you have any timeout errors from the RAID controller. They'll stand out as they have a red icon against them.

    Regards
  • 406

    0

    Posted February 13th, 2007 20:00

    No problem, I can do...please can you tell me how I do this?
  • thetrikster

    37 Posts

    406

    0

    Posted February 13th, 2007 21:00

    Hmm. I'm away from home at the moment so don't have a Vista system to look at :-(

    From memory though, firstly you need to run the event viewer, "eventvwr.exe"
    Then open the "Windows Logs" list and then select "System".
    The middle view should now show the system events that have been logged.

    Have a look in there for errors. If you click on an event then the bottom pane shows the details. On my system I'm seeing intermittent errors from the raid controller, iaStor0 that really shouldn't be there.

    Regards
  • Wyntha

    56 Posts

    406

    0

    Posted February 14th, 2007 15:00

    I also have a new 9200 with Vista Premium installed. It system is running Raid-0 configuration. I have same problems as 2 of you have reported. Have also reset the error flag on drive 0 using the supplied Intel Utility. Have run Scan on all disk sectors plus Dell diagnostic utilities and nothing found. However there is more to tell:-
     
    I have looked into system event log and also seen many iestor.exe errors on disk-0. In addition I've seen NFTS file system errors being reported and files being read and reported as corrupt due to checksum errors. NFTS errors resulted in a scheduling of Chkdsk on startup of PC and when it happens it finds errors which it corrects.
     
    Vista has also played up and it could be as a result of above. For example some programs fail to startup or complete properly (WIndows Calendar, Windows Media Player) and WMP 11 library has got corrupted 3 times and I've had to rebuild from scratch.
     
    Dell Support not helpful so we who have problems with these new machines need to keep close and see how we put pressure on Dell to accept that an error exists and to do something for us.
     
    Let's keep this thread active.
     
     
  • 333

    0

    Posted February 16th, 2007 08:00

    OK, I went through the error log and all the iaStor errors seem to have been logged prior to when my PC was fixed (8 Feb). The errors I had were:

    The device, \Device\Ide\iaStor0, did not respond within the timeout period.
    ------------------
    A parity error was detected on \Device\Ide\iaStor0.
    ------------------
    The description for Event ID 9 from source iaStor cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the event.

    The following information was included with the event:

    21:39:44
    07/02/2007
    371

    The specified resource type cannot be found in the image file
    ------------------
    The description for Event ID 55 from source Ntfs cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the event.

    The following information was included with the event:

    upnphost
    {204810B9-73B2-11D4-BF42-00B0D0118B56}

    the message resource is present but the message is not found in the string/message table