MLDalglish
Level 1 (4 points)
Windows Software

Q: After system image restore, disk contents don't match up

I feel like every time I think I've got this darn computer fixed, another problem pops up...


Okay, so after much headache, I was able to restore Boot Camp from a VHD image... however... what OSX sees as the contents of the BOOTCAMP disk, and what BOOTCAMP sees of itself are completely different.

According to OSX, here's the contents:

Kenz$~:   cd /Volumes/BOOTCAMP/

Kenz$~:   ls

$Recycle.Bin/              Program Files/             Users/

BOOTSECT.BAK*              Program Files (x86)/       Windows/

Boot/                      ProgramData/               WindowsImageBackup/

DRIVERS/                   RHDSetup.log*              bootmgr*

Documents and Settings/    Recovery/                  hiberfil.sys*

Intel/                     Recovery.txt*              pagefile.sys*

PerfLogs/                  System Volume Information/

This is how the drive looked before System Restore, yet OSX still thinks this is what is on the disk...

Here's the contents as seen from Windows, for comparison:

Directory of C:\

 

10/06/2015  02:45 PM                58 AppleBcInstaller.log

04/19/2016  09:08 AM             4,528 app_updater.log

02/02/2015  10:19 AM    <DIR>          Autodesk

01/03/2015  07:41 PM    <DIR>          Intel

07/13/2009  10:20 PM    <DIR>          PerfLogs

11/12/2015  03:02 PM    <DIR>          PhSp_CS2_UE_Ret

07/11/2016  05:44 PM    <DIR>          Program Files

07/15/2016  03:37 PM    <DIR>          Program Files (x86)

07/15/2016  11:58 AM    <DIR>          RegBackup

10/15/2015  07:13 PM             2,058 RHDSetup.log

01/04/2015  06:47 PM    <DIR>          Sandbox

01/03/2015  05:13 PM    <DIR>          Users

07/22/2016  03:48 PM    <DIR>          Windows

               3 File(s)          6,644 bytes

              10 Dir(s)  66,776,281,088 bytes free

I feel this is an OSX problem, like I need to reset its memory of the BOOTCAMP volume or something.

I have unmounted than re-mounted the disk, reset NVRAM/PRAM and disabled Tuxera NTFS... but it still shows this as the contents.

 

Any ideas on how to fix this? While I could leave it alone since both OSX and Windows function and boot properly, I would like to create a WinClone image of Boot Camp, and in this situation it would probably create an image of the wrong thing, so I'd like OSX to see the disk correctly. The driving factor here is I'd like to take advantage of the free Windows 10 upgrade, but I want to be able to roll back to where I was in the worst-case scenario.

MacBook Pro with Retina display, OS X Mavericks (10.9), Windows 7 Boot Camp

Posted on Jul 22, 2016 3:02 PM

by Loner T,Solvedanswer
Loner T Loner T
Level 7 (23,828 points)
Safari
A:

Please try the following...

 

sudo gdisk /dev/disk0

 

x (Experts menu)

l (lower case L, set sector alignment)

1 (one sector)

m (Main menu)

n (New)

1 (GPT 1)

40 (Start)

409639 (End)

EF00 (EFI)

n (New)

2 (GPT 2)

409640 (Start)

591069855 (End)

AF00 (OSX)

n (New)

3 (GPT 3)

591069856 (Start)

592339391 (End)

AB00 (Recovery HD)

n (New)

4 (GPT 4)

666378240 (Start)

977104895 (End)

0700 (Microsoft Basic Data)

p

w

y

Posted on Jul 31, 2016 8:01 PM

Close
MLDalglish

Q: After system image restore, disk contents don't match up

  • All replies
  • Helpful answers

Previous Page 2 of 4 last Next

  • by Loner T,

    Loner T Loner T Jul 27, 2016 9:05 AM in response to MLDalglish
    Level 7 (23,828 points)
    Safari
    Jul 27, 2016 9:05 AM in response to MLDalglish

    Mount it back, and check the directories and files in /Volumes/Bootcamp .

  • by MLDalglish,

    MLDalglish MLDalglish Jul 27, 2016 9:16 AM in response to Loner T
    Level 1 (4 points)
    Windows Software
    Jul 27, 2016 9:16 AM in response to Loner T

    The directories and files are the same as before, no change.

  • by Loner T,

    Loner T Loner T Jul 27, 2016 10:48 AM in response to MLDalglish
    Level 7 (23,828 points)
    Safari
    Jul 27, 2016 10:48 AM in response to MLDalglish

    1. How was the restored Windows System Image created?

    2. How did you restore the Windows System Image? Please describe as much detail as you can.

  • by MLDalglish,

    MLDalglish MLDalglish Jul 28, 2016 7:49 PM in response to Loner T
    Level 1 (4 points)
    Windows Software
    Jul 28, 2016 7:49 PM in response to Loner T

    The image was created via the built-in Windows 7 backup software.

    It was restored via a Windows 7 install/repair disk.

  • by Loner T,

    Loner T Loner T Jul 28, 2016 8:43 PM in response to MLDalglish
    Level 7 (23,828 points)
    Safari
    Jul 28, 2016 8:43 PM in response to MLDalglish

    Was the original and restored partition of different size? Was there an issue you were trying to resolve via the restore?

  • by MLDalglish,

    MLDalglish MLDalglish Jul 29, 2016 2:56 PM in response to Loner T
    Level 1 (4 points)
    Windows Software
    Jul 29, 2016 2:56 PM in response to Loner T

    Yes, they were different sizes. The image was created from a 150 GB partition, and restored to a 197 GB partition.

     

    There was an issue I was trying to resolve, yes. I had extended the size of my Windows Partition from 100 to 150GB, and ever since then the OSX side could not detect the Windows partition, reported empty space, and an unreadable partition labeled s04. I wiped these by restoring Macintosh HD to a single volume and re-partitioning with Boot Camp assistant.

     

    I made another system image last night from the 197 GB partition; should I try a fresh install again to see if restoring to the same size partition would solve the problem?

  • by Loner T,

    Loner T Loner T Jul 29, 2016 4:10 PM in response to MLDalglish
    Level 7 (23,828 points)
    Safari
    Jul 29, 2016 4:10 PM in response to MLDalglish

    The size chronology is 100 -> 150 -> 197 GB.

     

    At 100GB the volume seen from OS X (BOOTCAMP) and C: will match.

     

    At 150 GB the volume seen from OS X and C: will not match due to the differences in MBR and GPT. Such differences manifest as disk0s4 nomenclature in DU, but Windows sees only the MBR.

     

    When the 150 GB partition is restored to a 197 GB, there is a 47GB gap and the Windows side should see a C: of size 150, but OS X sees 197GB. OS X has no way of inquiring inside the volume.

     

    Can you verify that

     

    1. the C: is 150GB as seen in Windows Disk Management,

    2. the OS X volume BOOTCAMP (right-click -> Get Info) should show 197GB.

     

    You can boot from a GParted Live CD and see the disk layout in much more detail with gaps.

     

    Windows Disk Management screen shot and the output of OS X Terminal commands

     

    diskutil list

    sudo gpt -vv -r show /dev/disk0

    sudo fdisk /dev/disk0

     

    should also help in the next step. The "sudo" command will ask for your password, which will not be echoed back to you.

  • by MLDalglish,

    MLDalglish MLDalglish Jul 29, 2016 4:36 PM in response to Loner T
    Level 1 (4 points)
    Windows Software
    Jul 29, 2016 4:36 PM in response to Loner T

    You are correct, Windows does show BOOTCAMP as being 150GB! Well, 147GB, but Windows usually shows numbers that are a bit off from the partitioned size.

     

    Capture.PNG

    OS X shows it as 197 GB.

    Screen Shot 2016-07-29 at 6.32.30 PM.png

    Here is the output of those commands:

     

    Last login: Fri Jul 29 18:33:22 on ttys000

    Kenz$~:  diskutil list

    /dev/disk0

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *500.3 GB   disk0

       1:                        EFI EFI                     209.7 MB   disk0s1

       2:                  Apple_HFS Macintosh HD            302.4 GB   disk0s2

       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3

       4:       Microsoft Basic Data BOOTCAMP                197.0 GB   disk0s4

    Kenz$~:  sudo gpt -vv -r show /dev/disk0

    Password:

    gpt show: /dev/disk0: mediasize=500277790720; sectorsize=512; blocks=977105060

    gpt show: /dev/disk0: Suspicious MBR at sector 0

    gpt show: /dev/disk0: Pri GPT at sector 1

    gpt show: error: bogus map

    gpt show: unable to open device '/dev/disk0': Undefined error: 0

    Kenz$~:   sudo fdisk /dev/disk0

    Disk: /dev/disk0 geometry: 60821/255/63 [977105060 sectors]

    Signature: 0xAA55

             Starting       Ending

    #: id  cyl  hd sec -  cyl  hd sec [     start -       size]

    ------------------------------------------------------------------------

    1: EE    0   0   2 -   25 127  14 [         1 -     409639] <Unknown ID>

    2: 07   25 127  15 - 1023 254  63 [    409640 -  664698912] HPFS/QNX/AUX

    3: AB 1023 254  63 - 1023 254  63 [ 665108552 -    1269536] Darwin Boot

    *4: 07 1023 254  63 - 1023 254  63 [ 666378240 -  309805056] HPFS/QNX/AUX

  • by Loner T,

    Loner T Loner T Jul 29, 2016 5:03 PM in response to MLDalglish
    Level 7 (23,828 points)
    Safari
    Jul 29, 2016 5:03 PM in response to MLDalglish

    Apple uses 1000 as the divisor, while Windows uses 1024, so the small difference between 150 and 147 is not that significant.

     

    The clear issue is the 197GB vs 150GB. Windows System Image restores do not change the partition size.

     

    Your GPT is corrupt. Please download GPT Fdisk from https://sourceforge.net/projects/gptfdisk/ and we can correct the corruption. This will also allow MBR vs GPT mismatches to be addressed.

  • by MLDalglish,

    MLDalglish MLDalglish Jul 29, 2016 7:50 PM in response to Loner T
    Level 1 (4 points)
    Windows Software
    Jul 29, 2016 7:50 PM in response to Loner T

    Is the GPT thing for Mac or Windows?

  • by Loner T,

    Loner T Loner T Jul 29, 2016 8:20 PM in response to MLDalglish
    Level 7 (23,828 points)
    Safari
    Jul 29, 2016 8:20 PM in response to MLDalglish

    The OS which is currently running will determine whether you get OS X or Windows version. The utility works on both OSes.

  • by MLDalglish,

    MLDalglish MLDalglish Jul 30, 2016 7:56 AM in response to Loner T
    Level 1 (4 points)
    Windows Software
    Jul 30, 2016 7:56 AM in response to Loner T

    I downloaded and installed it on the OS X partition of my computer. How do I run it?

  • by Loner T,

    Loner T Loner T Jul 30, 2016 8:01 AM in response to MLDalglish
    Level 7 (23,828 points)
    Safari
    Jul 30, 2016 8:01 AM in response to MLDalglish

    You may want to disable OSX SIP before running Gdisk, in case the GPT needs an update.

     

    1. Boot into Local Recovery (Command+R).

    2. Start Utilities -> Terminal.

    3. Type csrutil disable in Terminal and press Enter/Return.

    4. Type csrutil status.

    5. Boot normally, and type csrutil status to confirm that all individual entries are still disabled.

    Here is the main Gdisk help menu. Please post the output of the 'p' command. If you are asked about choosing a MBR or GPT, use GPT.

    sudo gdisk /dev/disk0

    Password:

    GPT fdisk (gdisk) version 1.0.0

     

    Warning: Devices opened with shared lock will not have their

    partition table automatically reloaded!

    Partition table scan:

      MBR: hybrid

      BSD: not present

      APM: not present

      GPT: present

     

    Found valid GPT with hybrid MBR; using GPT.

     

    Command (? for help): ?

    b back up GPT data to a file

    c change a partition's name

    d delete a partition

    i show detailed information on a partition

    l list known partition types

    n add a new partition

    o create a new empty GUID partition table (GPT)

    p print the partition table

    q quit without saving changes

    r recovery and transformation options (experts only)

    s sort partitions

    t change a partition's type code

    v verify disk

    w write table to disk and exit

    x extra functionality (experts only)

    ? print this menu

  • by MLDalglish,

    MLDalglish MLDalglish Jul 30, 2016 8:17 AM in response to Loner T
    Level 1 (4 points)
    Windows Software
    Jul 30, 2016 8:17 AM in response to Loner T

    Booted into Recovery via Command + R, opened terminal.

     

    When I try "csrutil disable", bash returns "command not found".

    I also tried /usr/bin/csrutil disable and it said no such file or directory exists.

     

    Side note, a lot of help forums talking about csrutil issues mention OS X El Capitan... I have Mavericks, is there a chance I just don't have csrutil?

  • by Loner T,

    Loner T Loner T Jul 30, 2016 8:20 AM in response to MLDalglish
    Level 7 (23,828 points)
    Safari
    Jul 30, 2016 8:20 AM in response to MLDalglish

    Mavericks does not have SIP, so you can skip csrutil steps.

Previous Page 2 of 4 last Next