• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Had to happen on a Friday :)

child of wonder

child of wonder

Diamond Member
We have a backup server here that is a failover for one of our primary application servers. The other day when it was rebooted after installing some Windows updates it reported an imminent failure on one of the OS disks.

"No big deal," I thought. "The application vendor set up this server and the two OS drives are in RAID 1. I'll power down, remove the failing drive, insert the new drive, power on, and the RAID array will sync up."

Anyway, after I replaced the drive it booted into Windows 2003 OK. I go into Disk Management and lo and behold it turns out... no... they did NOT set up RAID. My mistake for trusting they had set the server up properly.

The original OS drive is sitting there as a basic disk. I was expecting they had used the onboard RAID controller to mirror the OS drives or using dynamic disks. They had done neither.

So I decided to convert the existing disk and the new disk into dynamic disks, reboot the server, then add the new drive as a mirror of the original.

Sounds like a great plan until the server reboots into a BSOD with a Stop 0x0000007B error.

Looks like converting the disk to dynamic hosed it somehow and now it won't boot at all.

Anyone have any ideas on how to get this stupid drive to boot up? Worst case scenario we can send the server to the application vendor and they'll stage it again for us (this time using RAID 1) and no data will be lost since it's just a failover server.

However, I'd really rather fix this than admit defeat. 😱
 
No one has any ideas? I've tried chkdsk /r from a recovery console and a repair install. Same BSOD and error.

Only thing that manages to do anything different is a boot from last known good config which gives me a 0x0000006F error instead of 0x0000007B however they both have to do with an unsuccessful conversion from basic to dynamic disk.
 
As far as I've been taught, the only thing you can do is data recovery... there's no "undo" when converting disk types like that.
 
Partition Commander can repair your master boot record (seems like that's what is broken). It can also reconvert your partition.
 
Originally posted by: child of wonder
We have a backup server here that is a failover for one of our primary application servers. The other day when it was rebooted after installing some Windows updates it reported an imminent failure on one of the OS disks.

"No big deal," I thought. "The application vendor set up this server and the two OS drives are in RAID 1. I'll power down, remove the failing drive, insert the new drive, power on, and the RAID array will sync up."

Anyway, after I replaced the drive it booted into Windows 2003 OK. I go into Disk Management and lo and behold it turns out... no... they did NOT set up RAID. My mistake for trusting they had set the server up properly.

The original OS drive is sitting there as a basic disk. I was expecting they had used the onboard RAID controller to mirror the OS drives or using dynamic disks. They had done neither.

So I decided to convert the existing disk and the new disk into dynamic disks, reboot the server, then add the new drive as a mirror of the original.

Sounds like a great plan until the server reboots into a BSOD with a Stop 0x0000007B error.

Looks like converting the disk to dynamic hosed it somehow and now it won't boot at all.

Anyone have any ideas on how to get this stupid drive to boot up? Worst case scenario we can send the server to the application vendor and they'll stage it again for us (this time using RAID 1) and no data will be lost since it's just a failover server.

However, I'd really rather fix this than admit defeat. 😱
Click to expand...

Call Microsoft and they (the Setup group) can walk you through converting the disk back to Basic. If that's all you did, and that's the culprit for the no-boot (and with Stop 7B that's plausible) then that will fix you up.
 
I don't need to convert the disk back to basic, just get it to boot as dynamic. The disk will actually get to the windows splash screen but will only make it about one bar length across before it BSODs.
 
Well, if that's the one thing you changed, I'd look into undoing that first. You might also run CHKDSK on the volume (boot to recovery console) and see if that helps too. Stop7Bs are disk issues, so those two are likely candidates for the fix.
 
I tried a chkdsk /r but that didn't help. The only thing that made any difference was starting to Last Known Good Config and then I got a 6F stop instead.
 
If that's the case I'd take the disk setup to another machine, examine the disk, and change the disk from dynamic to basic and see if I could then boot. MS can talk you thru the process.
 
For anyone interested, this is how I fixed this problem.

I had to install a parallel install on Windows Server on it, load the original install's registry, and delete the Primary Disk Groups from each Controlset00x - Services - dmio - boot section of the registry. Then the disk would boot again.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top