On Tue, Apr 5, 2011 at 5:23 PM, Nicholas Blatter <[email protected]> wrote:
> If Windows 7 creates a boot partition, it will usually be 100MB in
> size and formatted as NTFS.  That 17MB partition isn't it.  However,
> it is not required to store the boot files on a separate partition --
> look on your primary NTFS partition for a (hidden) Boot folder.  If
> it's there, then your primary NTFS partition is Windows' primary boot
> volume.

Then I think that may have been the case.  But now, according to
Ubuntu (nautilus file manager and $ ls /the-mount-point), the
partition has no files in it.  But GParted says 3 GB have been used.
The before-this-whole-mess Windows filesystem had way more used space
than that though.  Curse the recovery system again.
>
> I would guess that the reason your recovery attempt failed was that
> you've altered the partition table of the disk.  It's quite possible
> that, to prevent data loss, the recovery software won't proceed if
> things don't look right.  To fix this, you might try deleting the two
> Linux partitions and using something like GParted to recombine those
> partitions back into one big NTFS partition.  Try the recovery again
> and things might work out.
>
I had reinstalled linux so I would have a bootloader with which to
attempt booting Windows and/or the recovery partition.  I guess I can
use grub on my usb drive.  However, the recovery seems to have done an
impressive job of data loss already.

> If your goal is to restore the system to a Windows-only state without
> worrying about keeping any Linux stuff, you might be better off just
> reinstalling (or repairing) Windows using a full Windows 7 disc.  If
> you're enrolled in any CS classes you probably have access to MSDNAA,
> which includes free licenses for Windows 7.  You can download an ISO
> image and create a disc to (possibly) repair, or just reinstall the
> whole thing.
>
> Nick


Forgot about that.  I used to be able to log in to the MSDNAA thing
from the CS website.  I just now tried to log in, but it won't let me
since I'm not "currently" taking a class.  I'm currently on enrollment
deferment for my mission, which begins in a week.  Too bad I didn't
download an iso last semester.  You'd think it would be open to CS
Majors even if I wasn't currently in a class.  Maybe I could try to
find somebody with a disc I could (possibly) repair with.  I'm at home
in Texas, though.

If there's 3GB used space and no files on an NTFS partition, does that
mean that it's file indexes have been damaged?  I ran ntfsfix on it
and it "was processed sucessfully," but there are still no files
showing up when I mount and $ ls the partition.

I ran the bootinfoscript as Bill suggested.  Here's the relevant parts:
sda1: _________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows Vista/7
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:
    Boot files/dirs:
sda3: _________________________________________________________________________

    File system:       vfat
    Boot sector type:  Vista: Fat 32
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:
    Boot files/dirs:   /bootmgr /boot/bcd

sda4: _________________________________________________________________________

    File system:
    Boot sector type:  Unknown
    Boot sector info:
    Mounting failed:
mount: unknown filesystem type ''

So the BOOTMGR is in /dev/sda3, the 10gb fat32, recovery partition.
Unless of course the recovery system has its own bootmgr and there's
supposed to be one in /dev/sda1.

Timothy
--------------------
BYU Unix Users Group 
http://uug.byu.edu/ 

The opinions expressed in this message are the responsibility of their
author.  They are not endorsed by BYU, the BYU CS Department or BYU-UUG. 
___________________________________________________________________
List Info (unsubscribe here): http://uug.byu.edu/mailman/listinfo/uug-list

Reply via email to