Win2K Crash Raid 5, Long Post

[Guest]

Hi Everyone,
If you can help, please read through the whole post and then give me your answers

I've tried everything and still getting the STOP: 0x0000007B INACCESSIBLE BOOT DEVIC

And by everything I mean the following

1. PowerEdge Server, configured with Raid5 4x18Gb SCSI drives
One of these failed and Win2K reported in the Event Viewer to place the drive offline, change and restart
So, I've placed the drive offline, sure enough the server started beeping
The only drive I had available was a 36 G drive, which somehow, I managed to place in the server
Through the Perc Bios, I've rebuild the Raid5 array and all drives were back to online status, and the container
shows it's status as being Optimal. So far so good for a total of 50+gig, same as before..

2. I've restarted the server thinking, hey that's a great start to my Valentine's day weekend, but no..
STOP: 0x0000007B INACCESSIBLE BOOT DEVIC

3. Time to bring out the recovery dis
STOP: 0x0000007B INACCESSIBLE BOOT DEVIC

4. Time to go into the recovery consol
Now I've had access to the C: drive, chkdsk-ed it with /p and /r and reported that found some errors and fixed them
Restarted and STOP: 0x0000007B INACCESSIBLE BOOT DEVIC

5. Went back to the recovery console and chkdsk-ed all partitions 5 in total, some reported some errors that were fixed
Restarted and STOP: 0x0000007B INACCESSIBLE BOOT DEVIC

6. Again in the recovery console, tried the fixboot comman
STOP: 0x0000007B INACCESSIBLE BOOT DEVIC

7. Last resort. in the recovery console tried the fixmbr, sure I'm sure..
STOP: 0x0000007B INACCESSIBLE BOOT DEVIC

So, the only thing I can do at the moment, is see the data under the recovery console.
I'd like to have access to this data from the network somehow. I have about 90% backed up and I'd lik
to get my hands on the rest

If you know of a way to bypass this STOP: 0x0000007B INACCESSIBLE BOOT DEVICE, I'd love to hear from you
What are my options

If you know of a way to get to this data from the network, that would be great as well
Thanx for reading this post

 

[MyndPhlyp]

Hi Everyone,
If you can help, please read through the whole post and then give me your answers.

I've tried everything and still getting the STOP: 0x0000007B INACCESSIBLE BOOT DEVICE

And by everything I mean the following:

1. PowerEdge Server, configured with Raid5 4x18Gb SCSI drives.
One of these failed and Win2K reported in the Event Viewer to place the

drive offline, change and restart.

So, I've placed the drive offline, sure enough the server started beeping.
The only drive I had available was a 36 G drive, which somehow, I managed to place in the server.
Through the Perc Bios, I've rebuild the Raid5 array and all drives were

back to online status, and the container

shows it's status as being Optimal. So far so good for a total of 50+gig, same as before...

2. I've restarted the server thinking, hey that's a great start to my

Valentine's day weekend, but no...

STOP: 0x0000007B INACCESSIBLE BOOT DEVICE

<...snip...>

I did a quick search on Google and briefly scanned several hits. Most of
them talk about IDE drives. Some include other "mass storage devices" or
mention RAID. The one chant they all seem to have in common is missing or
corrupted drivers and/or resource conflicts and/or a boot sector virus.

You might be looking at a reinstall of Win2K Server atop your existing
install just to reinstall the PERC drivers.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;122926

 

[Leonard Severt [MSFT]]

Hi Everyone,
If you can help, please read through the whole post and then give me
your answers.

I've tried everything and still getting the STOP: 0x0000007B
INACCESSIBLE BOOT DEVICE

And by everything I mean the following:

1. PowerEdge Server, configured with Raid5 4x18Gb SCSI drives.
One of these failed and Win2K reported in the Event Viewer to place
the drive offline, change and restart. So, I've placed the drive
offline, sure enough the server started beeping. The only drive I had
available was a 36 G drive, which somehow, I managed to place in the
server. Through the Perc Bios, I've rebuild the Raid5 array and all
drives were back to online status, and the container shows it's status
as being Optimal. So far so good for a total of 50+gig, same as
before...

2. I've restarted the server thinking, hey that's a great start to my
Valentine's day weekend, but no... STOP: 0x0000007B INACCESSIBLE BOOT
DEVICE

3. Time to bring out the recovery disk
STOP: 0x0000007B INACCESSIBLE BOOT DEVICE

4. Time to go into the recovery console
Now I've had access to the C: drive, chkdsk-ed it with /p and /r and
reported that found some errors and fixed them. Restarted and STOP:
0x0000007B INACCESSIBLE BOOT DEVICE

5. Went back to the recovery console and chkdsk-ed all partitions 5 in
total, some reported some errors that were fixed. Restarted and STOP:
0x0000007B INACCESSIBLE BOOT DEVICE

6. Again in the recovery console, tried the fixboot command
STOP: 0x0000007B INACCESSIBLE BOOT DEVICE

7. Last resort. in the recovery console tried the fixmbr, sure I'm
sure... STOP: 0x0000007B INACCESSIBLE BOOT DEVICE

So, the only thing I can do at the moment, is see the data under the
recovery console. I'd like to have access to this data from the
network somehow. I have about 90% backed up and I'd like to get my
hands on the rest.

If you know of a way to bypass this STOP: 0x0000007B INACCESSIBLE BOOT
DEVICE, I'd love to hear from you. What are my options?

If you know of a way to get to this data from the network, that would
be great as well. Thanx for reading this post.

This appears to be a file system / hardware problem. About the only
thing you can do to get to the data is put in another hard drive, make
it your boot drive and install Windows to it. You will then be able to
copy of data. Then you will need to rebuild your RAID.

Leonard Severt

Windows 2000 Server Setup Team.