Raid array problem

[deejayry]

Hi guys.

I've been having a lot of problems with all of my computers lately, but i wont bore you all with the whole story, just the problem that is causing me the most trouble.

one of my computers which i use as a media server has recently developed a problem which appears to be somthing to do with the raid 0 array used to store my media.

with the raid array connected to the raid controller the computer will not boot if i dissable automatic restart on failure i get the following error message:

STOP: 0X00000024 (0X001902FE, 0XF794AB6C, 0XF794A868, 0XF7B638D6)

NTFS.SYS - ADDRESS F7B636DD BASE AT F7B52000, DATESTAMP 48025BE5

I tried to get in to safemode with command prompt so i could perform a chkdsk, but the computer reboots before the command prompt has loaded. So i then decided to try using the recovery console on the XP setup CD, The problem is that there is no driver for my raid array included in the XP setup, and i have no FDD to use with the F6 option.

It was suggested that i try using nlite to create a custom XP cd with the correct drivers already installed, which i have done but it seems that the driver i added does not get loaded by setup before entering the recovery console.

I'd be really grateful if someone could advise on how i might fix this problem, I understand that there is the chance that the data is too severely corrupted to recover, but i'd really like to give it a go, i've got my entire music collection on there and have not backed it up for some time so i'd be gutted if i loose it.

[Guest]

You need to add the driver to nLite as a textmode driver. It should then load during textmode portion of setup.

Edited July 26, 2009 by -X-

[deejayry]

Ok... the txtsetup.oem file was located in a different folder, now i have moved it to the same folder as iteraid.sys the computer recognised the raid array, but before the RC has loaded i get a BSOD displaying the same error as before.

now i've got no idea of what to do, the only thing i can think of is to rebuild the raid array and format the disks again, but i want to be sure i have tried all options before i go and erase all of my media.

anyone got any other suggestions for checking the disk?

[Guest]

First hit on Google.

http://www.geekswhoknow.com/articles/stop-...-error-code.htm

Looks like your disk is corrupt and u need to run chkdsk. It also links to a MS knowledge base article I mean run chkdsk from a floppy

Edited July 26, 2009 by -X-

[Guest]

Something just dawned on me. Running chkdsk from a floppy wont work because your raid drivers aren't loaded.

Disregard my last post. Having a blond day.

[deejayry]

hehe, i did notice that as being an issue with the method shown in that link, but you beat me to pointing it out!!

i've just had a thought, i have the instalation cd's for a distro of redhat linux, what are the chances that i might be able to error check the array using that? only problem i dont have any .nix experience.

any thoughts?

[uid0]

I'd try BartPE - you can add your drivers before building a recovery cd.

Or see if your drivers are in the ubcd4win driverpacks.

Then run chkdsk.

[deejayry]

Thanks uid1. I actually downloaded bartPE last night as recomended by a friend so i'll be giving it a go once i've built the CD.

it doesnt apear that UBCD have the drivers to support my raid card.

[deejayry]

I've just tried using Bart PE, but i still get the same STOP: 0X00000024 error.

Heres what i see on screen before the computer halts.

usual bios/raid driver post details

launching BartPe with status bar

windows xp splash screen

windows desktop background colour blue screen (not BSOD)

black screen

BSOD with STOP: 0X00000024 error.

does this seem normal, i was under the impresson that with bart PE the "STOP: 0X00000024" error would be ignored and i would get access to recovery tools. Is it likeley that i have done somthing wrong when creating the bartPE disk?

*edit*

After a bit more research i discovered that the driverpack includued with UBCD supported my raid array, after loading NTFS4DOS and performing a CHKDSK access to my raid array has been restored, there were a few damaged files, but none of them important... Phew!!

Thanks to all of you who helped!

Edited August 2, 2009 by deejayry