Re: findpart/editpart help, please! Ran fixboot from Rec Console on 200G disk



MartyEgan <martyegan@xxxxxxxxx> wrote

> Here's how I got where I am:

> System is a few months old HP Pavilion, with a single
> 200Gig SATA drive. It came from the store with 2 partitions
> - a "Recovery Partition" of about 6 Gig, and another partition
> of about 180Gig where WinXP Home was installed.

What was the story with that service pack wise ?

> I upgraded WinXP Home to WinXP Pro by running an in-place
> upgrade. Applied Service Pack 2. Everything seemed to work fine.

> The system became infected with numerous spyware, etc, and
> I had to clean it up. I used the MS Antispyware. I booted into
> Safe Mode and ran the MS Antispyware scan. The following
> day, my wife said it wasn't working. I wasn't able to boot,

Presumably you could boot after completing the antispywhere scan ?

> with an error - "Windows could not start because of
> an error in the software. Please report this problem
> as : load needed DLLs for kernel. Please contact
> your support person to report this problem.".

> I booted into BartPE (built with from a SP2-slipstreamed WinXP Pro
> disk amd UBCD from ubcd4win.com), and wanted to see the event
> logs, so I looked for them in %systemroot%\system32\config where
> they are normally. They weren't there. This seemed quite odd to me.
> However, most everything else looked normal - including that my
> personal data files were where I expected them to be.

> Booted with my original "non-slipstreamed" Windows XP
> Pro CD, loading the SATA drivers by pressing F6 during
> startup of the CD. I tried to do a repair, but was not allowed.
> The only thing I could do was format the partition where
> "C:" was, because it was labeled with "(Unknown)".

So its likely it was corrupt by then, before you had written to it.

> I then booted into the Recovery Console using the
> same CD, and ran "fixboot", hoping to fix the partition.
> (Duh! I didn't know about the 48-bit LBA issues then.
> I suspect that the 48-bit LBA issues are why it was
> labeled "(Unknown)", right?)

Not likely, as long as you havent written to the drive without
48-bit LBA support, it shouldnt have produced that.

> Afterwards, the 180Gig volume appears to be only 10Meg, and FAT12
> instead of ~180Gig an NTFS. The directory listing on the drive (using
> BartPE again) shows a bunch of odd characters, but no files of mine.

> I tried looking at it with Partition Magic 8, but that wasn't helpful.
> I haven't modified the drive since the goof with "fixboot".

> Here's what I've done so far using findpart. I'm not sure where to
> go from here. I've tried to delete the incorrect partition table entries
> (see output below), but it appears not to be working. What am I
> doing wrong? What should I do? Any help sincerely appreciated!

I'd run the hard drive manufacturer's diagnostic
on the drive to see if the drive is just dying.

Check the SMART data with Everest too.


.



Relevant Pages

  • Re: Question about OS/2 FDisk/BM pre/post FP13
    ... For instance, it was boot used while booted to a DOS, that won't work, because DOS itself requires Cylinders/Heads/Sectors, and does not use LBA. ... and logical partition type "F" support), which back then in 2002 was also named to be LBA capable, booted from my now finally working updated W4 Installation disks, using the /query command. ... But its result and my late test experience indicate, that the limiting factor still today is FDisk/BM, since quite obvious, it still cannot handle the BIOS' LBA mode. ... You have to exit fdisk in the middle to make it install the newer version or else it detects the existing one and neglects to reinstall it. ...
    (comp.os.os2.misc)
  • Re: Question about OS/2 FDisk/BM pre/post FP13
    ... For instance, it was boot used while booted to a DOS, that won't work, because DOS itself requires Cylinders/Heads/Sectors, and does not use LBA. ... But its result and my late test experience indicate, that the limiting factor still today is FDisk/BM, since quite obvious, it still cannot handle the BIOS' LBA mode. ... Even though it will report the BIOS's bootable partition limit, that does not mean that one is restricted to only installing operating systems and drivers that are so restricted. ... but no usable logical drives within to chose from. ...
    (comp.os.os2.misc)
  • Re: Win2000 "C" Drive only 2.0 GB - How do I increase it?
    ... I would plan to use that partition for data, photo backup, data ... First you have to make sure that your BIOS is 48-bit LBA compatible. ... Go in the BIOS and verify that the disk and its size is properly ...
    (microsoft.public.win2000.setup)
  • Re: Win2000 "C" Drive only 2.0 GB - How do I increase it?
    ... First you have to make sure that your BIOS is 48-bit LBA compatible. ... 48-Bit LBA BIOS you should have been able to create a 137GB partition. ... Go in the BIOS and verify that the disk and its size is properly ...
    (microsoft.public.win2000.setup)
  • Re: Adding a new hard drive
    ... >boot drive and WinXP Home and all my software and data are installed on it. ... in Unallocated space, take Create partition. ... click Settings and Move folder; ... data store, in its Tools - Options - Maintenance, click Store Folder. ...
    (microsoft.public.windowsxp.general)