Skip to main content

I'm seeing a repeated entry in the jamf.log on client machines.

"no container info found for disk with id disk2s1"

I have wiped the disk and then reinstalled the OS - maybe the cause?

Anyone shed any light on this?

I've also seen and pondered this log.

Out of curiosity, how are you wiping before install? Are you viewing all devices then erasing from disk0 (eg. Apple SSD..) removing all volumes / partitions?

Yes - I remove all volumes with the disk utility and then erase the disk that's left as it lets me name the disk Macintosh HD

Yes, that's what I had been doing also.

I've started leaning towards just pressing erase to the initial disk or running "resetpassword" in terminal and using the supplied "erase disk" prompt.

I wonder if either of those will change this, I will test today and see.

Yes, that's what I had been doing also.

I've started leaning towards just pressing erase to the initial disk or running "resetpassword" in terminal and using the supplied "erase disk" prompt.

I wonder if either of those will change this, I will test today and see.


I think the answer is here ... I feel a bit foolish  - it's the install thumb drive stuck in the back of the test Mac 

 

lab@dep54592 ~ % diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.3 GB disk0
1: EFI ⁨EFI⁩ 314.6 MB disk0s1
2: Apple_APFS ⁨Container disk1⁩ 500.0 GB disk0s2

/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +500.0 GB disk1
Physical Store disk0s2
1: APFS Volume ⁨Macintosh HD⁩ 15.3 GB disk1s1
2: APFS Snapshot ⁨com.apple.os.update-...⁩ 15.3 GB disk1s1s1
3: APFS Volume ⁨Preboot⁩ 283.1 MB disk1s2
4: APFS Volume ⁨Recovery⁩ 622.9 MB disk1s3
5: APFS Volume ⁨VM⁩ 1.1 MB disk1s4
6: APFS Volume ⁨Macintosh HD — Data⁩ 20.8 GB disk1s5

/dev/disk2 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *15.7 GB disk2
1: Apple_HFS ⁨Install macOS Big Sur⁩ 15.7 GB disk2s1

 

Similarly, this was just a mounted DMG that never un-mounted in an install script I tested a month ago. My device was not checking in with Jamf for days and would only check in upon a manual Poilicy/Inventory check via Self Service. As soon as I ejected it in /Volumes, things started working again!

Reply


Terms & ConditionsCookie settings