Markh789

Q: OS X El Cap startup - prohibited symbol

I'm having an issue with my Mac. I have a Samsung SSD 840 Evo 1TB in my MacBook Pro (13-inch, Mid 2010). I've only had the SSD in it for a few years now. The SSD and the memory are the only upgrades I have done (upgraded to 8GB RAM within a few months of ownership and to the SSD 2-3 years ago).

 

I do use FileVault 2 (I work with sensitive client information).

 

Last night I resumed my computer from sleep (open screen, wake up, login). Only to close my Spotify and the screen froze and become completely unresponsive (clock was not flashing, could not change dim on keyboard, cursor would not move, etc) - so after about 20 minutes I decided it was time to force it off and turn it back up, it presented the normal login screen showing my name and the guest account. Clicking into my account and entering my password, it starts its usual loading process, gets to about halfway.. but then shows the prohibited symbol.

 

After booting into Internet Recovery I was able to check the drive and do some basic checks and it was saying disk0s2 was not a CoreStorage volume.

 

So I switched back to my old (and slow) hard drive (10.10.1 is on this) and mounted the SSD separately using a sata2usb connector, and ran a repair and got back this - the same errors I got on the Internet Recovery:

 

     Verifying and repairing partition map for “Samsung SSD 840 EVO 1TB Media”

     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 all HFS data partition loader spaces

     Checking booter partitions

     Checking booter partition disk3s3

     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

     disk3s2: Scan for Volume Headers

     disk3s2: Scan for Disk Labels

     Invalid Disk Label @ 999328231424: bad MLV address

     Invalid Disk Label @ 999332425728: invalid field value

     Invalid Disk Label @ 999336620032: cksum mismatch

     Invalid Disk Label @ 999340814336: invalid field value

     disk3s2 is not a CoreStorage volume

     Storage system check exit code is 1.

     Repairing storage system

     Checking volume

     disk3s2: Scan for Volume Headers

     disk3s2: Scan for Disk Labels

     Invalid Disk Label @ 999328231424: bad MLV address

     Invalid Disk Label @ 999332425728: invalid field value

     Invalid Disk Label @ 999336620032: cksum mismatch

     Invalid Disk Label @ 999340814336: invalid field value

     disk3s2 is not a CoreStorage volume

     Storage system check exit code is 1.

     Repairing storage systemChecking volume

     disk3s2: Scan for Volume Headers

     disk3s2: Scan for Disk Labels

     Invalid Disk Label @ 999328231424: bad MLV address

     Invalid Disk Label @ 999332425728: invalid field value

     Invalid Disk Label @ 999336620032: cksum mismatch

     Invalid Disk Label @ 999340814336: invalid field value

     disk3s2 is not a CoreStorage volume

     Storage system check exit code is 1.

     Problems were encountered during repair of the partition map

     Error: This disk needs to be repaired. Click Repair Disk.

 

 

Executing "Repair Disk" gives back the same information.

 

From what I've seen on the internet already here is some information that may help:

 

% diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *750.2 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS Macintosh               701.3 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
   4:       Microsoft Basic Data BOOTCAMP                48.0 GB    disk0s4
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *8.0 GB     disk1
   1:                 DOS_FAT_32 NO NAME                 8.0 GB     disk1s1
/dev/disk3
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk3
   1:                        EFI                         209.7 MB   disk3s1
   2:          Apple_CoreStorage                         999.3 GB   disk3s2
   3:                 Apple_Boot Recovery HD             650.1 MB   disk3s3
% diskutil cs list
CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group D9884BF5-CC85-4359-B567-B05FE28189C5
    =========================================================
    Name:         -none-
    Status:       Initializing
    Size:         0 B (0 B)
    Free Space:   -none-
    |
    +-< Physical Volume 86EBE82F-BD40-4021-BE68-A8B41920E177
        ----------------------------------------------------
        Index:    18446744073709551615
        Disk:     disk3s2
        Status:   Failed
        Size:     -none-
% diskutil cs unlockVolume /dev/disk3s2
% diskutil cs unlockVolume disk3s2
% diskutil cs unlockVolume D9884BF5-CC85-4359-B567-B05FE28189C5
% diskutil cs unlockVolume 86EBE82F-BD40-4021-BE68-A8B41920E177
# all of the above give the same response:

xxx is not a CoreStorage Logical Volume UUID


% diskutil cs info /dev/disk3s2
Core Storage Properties:
   Role:                       Physical Volume (PV)
   UUID:                       86EBE82F-BD40-4021-BE68-A8B41920E177
   Parent LVG UUID:            D9884BF5-CC85-4359-B567-B05FE28189C5
   Device Identifier:          disk3s2
   PV Status:                  Failed
% sudo fsck_cs /dev/disk3s2
Password:
   Executing fsck_cs (version 471)
** Checking volume
** disk3s2: Scan for Volume Headers
** disk3s2: Scan for Disk Labels
   Invalid Disk Label @ 999328231424: bad MLV address
   Invalid Disk Label @ 999332425728: invalid field value
   Invalid Disk Label @ 999336620032: cksum mismatch
   Invalid Disk Label @ 999340814336: invalid field value
** disk3s2 is not a CoreStorage volume


 

 

I'm really regretting not backing up for a few weeks now, as there is a lot of work on this SSD I would like to have back!

 

I can mount my Recovery HD and the EFI volumes:

 

% diskutil mount /dev/disk0s3
Volume Recovery HD on /dev/disk0s3 mounted
% diskutil mount /dev/disk0s1
Volume EFI on /dev/disk0s1 mounted

 

Now I'm not sure what to do.

MacBook Pro, OS X El Capitan (10.11.6)

Posted on Sep 15, 2016 7:17 PM

Close

Q: OS X El Cap startup - prohibited symbol

  • All replies
  • Helpful answers

  • by Loner T,

    Loner T Loner T Sep 15, 2016 7:49 PM in response to Markh789
    Level 7 (23,935 points)
    Safari
    Sep 15, 2016 7:49 PM in response to Markh789

    You should not repair CS volumes using older versions of Disk Utility. They can cause unpredictable results.

     

    The EVO 1TB may need a firmware update. Can you check with the Samsung website if there are any pending updates?

     

    +-< Physical Volume 86EBE82F-BD40-4021-BE68-A8B41920E177 

            ---------------------------------------------------- 

            Index:    18446744073709551615 

    This is a corrupted physical volume.

  • by leroydouglas,

    leroydouglas leroydouglas Sep 15, 2016 7:57 PM in response to Markh789
    Level 7 (23,583 points)
    Notebooks
    Sep 15, 2016 7:57 PM in response to Markh789

    So from Recovery you ran the Disk FirstAid ?

     

    If you can not repair the disk, it points to a failed drive. What kind of guarantee does Samsung provide on thre  Evo, you may at least be able to get the drive replaced?

     

    Redundancy is the key to a successful back up strategy.

    How to create a boot clone

  • by Markh789,

    Markh789 Markh789 Sep 15, 2016 8:20 PM in response to Loner T
    Level 1 (18 points)
    Mac OS X
    Sep 15, 2016 8:20 PM in response to Loner T

    Is there anything I can do to get the data (or any of the data) back? From a memory upgrading the firmware of Samsung SSDs is rather difficult from a Mac, but I did it not too long ago

     

    There is australian 3 year consumer law on electronics but I'm not sure it will apply to the hard drive. I believe Samsung had 24 month guarantee warranty (gone). However, I don't think the drive has failed - wouldn't that mean all partitions would be inaccessible?

  • by Loner T,

    Loner T Loner T Sep 15, 2016 8:27 PM in response to Markh789
    Level 7 (23,935 points)
    Safari
    Sep 15, 2016 8:27 PM in response to Markh789

    The first login should have been the FV2 login, not the OS X login. The error messages indicate that an IO operation failed. There are many reasons for such failures, and SSD complicates this further.

     

    How old is your back up? Can you reconstruct any missing data for the gap period?

  • by Markh789,

    Markh789 Markh789 Sep 15, 2016 8:31 PM in response to Loner T
    Level 1 (18 points)
    Mac OS X
    Sep 15, 2016 8:31 PM in response to Loner T

    My FV2 login has always showed my name and my guest account. My backup is too old to be useful (months).

     

    Is it best to bite the bullet and start fresh? I will be behind on work by weeks which is my main worry.

  • by Loner T,

    Loner T Loner T Sep 15, 2016 8:39 PM in response to Markh789
    Level 7 (23,935 points)
    Safari
    Sep 15, 2016 8:39 PM in response to Markh789

    Markh789 wrote:

     

    Is it best to bite the bullet and start fresh? I will be behind on work by weeks which is my main worry.

    Not yet.

     

    Do you have an external disk that can be erased and used to install a new copy of OS X? If yes, please install whatever OS X version is offered by Internet Recovery (it may be older than your current OS X version on disk3). Upgrade OS X  to the same version as the SSD. Boot from this external disk, and then run

     

    diskutil repairDisk disk3

     

    Make sure disk3 is the SSD, because OS X will re-number disks. Please post the Terminal output of the command.

  • by Markh789,

    Markh789 Markh789 Sep 15, 2016 9:45 PM in response to Loner T
    Level 1 (18 points)
    Mac OS X
    Sep 15, 2016 9:45 PM in response to Loner T

    Here is the result:

     

    Marks-MacBook-Pro:~ markhughes$ diskutil list

    /dev/disk0 (internal, physical):

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *750.2 GB   disk0

       1:                        EFI EFI                     209.7 MB   disk0s1

       2:                  Apple_HFS Macintosh               749.3 GB   disk0s2

       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3

    /dev/disk1 (external, physical):

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *1.0 TB     disk1

       1:                        EFI                         209.7 MB   disk1s1

       2:          Apple_CoreStorage                         999.3 GB   disk1s2

       3:                 Apple_Boot Recovery HD             650.1 MB   disk1s3

    Marks-MacBook-Pro:~ markhughes$ diskutil repairDisk disk1

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

    Started partition map repair on disk1

    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 disk1s3

    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

    disk1s2: Scan for Volume Headers

    disk1s2: Scan for Disk Labels

    Invalid Disk Label @ 999328231424: bad MLV address

    Invalid Disk Label @ 999332425728: invalid field value

    Invalid Disk Label @ 999336620032: cksum mismatch

    Invalid Disk Label @ 999340814336: invalid field value

    disk1s2 is not a CoreStorage volume

    Storage system check exit code is 1

    Repairing storage system

    Checking volume

    disk1s2: Scan for Volume Headers

    disk1s2: Scan for Disk Labels

    Invalid Disk Label @ 999328231424: bad MLV address

    Invalid Disk Label @ 999332425728: invalid field value

    Invalid Disk Label @ 999336620032: cksum mismatch

    Invalid Disk Label @ 999340814336: invalid field value

    disk1s2 is not a CoreStorage volume

    Storage system check exit code is 1

    Repairing storage system

    Checking volume

    disk1s2: Scan for Volume Headers

    disk1s2: Scan for Disk Labels

    Invalid Disk Label @ 999328231424: bad MLV address

    Invalid Disk Label @ 999332425728: invalid field value

    Invalid Disk Label @ 999336620032: cksum mismatch

    Invalid Disk Label @ 999340814336: invalid field value

    disk1s2 is not a CoreStorage volume

    Storage system check exit code is 1

    Problems were encountered during repair of the partition map

    Error: -69716: Storage system verify or repair failed

    Underlying error: 1: POSIX reports: Operation not permitted

  • by Loner T,

    Loner T Loner T Sep 16, 2016 8:58 AM in response to Markh789
    Level 7 (23,935 points)
    Safari
    Sep 16, 2016 8:58 AM in response to Markh789

    From the external disk, boot into it's Local Recovery using Command+R, disable SIP in Utilities -> Terminal using csrutil disable and boot normally and check SIP status using csrutil status. If csrutil status reports that SIP is disabled, retry your repairDisk and post the output.

  • by Markh789,

    Markh789 Markh789 Sep 16, 2016 7:34 PM in response to Loner T
    Level 1 (18 points)
    Mac OS X
    Sep 16, 2016 7:34 PM in response to Loner T

    Unfortunately no luck, but it is a different error message now. I've got it so the SSD is now my internal drive and running my backup OS off the external.

     

    So running from my backup OS:

     

    Marks-MacBook-Pro:~ markhughes$ diskutil list
    /dev/disk0 (internal, physical):
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *1.0 TB     disk0
       1:                        EFI                         209.7 MB   disk0s1
       2:          Apple_CoreStorage                         999.3 GB   disk0s2
       3:                 Apple_Boot Recovery HD             650.1 MB   disk0s3
    /dev/disk1 (external, physical):
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *750.2 GB   disk1
       1:                        EFI EFI                     209.7 MB   disk1s1
       2:                  Apple_HFS Macintosh               749.3 GB   disk1s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3
    
    
    Marks-MacBook-Pro:~ markhughes$ csrutil status
    System Integrity Protection status: disabled.
    
    Marks-MacBook-Pro:~ markhughes$ 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
    Problems were encountered during repair of the partition map
    Error: -69697: Partition map repair failed while adjusting structures to fit current whole disk size
    Underlying error: 5: POSIX reports: Input/output error
    
    
    

     

    Thank you so much for your help so far. I really appreciate it!

  • by Loner T,

    Loner T Loner T Sep 16, 2016 8:49 PM in response to Markh789
    Level 7 (23,935 points)
    Safari
    Sep 16, 2016 8:49 PM in response to Markh789

    The IO error is not a good sign. Can you post the output of

     

    diskutil cs list

     

    If possible, please disable FV2 temporarily. If FV2 is successfully disabled re-run the previous command and post that output as well.

  • by Markh789,

    Markh789 Markh789 Sep 16, 2016 8:57 PM in response to Loner T
    Level 1 (18 points)
    Mac OS X
    Sep 16, 2016 8:57 PM in response to Loner T

    Unfortunately I can't get into it and disable FV2. I've tried doing it before but it just says it's not a CoreStorage

     

    Marks-MacBook-Pro:~ markhughes$ diskutil cs list
    CoreStorage logical volume groups (1 found)
    |
    +-- Logical Volume Group D9884BF5-CC85-4359-B567-B05FE28189C5
        =========================================================
        Name:         -none-
        Status:       Initializing
        Size:         0 B (0 B)
        Free Space:   -none-
        |
        +-< Physical Volume 86EBE82F-BD40-4021-BE68-A8B41920E177
            ----------------------------------------------------
            Index:    18446744073709551615
            Disk:     disk0s2
            Status:   Failed
            Size:     -none-