Unable to mount Bootcamp in Finder after Yosemite update

Question

Unable to mount Bootcamp in Finder after Yosemite update

The Bootcamp partition shows up in DiskUtility but unable to mout it so impossible to see it in System Preferences/Startup disk. On starting up with OPTION key, I can boot normally on Windows XP Pro Edition. From Windows Control Panel, I can choose iMac as the startup disk. The only problem is I can't see my Bootcamp partition in the Finder.

Any help would be really appreciated.

Thanks!

iMac, OS X Yosemite (10.10.1), iMac, 3,06 Ghz Core 2 Duo

Posted on Mar 11, 2015 1:58 PM

Reply

Answer 1

Loner T

Level 9

59,536 points

Mar 11, 2015 2:57 PM in response to Normand Despins

1. Do you have any third-party NTFS software like Tuxera, Paragon, NTFS-3g/NTFS-Free, etc.?

2. DU uses a OS X built-in Apple NTFS driver, which is by default a read-only capable driver. Since you were able to repair it, it is functional.

3. System Preferences -> Startup Disk will block any NTFS volumes from being seen if a third-party driver has control of the volume.

4. The MBR/GPT look correct.

5. Can you post the output sudo dd if=/dev/rdisk0s4 count=1 2>/dev/null | hexdump -C? This will show the first block of the NTFS header. It should be clean, since you can Option-boot Windows.

6. In Finder Preferences, if you enable Hard Disks, what disks can you see?

Reply

Answer 2

Mar 12, 2015 7:19 AM in response to Loner T

Thank-you so much for your time Loner T !

1. Do you have any third-party NTFS software like Tuxera, Paragon, NTFS-3g/NTFS-Free, etc.? Yes I had one when I started the upgrade but since I had problems, I uninstalled Paragon.

2. DU uses a OS X built-in Apple NTFS driver, which is by default a read-only capable driver. Since you were able to repair it, it is functional. All Apple drivers were installed upon installing Windows XP so I didn't touch anything on the Bootcamp partition before upgrading to Yosemite.

3. System Preferences -> Startup Disk will block any NTFS volumes from being seen if a third-party driver has control of the volume. I have uninstalled Paragon the day after the upgrade but didn't return in System Preferences to see if it was gone. Today, I returned just to see and even if the uninstall was successful, Paragon is still there ... Looks strange!!!

4. The MBR/GPT look correct.

5. Can you post the output sudo dd if=/dev/rdisk0s4 count=1 2>/dev/null | hexdump -C? This will show the first block of the NTFS header. It should be clean, since you can Option-boot Windows.

6. In Finder Preferences, if you enable Hard Disks, what disks can you see? Only Macintosh HD

If everything looks good, your remark regarding Paragon makes me think the problem may originate from that software??? Do you have any hint?

Reply

Answer 3

Loner T

Level 9

59,536 points

Mar 12, 2015 7:44 AM in response to Normand Despins

The Paragon uninstaller may still l eave Kernel Extensions on the internal disk. One option you have is to re-install OSX (which will not modify any of your files). Please backup your OSX and Windows installations, if you choose to reinstall OSX.

Please see OS X: About OS X Recovery - Apple Support .

Reply

Answer 4

Mar 12, 2015 1:18 PM in response to Loner T

I'll reinstall OS X and I'll come back with the result!

Thanks !

Reply

Answer 5

Mar 12, 2015 2:38 PM in response to Loner T

Loner T, you're a GENIUS !!! Wow you put the finger right on the spot.

As you mentionned in the previous post, I had 2 extensions in HD/Library/Filesystems (fusefs.fs & prlufs.fs) witch needed to be moved to the trash. I would guess these two extensions were left by an old Parallels Desktop installation. I found on Parallels site a post about that. Here is the post:"Just discovered that Parallels 7 actually doesn't use MacFUSE, it uses a modified version called prlufs.fs. Unfortunately, the upgrade process doesn't remove MacFUSE and neither MacFUSE own installer (fails silently, doesn't actually delete the files)". After a reboot, Bootcamp is back on the Desktop

Thank-you so much for your help. Without your help, I would still be working on that!

Reply

Answer 6

Loner T

Level 9

59,536 points

Mar 12, 2015 4:02 PM in response to Normand Despins

Glas to see it working. Very nice.

Reply

Answer 7

erenacar

Level 1

8 points

Oct 6, 2016 3:04 AM in response to Loner T

Hey LonerT, could you check out my problem as well?

I have been using Windows on my iMac without a problem but today, after i booted MacOS Yosemite (for a simple file control), cannot boot back to Windows again. Didn't have any bootcamp problems before... haven't used any 3rd party disk utility either. The only thing recently I did was increasing Windows partition size 200GB by decreasing MacOS partition via Disk Utility (a month ago, no problem since then, till today)

1. Windows disappeared from Startup Disk

2. Disk utility shows disk0s4 greyed out and cannot be mounted. Moreover, the correct partition size was 700 GB but here its shown as 500GB (which was the old size before increasing it)

3. When i try to reboot with ALT pressed, Windows shows up, but cannot reboot, with a black screen showing “a disk error occurred”

I am not very familiar with any more technicals. I only tried to install “Refind” but cannot succeed anything with it.

I tried your advice above and seems NTFS is there...

Need my Windows ASAP, what more should i do?

I haven't upgraded to Sierra yet. Should I? Or will it make worse?

I have tons of files on Windows that I need and unfortunately not backed up anywhere (very sorry about it now).

Please help...

Reply

Answer 8

erenacar

Level 1

8 points

Oct 6, 2016 3:41 AM in response to erenacar

one more thing... when I try to verify disk0s4, says "it needs to be repaired". when i hit repair; it says this:

Reply

Answer 9

Loner T

Level 9

59,536 points

Oct 6, 2016 5:41 AM in response to erenacar

Can you start a new discussion and post this information on the new discussion? You do not have the same issue as the OP and it may confuse future readers when two different issues are tackled in the same discussion.

Do not upgrade to Sierra.

Reply