I have been having trouble loading Bootcamp, everything seems OK except for an SSD / AFPS related warning in the disc utility:
crypto_val: object (oid 0x4): invalid state.major_version (0)
warning: crypto_val: object (oid 0x4): invalid state.key_os_version (0x0)
warning: crypto_val: object (oid 0x4): invalid state.key_revision (0)
I am not sure what the significance of this is and how this could be impacting my attempts to load Bootcamp.
If you ignore all the '(disk image)' entries, you are left with
We can safely ignore disk4/disk5.
You want to run
fsck_apfs -s -o -y /dev/rdisk2
If necessary, unmount it, first.
Good to see it successfully unmount all volumes. Run
sudo fsck_apfs -s -o -y /dev/rdisk1
and post the output.
Last login: Wed Jan 16 16:54:20 on console
Restored session: Wed 16 Jan 2019 16:43:09 GMT
Brians-MBP:~ briankneller$ diskutil unmountDisk disk1
Unmount of all volumes on disk1 was successful
Brians-MBP:~ briankneller$ sudo fsck_apfs -s -o -y /dev/rdisk1
Password:
Sorry, try again.
Password:
dev_init:590: Using /private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/fsck_apfs.478.1/apfs and /private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/fsck_apfs.478.1/nx for device-io.
dev_init:590: Using /private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/fsck_apfs.478.4/apfs and /private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/fsck_apfs.478.4/nx for device-io.
** Checking the container superblock.
** Checking the EFI jumpstart record.
** Checking the space manager.
** Checking the space manager free queue trees.
** Checking the object map.
** Checking volume.
** Checking the APFS volume superblock.
** The volume Macintosh HD was formatted by newfs_apfs (748.30.63) and last modified by apfs_kext (945.230.6).
** Checking the object map.
** Checking the snapshot metadata tree.
** Checking the snapshot metadata.
** Checking snapshot 1 of 1.
** Checking the extent ref tree.
** Checking the fsroot tree.
** Checking volume.
** Checking the APFS volume superblock.
** The volume Preboot was formatted by newfs_apfs (748.77.4) and last modified by apfs_kext compiled @ Nov 2 201.
** Checking the object map.
** Checking the snapshot metadata tree.
** Checking the snapshot metadata.
** Checking the extent ref tree.
** Checking the fsroot tree.
** Checking volume.
** Checking the APFS volume superblock.
** The volume Recovery was formatted by newfs_apfs (748.77.4) and last modified by apfs_kext compiled @ Nov 2 201.
** Checking the object map.
** Checking the snapshot metadata tree.
** Checking the snapshot metadata.
** Checking the extent ref tree.
** Checking the fsroot tree.
** Checking volume.
** Checking the APFS volume superblock.
** The volume VM was formatted by newfs_apfs (748.77.8) and last modified by apfs_kext compiled @ Nov 2 201.
** Checking the object map.
** Checking the snapshot metadata tree.
** Checking the snapshot metadata.
** Checking the extent ref tree.
** Checking the fsroot tree.
** Verifying allocated space.
Space allocation summary:
category block count
-------- -----------
container 28166
spaceman 22856
omap 1612
fs root tree 116061
extent ref tree 7238
volume metadata 10
file data 34869088
Total blocks marked by fsck: 35045031
Total blocks allocated by spaceman: 35045031
** Performing deferred repairs.
** The volume /dev/rdisk1 appears to be OK.
Brians-MBP:~ briankneller$
Mojave.3 was released. Run fsck_apfs and check.
Can you post the output of
sudo fsck_apfs -n -l /dev/rdisk1
You can copy paste text, instead of posting images, if it is more convenient.
Run
diskutil unmountDisk disk1
and post the output.
Can you post the output of
sudo fsck_apfs -n -l /dev/rdisk1
from the High Sierra side?
You seem to be in Recovery. Try to boot normally.
Under normal boot, you will need to use
sudo fsck_apfs -n -l /dev/rdisk1
Since SSU is valid only on T2 Macs (About Secure Boot - Apple Support), what is the current macOS and macOS version shipped with this Mac. I assume this is the 2018 Mac we are referring to. Is this Mac managed through your corporate IT department?
-bash-3.2# fsck_apfs -n -l /dev/rdisk1
0000: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
. . .
01b0: 0000 0000 0000 0000 0000 0000 0000 00fe |................|
01c0: ffff eefe ffff 0100 0000 d7ff 3f00 0000 |................|
01d0: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
. . .
01f0: 0000 0000 0000 0000 0000 0000 0000 55aa |..............U.|
0200: 4546 4920 5041 5254 0000 0100 5c00 0000 |EFI.PART........|
0210: 191a 382f 0000 0000 0100 0000 0000 0000 |..8.............|
0220: d7ff 3f00 0000 0000 2200 0000 0000 0000 |................|
0230: b6ff 3f00 0000 0000 89c3 7427 5cb2 8145 |..........t....E|
0240: a367 7948 1fac ad69 0200 0000 0000 0000 |.gyH...i........|
0250: 8000 0000 8000 0000 1859 c6e2 0000 0000 |.........Y......|
0260: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
. . .
0400: 0053 4648 0000 aa11 aa11 0030 6543 ecac |.SFH.......0eC..|
0410: 700c d2e3 0293 d141 b59a 9481 4995 95a0 |p......A....I...|
0420: 2800 0000 0000 0000 afff 3b00 0000 0000 |................|
0430: 0000 0000 0000 0000 6400 6900 7300 6b00 |........d.i.s.k.|
0440: 2000 6900 6d00 6100 6700 6500 0000 0000 |..i.m.a.g.e.....|
0450: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
. . .
0ff0: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
error: Device does not contain a valid APFS container.
-bash-3.2#
Can you install Mojave on an external disk? High Sierra fsck_apfs is not the same as
From the man page of fsck_apfs on High Sierra...
"In its current state, fsck_apfs checks the integrity of various container data structures. We do not check for overlapping allocations."
Here is the full page...
FSCK_APFS(8) BSD System Manager's Manual FSCK_APFS(8)
NAME
fsck_apfs -- APFS consistency check
SYNOPSIS
fsck_apfs [-q | -n | -y] [-l] device
DESCRIPTION
The fsck_apfs utility verifies and repairs APFS containers and volumes.
fsck_apfs checks the specified APFS containers and volumes and tries to repair all detected inconsistencies.
Because of inconsistencies between the block device and the buffer cache, the raw device should always be used.
In its current state, fsck_apfs checks the integrity of various container data structures. We do not check for overlapping allocations.
The options are as follows:
-l Enable live verification mode. This makes it possible to check an APFS container which is currently mounted read-write,
although no repairs can be made.
-q Causes fsck_apfs to quickly check whether the volume is `clean'.
-n Never attempt to repair any damage that is found.
-y Always attempt to repair any damage that is found.
EXIT VALUES
fsck_apfs exits 0 on success, and >0 if error occurs.
SEE ALSO
fsck(8)
Mac OS X December 3, 2015 Mac OS X
See Bootcamp Windows installation error with … - Apple Community as an example of the Mojave version in action.
Hi, I have installed Mojave on an external drive and tried it with my production PC, it works. Tried it with the new High Sierra machine with the AFPS issue. I have to use Startup Security Utility (SSU). The issue I now have the SSU will not accept the admin password,I checked and this works OK when I logon normally. I then created another admin account and reset the password from Recovery (Cmd/R) which accepted this reset. Then trying this password with Startup Security Utility still no joy. Finally did an SMC and PRAM reset and tried again - no luck. Maybe gatekeeper is having an influence or the keyboard map for the SSU is different. I attach a copy of the Terminal startup which mentions duplicate layout identifiers -- not sure of the significance of this. -- applogies for the moire fringes
Hi, I have installed Mojave on an external drive and tried it with my production PC, it works.
Nice.
Tried it with the new High Sierra machine with the AFPS issue. I have to use Startup Security Utility (SSU). The issue I now have the SSU will not accept the admin password,I checked and this works OK when I logon normally. I then created another admin account and reset the password from Recovery (Cmd/R) which accepted this reset. Then trying this password with Startup Security Utility still no joy. Finally did an SMC and PRAM reset and tried again - no luck.
Disconnect the Mojave disk, boot into SSU using the internal disk, and set the level to 'No Security'/'Allow Booting from external Media'. Now, try to boot from Mojave external disk and test.
Success, a password issue, not sure why it has happened. I installed Mojave onto the samsung external drive using my production machine - it picked the admin password from that The SSU access asks for a admin pswd from the High Sierra machine -- passwords are different and so it is rejected. When I changed the high sierra admin password using the cmd/R password reset in terminal the SSU stil rejected that but accepted the admin password of the production machine ... hope that makes sense. I am not familiar with the detailed syntax for the fsck command and given the imporance of what we are doing could you provide this detail please, ist of disk volumes attached.
AFPS crypto val warning what is the significance?