HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

Proliant 800 Pentium Pro BSOD from controller upgrade

 
Diane Armstrong_2
Occasional Visitor

Proliant 800 Pentium Pro BSOD from controller upgrade

System: Proliant 800 Pentium pro 200
OP Sys: SBS 4.5
My Compaq DLT drive failed to operate after a tape broke and wrapped itself around the head. I sent it to get refurbished and when it was returned it still didn't operate even after the head was replaced. (btw.. the DLT did operate ok on another proliant server) The controller driver was then upgraded due to age and when the server was rebooted got the BSOD. The controller firmware was then flashed but this didn't fix it. No ERD was prepared ahead of time and no recent backup. Old registry was recovered from an old SCSI HD which seems not a bad idea because not many changes happened on the server other then NT Service Pack. When server was rebooted all appeared fine except network settings. But upon clicking on a folder on the C: drive we received a black screen. We had no choice but to hard boot. When the server came back it appeared to have corrupted the E: partition on the same drive. I'm not sure whether to suspect the SCSI controller or the old registry. I understand there is bus numbering which gets put into the registry. Could this have caused corruption on the MBR? I'm leaning away from the SCSI controller because other then the DLT drive not operating correctly there have been no other POST errors or HD corruption or other boot issues. Any suggestions to try to get this machine to boot without BSOD. Any ideas on the e: partition failure?
1 REPLY
Sunil Jerath
Honored Contributor

Re: Proliant 800 Pentium Pro BSOD from controller upgrade

Hello Diane,
In the past a situation like this could be corrected by updating system bios and the firmware of Array controller. In your case I assume you have done all that. Is it possible if you could post the STOP error code please.

Regards,