hp server raid 1 drive failed

we have a single hp server running sbs2008 which has 2 x seagate 500gb drives configured in a raid 1.

I have removed the defective drive now, but the server still won't boot.

it gets to the Windows progress bar than fails to a blue screen stating :-

a problem has been detected and Windows has been shut down.....,,

STOP: 0x00000024 (0x00000000009044, 0xFFFFFA8007184C70, 0xFFFFFFFFC0000102, 0x00000000000000)

can anyone advise whether it is possible to get this server into a bootable condition whilst we are waiting for the replacement drive to arrive?

many thanks
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Raheman M. AbdulSenior Infrastructure Support Analyst & Systems DeveloperCommented:
Have you tried to boot into last known good configuration?
tried in safe mode?
Then run chkdsk /r
nigelbeatsonMDAuthor Commented:
yes tried both of those options
nigelbeatsonMDAuthor Commented:
I seem to recall from years ago, that there was only one of the pair of drives that was actually bootable, and if it was that one that failed, you had to make a change to some config somewhere to tell it to use the other one.

I was hoping that things had improved since then, but it may not be that, of course. it happens so infrequently, I thought I would ask the experts.😀
5 Ways Acronis Skyrockets Your Data Protection

Risks to data security are risks to business continuity. Businesses need to know what these risks look like – and where they can turn for help.
Check our newest E-Book and learn how you can differentiate your data protection business with advanced cloud solutions Acronis delivers

KimputerIT ManagerCommented:
That stop code usually calls for a
chkdsk /f
chkdsk /r (depending on how much time you want to spend on it)
nigelbeatsonMDAuthor Commented:
I noticed that the raid 1 was marked as degraded and not marked as bootable.

I marked the raid, although it showed that a member drive was missing, as bootable, and it started up into Windows with a command prompt running wpe init???

I was not expecting this so closed it down.

can anyone throw any light on what this is and why it would invoke this?

many thanks
KimputerIT ManagerCommented:
Windows with a command prompt in WPE environment can happen if a boot loops a few times and Windows decides you need to repair it.
nigelbeatsonMDAuthor Commented:
so you think it's ok for me to let it run and complete? I did not want to somehow reconfigure the whole server.

KimputerIT ManagerCommented:
There's nothing to run and complete. The prompt is probably there waiting for you. In this screen though, you can run the chkdsk /f or /r, so at least the NTFS file system gets repaired.
nigelbeatsonMDAuthor Commented:
the command which runs on startup is doing something, it sat there for a few seconds, but I closed the server down, as I did not want to reconfigure the server. as I said, I did not know what it was doing, but if you think it's ok to start the server and let the " wpe init" process complete, I will do so.

if it then starts up to the desktop I can run the chkdsk as suggested.

please confirm
KimputerIT ManagerCommented:
Usually, if command boxes open during boot up, those are always checks (like file checks etc), it will NEVER be a full re-install or extensive reconfiguration (that needs you to press multiple OK buttons anyway)

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
nigelbeatsonMDAuthor Commented:
it just started to run the wpe init process in the command box, but I did not let it complete.

if you are confident it is ok to let it continue to completion I will restart the server, and let it run.

many thanks
nigelbeatsonMDAuthor Commented:
ok - I have let the command run ie wpe init, it completed, then it ran hpssbem.exe

but this came back :-

the file or directory is corrupted and unreadable.

I would remind you that this was a mirrored pair and we only now have one of the 2 drives installed.

I cannot run chkdsk /f as it reports that :-

cannot lock current drive.
Windows cannot run disk checking on this volume because it is write protected.

any suggestions on where we go from here?

many thanks
You have to run chkdsk when the server is booting. If you try running it from within Windows from an elevated CMD prompt, and you enter chkdsk /f, it should tell you that it can't run now as it needs exclusive access to the disk, whether you want to run it during next boot. Answer this Q with "Y", then reboot and chkdsk should start running.
nigelbeatsonMDAuthor Commented:
hssbem.exe states that :-

the file or directory is corrupt and unreadable

I then just have a command prompt.

if I type chkdsk /f

we get :-

cannot lock the current drive
Windows cannot run disk checking on this volume because it is write protected.

we then just get a command prompt again.

it does not ask if we want to run it at the next reboot??

if we exit the command prompt, the server will reboot, but chkdsk does not run, it just goes back into wme init followed by hpssbem.exe

any ideas

many thanks
nigelbeatsonMDAuthor Commented:
The second drive was had also bad sectors on it, and we ended up sending it out for data recovery.

I am not quite sure how to handle this incident, as we did not get a resolution.

I am quite happy allocating points if it is appropriate, but I think I should just close the incident.

If anyone has any problems with that, please let me know.

Many thanks to all who tried to help.
KimputerIT ManagerCommented:
Yes you can allocate points. Most people here tried to get you to do a chkdsk to check the reliability of that disk. And that is a solution, as experts here can't just drive to your house and take the disk to their high tech data recovery lab. We can only advise you, and that advice led you to send it off to a data recovery center.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.