Raid 5 single disk failure, bad boot

Jlapointe

Actually chkdsk does not cause damage but after it does it thing it may look like it does by creating files from cross links etc. Anything chkdsk fixes  is already in trouble. Another issue of running it now is it could take a long time to complete. I would avoid for the present.

Run fixboot first, see what happens. If it still has problems booting, do an "over the top" repair. If the OS is repairable, this type of repair install does no damage 99.9% of the time. If it does not work, it not because of the repair install, but you have bigger issues with partition or the file structure.

Although I have used CHKDSK /R for many recoveries (some more serious, some less), I also know that pcmeiners knows his stuff, so trust his recommendation.

In 2003, just FIXBOOT is sufficient (2008 and later require the BOOTREC be pre-appended) :)

Sorry should have wrote chkdsk /r and fixboot.

I was looking around and the D partition looks complete.

Will avoid chkdsk /r and try as you suggested.

Fixboot is not part of the chkdsk command...

If you have major damage to the OS or the array structure, I would avoid chkdsk /r. 

Try this first

bootrec.exe /fixboot

With 2003 you can do a "over the top "  repair install, I suggest you do this.  Google     over the top repair install.

fixboot no change.

over the top, offered to remove files 'bcraid.sys' & 'bccfg.sys', I selected to leave them. After reboot presented with gui screen (install windows, finalize install) and its prompting if "matrox display driver settings" should be overwritten. Should I replace or leave as is?

Thanks

Some of the files are open, which are not allowed by the system  to be backed up.

Run chkdsk /r

I would download CCleaner (free version), run the "registry" cleanup and the "cleaner"

Shutdown, restart, run chkdsk again.

Down load and run "Malwarebytes" ( free version), run it

Get up to date on MSupdates

Check for new drivers from the Dell site

"Please note that on this series of controllers I have seen this issue many times and attempts at repairing the OS are mostly in vain."

Like Flash I too have had multiple issues with low end controllers, I replaced more then one rather then deal with issues which should not occur.

chkdsk /r displays volume creation date and serial number, hard disk light was constant now slow blinking, is it working or hanging?

Please disregard my previous post.

chkdsk /r in RE gives me  'There is no disk in the drive or the file system is not supported"

Still boots normally, and everything seems normal, web server operating as it should etc.

So hopefully one of my last questions relates to the point in your post. In your opinion...

*Should I try updates, (Explorer 8) run OMSA to attempt and rebuild array with refurb drive?

*Install a brand new drive to system, boot from there, try and restore the backup with many skipped files and bad system backup and run with that? I really am trying to avoid reconfiguring database, IIS etc. If I had a clean backup, I would be all for this.

*Should I install 3 or 4 new drives to raid can and rebuild using new drives (Enterprise?)

Time is really an issue right now.

Thanks again

chkdsk can take time to complete, be patient. 

I am out in field until 6 pm.