You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
might be a simple answer but Im not simply understanding. i have yet to encounter this with previous reinstalls. im hoping this means its working right for Monterey on an 2020 AirM1? Can anyone tell me if that is normal now?
MacBook Air (2020 or later)
j2dkno1 wrote:
finally back home crazy day here is that
https://discussions.apple.com/content/attachment/5b3452d0-f6a5-4efc-ba4a-2f21c591a05e
I see no disk 4 your are asking about...
Your output looks normal for an M1, I see no issue
compare to an example M1 macbook air —
/dev/disk0 (internal):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme 251.0 GB disk0
1: Apple_APFS_ISC 524.3 MB disk0s1
2: Apple_APFS Container disk3 245.1 GB disk0s2
3: Apple_APFS_Recovery 5.4 GB disk0s3
/dev/disk3 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +245.1 GB disk3
Physical Store disk0s2
1: APFS Volume Macintosh HD 15.3 GB disk3s1
2: APFS Snapshot com.apple.os.update-... 15.3 GB disk3s1s1
3: APFS Volume Preboot 306.3 MB disk3s2
4: APFS Volume Recovery 1.0 GB disk3s3
5: APFS Volume Data 64.1 GB disk3s5
6: APFS Volume VM 1.1 GB disk3s6
j2dkno1 wrote:
finally back home crazy day here is that
https://discussions.apple.com/content/attachment/5b3452d0-f6a5-4efc-ba4a-2f21c591a05e
I see no disk 4 your are asking about...
Your output looks normal for an M1, I see no issue
compare to an example M1 macbook air —
/dev/disk0 (internal):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme 251.0 GB disk0
1: Apple_APFS_ISC 524.3 MB disk0s1
2: Apple_APFS Container disk3 245.1 GB disk0s2
3: Apple_APFS_Recovery 5.4 GB disk0s3
/dev/disk3 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +245.1 GB disk3
Physical Store disk0s2
1: APFS Volume Macintosh HD 15.3 GB disk3s1
2: APFS Snapshot com.apple.os.update-... 15.3 GB disk3s1s1
3: APFS Volume Preboot 306.3 MB disk3s2
4: APFS Volume Recovery 1.0 GB disk3s3
5: APFS Volume Data 64.1 GB disk3s5
6: APFS Volume VM 1.1 GB disk3s6
ok will do when i get home shortly all i have on me is this pic of prt of the instalation process i did have the one after but its magicly gone now and yes there are more problems that was just the last thing that that i had noticed take efect before watchdog couldnt find its own files maybe u seesomethingi just want the machine to run like it does thethe first few days after the restore apple did oct1 or the countless times i called support and they would just walk me through a erase reinstal so thats what i do whenever whatever comes in and starts signifantly altering things post the disk util in about an hour thank you
j2dkno1 wrote:
why if u erase and rename disk3 does disk utility change it to disk 4
might be a simple answer but Im not simply understanding. i have yet to encounter this with previous reinstalls. im hoping this means its working right for Monterey on an 2020 AirM1? Can anyone tell me if that is normal now?
Why are you having to reinstall on a 2020 AirM1— are you having some other issue besides micro-managing the naming protocol?
The numbering scheme is relative...not fixed .
Maybe a little more insight would be helpful here...
lets see the big picture from the Terminal.app copy&paste:
diskutil list internal
finally back home crazy day here is that
thanks i was just going by what the install log said so it looks like its all good where can i find how to protect again something else acquiring root privaliges
why if u erase and rename disk3 does disk utility change it to disk 4