Frank-APP

Q: bootcamp partition no longer mountable

I was trying to get OSX to be able to read the 2 Windows partitions( named System and Data repectively). Maybe due to installations of Paragon and Tuxera, now the System partition no longer mountable in OS X,  the Data partition is still accessible.

 

I have read LonerT's instructions to other similar problems, and here are the results of those routine checks:

 

localhost:~ Leibniz$ diskutil list

/dev/disk0 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *500.3 GB   disk0

   1:                        EFI EFI                     209.7 MB   disk0s1

   2:          Apple_CoreStorage Macintosh HD            199.4 GB   disk0s2

   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3

   4:       Microsoft Basic Data Untitled                150.6 GB   disk0s4

   5:       Microsoft Basic Data Data                    149.4 GB   disk0s5

/dev/disk1 (internal, virtual):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:                  Apple_HFS Macintosh HD           +199.0 GB   disk1

                                 Logical Volume on disk0s2

                                 65526698-B9FC-4FC5-A4D6-379C934E289C

                                 Unlocked Encrypted

 

 

localhost:~ Leibniz$ sudo gdisk -l /dev/disk0

Password:

GPT fdisk (gdisk) version 1.0.1

 

Warning: Devices opened with shared lock will not have their

partition table automatically reloaded!

Partition table scan:

  MBR: protective

  BSD: not present

  APM: not present

  GPT: present

 

Found valid GPT with protective MBR; using GPT.

Disk /dev/disk0: 977105060 sectors, 465.9 GiB

Logical sector size: 512 bytes

Disk identifier (GUID): E58684AF-9C11-4E9B-BCAF-2B812CDC8F7B

Partition table holds up to 128 entries

First usable sector is 34, last usable sector is 977105026

Partitions will be aligned on 8-sector boundaries

Total free space is 2185 sectors (1.1 MiB)

 

Number  Start (sector)    End (sector)  Size       Code  Name

   1              40          409639   200.0 MiB   EF00  EFI System Partition

   2          409640       389775583   185.7 GiB   AF05  Customer

   3       389775584       391045119   619.9 MiB   AB00  Recovery HD

   4       391045120       685228031   140.3 GiB   0700  BOOTCAMP

   5       685228032       977102847   139.2 GiB   0700  Basic data partition

localhost:~ Leibniz$ sudo gpt -r -vv show disk0

Password:

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  389365944      2  GPT part - 53746F72-6167-11AA-AA11-00306543ECAC

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

  391045120  294182912      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

  685228032  291874816      5  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

  977102848       2179        

  977105027         32         Sec GPT table

  977105059          1         Sec GPT header

 

 

localhost:~ Leibniz$ sudo fdisk /dev/disk0

Password:

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] <Unknown ID>

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     

localhost:~ Leibniz$ diskutil list

/dev/disk0 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *500.3 GB   disk0

   1:                        EFI EFI                     209.7 MB   disk0s1

   2:          Apple_CoreStorage Macintosh HD            199.4 GB   disk0s2

   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3

   4:       Microsoft Basic Data System                  150.6 GB   disk0s4

   5:       Microsoft Basic Data Data                    149.4 GB   disk0s5

/dev/disk1 (internal, virtual):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:                  Apple_HFS Macintosh HD           +199.0 GB   disk1

                                 Logical Volume on disk0s2

                                 65526698-B9FC-4FC5-A4D6-379C934E289C

                                 Unlocked Encrypted

 

 

 

TestDisk 7.0, Data Recovery Utility, April 2015

Christophe GRENIER <grenier@cgsecurity.org>

http://www.cgsecurity.org

 

Disk /dev/disk0 - 500 GB / 465 GiB - 977105060 sectors (RO)

Current partition structure:

     Partition                  Start        End    Size in sectors

 

1 P EFI System                    40     409639     409600 [EFI System Partition]

2 P Unknown                   409640  389775583  389365944 [Customer]

3 P Mac Boot               389775584  391045119    1269536 [Recovery HD]

Warning: number of heads/cylinder mismatches 255 (NTFS) != 1 (HD)

Warning: number of sectors per track mismatches 63 (NTFS) != 1 (HD)

4 P MS Data                391045120  685228031  294182912 [BOOTCAMP]

Warning: number of heads/cylinder mismatches 255 (NTFS) != 1 (HD)

Warning: number of sectors per track mismatches 63 (NTFS) != 1 (HD)

5 P MS Data                685228032  977102847  291874816 [Basic data partition]

]]

 

is it normal that fdisk has only 1 line? should have at least 4 here?  Testdisk can't print out filenames, reporting something is damaged...


Please HELP!! Many Many Thanks!!

Posted on Sep 4, 2016 7:24 AM

Close

Q: bootcamp partition no longer mountable

  • All replies
  • Helpful answers

first Previous Page 3 of 3
  • by Loner T,

    Loner T Loner T Sep 6, 2016 9:27 AM in response to Frank-APP
    Level 7 (23,493 points)
    Safari
    Sep 6, 2016 9:27 AM in response to Frank-APP

    Please see http://kb.parallels.com/en/114053 as an example.

  • by Frank-APP,

    Frank-APP Frank-APP Sep 6, 2016 9:46 AM in response to Loner T
    Level 1 (4 points)
    Windows Software
    Sep 6, 2016 9:46 AM in response to Loner T

    yes, did accordingly! but this procedure can adds folds/drives that already visible in Mac Finder. Again, System partition is not mountable in Mac to begin with... Am I mistaken?

  • by Loner T,

    Loner T Loner T Sep 6, 2016 9:49 AM in response to Frank-APP
    Level 7 (23,493 points)
    Safari
    Sep 6, 2016 9:49 AM in response to Frank-APP

    What is the output of the following OSX Terminal command?

     

    diskutil list

  • by Frank-APP,

    Frank-APP Frank-APP Sep 6, 2016 9:51 AM in response to Loner T
    Level 1 (4 points)
    Windows Software
    Sep 6, 2016 9:51 AM in response to Loner T

    /dev/disk0 (internal, physical):

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *500.3 GB   disk0

       1:                        EFI EFI                     209.7 MB   disk0s1

       2:          Apple_CoreStorage Macintosh HD            199.4 GB   disk0s2

       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3

       4:       Microsoft Basic Data System                  150.6 GB   disk0s4

       5:       Microsoft Basic Data Data                    149.4 GB   disk0s5

    /dev/disk1 (internal, virtual):

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                  Apple_HFS Macintosh HD           +199.0 GB   disk1

                                     Logical Volume on disk0s2

                                     65526698-B9FC-4FC5-A4D6-379C934E289C

                                     Unlocked Encrypted

  • by Loner T,

    Loner T Loner T Sep 6, 2016 10:14 AM in response to Frank-APP
    Level 7 (23,493 points)
    Safari
    Sep 6, 2016 10:14 AM in response to Frank-APP

    Did you have the System partition imported as a VM in Parallels in the past? Can you test importing disk0s4 as a VM in Parallels? It should run chkdsk or report an error.

  • by Frank-APP,

    Frank-APP Frank-APP Sep 6, 2016 10:19 AM in response to Loner T
    Level 1 (4 points)
    Windows Software
    Sep 6, 2016 10:19 AM in response to Loner T

    Yes, both NTFS partitions were automatically mounted by Parallels back in the old days. How to import disk0s4 as a VM in Parallels?

  • by Loner T,

    Loner T Loner T Sep 6, 2016 2:07 PM in response to Frank-APP
    Level 7 (23,493 points)
    Safari
    Sep 6, 2016 2:07 PM in response to Frank-APP

    Let us try a simpler repair first, since you have Testdisk.  In the Advanced menu, select your System NTFS partition, choose Boot, then Repair MFT.

  • by Frank-APP,

    Frank-APP Frank-APP Sep 6, 2016 4:15 PM in response to Loner T
    Level 1 (4 points)
    Windows Software
    Sep 6, 2016 4:15 PM in response to Loner T

    Just asking, you think the route of using NTFS tools (e.g. chkdsk from a windows VM) to repair NTFS partitions in OS X  is no longer possible? Remember you cautioned against using NTFS MTF tools to alter OS X's GPT and vice versa ...?

  • by Loner T,

    Loner T Loner T Sep 6, 2016 4:18 PM in response to Frank-APP
    Level 7 (23,493 points)
    Safari
    Sep 6, 2016 4:18 PM in response to Frank-APP

    It is valid, provided disk0s4 can be imported in the first place. If the issue is only MFT, it is faster to use Testdisk.

     

    The Parallels import is http://kb.parallels.com/en/112941 - Option 1.

     

    Try one or the other method.

  • by Frank-APP,

    Frank-APP Frank-APP Sep 6, 2016 8:10 PM in response to Loner T
    Level 1 (4 points)
    Windows Software
    Sep 6, 2016 8:10 PM in response to Loner T

    Following the instructions listed in http://kb.parallels.com/en/112941 - Option 1, at this step "From the Source drop-down list, choose your physical Boot Camp partition:"   my bootcamp partition System(disk0s4) was not listed at all. I guess VM import requires the bootcamp partition is mountable in Mac  Any other possibilities for a NTFS chkdsk on /dev/disk0s4?

     

    For the testdisk option, is there a risk of using teskdisk to repair MFT?

    steps I did so far is

     

    ./testdisk  -> append log -> choose /dev/disk0 to proceed -> to this menu

     

    Disk /dev/disk0 - 500 GB / 465 GiB (RO)

     

    Write access for this media is not available.

    TestDisk won't be able to modify it.

     

    - No partition from this disk must be mounted:

    Open the Disk Utility (In Finder -> Application -> Utility folder)

    and press Unmount button for each volume from this disk

    - This media may be physically write-protected, check the jumpers.

     

    >[ Continue ] Continue even if write access isn't available

     

     

    it says no write permission...   waiting for your confirmations to proceed

     

    here I detoured into DU and umounted Data, and remounted it then try to mount System as well, here is the System.log reports:

     

    Mounting Data partition (/dev/disk0s5):

    9/7/16 11:03:46.000 AM kernel[0]: NTFS volume name Data, version 3.1.

    9/7/16 11:03:46.000 AM kernel[0]: NTFS-fs warning (device /dev/disk0s5, pid 9118): ntfs_system_inodes_get(): NTFS volume is dirty.  You should unmount it and run chkdsk.

    9/7/16 11:03:46.589 AM mds[60]: (Volume.Normal:2464) volume:0x7f8273831800 ********** Bootstrapped Creating a default store:1 SpotLoc:(null) SpotVerLoc:(null) occlude:0 /Volumes/Data

     

    Mountting System partition (/dev/disk0s4):

    9/7/16 11:07:19.000 AM kernel[0]: NTFS-fs error (device /dev/disk0s4, pid 9140): ntfs_attr_find_in_attribute_list(): Base inode 0x5 contains corrupt attribute list attribute. Unmount and run chkdsk.

    9/7/16 11:07:19.000 AM kernel[0]: NTFS-fs error (device /dev/disk0s4, pid 9140): ntfs_index_inode_read(): Failed to lookup index root attribute.

    9/7/16 11:07:19.000 AM kernel[0]: NTFS-fs error (device /dev/disk0s4, pid 9140): ntfs_index_inode_read(): Failed (error 5) for index inode 0x5, index name_len 0x4.  Run chkdsk.

    9/7/16 11:07:19.000 AM kernel[0]: NTFS-fs error (device /dev/disk0s4, pid 9140): ntfs_inode_get(): Failed to get index inode.

    9/7/16 11:07:19.000 AM kernel[0]: NTFS-fs error (device /dev/disk0s4, pid 9140): ntfs_inode_attach(): Failed to load inode 0x5.

    9/7/16 11:07:19.000 AM kernel[0]: NTFS-fs error (device /dev/disk0s4, pid 9140): ntfs_system_inodes_get(): Failed to load root directory.

    9/7/16 11:07:19.000 AM kernel[0]: NTFS-fs error (device /dev/disk0s4, pid 9140): ntfs_mount(): Failed to load system files (error 5).

    9/7/16 11:07:19.000 AM kernel[0]: NTFS-fs error (device /dev/disk0s4, pid 9140): ntfs_mount(): Mount failed (error 5).

    9/7/16 11:07:19.722 AM diskarbitrationd[66]: unable to mount /dev/disk0s4 (status code 0x00000047).

    9/7/16 11:07:19.722 AM storagekitd[9060]: Mount of disk0s4 blocked by dissenter PID=0 (kernel) status=0x0000c047 (Too many levels of remote in path)

    9/7/16 11:07:19.831 AM Disk Utility[9059]: Could not mount disk: Error Domain=com.apple.DiskManagement Code=49223 "(null)" UserInfo={DissenterPID=0, Dissenter=true, Target=disk0s4, Action=Mount, DissenterStatus=49223}

     

    It also suggests doing chkdsk on the two partitions... which chkdsk?

first Previous Page 3 of 3