Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Question:

Question: macOS (APFS) and bootcamp partitions no longer mount

I recently applied two updates to my Windows 7 system (system is kept up to date regularly). They were applied following a shutdown. When I rebooted a short time later, the system started from my High Sierra backup drive. My primary macOS (High Sierra, APFS) and Windows 7 partitions configured on a hardware RAID drive (Velocity x2) did not appear in the Finder.


I ran diskutil list in a terminal window and got the following results:

User uploaded file

The RAID is 500GB total created from two 250GB Samsung SSDs (disk5). It is encouraging to see two partitions showing up in the terminal window, although the APFS volume shows as HFS.


I wanted to post here before I make any recovery attempt. Another user suggested booting into Parted Magic. The Partition Editor has an option to scan but I'm concerned that it might do more than read and report. Although the Windows bootcamp partition is actually more important to me right now, I would like to get back the APFS partition also if possible.


Hopefully this is something simple for those skilled using the terminal window.


Good to see that Loner T is still active here. 🙂


My system is a 2009 MacPro.

Posted on

Reply

Page content loaded

Mar 9, 2018 3:08 PM in response to Loner T In response to Loner T

The system is currently booting from a backup of High Sierra on separate drive. This is what was used to generate the diskutil output I posted. Neither OS on the RAID drive is bootable. No attempt by an older macOS system to access an APFS volume has been made.


NOTE: I have a Sierra drive too but not have not booted from it since moving to HS. Not that you've warned me, I won't! 🙂

Mar 9, 2018 3:08 PM

Reply Helpful

Mar 9, 2018 8:33 PM in response to Loner T In response to Loner T

Yep. I know how to create one. No problem to do that but I'm curious though on why diskutil list must be done from an external boot drive. Looks like my High Sierra backup drive has a working recovery boot option. I have not tried it yet though. Would that be okay to use?


Thanks.

Mar 9, 2018 8:33 PM

Reply Helpful

Mar 9, 2018 8:49 PM in response to Jeff Robertson In response to Jeff Robertson

Here is the terminal output when booted from the recovery partition.


Let me know if this is ok.


-bash-3.2# diskutil list

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *128.0 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_APFS Container disk3 127.8 GB disk0s2


/dev/disk1 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *64.0 GB disk1

1: EFI EFI 209.7 MB disk1s1

2: Apple_HFS Sierra 63.7 GB disk1s2


/dev/disk2 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: FDisk_partition_scheme *500.1 GB disk2

1: Windows_NTFS Storage 500.1 GB disk2s1


/dev/disk3 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +127.8 GB disk3

Physical Store disk0s2

1: APFS Volume Backup 37.8 GB disk3s1

2: APFS Volume Preboot 21.0 MB disk3s2

3: APFS Volume Recovery 522.8 MB disk3s3

4: APFS Volume VM 20.5 KB disk3s4


/dev/disk4 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *2.0 TB disk4

1: EFI EFI 209.7 MB disk4s1

2: Apple_HFS Stash 2.0 TB disk4s2


/dev/disk5 (disk image):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme +2.1 GB disk5

1: Apple_HFS OS X Base System 2.0 GB disk5s1


/dev/disk6 (external, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *250.1 GB disk6

1: EFI EFI 209.7 MB disk6s1

2: Apple_HFS 249.7 GB disk6s2


/dev/disk7 (disk image):

#: TYPE NAME SIZE IDENTIFIER

0: untitled +5.2 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 +524.3 KB disk10


/dev/disk11 (disk image):

#: TYPE NAME SIZE IDENTIFIER

0: untitled +2.1 MB disk11


/dev/disk12 (disk image):

#: TYPE NAME SIZE IDENTIFIER

0: untitled +524.3 KB disk12


/dev/disk13 (disk image):

#: TYPE NAME SIZE IDENTIFIER

0: untitled +524.3 KB disk13


/dev/disk14 (disk image):

#: TYPE NAME SIZE IDENTIFIER

0: untitled +12.6 MB disk14


/dev/disk15 (disk image):

#: TYPE NAME SIZE IDENTIFIER

0: untitled +2.1 MB 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 +2.1 MB disk17


/dev/disk18 (disk image):

#: TYPE NAME SIZE IDENTIFIER

0: untitled +524.3 KB 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 +1.0 MB disk20


/dev/disk21 (disk image):

#: TYPE NAME SIZE IDENTIFIER

0: untitled +6.3 MB disk21


/dev/disk22 (disk image):

#: TYPE NAME SIZE IDENTIFIER

0: untitled +6.3 MB disk22


/dev/disk23 (disk image):

#: TYPE NAME SIZE IDENTIFIER

0: untitled +524.3 KB disk23


/dev/disk24 (disk image):

#: TYPE NAME SIZE IDENTIFIER

0: untitled +2.1 MB disk24


-bash-3.2#

Mar 9, 2018 8:49 PM

Reply Helpful

Mar 10, 2018 3:59 AM in response to Jeff Robertson In response to Jeff Robertson

My primary macOS (High Sierra, APFS) and Windows 7 partitions configured on a hardware RAID drive (Velocity x2) did not appear in the Finder.

Since the underlying RAID configuration is not visible from diskutil, your current output does show an APFS container and a NTFS file system. Do these no longer mount, but can they be manually mounted?


Which specific W7 patches were applied?

Mar 10, 2018 3:59 AM

Reply Helpful

Mar 10, 2018 7:15 AM in response to Loner T In response to Loner T

One of the updates was for security essentials definitions. The other was a single critical system update but I did not note which one. It was part of the monthly updates for March, I'm sure.


Mounting did not go so well, with the exception of the EFI:


Mac-Pro:~ jeff$ diskutil mount /dev/disk5

Volume on disk5 failed to mount; if it has a partitioning scheme, use "diskutil mountDisk"

If the volume is damaged, try the "readOnly" option

Mac-Pro:~ jeff$ diskutil mount readOnly /dev/disk5

Volume on disk5 failed to mount; if it has a partitioning scheme, use "diskutil mountDisk"

If the volume is damaged, try the "readOnly" option

Mac-Pro:~ jeff$ diskutil mount readOnly /dev/disk5s1

Volume EFI on /dev/disk5s1 mounted

Mac-Pro:~ jeff$ diskutil mount readOnly /dev/disk5s2

Volume on disk5s2 failed to mount

If the volume is damaged, try the "readOnly" option


Although not listed above I did try mountDisk also.

Mar 10, 2018 7:15 AM

Reply Helpful

Mar 10, 2018 7:23 AM in response to Jeff Robertson In response to Jeff Robertson

Based on the last output from diskutil list, disk5 is

/dev/disk5 (disk image):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme +2.1 GB disk5

1: Apple_HFS OS X Base System 2.0 GB disk5s1

which should already be mounted and should be your boot disk. If disk5 is something different, did you reboot? Reboot can renumber disks.

Mar 10, 2018 7:23 AM

Reply Helpful

Mar 10, 2018 7:29 AM in response to Loner T In response to Loner T

My apologies. I tried to mount while booted normally from the backup drive. I'll be able to actually see the mounted volumes this way, if successful.


Should I stay in the recovery boot while troubleshooting, for now?

Mar 10, 2018 7:29 AM

Reply Helpful
User profile for user: Jeff Robertson

Question: macOS (APFS) and bootcamp partitions no longer mount