diskutil list shows 20 disk partitions, I only know 3, what are the rest?FFFFFFFF problem with hybrid partitioned drive, not able to fix with the guide in other topicsMackbook Pro, can't boot into Windows, how to fix the MBR?Why do I have /Volumes/Storage Drive?I think I messed up the Fusion Drive on my 1TB iMac (with BootCamp)Install rEFInd on another partitionBoot Camp failed and reduced Macintosh HD partition from 3TB to 1,46TBCannot Repair Macintosh HD, after loading into OSX, it become a [X]Messed up 1TB Fusion Drive Partitions (on iMac 5K) - 100% Disk Space usedSluggish 2013 21.5" El Capitan iMacMounting an external hard disk clone that shares the same partition GUIDs as the source/host hard diskMy Fusion Drive Partitioning Seems Wrong/Strange/WonkyHow to fix “error: no room for the backup header”
What happened to Captain America in Endgame?
A strange hotel
How do I reattach a shelf to the wall when it ripped out of the wall?
How do I check if a string is entirely made of the same substring?
Is there an implicit type promotion in "float = float - float"?
Can two odd numbers sum up to an odd number?
Why must Chinese maps be obfuscated?
A Paper Record is What I Hamper
Mistake in years of experience in resume?
My bank got bought out, am I now going to have to start filing tax returns in a different state?
How do I produce this Greek letter koppa: Ϟ in pdfLaTeX?
"Whatever a Russian does, they end up making the Kalashnikov gun"? Are there any similar proverbs in English?
Is there really no use for MD5 anymore?
Which term is being referred to with "reflected-sound-of-underground-spirits"?
What is the most expensive material in the world that could be used to create Pun-Pun's lute?
Is there a grandfather paradox in Endgame?
What is meant by "Prämie" in this letter? Do I have to pay it or it is just a reminder?
How do I deal with a coworker that keeps asking to make small superficial changes to a report, and it is seriously triggering my anxiety?
Critique of timeline aesthetic
As an international instructor, should I openly talk about my accent?
Can a barbarian keep raging if she shoves an enemy on her turn?
How to not starve gigantic beasts
Negative Resistance
Determine the application client is using to connect
diskutil list shows 20 disk partitions, I only know 3, what are the rest?
FFFFFFFF problem with hybrid partitioned drive, not able to fix with the guide in other topicsMackbook Pro, can't boot into Windows, how to fix the MBR?Why do I have /Volumes/Storage Drive?I think I messed up the Fusion Drive on my 1TB iMac (with BootCamp)Install rEFInd on another partitionBoot Camp failed and reduced Macintosh HD partition from 3TB to 1,46TBCannot Repair Macintosh HD, after loading into OSX, it become a [X]Messed up 1TB Fusion Drive Partitions (on iMac 5K) - 100% Disk Space usedSluggish 2013 21.5" El Capitan iMacMounting an external hard disk clone that shares the same partition GUIDs as the source/host hard diskMy Fusion Drive Partitioning Seems Wrong/Strange/WonkyHow to fix “error: no room for the backup header”
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
Following the post FFFFFFFF problem with hybrid partitioned drive, not able to fix with the guide in other topics, diskutil list gives me the following big list of disk partitions, what are the /dev/disk3 to /dev/disk20, can I delete them, and how?
-bash-3.2# diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *251.0 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF 217.0 GB disk0s2
3: Microsoft Basic Data BOOTCAMP 33.8 GB disk0s3
/dev/disk1 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *16.0 GB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_HFS Install macOS Mojave 15.7 GB disk1s2
/dev/disk2 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme +2.1 GB disk2
1: Apple_HFS OS X Base System 2.0 GB disk2s1
/dev/disk3 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +5.2 MB disk3
/dev/disk4 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk4
/dev/disk5 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk5
/dev/disk6 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk6
/dev/disk7 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +2.1 MB disk7
/dev/disk8 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk8
/dev/disk9 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk9
/dev/disk10 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +12.6 MB disk10
/dev/disk11 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +4.2 MB disk11
/dev/disk12 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +1.0 MB disk12
/dev/disk13 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +2.1 MB disk13
/dev/disk14 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk14
/dev/disk15 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk15
/dev/disk16 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +1.0 MB disk16
/dev/disk17 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +6.3 MB disk17
/dev/disk18 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +6.3 MB disk18
/dev/disk19 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk19
/dev/disk20 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +2.1 MB disk20
-bash-3.2# gpt -r show disk0
gpt show: disk0: Suspicious MBR at sector 0
start size index contents
0 1 MBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
409640 423829464 2 GPT part - FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF
424239104 65994752 3 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
490233856 863
490234719 32 Sec GPT table
490234751 1 Sec GPT header
-bash-3.2#
hard-drive disk-utility partition
asked 2 hours ago
answersunanswersun
255
New contributor
answersun is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Following the post FFFFFFFF problem with hybrid partitioned drive, not able to fix with the guide in other topics, diskutil list gives me the following big list of disk partitions, what are the /dev/disk3 to /dev/disk20, can I delete them, and how?
-bash-3.2# diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *251.0 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF 217.0 GB disk0s2
3: Microsoft Basic Data BOOTCAMP 33.8 GB disk0s3
/dev/disk1 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *16.0 GB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_HFS Install macOS Mojave 15.7 GB disk1s2
/dev/disk2 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme +2.1 GB disk2
1: Apple_HFS OS X Base System 2.0 GB disk2s1
/dev/disk3 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +5.2 MB disk3
/dev/disk4 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk4
/dev/disk5 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk5
/dev/disk6 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk6
/dev/disk7 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +2.1 MB disk7
/dev/disk8 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk8
/dev/disk9 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk9
/dev/disk10 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +12.6 MB disk10
/dev/disk11 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +4.2 MB disk11
/dev/disk12 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +1.0 MB disk12
/dev/disk13 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +2.1 MB disk13
/dev/disk14 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk14
/dev/disk15 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk15
/dev/disk16 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +1.0 MB disk16
/dev/disk17 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +6.3 MB disk17
/dev/disk18 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +6.3 MB disk18
/dev/disk19 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk19
/dev/disk20 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +2.1 MB disk20
-bash-3.2# gpt -r show disk0
gpt show: disk0: Suspicious MBR at sector 0
start size index contents
0 1 MBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
409640 423829464 2 GPT part - FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF
424239104 65994752 3 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
490233856 863
490234719 32 Sec GPT table
490234751 1 Sec GPT header
-bash-3.2#
hard-drive disk-utility partition
asked 2 hours ago
answersunanswersun
255
New contributor
answersun is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Following the post FFFFFFFF problem with hybrid partitioned drive, not able to fix with the guide in other topics, diskutil list gives me the following big list of disk partitions, what are the /dev/disk3 to /dev/disk20, can I delete them, and how?
-bash-3.2# diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *251.0 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF 217.0 GB disk0s2
3: Microsoft Basic Data BOOTCAMP 33.8 GB disk0s3
/dev/disk1 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *16.0 GB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_HFS Install macOS Mojave 15.7 GB disk1s2
/dev/disk2 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme +2.1 GB disk2
1: Apple_HFS OS X Base System 2.0 GB disk2s1
/dev/disk3 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +5.2 MB disk3
/dev/disk4 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk4
/dev/disk5 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk5
/dev/disk6 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk6
/dev/disk7 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +2.1 MB disk7
/dev/disk8 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk8
/dev/disk9 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk9
/dev/disk10 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +12.6 MB disk10
/dev/disk11 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +4.2 MB disk11
/dev/disk12 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +1.0 MB disk12
/dev/disk13 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +2.1 MB disk13
/dev/disk14 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk14
/dev/disk15 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk15
/dev/disk16 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +1.0 MB disk16
/dev/disk17 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +6.3 MB disk17
/dev/disk18 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +6.3 MB disk18
/dev/disk19 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk19
/dev/disk20 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +2.1 MB disk20
-bash-3.2# gpt -r show disk0
gpt show: disk0: Suspicious MBR at sector 0
start size index contents
0 1 MBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
409640 423829464 2 GPT part - FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF
424239104 65994752 3 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
490233856 863
490234719 32 Sec GPT table
490234751 1 Sec GPT header
-bash-3.2#
hard-drive disk-utility partition
asked 2 hours ago
answersunanswersun
255
New contributor
answersun is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Following the post FFFFFFFF problem with hybrid partitioned drive, not able to fix with the guide in other topics, diskutil list gives me the following big list of disk partitions, what are the /dev/disk3 to /dev/disk20, can I delete them, and how?
-bash-3.2# diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *251.0 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF 217.0 GB disk0s2
3: Microsoft Basic Data BOOTCAMP 33.8 GB disk0s3
/dev/disk1 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *16.0 GB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_HFS Install macOS Mojave 15.7 GB disk1s2
/dev/disk2 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme +2.1 GB disk2
1: Apple_HFS OS X Base System 2.0 GB disk2s1
/dev/disk3 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +5.2 MB disk3
/dev/disk4 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk4
/dev/disk5 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk5
/dev/disk6 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk6
/dev/disk7 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +2.1 MB disk7
/dev/disk8 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk8
/dev/disk9 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk9
/dev/disk10 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +12.6 MB disk10
/dev/disk11 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +4.2 MB disk11
/dev/disk12 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +1.0 MB disk12
/dev/disk13 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +2.1 MB disk13
/dev/disk14 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk14
/dev/disk15 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk15
/dev/disk16 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +1.0 MB disk16
/dev/disk17 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +6.3 MB disk17
/dev/disk18 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +6.3 MB disk18
/dev/disk19 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk19
/dev/disk20 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +2.1 MB disk20
-bash-3.2# gpt -r show disk0
gpt show: disk0: Suspicious MBR at sector 0
start size index contents
0 1 MBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
409640 423829464 2 GPT part - FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF
424239104 65994752 3 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
490233856 863
490234719 32 Sec GPT table
490234751 1 Sec GPT header
-bash-3.2#
hard-drive disk-utility partition
hard-drive disk-utility partition
asked 2 hours ago
answersunanswersun
255
New contributor
answersun is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 2 hours ago
answersunanswersun
255
New contributor
answersun is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 2 hours ago
answersunanswersun
255
New contributor
answersun is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 2 hours ago
answersunanswersun
255
asked 2 hours ago
answersunanswersun
255
255
New contributor
answersun is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
answersun is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answersun is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I presume you’re running diskutil list from the Recovery environment. These disks are not real disks, shown by the ‘disk image’ phrase appended to the name of the disk. They are used to support Recovery as temporary read/write areas separate from the main HD. If you run diskutil list from a normal installation of macOS, these disks are missing as they are not necessary.
answered 2 hours ago
grg♦grg
139k25221327
Yes, thediskutil listresult was from recovery environment (booted in macOS installation disk), so it is normal and I don't need to worry about it?
– answersun
1 hour ago
@answersun Yes it's perfectly normal in the recovery environment.
– grg♦
1 hour ago
Thank you for your information @grg, I'll accept your answer.
– answersun
1 hour ago
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I presume you’re running diskutil list from the Recovery environment. These disks are not real disks, shown by the ‘disk image’ phrase appended to the name of the disk. They are used to support Recovery as temporary read/write areas separate from the main HD. If you run diskutil list from a normal installation of macOS, these disks are missing as they are not necessary.
answered 2 hours ago
grg♦grg
139k25221327
Yes, thediskutil listresult was from recovery environment (booted in macOS installation disk), so it is normal and I don't need to worry about it?
– answersun
1 hour ago
@answersun Yes it's perfectly normal in the recovery environment.
– grg♦
1 hour ago
Thank you for your information @grg, I'll accept your answer.
– answersun
1 hour ago
add a comment |
I presume you’re running diskutil list from the Recovery environment. These disks are not real disks, shown by the ‘disk image’ phrase appended to the name of the disk. They are used to support Recovery as temporary read/write areas separate from the main HD. If you run diskutil list from a normal installation of macOS, these disks are missing as they are not necessary.
answered 2 hours ago
grg♦grg
139k25221327
Yes, thediskutil listresult was from recovery environment (booted in macOS installation disk), so it is normal and I don't need to worry about it?
– answersun
1 hour ago
@answersun Yes it's perfectly normal in the recovery environment.
– grg♦
1 hour ago
Thank you for your information @grg, I'll accept your answer.
– answersun
1 hour ago
add a comment |
I presume you’re running diskutil list from the Recovery environment. These disks are not real disks, shown by the ‘disk image’ phrase appended to the name of the disk. They are used to support Recovery as temporary read/write areas separate from the main HD. If you run diskutil list from a normal installation of macOS, these disks are missing as they are not necessary.
answered 2 hours ago
grg♦grg
139k25221327
I presume you’re running diskutil list from the Recovery environment. These disks are not real disks, shown by the ‘disk image’ phrase appended to the name of the disk. They are used to support Recovery as temporary read/write areas separate from the main HD. If you run diskutil list from a normal installation of macOS, these disks are missing as they are not necessary.
answered 2 hours ago
grg♦grg
139k25221327
answered 2 hours ago
grg♦grg
139k25221327
answered 2 hours ago
grg♦grg
139k25221327
answered 2 hours ago
grg♦grg
139k25221327
139k25221327
Yes, thediskutil listresult was from recovery environment (booted in macOS installation disk), so it is normal and I don't need to worry about it?
– answersun
1 hour ago
@answersun Yes it's perfectly normal in the recovery environment.
– grg♦
1 hour ago
Thank you for your information @grg, I'll accept your answer.
– answersun
1 hour ago
add a comment |
Yes, thediskutil listresult was from recovery environment (booted in macOS installation disk), so it is normal and I don't need to worry about it?
– answersun
1 hour ago
@answersun Yes it's perfectly normal in the recovery environment.
– grg♦
1 hour ago
Thank you for your information @grg, I'll accept your answer.
– answersun
1 hour ago
Yes, the
diskutil list result was from recovery environment (booted in macOS installation disk), so it is normal and I don't need to worry about it?– answersun
1 hour ago
Yes, the
diskutil list result was from recovery environment (booted in macOS installation disk), so it is normal and I don't need to worry about it?– answersun
1 hour ago
@answersun Yes it's perfectly normal in the recovery environment.
– grg♦
1 hour ago
@answersun Yes it's perfectly normal in the recovery environment.
– grg♦
1 hour ago
Thank you for your information @grg, I'll accept your answer.
– answersun
1 hour ago
Thank you for your information @grg, I'll accept your answer.
– answersun
1 hour ago
add a comment |
