Can't boot into windows after resizing partitions

i am sorry, i meant camptune - i think it has capability to resize both os 10 and windows partitions on a mac with a single ssd

My experience with Camptune is limited to some testing. It does work.

I would like to give it a shot, although I'm not sure how successful I'll be with the file exit code 8 that seems to re-appear after I use disk utility in recovery mode as well as when I use fsck.

It seems that 1 reboot after I fix the file system, exit code 8 comes back. this error causes me problems with clonezilla since it will not create the disk image if there is this error. I am usually able to create the image right after fixing the error.

can someone tell me if file exit code 8 is related to an OS/software issue or whether it's related to a hardware issue ? having trouble finding in-depth info related to this error.

after I figure it all out and fix the issue I would then proceed to redistribute my partition sizes with camptune.

Is it possible to post the output of fsck? In Internet Recovery, if you run diskutil repairDisk disk0, can you post a screen shot/image of it?

i will try to copy the output when i run fsck -fy.

i used to run this command in single user mode, running it twice it seems that it fixes the error. but it returns after 1 reboot.

more recently i have tried running disk utility in recovery mode. since then i have restarted into OS X a couple of times, restarted into windows and back to OS X, and the file exit code 8 hasn't appeared, 'yet'

when/if it does, i will post the output

You can also boot from an external OS X installation - How to install OS X on an external drive connected to your Mac - Apple Support - and run fsck and/or repairDisk. Do you have a CoreStorage volume on your source disk?

Cloning a drive using Clonezilla also includes UUIDs of the source disk. If both old and new disks are connected to the system simultaneously, file corruption is possible. Consider GPT Fdisk to change the UUIDs of the new cloned disk to avoid such issues.

ok, so i am getting file exit code 8 within DU. unfortunately i cannot find any log files to copy/paste the output.

instead i ran fsck -fy from single-user mode then took a snapshot of the output displayed. i'm sorry if this is crude, didn't have any other way to do it at this time.

or if there are log files stored somewhere i can just dig them up and post. in the meantime, this is what i have:

https://drive.google.com/file/d/0B5FH3snPwEXydmdZYUJTM0U3bzQ/view?usp=sharing

Is this the original disk, or a cloned disk on which DU returns error code 8. Unix error code 8 is a when a binary which is invalid for the platform is executed. Is there a POSIX error code?

Are you able to boot normally into OS X? If yes, can you post the output of diskutil repairDisk disk0 ?

Loner T,

this is a single SSD on a late 2013 macbook pro. the SSD is 256 GB, I have loaded windows on the partition i created using bootcamp.

i bounce between OS's frequently. Everything works fine in OS 10, boots normally, runs fine (except that my finder is unresponsive after a fresh boot - relaunch fixes that).

i attempted to run the command you suggested, it wants to delete the EFI partition.

Admins-MBP:~ adminuser$ diskutil repairDisk disk0

Repairing the partition map might erase disk0s1, proceed? (y/N) n

Repair canceled

Here's what partitions are on the SSD now:

Admins-MBP:~ adminuser$ diskutil list

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *251.0 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_HFS Macintosh HD 60.0 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

4: Microsoft Basic Data Windows 189.8 GB disk0s4

Disk0s1 is Mac's EFI. DU will put down a new EFI, if necessary. I have rarely seen it being actually erased.

If you can run the repair in Internet Recovery, it may be a safer option.

after fixing the invalid file count from within single user mode, i have to wait for du to report exit code 8 again. usually after fixing, i just get exit code 0.

i would then run diskutil as you suggested .... what is a POSIX error code ?

this exit code is coming up for Macintosh HD, do you think it's caused by the OS or there could be a bad sector on the SSD ?

is exit code 8 common ? i'd want to make sure all partitions are healthy before using camptune and before trying to save the disk image using clonezilla.

POSIX is set of standards, which were intended to "unify" variants/derivatives of Unix. The OS X branch has parts of BSD, OSF, NeXT and some of its own but to allow portability of interfaces between variants/derivatives.

Here is my diskutil repairDisk run on a normally-booted OS X.

diskutil repairDisk disk0

Repairing the partition map might erase disk0s1, proceed? (y/N) y

Started partition map repair on disk0

Checking prerequisites

Checking the partition list

Adjusting partition map to fit whole disk as required

Checking for an EFI system partition

Checking the EFI system partition's size

Checking the EFI system partition's file system

Checking the EFI system partition's folder content

Checking all HFS data partition loader spaces

Checking booter partitions

Checking booter partition disk0s3

Repairing file system

Checking Journaled HFS Plus volume

Checking extents overflow file

Checking catalog file

Checking multi-linked files

Checking catalog hierarchy

Checking extended attributes file

Checking volume bitmap

Checking volume information

The volume Recovery HD appears to be OK

File system check exit code is 0

Updating boot support partitions for the volume as required

Reviewing boot support loaders

Checking Core Storage Physical Volume partitions

Verifying storage system

Checking volume

disk0s2: Scan for Volume Headers

disk0s2: Scan for Disk Labels

Logical Volume Group 57578357-3715-48A5-AB8A-4107AF12F7FB on 1 device

disk0s2: Scan for Metadata Volume

Logical Volume Group has a 24 MB Metadata Volume with double redundancy

Start scanning metadata for a valid checkpoint

Load and verify Segment Headers

Load and verify Checkpoint Payload

Load and verify Transaction Segment

Incorporate 0 newer non-checkpoint transactions

Load and verify Virtual Address Table

Load and verify Segment Usage Table

Load and verify Metadata Superblock

Load and verify Logical Volumes B-Trees

Logical Volume Group contains 1 Logical Volume

Load and verify 11EBF920-AA4B-4EC6-AC7F-7CC70E69883C

Load and verify 8A0116D5-7E1E-44D8-B2A0-8D4E4D48298D

Load and verify Freespace Summary

Load and verify Block Accounting

Load and verify Live Virtual Addresses

Newest transaction commit checkpoint is valid

Load and verify Segment Cleaning

The volume 57578357-3715-48A5-AB8A-4107AF12F7FB appears to be OK

Storage system check exit code is 0

Repairing storage system

The volume disk0s2 cannot be repaired when it is in use

Checking volume

disk0s2: Scan for Volume Headers

disk0s2: Scan for Disk Labels

Logical Volume Group 57578357-3715-48A5-AB8A-4107AF12F7FB on 1 device

disk0s2: Scan for Metadata Volume

Logical Volume Group has a 24 MB Metadata Volume with double redundancy

Start scanning metadata for a valid checkpoint

Load and verify Segment Headers

Load and verify Checkpoint Payload

Load and verify Transaction Segment

Incorporate 0 newer non-checkpoint transactions

Load and verify Virtual Address Table

Load and verify Segment Usage Table

Load and verify Metadata Superblock

Load and verify Logical Volumes B-Trees

Logical Volume Group contains 1 Logical Volume

Load and verify 11EBF920-AA4B-4EC6-AC7F-7CC70E69883C

Load and verify 8A0116D5-7E1E-44D8-B2A0-8D4E4D48298D

Load and verify Freespace Summary

Load and verify Block Accounting

Load and verify Live Virtual Addresses

Newest transaction commit checkpoint is valid

Load and verify Segment Cleaning

The volume 57578357-3715-48A5-AB8A-4107AF12F7FB appears to be OK

Storage system check exit code is 0

Updating Windows boot.ini files as required

The partition map appears to be OK

Finished partition map repair on disk0

I suggest looking at Using Disk Utility to verify or repair disks - Apple Support and the linked articles. Unless absolutely necessary, I prefer using DU over fsck. Please also see the fsck man page, since fsck is a wrapper for underlying file system-specific utilities.

thanks for posting that ... looks lengthy maybe you had some errors on your volumes ? not sure how it would handle a windows NTFS formatted partition, is it able to check and repair it ?

No. DU will not repair NTFS. You will need to use chkdsk in Windows Safe Mode to run the equivalent function.

Loner,

exit code 8 is back again .... here is what I'm seeing in terminal .... just bewildered because I also did a diskutil repairDisk disk0 before doing this check.

I did it in terminal, within OS 10. Not from single user mode or recovery mode. what was the root cause of this again ? I am just checking the Macintosh HD volume.

Admins-MBP:~ adminuser$ diskutil list

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *251.0 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_HFS Macintosh HD 60.0 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

4: Microsoft Basic Data Windows 189.8 GB disk0s4

Admins-MBP:~ adminuser$ diskutil verifyVolume disk0s2

Started file system verification on disk0s2 Macintosh HD

Verifying file system

Using live mode

Performing live verification

Checking Journaled HFS Plus volume

Checking extents overflow file

Checking catalog hierarchy

Checking extended attributes file

Checking volume bitmap

Checking volume information

Checking volume information

Invalid volume file count

Checking volume information

Invalid volume file count

Invalid volume file count

(It should be 794329 instead of 794800)

The volume Macintosh HD was found corrupt and needs to be repaired

File system check exit code is 8

Error: -69845: File system verify or repair failed

Underlying error: 8: POSIX reports: Exec format error

Admins-MBP:~ adminuser$