Question

damaged MBR

Asked by: ahoffmann

After doing a
  convert C: /fs:ntfs
the MBR is damaged that way it didn't find anything on the disk, even ntld( no message at all after reboot).
After connecting the disk as second drive, I can access all files on all partitions. So I'm pretty shure that the FS and the partition table is ok. NT's and Linux's fdisk show the right partition table, while dskprobe shows useless data.
ERD didn't reinstall a valid MBR too.

How can I get (and store) a valid MBR on this disk?

This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.

Subscribe now for full access to Experts Exchange and get

Instant Access to this Solution

  • Plus...
  • 30 Day FREE access, no risk, no obligation
  • Collaborate with the world's top tech experts
  • Unlimited access to our exclusive solution database
  • Never be left without tech help again

Subscribe Now

Asked On
1998-11-01 at 22:47:55ID10094586
Tags

mbr

Topic

Windows NT Setup

Participating Experts
12
Points
500
Comments
55

Trusted by hundreds of thousands everyday for fast, accurate and reliable tech support.

  • "The time we save is the biggest benefit of Experts Exchange to Warner Bros. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange." Mike Kapnisakis, Warner Bros.
  • "Our team likes having a resource that is more secure than just using Google and most experts using this service really know their stuff. It's nice to look here first versus using Google." Dayna Sellner, Lockheed Martin
  • "Anytime that I've been stumped with a problem, 9 out of 10 times Experts Exchange has either the accepted solution or an open discussion of the potential solution to the problem." Kenny Red, eBay Inc.

See what Experts Exchange can do for you.

Got a question?

We've got the answer.

Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.

Screenshot of Experts Exchange Knowledgebase

Need individual assistance?

Our experts are ready to help.

If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.

Screenshot of Experts Exchange Knowledgebase

Want to learn from the best?

Read articles from industry experts.

Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.

Screenshot of an Article

Working on a long term project?

Store your work and research.

Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.

Screenshot of Experts Exchange Knowledgebase

Access the answers to your technology questions today.

Subscribe Now

30-day free trial. Register in 60 seconds.

What Makes Experts Exchange Unique?

Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Trusted by the world's most respected brands.

image of each brand's logo

Faithfully serving IT professionals since 1996.

Experts Exchange Logo

Try it out and discover for yourself.

Subscribe Now

30-day free trial. Register in 60 seconds.

Related Solutions

  1. recreate MBR: How?
    How can I recreate my MBR without re-installing the whole OS? Recently I installed Virus-detecting software, but it was too late. The WELCOMB virus was found. It cannot be cleaned with my virus-software (McAfee's NetShield).
  2. Erase MBR in Linux
    Hi, I have installed grub as bootloader. How can I erase MBR in linux in order to uninstall grub? Thanks in advance

Free Tech Articles

  1. WARNING: 5 Reasons why you should NEVER fix a computer for free.
    It is in our nature to love the puzzle. We are obsessed. The lot of us. We love puzzles. We love the challenge. We thrive on finding the answer. We hate disarray. It bothers us deep in our soul. W...
  2. SCCM OSD Basic troubleshooting
    SCCM 2007 OSD is a fantastic way to deploy operating systems, however, like most things SCCM issues can sometimes be difficult to resolve due to the sheer volume of logs to sift through and the dispe...
  3. Migrate Small Business Server 2003 to Exchange 2010 and Windows 2008 R2
    This guide is intended to provide step by step instructions on how to migrate from Small Business Server 2003 to Windows 2008 R2 with Exchange 2010. For this migration to work you will need the fo...
  4. Create a Win7 Gadget
    This article shows you how to create a simple "Gadget" -- a sort of mini-application supported by Windows 7 and Vista. Gadgets can be dropped anywhere on the desktop to provide instant information, ...
  5. Outlook continually prompting for username and password
    There have been a lot of questions recently regarding Outlook prompting for a username and password whilst using Exchange 2007. There are a few reasons why this would happen and I will try to cover t...
  6. Backup Exchange 2010 Information Store using Windows Backup
    There seems to be quite a lot of confusion around the ability to backup Exchange 2010 using the built in Windows Backup feature. This stems from the omission of this feature prior to Exchange 2007 s...

Cloud Class Webinars

  1. Avoiding Bugs in Microsoft Access
    Alison Balter takes and in-depth look at avoiding bugs in Access. In this webinar you will learn about using the immediate window to debug your applications, invoking the debugger, using breakpoints to troubleshoot, stepping through code, setting the next statement to execute, ...
  2. Top 10 Best New Features in Visio 2010
    Scott Helmers gives live demonstrations of the top 10 new features in Visio 2010. This webinar will teach you how to create compelling diagrams by adding shapes to the page with a single click, linking the shapes in a diagram to data in Excel (or SQL Server, or SharePoint), ...
  3. IT Consultant Business Secrets Revealed
    Michael Munger, Experts Exchange tech pro and IT consultant, pulls back the curtain on his very successful businesses and answers question on every IT consultant and business owner should know about. He shares secrets on what he did to solve the 5 most common problems in IT, ...
  4. Disaster Recovery and Business Continuity
    Quest CTO, Mike Billon, gives an overview of the steps involved in building a dunamic disaster recovery plan. Through case studies and an examination of software/hardware tooles for monitoring and testing, you'll gain a better understandin of where you are, where you want ...
  5. Organize Your Visio Diagrams with Containers and Lists
    Scott Helmers uses cross functional flowcharts, wireframe diagrams, data graphic legends and seating charts to teach you: how to ustilize all three new structured diagram components in Visio 2010, the best practices for organizeing shapes in previous version of Visio, how to organize ...
  6. How to Us Objects, Properties, Events and Methods in Microsoft Access
    Alison Dalter gives an in-depbth look at objects, properties, events and methods in Microsoft Access. In this webinar you will learn about using the object browser, referring to objects, working with properties and methods, working with object variables, understanding the ...

Join the Community

Give a Little. Get a Lot.

Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.

Join the Community

Answers

 

by: BlackManPosted on 1998-11-02 at 05:31:34ID: 1771443

FDISK /MBR should do it...

 

by: ahoffmannPosted on 1998-11-02 at 06:15:01ID: 1771444

Which fdisk (does NT have one)?
DOS' fdisk didn't help.

 

by: BlackManPosted on 1998-11-02 at 06:19:28ID: 1771445

Hmm, I did it with a DOS 6.22 FDISK a couple of month ago?! What is the error? Or did it just not fix the problem?

 

by: ahoffmannPosted on 1998-11-02 at 06:48:43ID: 1771446

DOS' fdisk didn't work, just hangs (not shure if there was no message at all or "no operating system founs")

 

by: BlackManPosted on 1998-11-02 at 09:37:29ID: 1771447

You did call it with /MBR? As fas as I remember, this switch is not available before DOS 6.0

 

by: ahoffmannPosted on 1998-11-02 at 09:41:36ID: 1771448

DOS 6.20: fdisk /MBR

 

by: BlackManPosted on 1998-11-02 at 11:07:14ID: 1771449

Just checked with MS, seems like I was wrong about the DOS version..
Check
http://support.microsoft.com/support/kb/articles/q69/0/13.asp?FR=0

BTW., just don't have BIOS Boot-sector virus protection enabled? This will prevent you from creating a MBR.

 

by: leewPosted on 1998-11-02 at 16:00:45ID: 1771450

A DOS Fdisk/mbr may not work with an NTFS drive.

 

by: tcalesaPosted on 1998-11-04 at 08:32:42ID: 1771451

I've gad to do the fdisk /mbr on a number of NTFS drives because of a virus problem at one of my sites.

Used dos 6.21 disk with no problems

 

by: jminckPosted on 1998-11-04 at 12:09:47ID: 1771452

1)open dskprobe
2)click 'drives | physical volume'
3)double click the correct drive, then click 'set active' on the handle
4)click 'sectors | read' sector 0, # of sectors 1
5)click 'view | bytes'
at offset 0000, the first byte pair should be FA
at offset 01F0, the last 2 byte pairs should be 55 AA
There should be nothing between offset 00E0 and 01A0 except 0's
if there is you proabaly have a bootsector virus
If partition 1 is supposed to be active, you should have an 80 at offset 01BE. If partition 2 is supposed to be active, then the 80 would be at 01CE, etc...
If you want, you can click on 'file | Save as' and email me the sector at joey@minckler.net

 

by: ahoffmannPosted on 1998-11-05 at 03:55:42ID: 1771453

fdisk /MBR didn't help (it's NTFS, read the question).

jminck, I also played with dskprobe (see question) and I did not
try to change and save anything 'cause it definitely shows a wrong partition table, which in fact, is ok (tested with several fdisk). Unfortunately dskprobe writes 512 bytes, as far as I understand, and this may destroy my working partition table.
I'd like to do dskprobe, if I'm save that it will not destroy my partition table ('cause then I'll loose my data).

About viruses, I cleand the first 448 bytes of the MBR, then used all methods described here before without success. If it's a virus it must be in all my fdisks *and* convert *and* several MBRs from other installations I tested, unbelievable.

 

by: ahoffmannPosted on 1998-11-05 at 03:56:04ID: 1771454

Adjusted points to 500

 

by: waynebPosted on 1998-11-05 at 04:42:30ID: 1771455

There is only one way to repair a mbr or for that matter any corrupted installation of Nt.

You will have to have the 3 windows setup floppy disks that come with nt or you can make and boot off of disk 1 and then follow the prompts to repair the boot sector, it should beable to repair the Mbr and allow your system to boot up into Nt once again. Nt will ask you if you have a repair disk if you don't it makes things harder but should still beable to be done.

You can create setup floppys from a Windows 95 Box or another machine by using this procedure.

goto start and then run and type after inserting the Nt cdrom in the cd drive.

d:\i386\winnt.exe /ox   This will work on an Win95 Box.

where d:\ is your cdrom letter


How to: Create setup disks.
Solution:

At the command prompt, change the directory to x:i386 is (where x is the CD-ROM drive). Enter the following at the command prompt:
START WINNT32 /OX


1) Open the 'Command Prompt'.
2) At the command prompt, to change to the CD drive enter:
CD /D x:
(where x is the CD drive letter).
3) Insert the Windows NT 4.0 Server installation CD.
NOTE: The 'Windows NT CD-ROM' dialog box appears; close this dialog box.
4) Enter the following to change to the i386 directory:
CD I386
5) Enter the following at the command prompt:
WINNT32 /OX
NOTE: NOTE: If the Setup disks are being created on a DOS, Windows 3.x or Windows 95 machine, use the command WINNT.EXE.
(The 'Windows NT 4.0 Upgrade/Installation' dialog box appears.)
6) Click 'Continue'. (A new 'Windows NT 4.00 Server Installation/Upgrade' dialog box appears.)
 Windows NT 4.00 Upgrade/Installation
7) Label 3 blank formatted diskettes as follows:

a) 'Windows NT Server Setup Disk 3'
b) 'Windows NT Server Setup Disk 2'
c) 'Windows NT Server Boot Disk'

8) Insert the disk labeled 'Windows NT Server Setup Disk 3' into the floppy drive.
 Insert Setup Disk 3
9) Click 'OK'. (Files are copied to the diskette; a new dialog box appears, prompting the user to eject the diskette and insert 'Setup Disk 2'.)
10) Insert the disk labeled 'Windows NT Server Setup Disk 2' into the floppy drive.
 Insert Setup Disk 2
11) Click 'OK'. (Files are copied to the floppy diskette; another dialog box appears prompting the user to eject the diskette and insert 'Boot Disk'.)
12) Insert the disk labeled 'Windows NT Server Boot Disk' into the floppy drive.
13) Click 'OK'. (Files are copied to the floppy diskette.)
 Insert Setup Boot Disk

Good Luck


 

by: ahoffmannPosted on 1998-11-05 at 04:56:42ID: 1771456

wayneb, please read my question: I still said that ERD didn't help
Also keep in mind that my ERD is made from FAT and I'm now to boot on NTFS, There is also no MBR on ERD, it must be made before using dskprobe :-O
Setup "constructs" an MBR, but where did it get its information from?

PLEASE, read the question before posting huge useless texts :-(

 

by: tcalesaPosted on 1998-11-05 at 07:43:11ID: 1771457

ahoffmann,
I'm not trying to waste your time, but it sounds like you may be screwed. Do you have some unused hardware lying around? if so try this. Get some similar hardware together and try a repair installation to a different physical drive and use FAT. Swap the drives and try to boot up. This may get you up and going.

I know there is no finesse to this approach, but it may provide quicker results than trying to figure out the boot sector of the original drive.

You may even want to convert the new drive to NTFS while it is in the new PC. reboot and test before swapping to verify that it will work prior to moving to the old platform.

Ignore errors logged into the event viewer as they would probable be drivers that will work once thw drive is moved into the old machine.

As always, Good Luck

 

by: ahoffmannPosted on 1998-11-05 at 08:14:35ID: 1771458

tcalesa, what do you mean by:
"try a repair installation to a different physical drive"

How will I do a repair installation?
BTW, I know that my pertition *is* NTFS and working as 2'nd drive'

So, the question is very simple:
  how can I make a valid MBR for 2'nd drive on the 2'nd drive
If this works it should be easy to patch this MBR to be used as 1'st drive and swap the drives.
Or am I barking up the wrong tree?

 

by: leewPosted on 1998-11-05 at 08:24:06ID: 1771459

Ok, my only suggestion is this:  

Reinstall nt to a different location.  This should rewrite the masterboot record.

Something else you can do to boot up to the partition (not that you want to do this all the time)
is create an NT boot disk.  See:
http://support.microsoft.com/support/ntserver/serviceware/10140511.asp

 

by: tcalesaPosted on 1998-11-05 at 08:44:27ID: 1771460

What I meant was try to get NT set up on a different computer on a similar drive and then move the new drive to the old CPU "box".

I assume you have the ERD. Run setup on another PC with a sililar  Hard drive scheme and do an ERD installation on the clean hardware.
Then just move the new hard drive to the old hardware.

I rarely like to say reinstall, but it may be your only option at this point.

Actually, leew's suggesstionmay work and better. Try it and if it doesn't work, you may be looking at a reinstall.

 

by: tcalesaPosted on 1998-11-05 at 08:44:52ID: 1771461

What I meant was try to get NT set up on a different computer on a similar drive and then move the new drive to the old CPU "box".

I assume you have the ERD. Run setup on another PC with a sililar  Hard drive scheme and do an ERD installation on the clean hardware.
Then just move the new hard drive to the old hardware.

I rarely like to say reinstall, but it may be your only option at this point.

Actually, leew's suggesstionmay work and better. Try it and if it doesn't work, you may be looking at a reinstall.

 

by: ahoffmannPosted on 1998-11-05 at 09:09:04ID: 1771462

tcalesa, you suggest a new installation.
Not realy what I want (otherwise I still would have done it), 'cause it's not the first time I got this behavior.
I need a fix, means a repair, not a workaround or reinstallation.
Thanks anyway.

 

by: tcalesaPosted on 1998-11-05 at 09:36:00ID: 1771463

ahoffmann
I suggested a repair installation of your original on a different platform.

Sorry that won't work for you.

Good luck resolving

 

by: bchewPosted on 1998-11-05 at 09:47:11ID: 1771464

Do you have technet?  If so, have you read articles Q153973
 and Q121517?  I think one of these contains your answer.  They are quite long so I won't post them unless you ask for them.  Or I could e-mail them if you leave your address.

Regards,
Bert.

 

by: kklamPosted on 1998-11-05 at 14:21:15ID: 1771465

I ran into a situation like that once long time ago.  Let see if I remember how I fixed it...

The way that I fixed it basically involved with half a new install:

1) Put your damaged drive back as your primary active drive.  
2) Using your NT installation media, i.e. either your three NT installation disks or bootable CD.
3) Start a new NT installation on the damaged drive but don't overwrite your old NT directory.  Changed the new installed
directory to something like winnt-spare.
4) Follow all the instructions like a normal installation until it start copying setup files on your harddisk.
5) While it is copying files onto your drive.  Abort the installation.
6) Remove the installation media and reboot your PC.
7) If the Boot manager comes back, you are back in business.
Otherwise, good luck!
8) If 7) is OK, you still need to clean up your "boot.ini" and
the temporary directory which stores the NT setup files.


 

by: ahoffmannPosted on 1998-11-05 at 23:45:11ID: 1771466

Thanks kklam, I still tried this too, but when I try to install NT again it complains that it did not have a disk. Crazy :-o

leew, using a boot disk ends up in a message that there is no valid or a currupted NT installation (that's not realy true).

bchew, M$'s articles Q153973 points to the right direction.
Unfortunately when I want to write the backup bootsector, it complains with "invalid data" (or similar) and then aborts without writing the sector.
So either the backupsector is damaged also, or it points to the FAT layout (even the bytes in dskprobe state that it is NTFS).
But I think that this article is wrong, or I missed something essential in dskprobe:
  In the step where to write the bootsector, it says to type the number of relative sectors from step #5. IMO this would overwrite the backup bootsector with itself.
Could you please verify if this is true (and therefore the article wrong)?

 

by: leewPosted on 1998-11-06 at 08:25:50ID: 1771467

The boot disk has worked for me once (I've only tried it twice and the other time was with a system with a very screwed up hard disk).  You did verify the boot.ini on the floppy points to the right disk and partition?

 

by: ahoffmannPosted on 1998-11-06 at 08:49:34ID: 1771468

> You did verify the boot.ini on the floppy points to the right disk

Yes, cause I copied it from the damaged disk :-)
(It's the same as on my ERD)
Did convert change partition sequences, eventually?

 

by: hugheiaPosted on 1998-11-09 at 06:10:38ID: 1771469

Good luck - because ive got a similar problem with a corrupt MBR and ive been trying for ages to fix it.

 

by: bbaoPosted on 1998-11-09 at 06:28:16ID: 1771470

1. Make sure the first physical hard disk has a good and bootable MBR.
2. Make sure the second physical hard disk is that not-bootable one.
3. Make sure you have no mirror, volume or strip set partitions on the second disk.
4. Boot system with a clear DOS startup disk
5. Run DEBUG and input the following except comments after ";".

a100
     mov ax,0201    ; read 1st disk's MBR to offset 1000h
     mov bx,1000
     mov cx,1
     mov dx,80
     int 13
     mov ax,0201    ; read 2nd disk's MBR to offset 1000h
     mov bx,2000
     mov cx,1
     mov dx,80
     int 13
     int 3
g=100
m1000 10bd 2000    ; move 1st' MBR code to the 2nd
a=200
     mov ax,0301    ; write new MBR to 2nd disk
     mov bx,2000
     mov cx,1
     mov dx,80
     int 13
     int 3

What the meaning of above procedures is to copy a good MBR code to the bad one without changing its partition information. Since it is very low level operation, I strongly recommend you indeed understand every step and meaning of the assembly code. Make very sure it is suitable to you. Else, the data on your second disk, even the first disk, may be lost.

In fact, FDISK /MBR does the same thing, except it does not work with NTFS.

 

by: bbaoPosted on 1998-11-09 at 06:34:32ID: 1771471

Sorry, the last paragraph should be:

a200    ; write assembly code at offset 200h
    mov ax,0301    ; write new MBR to 2nd disk
    mov bx,2000
    mov cx,1
    mov dx,80
    int 13
    int 3
g=200    ; run assembly code from offset 200h

 

by: ahoffmannPosted on 1998-11-10 at 01:24:55ID: 1771472

bbao, I'll give it a try (on my risk)-:

Questions:
1) your last comment did not change anything (except a comment), or did you mean that the line (in the answer)    m1000 10bd 2000
is obsolete?

2) Reading MBR on the 2'nd disk, why is it necessary?
    Are you shure this section starts with   mov ax,0201

 

by: bbaoPosted on 1998-11-10 at 03:26:04ID: 1771473

1. It should be "a200", not "a=200". "g=200" is needed to run the code. "m1000 10bd 2000" is used to copy the 1st MBR's good boot code to the 2nd one at 2000.

2. It is necessary, since you should keep the 2nd disk's partition table. Yes, it starts with "mov ax, 0201", but sorry for a wrong comment, the comment of this should be "read 2nd disk's MBR to offset 2000h".

As you and I mentioned, it has risk, so I think you should backup all the data as possible as you can do.

Good luck!

 

by: ahoffmannPosted on 1998-11-10 at 07:56:54ID: 1771474

ok bbao, I understand :-)
This is equivalent to do following under UNIX:

dd bs=190 count=1 if=/dev/hda of=/dev/hdb

 

by: bbaoPosted on 1998-11-10 at 08:39:04ID: 1771475

Nice to hear this, is it what you want? Please let me know how it goes. :-)

BTW, your UNIX experience is pretty rich, could you explain what does the command-line mean?

 

by: ahoffmannPosted on 1998-11-10 at 23:45:41ID: 1771476

> dd bs=190 count=1 if=/dev/hda of=/dev/hdb
   bs=190  (blocksize)
   count=1 (use one block)
   if=/dev/hda (input file; /dev/hda is first sector on first drive)
   of=/dev/hdb (output file; /dev/hdb is first sector on 2'nd drive)

Or simply: copy 190 bytes from the very beginning of 1'st to beginning of 2'nd drive.
(Things could be so easy :-))

 

by: ahoffmannPosted on 1998-11-12 at 22:26:56ID: 1771477

bbao, patching the MBR in the suggested way didn't change anything :-(

 

by: bbaoPosted on 1998-11-13 at 02:00:56ID: 1771478

The error message is same as the before?

 

by: ahoffmannPosted on 1998-11-13 at 02:42:07ID: 1771479

no error message, I said "nothing changed". Means that it just did not find anything on the disk, even ntldr.
Probably I should tell you that this is a 4.3GB IDE disk with 4 partitions as follows:
    bootable 1 600MB
                     2 1000MB
                     3 600MB
                     4 1100MB

 

by: tcalesaPosted on 1998-11-13 at 07:20:27ID: 1771480

I was just rereading the comments. I know you have probably checked this, but have you taken blackmans suggestion to investigate boot sector protection in the bios of the pc?

Have you also run a disk checking utility like Checkit Pro to ensure there is nothing physically wrong with the drive?

I'm sorry if I wasted your time, but I thought it a good idea to at least ask.

 

by: ahoffmannPosted on 1998-11-13 at 08:37:30ID: 1771481

How could I install NT on another blank drive if there is a boot sector protection enabled in BIOS? Anyway, I checked.

About Checkit Pro, don't have it.
I also agree that it could be a physical problem. But as I said before, I've had this problem on another machine and solved by re-installing.
Also chkdisk does not report any errors.

I will believe that convert is buggy, but chkdisk also?

 

by: ahoffmannPosted on 1998-11-17 at 23:10:16ID: 1771483

.. I should remove and repost this question, squeezing all the comments to the informational ones.
It's to much to read, right Jason_Shulenberger ?-))

 

by: tcalesaPosted on 1998-11-20 at 08:52:48ID: 1771484

ahoffman,
did the disk dump work? I may have a machine with a similar problem.

 

by: ahoffmannPosted on 1998-11-20 at 09:39:50ID: 1771485

Which disk dump?

> similar problem
nice to see that it's not only me :-((
I've read somthing about such things in a german journal (iX)
I'll try to contact the author next week; probaly it has to
do with the 4.3GB disk.

 

by: tcalesaPosted on 1998-11-20 at 09:43:27ID: 1771486

bbao's debug dd equiv.

Are you saying it has to do with this particular brand of har disk?

Keep me posted it you could I'd appreciate it.

Good luck.

 

by: sweatbeastPosted on 1998-11-20 at 20:01:42ID: 1771487

Technical note: The ERD WILL NOT repair the MBR. FDISK /MBR is the best way to do this. Dos 6.0 and above supports this command.

 

by: lieblaPosted on 1998-11-26 at 07:04:27ID: 1771488

The current situation:
NT4 installed on drive c:\ using NTFS
invalid boot sector

Make the 3 NT floppy disks as described.
Create an Emergency Repair Disk on a different NT workstation with NT 4 installed on drive C:\ using NTFS, too.

Boot with the first of the three disks.
There is a point where you can select to repair a damaged NT4 installation.
There is a point where you can restrict the error search to the bootenvironment.
Restrict it and you should be able to recreate all necessary startup files and a proper boot sector with the repairdisk created on the other NT 4 workstation

 

by: leewPosted on 1998-11-29 at 06:58:06ID: 1771489

So, If I've processed these comments again correctly, you have a second drive you installed NT on so you could boot and look at the file system on the first drive.  Correct?  If so, then have you run NT's Chkdsk on the disk with the MBR problem?  

 

by: lieblaPosted on 1998-11-30 at 00:59:35ID: 1771490

My solution does not require to install NT a second time and it does not require to put the harddisk with the invalid MBR from the workstation to another workstation.

The repair of the damaged MBR could be done with the 3 boot disks created via winnt /ox
AND the Emergency repair disk (created using rdisk.exe).
Only for this rdisk.exe you need a RUNNING NT 4 Workstation, winnt /OX can be run under pure MS DOS, too.

Please let me know if you had success with this procedure.

The problem is: You need write access to your NTFS partition which is possible by booting with the 3 NT boot disks.

the boot sector of two NT workstations installed on C:\ using NTFS is identical.
But as I said in my first comment, restrict the repair to the bootenvironment.

 

by: ahoffmannPosted on 1998-11-30 at 03:33:59ID: 1771491

leew, you're right: I use the damaged disk as secondary drive.
There are no Problems at all (chkdsk reports OK), see also my comment from November 05 1998 - 11:45PM PST .
liebla, tried this in you variant (ERD from another NT) too, didn't help.

Sounds that there is no solution without reinstalling NT, which I won't do because of SP3 + hotfixes + several apps + etc. + ..

 

by: tcalesaPosted on 1998-11-30 at 07:11:53ID: 1771492

ahoffmann,
How about running a full backup of the affected system and restoring to another server/hard drive? this would prevent the full reinstall problem with the apps etc. then you can format and recover the old hardware and do another backup/restore to it.

 

by: ahoffmannPosted on 1998-11-30 at 08:41:21ID: 1771493

tcalesa, I'm half the way doing something like you suggested.
But unfortunatelly there are still some dragons to beat (see early comments).
BTW, this still is not an acceptable workaround, 'cause I just want to get back a valid MBR (destroyed by convert), nothing else.

 

by: tcalesaPosted on 1998-11-30 at 08:55:15ID: 1771494

I'm not worried about the points, I'm just not sure if trying to hack the MBR is going to work, so I made another suggestion.

If you do fix the problem and have no luck with the MBR, could you contact EE cust service to adjust this to a zero point Q? It'd make and interesting PAQ at least, and you'll save the points as it seems no acceptable solution was found.

BTW, I take the to mean that the Debug command didn't work? I did get my similar problem fixed, I had used FDISK from a Win95 disk inadvertently. I tried again with a Dos 6.22 disk and all was well. I probably had something easier to fix.

Good luck

 

by: ahoffmannPosted on 1998-12-02 at 00:08:10ID: 1771495

Following workaround solved the problem without going through the whole installation of NT and apps etc.

1.  damaged drive as primary master
2.  boot linux (from floppy or whatever)
3.  change partition type (where NT resides) to type DOS FAT
    using linux's fdisk
4.  backup NT partition as follows:
    dd bs=1024 count=620000 if=/dev/hda1 of=a_save_place
5.  boot DOS from floppy
6.  fdisk /MBR
7.  install NT (using NTFS)
8.  boot linux
9.  restore previous installation:
    dd bs=1024 count=620000 if=a_save_place of=/dev/hda1
10. cross your fingers

I'm not shure if step 5. and 6. are necessary. Probably the NT
installation in step 7. can be aborted after it converts to NTFS.

If this fails too, the existing installation must be copied using
NT as follows:

1.  damaged drive as slave, working NT as primary master
2.  boot NT, copy NT from slave to a_save_place
3.  damaged drive as primary master
4.  boot linux (from floppy or whatever)
5.  change partition type (where NT resides) to type DOS FAT
    using linux's fdisk
6.  boot DOS from floppy
7.  fdisk /MBR
8.  install NT (using NTFS)
9.  see 1.
10. boot NT
11. restore previous installation:
    copy a_save_place slave
12. see 3.
13. cross your fingers


I'm still searching for a clean, straight forward, solution.
Any comments are welcome.

 

by: lindaPosted on 1998-12-02 at 06:16:27ID: 1771496

I am posting the solution found by ahoffmann so it can be saved in the previously asked questions.  

Linda Gardner
Customer Service @ Experts Exchange

Comment From: ahoffmann
                               Date: Wednesday, December 02 1998 - 12:08AM PST

     Following workaround solved the problem without going through the whole
     installation of NT and apps etc.

     1.  damaged drive as primary master
     2.  boot linux (from floppy or whatever)
     3.  change partition type (where NT resides) to type DOS FAT
         using linux's fdisk
     4.  backup NT partition as follows:
         dd bs=1024 count=620000 if=/dev/hda1 of=a_save_place
     5.  boot DOS from floppy
     6.  fdisk /MBR
     7.  install NT (using NTFS)
     8.  boot linux
     9.  restore previous installation:
         dd bs=1024 count=620000 if=a_save_place of=/dev/hda1
     10. cross your fingers

     I'm not shure if step 5. and 6. are necessary. Probably the NT
     installation in step 7. can be aborted after it converts to NTFS.

     If this fails too, the existing installation must be copied using
     NT as follows:

     1.  damaged drive as slave, working NT as primary master
     2.  boot NT, copy NT from slave to a_save_place
     3.  damaged drive as primary master
     4.  boot linux (from floppy or whatever)
     5.  change partition type (where NT resides) to type DOS FAT
         using linux's fdisk
     6.  boot DOS from floppy
     7.  fdisk /MBR
     8.  install NT (using NTFS)
     9.  see 1.
     10. boot NT
     11. restore previous installation:
         copy a_save_place slave
     12. see 3.
     13. cross your fingers

     I'm still searching for a clean, straight forward, solution.
     Any comments are welcome.

 

by: tcalesaPosted on 1998-12-02 at 07:27:41ID: 1771497

Pretty clever ahoffmann. I am saving this one is case of a rainy day!!!

 

by: ahoffmannPosted on 1998-12-04 at 03:37:14ID: 1771498

20120131-EE-VQP-002

3 Ways to Join

30-Day Free Trial

The Experts

98% positive feedback on 31,087 answers since March 2000. angeliii is a Microsoft Most Valuable Professional for his work with MS SQL Server & Develoment.

He has also proven his knowledge of Visual Basic Programming, PHP Scripting and Oracle Databases.

The Experts

97% positive feedback on 10,752 answers since July 2000. lrmoore has more than 18 years experience in the networking industry.

The six-time Mircosoft MVPs specialties include firewalls, virtual private networking, and network management.

Testimonials

"...and excellent source for support... Kind of like having your very own IT dept." Electriciansnet

Testimonials

"I was apprehensive at signing up at first. However... it has already made my life as an IT administrator much easier." JaCrews

Testimonials

"WOW! You guys have great, active, and knowledgeable people on here." moore50

Business Clients

Business Clients

In the Press

"If you’ve got a question... Experts Exchange can supply an answer.”

In the Press

"...an invaluable aid for both IT professionals and those who require tech support."

In the Press

"where IT professionals provide quick answers on just about any topic"

Business Account Plans

Loading Advertisement...