MBR 3 & 1 errors

Toggle sidebar Toggle sidebar
W

Whirlingdervish

Distinguished
Aug 26, 2012
40
1
18,535
Hi all…

Sorry to have to ask you guys all of this… I tried my best to figure it out.

W7 64 bit

My computer froze, and upon reboot I'm getting both of the above errors.

I tried everything I could, and then resorted to the installation disk, and tried all of the recovery options there, which failed.

Not sure to go with it here. I could likely wipe the desk clean and start from scratch, but there's so much stuff on there to reload, it would be a nightmare!

Thoughts? I know I'm not giving you much to go on… :)
 
Solution
stdragon
Yeah, sounds like a failed drive with excessive corruption. Have you attempted to move the drive to another computer just to see if you can mount the volume that way? Worth a shot.

Acronis is a good program for backups and BMR (Bare Metal Recovery). Though I've been using the free edition of Veeam. I've actually cloned drives with it before via backup and restore. So I know it works well. You can also recover individual files if you want. Oh, and what's really awesome is that you can target a NAS or other remove SMB share to another location. And yes, you can boot from a Veeam recovery USB flash drive, and restore from files located on on that share. Yes, I've also tested a BRM restoration that way too, it works very well and is super...
Sort by date Sort by votes
W

Whirlingdervish

Distinguished
Aug 26, 2012
40
1
18,535


Hi there, yes I did try to recover windows seven using the first recommendations, and nothing is successful…

- upon the windows 7 installation disc coming up, there is no sign of Windows 7 in the installation field.

- it will not allow me to use System Restore or Recovery, or even check memory for problems, since each of those commands requires the system seeing a copy of Windows 7, which it doesn't apparently see it all.

- start up recovert log shows that there is no valid system partition.

- The command prompt suggestions yielded: MBR 3 showed successful, and MBR 1 failed. No change upon start up. Computer lands on the same error codes and will not boot windows seven.

- Final command prompt failed… chkdsk /f & r says it cannot perform the check because The volume is write protected.

I do have a CD drive back up from my Acronis 2011 from about a month ago. I'm not sure if it's bootable, though. I tried using it last night with no luck, but I may try again.

My fear is that I have a bad drive. I'd rather go through all my options before I try to do a complete rewrite of the operating system. The drive has tons of software on it.

Other thoughts?

 
Upvote 0 Downvote
stdragon

stdragon

Admirable
Apr 5, 2018
1,546
4
6,165
Yeah, sounds like a failed drive with excessive corruption. Have you attempted to move the drive to another computer just to see if you can mount the volume that way? Worth a shot.

Acronis is a good program for backups and BMR (Bare Metal Recovery). Though I've been using the free edition of Veeam. I've actually cloned drives with it before via backup and restore. So I know it works well. You can also recover individual files if you want. Oh, and what's really awesome is that you can target a NAS or other remove SMB share to another location. And yes, you can boot from a Veeam recovery USB flash drive, and restore from files located on on that share. Yes, I've also tested a BRM restoration that way too, it works very well and is super easy.

https://www.veeam.com/windows-endpoint-server-backup-free.html
 
Upvote 0 Downvote
Solution
W

Whirlingdervish

Distinguished
Aug 26, 2012
40
1
18,535



Thanks for the thoughts. Other than transplant the drive, is there anyway on a computer that won't boot to determine that a drive is definitively dead?

 
Upvote 0 Downvote
stdragon

stdragon

Admirable
Apr 5, 2018
1,546
4
6,165


Yes, you can run vendor specific diagnostics to validate SMART health. For example of this is a Western Digital drive, look for the Data Lifeguard Diagnostic utility.

Although to be honest, a SMART error is often not flagged in the event of a drive failure. It should, but my professional experience tells me it doesn't all the time. In fact, rarely will SMART warn of a pending failure in advance.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom