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 topicsMacBook 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”
Feels like I am getting dragged into office politics
How to implement float hashing with approximate equality
How to get SEEK accessing converted ID via view
Problems with numbers (result of calculations) alignment using siunitx package inside tabular environment
How did Arya manage to disguise herself?
Is lying to get "gardening leave" fraud?
Who died in the Game of Thrones episode, "The Long Night"?
How did Captain America use this power?
Applying a function to a nested list
Selecting a secure PIN for building access
What are the spoon bit of a spoon and fork bit of a fork called?
How did Arya get back her dagger from Sansa?
If an enemy is just below a 10-foot-high ceiling, are they in melee range of a creature on the ground?
Historically, were women trained for obligatory wars? Or did they serve some other military function?
What happened to Rhaegal?
Disabling Resource Governor in SQL Server
Can I use 1000v rectifier diodes instead of 600v rectifier diodes?
Unexpected email from Yorkshire Bank
Floor tile layout process?
How long can a 35mm film be used/stored before it starts to lose its quality after expiry?
Power LED from 3.3V Power Pin without Resistor
What is the most remote airport from the center of the city it supposedly serves?
How do I tell my manager that his code review comment is wrong?
Stark VS Thanos
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 topicsMacBook 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 Apr 26 at 9:28
answersunanswersun
405
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 Apr 26 at 9:28
answersunanswersun
405
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 Apr 26 at 9:28
answersunanswersun
405
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 Apr 26 at 9:28
answersunanswersun
405
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 Apr 26 at 9:28
answersunanswersun
405
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 Apr 26 at 9:28
answersunanswersun
405
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 Apr 26 at 9:28
answersunanswersun
405
asked Apr 26 at 9:28
answersunanswersun
405
405
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.
Just boot back to a normal OS installation and running diskutil list will not show these disks as they are not necessary for normal functioning in a fully booted macOS.
edited Apr 26 at 19:10
bmike♦
163k46293634
answered Apr 26 at 10:11
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
Apr 26 at 10:38
@answersun Yes it's perfectly normal in the recovery environment.
– grg♦
Apr 26 at 10:38
Thank you for your information @grg, I'll accept your answer.
– answersun
Apr 26 at 10:40
It should be made clear that a list of discs is not a list of disc partitions.
– JdeBP
Apr 26 at 14:41
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.
Just boot back to a normal OS installation and running diskutil list will not show these disks as they are not necessary for normal functioning in a fully booted macOS.
edited Apr 26 at 19:10
bmike♦
163k46293634
answered Apr 26 at 10:11
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
Apr 26 at 10:38
@answersun Yes it's perfectly normal in the recovery environment.
– grg♦
Apr 26 at 10:38
Thank you for your information @grg, I'll accept your answer.
– answersun
Apr 26 at 10:40
It should be made clear that a list of discs is not a list of disc partitions.
– JdeBP
Apr 26 at 14:41
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.
Just boot back to a normal OS installation and running diskutil list will not show these disks as they are not necessary for normal functioning in a fully booted macOS.
edited Apr 26 at 19:10
bmike♦
163k46293634
answered Apr 26 at 10:11
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
Apr 26 at 10:38
@answersun Yes it's perfectly normal in the recovery environment.
– grg♦
Apr 26 at 10:38
Thank you for your information @grg, I'll accept your answer.
– answersun
Apr 26 at 10:40
It should be made clear that a list of discs is not a list of disc partitions.
– JdeBP
Apr 26 at 14:41
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.
Just boot back to a normal OS installation and running diskutil list will not show these disks as they are not necessary for normal functioning in a fully booted macOS.
edited Apr 26 at 19:10
bmike♦
163k46293634
answered Apr 26 at 10:11
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.
Just boot back to a normal OS installation and running diskutil list will not show these disks as they are not necessary for normal functioning in a fully booted macOS.
edited Apr 26 at 19:10
bmike♦
163k46293634
answered Apr 26 at 10:11
grg♦grg
139k25221327
edited Apr 26 at 19:10
bmike♦
163k46293634
edited Apr 26 at 19:10
bmike♦
163k46293634
edited Apr 26 at 19:10
bmike♦
163k46293634
163k46293634
answered Apr 26 at 10:11
grg♦grg
139k25221327
answered Apr 26 at 10:11
grg♦grg
139k25221327
answered Apr 26 at 10:11
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
Apr 26 at 10:38
@answersun Yes it's perfectly normal in the recovery environment.
– grg♦
Apr 26 at 10:38
Thank you for your information @grg, I'll accept your answer.
– answersun
Apr 26 at 10:40
It should be made clear that a list of discs is not a list of disc partitions.
– JdeBP
Apr 26 at 14:41
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
Apr 26 at 10:38
@answersun Yes it's perfectly normal in the recovery environment.
– grg♦
Apr 26 at 10:38
Thank you for your information @grg, I'll accept your answer.
– answersun
Apr 26 at 10:40
It should be made clear that a list of discs is not a list of disc partitions.
– JdeBP
Apr 26 at 14:41
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
Apr 26 at 10:38
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
Apr 26 at 10:38
@answersun Yes it's perfectly normal in the recovery environment.
– grg♦
Apr 26 at 10:38
@answersun Yes it's perfectly normal in the recovery environment.
– grg♦
Apr 26 at 10:38
Thank you for your information @grg, I'll accept your answer.
– answersun
Apr 26 at 10:40
Thank you for your information @grg, I'll accept your answer.
– answersun
Apr 26 at 10:40
It should be made clear that a list of discs is not a list of disc partitions.
– JdeBP
Apr 26 at 14:41
It should be made clear that a list of discs is not a list of disc partitions.
– JdeBP
Apr 26 at 14:41
add a comment |
