Posted on 06-02-2022 06:52 PM
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?
Solved! Go to Solution.
06-08-2022 01:51 AM - edited 06-08-2022 01:56 AM
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 <u+2068>EFI<u+2069> 314.6 MB disk0s1
2: Apple_APFS <u+2068>Container disk1<u+2069> 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 <u+2068>Macintosh HD<u+2069> 15.3 GB disk1s1
2: APFS Snapshot <u+2068>com.apple.os.update-...<u+2069> 15.3 GB disk1s1s1
3: APFS Volume <u+2068>Preboot<u+2069> 283.1 MB disk1s2
4: APFS Volume <u+2068>Recovery<u+2069> 622.9 MB disk1s3
5: APFS Volume <u+2068>VM<u+2069> 1.1 MB disk1s4
6: APFS Volume <u+2068>Macintosh HD — Data<u+2069> 20.8 GB disk1s5
/dev/disk2 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *15.7 GB disk2
1: Apple_HFS <u+2068>Install macOS Big Sur<u+2069> 15.7 GB disk2s1
nbsp;p54592 ~ % diskutil list /dev/disk0 (internal, physical): #: TYPE NAME SIZE
Posted on 06-03-2022 09:28 PM
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?
Posted on 06-06-2022 06:04 PM
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
06-06-2022 06:17 PM - edited 06-06-2022 06:17 PM
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.
06-08-2022 01:51 AM - edited 06-08-2022 01:56 AM
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 <u+2068>EFI<u+2069> 314.6 MB disk0s1
2: Apple_APFS <u+2068>Container disk1<u+2069> 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 <u+2068>Macintosh HD<u+2069> 15.3 GB disk1s1
2: APFS Snapshot <u+2068>com.apple.os.update-...<u+2069> 15.3 GB disk1s1s1
3: APFS Volume <u+2068>Preboot<u+2069> 283.1 MB disk1s2
4: APFS Volume <u+2068>Recovery<u+2069> 622.9 MB disk1s3
5: APFS Volume <u+2068>VM<u+2069> 1.1 MB disk1s4
6: APFS Volume <u+2068>Macintosh HD — Data<u+2069> 20.8 GB disk1s5
/dev/disk2 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *15.7 GB disk2
1: Apple_HFS <u+2068>Install macOS Big Sur<u+2069> 15.7 GB disk2s1
nbsp;p54592 ~ % diskutil list /dev/disk0 (internal, physical): #: TYPE NAME SIZE