Previous 1 78 79 80 81 82 Next 1,467 Replies Latest reply: Jun 20, 2015 10:52 AM by ManeeshAgarwal Go to original post Branched to a new discussion.
  • Christopher Murphy Level 3 Level 3 (555 points)

    Booted back to OSX to see if Finder recognized the partition, but it didn't.

     

    That isn't a good sign. Are you sure you only resized OS X's volume? You didn't resize or try to resize the Bootcamp volume in either OS X or in Windows did you? If you didn't, that NTFS volume should still be valid and mount read-only in OS X. It's possible there's a problem that causes even read-only mount to fail.

     

    I'd try booting the Windows installer, get to a command prompt, and see if chkdsk without options finds a valid NTFS volume and if it needs repairs. If it's found, but not prestine, then it needs to be fixed with chkdsk /f If that also doesn't find anything, then it sounds like you're in test disk territory.

  • Christopher Murphy Level 3 Level 3 (555 points)

    The 1MB boundary alignment can be confusing.

     

    All I look for are very large unallocated gaps. And to make sure the start-size values match between fdisk and gpt outputs. And that the Bootcamp MBR partition is type code 07 and flagged bootable. That's basically it. The really confusing part is inferring what the prior state was based on the existing state minus the poster's description of exactly what they did.

  • Loner T Level 6 Level 6 (9,065 points)

    Christopher Murphy wrote:

     

    The 1MB boundary alignment can be confusing.

     

    All I look for are very large unallocated gaps. And to make sure the start-size values match between fdisk and gpt outputs. And that the Bootcamp MBR partition is type code 07 and flagged bootable. That's basically it. The really confusing part is inferring what the prior state was based on the existing state minus the poster's description of exactly what they did.

    Resizing using OSX DU and Windows tools is where most posters step on themselves. Despite Apple warnings, this is a huge hole.

     

    It just makes me nervous to see gaps with possible MBR corruption. I do realise that boundary allignment can also cause this.

     

    I should have mentioned to ipecek and NUvect to start separate threads to avoid confusion.

     

    In NUvect's case I did not realise that drivers are removed in the cloning/migration process.

  • jamie.shaw Level 1 Level 1 (5 points)

    I too, have ran into issues with bootcamp recently and with a lack of terminal knowledge, am stumped at which process might help me.

     

    Last night, I was using Bootcamp fine through VMware Fusion, no issue at all.  I shut the VM down correctly and closed VMware.

    Later that evening, I was trying to copy files onto my iPad through iTunes and got the warning that I didn't have permissions to view the contents of that file – I checked file info, I do, and also transferred the same file to my iPhone no more than 5 minutes prior.

     

    Just in case, I booted into the recovery partition on 10.9.2 and ran permission and disk checks.  When verifying the entire disk however, I got the error "The partition map needs to be repaired because there's a problem with the EFI system partition's file system".
    A repair couldn't be done on the live disk so I booted back into OS X and created a recovery USB.  From this, I ran the repairs to the entire disk, and repaired the permissions and disk for my Mac HD partition, and then checked the disk again in the recovery partition and whilst in OS X – the error is no longer registering.

     

    From here – I no longer have access to Bootcamp.  The partition is mounting in Finder, and viewable in Disk Utility. It even appears in the "Startup Disk" pref pane.  Before I booted into the recovery partition using the "alt" key, the Windows parition was there.  Since that error, it's no longer available.

    Selecting the partition in "Startup disk" just results in a blank screen on boot.

     

    I've not resized the partition, nor have I changed any disk sizes.

    I did run the following commands following the iTunes issue in an attempt to correct:

     

    sudo chmod a+rx /volumes/*
    sudo chflags 0 /volumes/*

     

    Could that have caused an issue?

     

    I understand I can probably remove the partition and start again, but that defeats the point.  Surely there must be a fix through command line or something?

     

    Kind regards, and thanks in advance,

    Jamie

  • jamie.shaw Level 1 Level 1 (5 points)

    Oh, and here's the output through the various terminal commands:

     

    // sudo gpt -r -vv show disk0
    ------------------------------------------------------------------------------
    gpt show: disk0: mediasize=500277790720; sectorsize=512; blocks=977105060
    gpt show: disk0: PMBR at sector 0
    gpt show: disk0: Pri GPT at sector 1
    gpt show: disk0: Sec GPT at sector 977105059
          start       size  index  contents
              0          1         PMBR
              1          1         Pri GPT header
              2         32         Pri GPT table
             34          6        
             40     409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
         409640  876953152      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
      877362792    1269536      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
      878632328        632        
      878632960   97755136      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
      976388096     716931        
      977105027         32         Sec GPT table
      977105059          1         Sec GPT header
     
     
     
    // 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 1023 254  63 - 1023 254  63 [         1 -  977105059]
    2: 00    0   0   0 -    0   0   0 [         0 -          0] unused     
    3: 00    0   0   0 -    0   0   0 [         0 -          0] unused     
    4: 00    0   0   0 -    0   0   0 [         0 -          0] unused   



    // 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            449.0 GB   disk0s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
       4:       Microsoft Basic Data Windows HD              50.1 GB    disk0s4

  • Number88 Level 3 Level 3 (750 points)

    What model/year of Mac is this on please?

  • jamie.shaw Level 1 Level 1 (5 points)

    This is a late 2013 15" MacBook Pro with Retina Display, on it's internal 512GB SSD.

  • Number88 Level 3 Level 3 (750 points)

    Please go to the site below and use "option three" and give the output that you see.

    You can do this in a Finder Window using Bootcamp as "C:"

     

    http://www.eightforums.com/tutorials/29504-bios-mode-see-if-windows-boot-uefi-le gacy-mode.html

  • jamie.shaw Level 1 Level 1 (5 points)

    I had a look, but there doesn't appear to be a "Pather" folder in the Windows directory.  I had a google to see if there are any alternate locations; I found a "Setupact.log" in the Windows directory itself but this doesn't mention any reference to "EFI", "BIOS" or "BOOT".

  • Number88 Level 3 Level 3 (750 points)

    You mean "panther" - could you re-check please?

    I don't know what to say then.

    If your Windows is installed EFI then your fdisk output is correct. If Windows was installed in BIOS mode then your fdisk output is not correct and could cause your problem.

  • jamie.shaw Level 1 Level 1 (5 points)

    Apologies, mistype.  Yup, definitely no "Panther" folder in "C:\Windows\".

     

    Is there something that could have flipped it from EFI to BIOS?  I've had Windows 8 installed since I bought this laptop late last year and Windows has ran fine.

  • Number88 Level 3 Level 3 (750 points)

    Not really.

    As you haven't actually done any partitioning since Windows was installed your questions don't really belong in this thread.

    I suggest you make a new thread describing exactly what's happened and where you are now.

    And try to remember (or find out) whether Windows was installed in EFImode or in CSM (bios) mode.

    Sorry I can't be more helpful.

  • Loner T Level 6 Level 6 (9,065 points)

    jamie.shaw wrote:

     

    Apologies, mistype.  Yup, definitely no "Panther" folder in "C:\Windows\".

     

    Is there something that could have flipped it from EFI to BIOS?  I've had Windows 8 installed since I bought this laptop late last year and Windows has ran fine.

    From the OS X  Terminal, please run bless --info --verbose and look for the highlighted part...

     

    filesystem[2] '/dev/disk0s4' => '/Volumes/BOOTCAMP'

    Firmware feature mask: 0xE003FF37

    Firmware features: 0xE003F537

    Legacy mode suppported

    Got IODeviceTree:/rom

    Got start address ff990000

    Got size 1a0000

    Found PCI interconnect in protocol characteristics

    IOGUIDPartitionScheme

    APPLE SSD SM1024F Media

      IOBlockStorageDriver

       IOAHCIBlockStorageDevice

        AppleAHCIDiskDriver

         IOAHCIDevice

          PRT0

           AppleAHCI

            SSD0

             IOPP

              RP05

               AppleACPIPCI

                PCI0

                 AppleACPIPlatformExpert

                  MacBookPro11,3

                   Root

     

    Matching legacy device 'disk0s4'

    Legacy boot device detected

    mount: /Volumes/BOOTCAMP

     

    Mount point for /Volumes/BOOTCAMP is /Volumes/BOOTCAMP

    GPT detected

    Booter partition required at index 5

    System partition found

    Preferred system partition found: disk0s1

  • jamie.shaw Level 1 Level 1 (5 points)

    Hi Loner T,

     

    I ran "bless --info --verbose" in terminal and got the following results; none of which looks like what you have posted. :/

     

    EFI found at IODeviceTree:/efi

    Current EFI boot device string is: '<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia </string><key>IOPropertyMatch</key><dict><key>UUID</key><string>3B757275-3373-46 3B-9F6D-FDEF74395D5F</string></dict></dict><key>BLLastBSDName</key><string>disk0 s2</string></dict></array>'

    Boot option is 8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Boot0080

    Processing boot option 'Mac OS X'

    Boot option matches XML representation

    Found device: disk0s2

    Disk boot device detected

    mount: /

    Mount point for / is /

    GPT detected

    No auxiliary booter partition required

    System partition found

    Preferred system partition found: disk0s1

    Returning booter information dictionary:

    <CFBasicHash 0x7f8e195001d0 [0x7fff74fbdf00]>{type = mutable dict, count = 3,

    entries =>

              0 : <CFString 0x10e3d3e70 [0x7fff74fbdf00]>{contents = "System Partitions"} = (

        disk0s1

    )

              1 : <CFString 0x10e3d4650 [0x7fff74fbdf00]>{contents = "Data Partitions"} = (

        disk0s2

    )

              2 : <CFString 0x10e3d4670 [0x7fff74fbdf00]>{contents = "Auxiliary Partitions"} = (

    )

    }

     

    finderinfo[0]: 457078 => Blessed System Folder is /System/Library/CoreServices

    finderinfo[1]: 8279379 => Blessed System File is /System/Library/CoreServices/boot.efi

    finderinfo[2]:      0 => Open-folder linked list empty

    finderinfo[3]:      0 => No alternate OS blessed file/folder

    finderinfo[4]:      0 => Unused field unset

    finderinfo[5]: 457078 => OS X blessed folder is /System/Library/CoreServices

    64-bit VSDB volume id:  0x451C89A8F69D10BB

  • Loner T Level 6 Level 6 (9,065 points)

    jamie.shaw wrote:

     

    Hi Loner T,

     

    I ran "bless --info --verbose" in terminal and got the following results; none of which looks like what you have posted. :/

    Your EFI repair seems to have messed the MBR. For a Bootcamp installation, on my system, this is what I have in the MBR (I have an rMBP and it is a "regular" Bootcamp with W7 (not W8)).

     

    sudo fdisk /dev/disk0

    Disk: /dev/disk0          geometry: 121643/255/63 [1954210120 sectors]

    Signature: 0xAA55

             Starting       Ending

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

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

    1: EE 1023 254  63 - 1023 254  63 [         1 -     409639] <Unknown ID>

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

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

    *4: 07 1023 254  63 - 1023 254  63 [1454211072 -  499998720] HPFS/QNX/AUX

     

    Your GPT looks good (I just did the start+size which does point to the start of the next GPT part).

     

     

     

    If Windows does not boot AND your MBR is corrupted, more than likely you have a "legacy" (aka CSM-BIOS) installation.

     

    My recommendation is to use gdisk (GPT fdisk) from SourceForge and correct your MBR to see if W8 will boot. Number88 has a good set of steps to recreate the MBR via gdisk. I suggest you create a backup of the whole disk and your bootcamp partitions, both, before you start tinkering with the MBR.

Previous 1 78 79 80 81 82 Next