-
All replies
-
Helpful answers
-
Nov 24, 2015 3:20 PM in response to davefromhytheby Loner T,Boot into Local Recovery (Command+R) and run
diskutil repairVolume disk2
diskutil repairdisk disk0
diskutil repairdisk disk1
Please ensure the disk numbers are correct, because Recovery console may re-order the disks.
-
Nov 24, 2015 3:49 PM in response to Loner Tby davefromhythe,repairVolume disk2 fails,..invalid request -69886
repairdisk disk0 returns "Repairing the partition map might erase disk0s1, proceed? (y/N)
Do I proceed?
-
Nov 24, 2015 4:02 PM in response to davefromhytheby Loner T,Your CS volume contains disk0s2 and disk1s2. Disk0s1 is the EFI. It should not impact your CS volume. Will you be able to post a screen shot/image of the screen after it completes the repair. It should put the Free Space back into the CS volume.
Is Disk2 still your CS volume?
-
Nov 25, 2015 6:01 AM in response to Loner Tby davefromhythe,I proceeded with diskutil repairdisk disk2 which seems ok. I did another diskutil cslist and disk2 now seems to be disk3, is that correct?
-bash-3.2# diskutil repairVolume disk2
Error starting file system repair for disk2: Invalid request (-69886)
-bash-3.2# 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
Reviewing boot support loaders
Checking Core Storage Physical Volume partitions
Verifying storage system
Checking volume
disk1s2: Scan for Volume Headers
disk0s2: Scan for Volume Headers
disk1s2: Scan for Disk Labels
disk0s2: Scan for Disk Labels
Logical Volume Group 18033EC1-89B6-4B33-9479-810A2051D247 spans 2 devices
disk0s2+disk1s2: 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 41C80A87-B7EA-4C3D-9269-FE818EDBEB47
Load and verify 9B95CEA1-BCD9-41BD-8AF6-578044557A26
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 18033EC1-89B6-4B33-9479-810A2051D247 appears to be OK
Storage system check exit code is 0
Repairing storage system
The volume disk1s2+disk0s2 cannot be repaired when it is in use
Checking volume
disk1s2: Scan for Volume Headers
disk0s2: Scan for Volume Headers
disk1s2: Scan for Disk Labels
disk0s2: Scan for Disk Labels
Logical Volume Group 18033EC1-89B6-4B33-9479-810A2051D247 spans 2 devices
disk0s2+disk1s2: 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 41C80A87-B7EA-4C3D-9269-FE818EDBEB47
Load and verify 9B95CEA1-BCD9-41BD-8AF6-578044557A26
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 18033EC1-89B6-4B33-9479-810A2051D247 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
-bash-3.2# diskutil cs list
CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group 18033EC1-89B6-4B33-9479-810A2051D247
=========================================================
Name: Mac SSD
Status: Online
Size: 368337891328 B (368.3 GB)
Free Space: 248874012672 B (248.9 GB)
|
+-< Physical Volume D9EA3398-0524-4307-9146-DE2B0D0EA8C0
| ----------------------------------------------------
| Index: 0
| Disk: disk0s2
| Status: Online
| Size: 119197646848 B (119.2 GB)
|
+-< Physical Volume DBEE813F-F777-4CC6-8EBC-751CBB1B5D07
| ----------------------------------------------------
| Index: 1
| Disk: disk1s2
| Status: Online
| Size: 249140244480 B (249.1 GB)
|
+-> Logical Volume Family 41C80A87-B7EA-4C3D-9269-FE818EDBEB47
----------------------------------------------------------
Encryption Type: None
|
+-> Logical Volume 9B95CEA1-BCD9-41BD-8AF6-578044557A26
---------------------------------------------------
Disk: disk3
Status: Online
Size (Total): 118826336256 B (118.8 GB)
Revertible: No
LV Name: Mac SSD
Volume Name: Mac SSD
Content Hint: Apple_HFS
-bash-3.2#
-
Nov 25, 2015 6:45 AM in response to davefromhytheby Loner T,The volume disk1s2+disk0s2 cannot be repaired when it is in use
Are you booted in Internet Recovery or Local Recovery? You should be in Internet Recovery.
In Internet Recovery, run
diskutil cs resizeVolume 9B95CEA1-BCD9-41BD-8AF6-578044557A26 0g
This is the man page.
diskutil cs resizeVolume
Usage: diskutil coreStorage resizeVolume
lvUUID|MountPoint|DiskIdentifier|DeviceNode size
Resize a logical volume, which is one of one or more disks that consume storage
out of a logical volume group. The logical volume group will have more or less
available space after this operation, if it was a shrink or grow, respectively.
Specifying zero as the size asks for an "automatic" fit-to-fill-LVG operation.
Example: diskutil coreStorage resizeVolume
11111111-2222-3333-4444-555555555555 10g
Once complete, re-run the diskutil repairDisk disk0 command.
-
Nov 25, 2015 7:19 AM in response to Loner Tby davefromhythe,I rebooted in Internet recovery and ran "diskutil cs resizeVolume 9B95CEA1-BCD9-41BD-8AF6-578044557A26 0g"
message returned was "Error resizing CoreStorage Logical Volume: Not avalid CoreStorage Volume UUID (-69776)"
I retyped again with the same result. I am confident I typed all the digits correctly.
-
Nov 25, 2015 7:29 AM in response to davefromhytheby Loner T,The UUID came from your diskutil cs list output. Can you run diskutil cs list and verify that I did not cut/paste the incorrect value?
This was also the reason to post the syntax page, in case I had a typo.
-
Nov 25, 2015 8:04 AM in response to Loner Tby davefromhythe,I actully typed the sequence from the cs list output rather than your message to eliminate any typo's.Everthing looks right.
-
Nov 25, 2015 8:35 AM in response to davefromhytheby davefromhythe,I ran diskutil cs list again and have got a different output see below
-bash-3.2#
-bash-3.2# diskutil cs resizeVolume 9B95CEA1-BCD9-41BD-8AF6-578044557A26 0g
Error resizing CoreStorage Logical Volume: Not a valid CoreStorage Logical Volume UUID (-69776)
-bash-3.2# diskutil cs resizeVolume 9B95CEA1-BCD9-41BD-8AF6-578044557A26 0g
Error resizing CoreStorage Logical Volume: Not a valid CoreStorage Logical Volume UUID (-69776)
-bash-3.2# diskutil cs list
CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group 18033EC1-89B6-4B33-9479-810A2051D247
=========================================================
Name: -none-
Sequence: 0
Free Space: 0 B (0 B)
|
+-< Physical Volume D9EA3398-0524-4307-9146-DE2B0D0EA8C0
----------------------------------------------------
Index: 0
Disk: disk0s2
Status: Incompatible
Size: -none-
-bash-3.2#
-
Nov 25, 2015 10:04 AM in response to davefromhytheby Loner T,davefromhythe wrote:
-bash-3.2# diskutil cs list
CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group 18033EC1-89B6-4B33-9479-810A2051D247
=========================================================
Name: Mac SSD
Status: Online
Size: 368337891328 B (368.3 GB)
Free Space: 248874012672 B (248.9 GB)
|
+-< Physical Volume D9EA3398-0524-4307-9146-DE2B0D0EA8C0
| ----------------------------------------------------
| Index: 0
| Disk: disk0s2
| Status: Online
| Size: 119197646848 B (119.2 GB)
|
+-< Physical Volume DBEE813F-F777-4CC6-8EBC-751CBB1B5D07
| ----------------------------------------------------
| Index: 1
| Disk: disk1s2
| Status: Online
| Size: 249140244480 B (249.1 GB)
|
+-> Logical Volume Family 41C80A87-B7EA-4C3D-9269-FE818EDBEB47
----------------------------------------------------------
Encryption Type: None
|
+-> Logical Volume 9B95CEA1-BCD9-41BD-8AF6-578044557A26
---------------------------------------------------
Disk: disk3
Status: Online
Size (Total): 118826336256 B (118.8 GB)
Revertible: No
LV Name: Mac SSD
Volume Name: Mac SSD
Content Hint: Apple_HFS
-bash-3.2#
You had this layout when we started, but now you have...
-bash-3.2# diskutil cs list
CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group 18033EC1-89B6-4B33-9479-810A2051D247
=========================================================
Name: -none-
Sequence: 0
Free Space: 0 B (0 B)
|
+-< Physical Volume D9EA3398-0524-4307-9146-DE2B0D0EA8C0
----------------------------------------------------
Index: 0
Disk: disk0s2
Status: Incompatible
Size: -none-
Can you post the output of diskutil list?
-
Nov 25, 2015 11:14 AM in response to Loner Tby davefromhythe,diskutil list output as requested
-bash-3.2#
-bash-3.2# diskutil cs resizeVolume 9B95CEA1-BCD9-41BD-8AF6-578044557A26 0g
Error resizing CoreStorage Logical Volume: Not a valid CoreStorage Logical Volume UUID (-69776)
-bash-3.2# diskutil cs resizeVolume 9B95CEA1-BCD9-41BD-8AF6-578044557A26 0g
Error resizing CoreStorage Logical Volume: Not a valid CoreStorage Logical Volume UUID (-69776)
-bash-3.2# diskutil cs list
CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group 18033EC1-89B6-4B33-9479-810A2051D247
=========================================================
Name: -none-
Sequence: 0
Free Space: 0 B (0 B)
|
+-< Physical Volume D9EA3398-0524-4307-9146-DE2B0D0EA8C0
----------------------------------------------------
Index: 0
Disk: disk0s2
Status: Incompatible
Size: -none-
-bash-3.2# diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *240.1 GB disk0
1: EFI 209.7 MB disk0s1
2: Apple_CoreStorage 119.2 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
4: Microsoft Basic Data BOOTCAMP 120.0 GB disk0s4
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *250.0 GB disk1
1: EFI 209.7 MB disk1s1
2: Apple_CoreStorage 249.1 GB disk1s2
3: Apple_Boot Boot OS X 134.2 MB disk1s3
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: Apple_partition_scheme *1.4 GB disk2
1: Apple_partition_map 30.7 KB disk2s1
2: Apple_Driver_ATAPI 2.0 KB disk2s2
3: Apple_HFS Mac OS X Base System 1.4 GB disk2s3
/dev/disk3
#: TYPE NAME SIZE IDENTIFIER
0: untitled *524.3 KB disk3
/dev/disk4
#: TYPE NAME SIZE IDENTIFIER
0: untitled *524.3 KB disk4
/dev/disk5
#: TYPE NAME SIZE IDENTIFIER
0: untitled *524.3 KB disk5
/dev/disk6
#: TYPE NAME SIZE IDENTIFIER
0: untitled *524.3 KB disk6
/dev/disk7
#: TYPE NAME SIZE IDENTIFIER
0: untitled *524.3 KB disk7
/dev/disk8
#: TYPE NAME SIZE IDENTIFIER
0: untitled *6.3 MB disk8
/dev/disk9
#: TYPE NAME SIZE IDENTIFIER
0: untitled *2.1 MB disk9
/dev/disk10
#: TYPE NAME SIZE IDENTIFIER
0: untitled *1.0 MB disk10
/dev/disk11
#: TYPE NAME SIZE IDENTIFIER
0: untitled *524.3 KB disk11
/dev/disk12
#: TYPE NAME SIZE IDENTIFIER
0: untitled *524.3 KB disk12
/dev/disk13
#: TYPE NAME SIZE IDENTIFIER
0: untitled *1.0 MB disk13
-bash-3.2# diskutil cs list
CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group 18033EC1-89B6-4B33-9479-810A2051D247
=========================================================
Name: -none-
Sequence: 0
Free Space: 0 B (0 B)
|
+-< Physical Volume D9EA3398-0524-4307-9146-DE2B0D0EA8C0
----------------------------------------------------
Index: 0
Disk: disk0s2
Status: Incompatible
Size: -none-
-bash-3.2#
-
Nov 25, 2015 11:27 AM in response to davefromhytheby Loner T,Notice disk0 and disk1 show up as CS disks, but diskutil cs list show incompatible. In your Recovery console (Internet Recovery) what is the OS icon look like for the Re-install OSX option. If you are booted from an older OSX version (older than 10.8.5), diskutil cs will cause issues.
If this does not work, you may have to install Yosemite or install the original OSX that came with your Mac and upgrade the external disk to Yosemite and boot from it.
Please see
How to install OS X on an external drive connected to your Mac - Apple Support
OS X versions and builds included with Mac computers - Apple Support
-
Nov 25, 2015 2:45 PM in response to Loner Tby davefromhythe,The Re-install OSX icon is a lion.
I think I upgraded from Yosemite to el Capitan on the HDD and did a clean install of el Capitan on the SSD.
-
Nov 25, 2015 2:48 PM in response to davefromhytheby Loner T,Lion will not work. Can you install Lion on an external disk, and upgrade to at least Yosemite (or El Capitan)? I prefer Yosemite over El Capitan.
-
Nov 25, 2015 3:11 PM in response to Loner Tby davefromhythe,I thought I was already using el Capitan, isn't the Lion because I have booted via internet recovery?
I haven't got any installation disks.