Computing.Net > Forums > Windows 2000 > fdisk /mbr on second hard drive

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

fdisk /mbr on second hard drive

Reply to Message Icon

Name: Jan S
Date: March 24, 2005 at 08:34:19 Pacific
OS: win2000
CPU/Ram: 128
Comment:

This is my friend's Gateway PERFORMANCE 933 computer. AVG popped up "virus detected" on her computer. She does a scan and AVG finds 31 infected files. She reboots and receives this message: Invalid boot diskette. Insert BOOT Diskette in A: She brings it to me. I check for a floppy in the drive, none there. WD Lifeguard Diags for DOS says “NO DRIVE FOUND ERROR/CODE STATUS: 0120.” I then tried to boot with the 4 win2000 boot disks and end up with the ntdlr missing error. However, advanced settings in the bios do show the drive.
I was finally able to get back into the system with 98 boot disk and fdisk /mbr. In trying to save her data, I ran AVG, then had to reboot; however, upon reboot again received the invalid boot disk error. So I tried again to run the 98 boot disk to fdisk /mbr so I could wipe the whole drive from there instead of clean it from the os, (data is unimportant at this point) but now – even booting from the 98 boot disk I still get the invalid boot diskette error. Seems I now cannot get anything to work, I have unplugged and replugged cables to the floppy drive, tried 3 more boot disks and even changed the floppy drive and still get the same error, invalid boot disk error. I added this hard drive to my old computer and tho Everest system info can see the drive fdisk cannot. Is there any way to fdisk /mbr the second hard drive? Or anything! To reformat the drive? Thanks ahead for help.



Sponsored Link
Ads by Google

Response Number 1
Name: Curt R
Date: March 24, 2005 at 10:37:36 Pacific
Reply:

Try booting with the bootdisk and then run the fdisk utility. Use fdisk to delete the partition. If it's been converted to NTFS you'll have to choose the "non-DOS" partition in fdisk's delete menu (that's how it labels the NTFS partition). Once you've deleted the partition, recreate it and format it as FAT32 and you're ready to install.


0

Response Number 2
Name: Jan S
Date: March 24, 2005 at 10:53:51 Pacific
Reply:

Thanks, I tried that and of course, says "no non-dos partition" to delete. When my machine boots up, I see the my hard drive and the added WD hard drive, but nothing else is recognizing it because the mbr is either damaged or missing. Am at wit's end, lol.


0

Response Number 3
Name: Curt R
Date: March 24, 2005 at 12:58:24 Pacific
Reply:

The mbr (master boot record) is only important if you're trying to boot to the drive which you aren't right now.

Try this, go into Computer Management (right click on My Computer and select Manage) and open the Disk Manager. If you see the HDD in there, you can delete/create a partition on it and format it.


0

Response Number 4
Name: OtheHill
Date: March 24, 2005 at 13:39:29 Pacific
Reply:

Use Delpart to delete any partitions on the disk and then fdisk to create new partitions. Win2000 will format as part of the install process. Fdisk has problems with non dos or corrupted partitions. Find Delpart here: http://radified.com/Files/


0

Response Number 5
Name: wanderer
Date: March 24, 2005 at 14:35:46 Pacific
Reply:

you are wasting your time
"NO DRIVE FOUND ERROR/CODE STATUS: 0120."

The drive died. with no hardware the above suggestions are pointless.


0

Related Posts

See More



Response Number 6
Name: Jan S
Date: March 24, 2005 at 17:05:14 Pacific
Reply:

I believe you could be right. I have tried everything. This thing/beast should get awards for having every error message one can have; "I/O errors, no "operating system found" more "Ntdrl this/that" errors and woe, at some point the Everest system tools and Windows System Info also lost the data. Wasn't there. Once, after putting the drive back in the original tower, I almost made it into the 2000 os and was joyful - and then - all froze. Upon reboot lost the floppy again. And horrors, was going to check to see if any in the bios had changed after all this and it had somehow, in advanced settings, I didn't make it boot sequence, he, he, everything then froze in *there*. Imagine that. And I could not get back in there after that. I'm done, he, he. Thanks much for help above, is just that the bad thing was, there was nothing found anywhere to partition or seen in device manager. As wanderer said, I believe its dead. Boy, does she owe me.

Thanks, Jan


0

Response Number 7
Name: OtheHill
Date: March 24, 2005 at 17:11:25 Pacific
Reply:

wanderer

Can you explain why the disk would show in the BIOS if it were dead? I am not trying to be argumentative, I am wondering. I assume you know what 0120 means and that is the basis of your reply.


0

Response Number 8
Name: Jan S
Date: March 24, 2005 at 18:16:58 Pacific
Reply:

If this helps... this was a question I had also, but I now believe the thing was just dying slowly; also I should have said I did not see the drive that last time in the bios when I said things had changed in the bios, actually I am not sure exactly what I did see in the bios, I just know in those few seconds I was able to be there *nothing* looked the same. Also I believe the 0120 is one of the error codes in the Western Digital Data Lifeguard Diagnostic for DOS program.


0

Response Number 9
Name: OtheHill
Date: March 24, 2005 at 20:54:25 Pacific
Reply:

OK, then that makes more sense to me now.


0

Response Number 10
Name: wanderer
Date: March 25, 2005 at 16:14:39 Pacific
Reply:

Always happy to explain OtheHill.

Couple of things to consider. If the bios is set to auto vs manual. Manual setting will remain even if [depending on bios - i have seen this go both ways] the drive is removed. Auto detects each time.

But the bios is reading stored information from the drive. This does not mean what is beyond that [voice coil/spindle motor/platter integrity] reported is working. In otherwords the bios still will report the drive even when the drive heads are banging against the case or there has been a platter failure due to media failure.

Moral of the story: don't always believe the bios.


0

Response Number 11
Name: OtheHill
Date: March 25, 2005 at 16:50:07 Pacific
Reply:

Is there significance to the 0120 code?


0

Response Number 12
Name: XpUser
Date: March 27, 2005 at 09:24:18 Pacific
Reply:

HI OtheHill,

Error code 0120 is seek timeout. A Seek command did not complete in the time allotted for its completion. This may be an anomaly or a defect with the drive. Retest. The HD should be replaced if the error repeats.

Happy Easter :-)

i_XpUser


0

Sponsored Link
Ads by Google
Reply to Message Icon






Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows 2000 Forum Home


Sponsored links

Ads by Google


Results for: fdisk /mbr on second hard drive

installing win2k on second hard drive www.computing.net/answers/windows-2000/installing-win2k-on-second-hard-drive-/4883.html

install mutl OS on one hard drive? www.computing.net/answers/windows-2000/install-mutl-os-on-one-hard-drive/32325.html

Can't install second hard drive www.computing.net/answers/windows-2000/cant-install-second-hard-drive/48581.html