Resized Boot Camp partition; now have "disk0s4"

Question

Resized Boot Camp partition; now have "disk0s4"

Following this blog post:

http://blog.craigharvey.me/2012/09/02/resize-boot-camp-partition-for-free-window s-8/

I resized my Boot Camp partition to give Windows 7 more space. In Disk Utility on OS X ML, I reduced the size of my OS X partition. I booted into Windows and did a chkdsk /f. Then I ran the freeware program to extend the size of the Boot Camp Windows partition to take the unallocated space as its own.

I can boot into OS X fine.

I can boot into Windows 7 fine.

I've run chkdsk /f again on Windows 7 to repair the disk.

The problem is that now I cannot access my Boot Camp partition from OS X like I used to be able to. Disk Utility shows an unmountable disk0s4 drive instead of "BOOTCAMP".

Can anyone help me regain access to my Boot Camp partition (read only) so that I can copy files from my Windows partition to my OS X partition?

Ideally I would like to avoid deleting the Windows partition and recreating it using Boot Camp Assistant.

Thanks

MacBook Pro, OS X Mountain Lion

Posted on Dec 4, 2012 1:00 PM

Reply

Answer 1

Kappy

Level 10

361,741 points

Dec 4, 2012 1:04 PM in response to ruffellprefley

Try using Boot Runner.

Reply

Answer 2

Dec 4, 2012 1:17 PM in response to Kappy

Hmm.. I think we're looking for different solutions.

To clarify, I can boot into Windows 7 by holding the option button down at startup with no problems.

I want to be able to access the Boot Camp partition (drive) from within OS X to be able to copy files from the Windows partition to the OS X partition: computer game screen captures, for example.

I used to be able to do this until I increased the size of the W7 partition without deleting/recreating it.

Reply

Answer 3

Kappy

Level 10

361,741 points

Dec 4, 2012 1:30 PM in response to ruffellprefley

In Disk Utility did you try selecting the device then clicking on the Mount icon?

Reply

Answer 4

Dec 4, 2012 2:13 PM in response to Kappy

I did try manually mounting in DU, yes; unfortunately that doesn't appear to do anything with this volume.

Reply

Answer 5

Kappy

Level 10

361,741 points

Dec 4, 2012 2:19 PM in response to ruffellprefley

I don't have a solution, then. There have been other reports of your same problem, but no apparent solution. Something must have gone wrong leaving the volume in an unknown state, which is usually why you end up with a partition reported like yours.

Reply

Answer 6

Kappy

Level 10

361,741 points

Dec 4, 2012 2:28 PM in response to ruffellprefley

Something comes to mind from back when Lion was first released relating to installation issues with OS X and Boot Camp.

I believe the problem was fixed by booting into Windows repair mode then using ChkDsk to repair the Windows volume. Maybe you should give that a try and see what happens.

Reply