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

first Previous Page 4 of 4

  • by Loner T,

    Loner T Loner T Aug 1, 2016 3:07 AM in response to MLDalglish
    Level 7 (23,828 points)
    Safari
    Aug 1, 2016 3:07 AM in response to MLDalglish

    What is the year/model of your Mac?

     

    You will need to use a DVD or a USB+W10 ISO to build a Windows installer and run a Startup Repair.

     

    In Test 2, does the Bootcamp directory contain familiar Windows files?

  • by MLDalglish,

    MLDalglish MLDalglish Aug 1, 2016 12:35 PM in response to Loner T
    Level 1 (4 points)
    Windows Software
    Aug 1, 2016 12:35 PM in response to Loner T

    15" Retina Macbook Pro, Late 2013.

    More specifically, MacBookPro11,3.

     

    I will be doing that later this evening; I'll tell you how that goes when it finishes.

    Does Windows 10 support USB 3.0 natively? I'll need to know whether to put drivers on the Bootcamp partition to install or not.

     

    As for Test 2, the Bootcamp directory's files matched up perfectly.

  • by Loner T,

    Loner T Loner T Aug 1, 2016 2:46 PM in response to MLDalglish
    Level 7 (23,828 points)
    Safari
    Aug 1, 2016 2:46 PM in response to MLDalglish

    It may be safer to use a USB2, till BC drivers are installed on W10.

     

    Good to see the files now match.

  • by MLDalglish,

    MLDalglish MLDalglish Aug 1, 2016 4:11 PM in response to Loner T
    Level 1 (4 points)
    Windows Software
    Aug 1, 2016 4:11 PM in response to Loner T

    Okay, so I created a recovery disk using another computer and...

    Actually, it boots right up, no issues, from the recovery disk. But I still can't boot from the partition itself; it still BSODs.

     

    I also tried removing the recovery USB after booting up and nothing functioned, so it seems the recovery USB is supporting everything.

     

    ...Any ideas?

     

    EDIT: Was able to fix the boot issue using some command prompt commands. I will check to see if OS X still reads the partition correctly.

     

    EDIT2: Yep, it reads the partition correctly still. You mentioned something about growing the drive using some program, what would that be? And how do I do it?

  • by Loner T,

    Loner T Loner T Aug 1, 2016 4:33 PM in response to MLDalglish
    Level 7 (23,828 points)
    Safari
    Aug 1, 2016 4:33 PM in response to MLDalglish

    Usually, bootrec.exe can address quite a few issues.

     

    For the gap to be absorbed you will need to use a GParted Live CD or Live USB. Please see http://www.howtogeek.com/howto/windows-vista/using-gparted-to-resize-your-window s-vista-partition/ as an example. W10 should work similarly to Vista/W7. Before you go down this path, please make backups.

  • by MLDalglish,

    MLDalglish MLDalglish Aug 7, 2016 5:45 PM in response to Loner T
    Level 1 (4 points)
    Windows Software
    Aug 7, 2016 5:45 PM in response to Loner T

    Oooooooook. So I followed those instructions for GParted...I'm now met with "Missing Operating System" on startup.

     

    Went into cmd with a recovery disk and ran

     

    bootrec /scanos

    bootrec /rebuildbcd

    bootrec /fixmbr

    bootrec /fixboot

     

    scanos and fixmbr completed successfully but rebuildbcd and fixboot claimed the volume did not contain a known file system type (although rebuildbcd did recognize both windows and windows.old).

     

    ran chkdsk /r, no problems reported.

     

    Now what? I really, really do not want to reset my system because reinstalling everything takes such a long time.
    I have both a backup and a recent system image if necessary.

  • by Loner T,

    Loner T Loner T Aug 7, 2016 5:46 PM in response to MLDalglish
    Level 7 (23,828 points)
    Safari
    Aug 7, 2016 5:46 PM in response to MLDalglish

    Please post the output of

     

    sudo gpt -vv -r show /dev/disk0

    sudo fdisk /dev/disk0

  • by MLDalglish,

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

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

    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: /dev/disk0: Sec GPT at sector 977105059

          start       size  index  contents

              0          1         MBR

              1          1         Pri GPT header

              2         32         Pri GPT table

             34          6        

             40     409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B

         409640  630881192      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC

      631290832    1269536      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

      632560368       1296        

      632561664  344543232      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

      977104896        131        

      977105027         32         Sec GPT table

      977105059          1         Sec GPT header

    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   1 - 1023 254  63 [         1 -     409639] <Unknown ID>

    *2: AF 1023 254  63 - 1023 254  63 [    409640 -  630881192] HFS+       

    3: AF 1023 254  63 - 1023 254  63 [ 631290832 -    1269536] HFS+       

    4: 07 1023 254  63 - 1023 254  63 [ 632561664 -  344543232] HPFS/QNX/AUX

     

     

    ...I should mention I decided against the whole 35GB, extended OSX to 323GB, and then used GParted to give Windows the leftover space.

  • by MLDalglish,

    MLDalglish MLDalglish Aug 7, 2016 6:10 PM in response to MLDalglish
    Level 1 (4 points)
    Windows Software
    Aug 7, 2016 6:10 PM in response to MLDalglish

    Also, I just remembered... when I ran GParted, it said something like the journal was messed up so it edited the filesystem... which honestly can't be good.

     

    And I didn't seem to be able to edit my post.

  • by Loner T,Helpful

    Loner T Loner T Aug 7, 2016 7:21 PM in response to MLDalglish
    Level 7 (23,828 points)
    Safari
    Aug 7, 2016 7:21 PM in response to MLDalglish

    Your MBR is incorrect. Please ignore the i386 MBR error, but not any other messages, in the following steps.

     

    sudo fdisk -e /dev/disk0

    p

    setpid 3

    AB

    setpid 4

    07

    flag 4

    p

    w

    y

     

    Reboot and test.

  • by MLDalglish,

    MLDalglish MLDalglish Aug 7, 2016 6:34 PM in response to Loner T
    Level 1 (4 points)
    Windows Software
    Aug 7, 2016 6:34 PM in response to Loner T

    That worked! Well, more specifically, it brought me to the same BSOD as before... so I ran the bootrec commands and now I'm posting from Windows. Going to check that OSX still reads the disk...

     

    EDIT: Yep, OSX still sees the partition correctly. Thanks for all your help!

  • by Loner T,

    Loner T Loner T Aug 7, 2016 8:35 PM in response to MLDalglish
    Level 7 (23,828 points)
    Safari
    Aug 7, 2016 8:35 PM in response to MLDalglish

    Please back up OS X, Windows and create a Windows System Restore point.

first Previous Page 4 of 4