General discussion

  • Creator
    Topic
  • #2073607

    delpart

    Locked

    by chayes ·

    Ran delpart on a 10.1 gig IBM, IDE UDMA66 drive, and now NT4.0 server refuses to see the drive as a bootable device. Other versions of Win(95-98) still load to the drive with no prob. Several flavors of Linux see and load to the drive no prob. NT4.0 has been on this drive with this hardware config many times before…just not since delpart… What is now missing from this drive that prevents NT seeing it as a bootable device. Have tried using existing setup disks, and creating new from cd. M/B is ASUS P3B-F with Celeron 400 in Slot1 adaptor. Vid is Nvidia Riva 128. Is this thing salvageble for NT???

All Comments

  • Author
    Replies
    • #3893372

      delpart

      by guy ·

      In reply to delpart

      Delpart is silent and deadly.
      It has deleted the partition in NT’s eyes.
      If the other operating systems can still see it could you backup, then reformat the partition in NT then Restore?

      • #3783139

        delpart

        by chayes ·

        In reply to delpart

    • #3776420

      delpart

      by mckaytech ·

      In reply to delpart

      Most likely, your master boot record is toast. I’ve had some success with using a Windows95 boot disk and re-writing the MBR with fdisk /mbr.

      You can then create a new partition and explicitly set it to active and that may solve the problem.

      Alternately, you could use Boot Magic, System Commander or [Linux} lilo to write an MBR that re-directs the NT boot loader and that might work as well.

      Also, just for completeness, I’m assuming that this drive is the Master on the Primary IDE channel and the CMOS drive geometry is correct.

      best wishes with this interesting problem…

      paul

      • #3783140

        delpart

        by chayes ·

        In reply to delpart

    • #3777767

      delpart

      by raymond danner ·

      In reply to delpart

      The drive should be salvageable.. If you have Norton SystemWorks (or Norton Utilities) available, try running NDD32 against the drive and see if it sees the problem. If it does, allow NDD to correct the problem.

      Alternatively, try using PartitionMagic 5.x to scan and rewrite critical structures without having to damage data. While FDISK does work, it is terribly destructive, and the problems it can and does cause are too high. For me, FDISK is a last resort when nothing else works. FDISK /MBR rewrites a standard Master Boot Record, and will DISCONNECT multi-OS managers, often leaving those OS’es almost unusable.

      • #3783141

        delpart

        by chayes ·

        In reply to delpart

Viewing 2 reply threads