macOS Sierra Install issue - Could not mount /dev/rdisk4s1

Help and Support
1

Trying to install the Raspberry Pi Zero 2017.04-1 version to a 32GB Sandisk MicroSDHC card.
I’m using the built-in SDXC card reader on my MacBook Pro and the MicroSD->SD converter which came with my Pi.
I’ve tried several different branded MicroSD cards and a brand new full size 64GB SanDisk SDXC card (ie. without the converter)

OS version is macOS Sierra 10.12.5 on a ‘Mid 2012 13" MacBook Pro’

In all cases, the install fails at the end:

Mon Jun 5 18:02:46 2017 OSMC Installer running on Mac OS X
Mon Jun 5 18:02:47 2017 Detected locale as en_GB
Mon Jun 5 18:02:47 2017 Attempting to load translation for locale en_GB
Mon Jun 5 18:02:47 2017 Could not load translation!
Mon Jun 5 18:02:47 2017 Resolving a mirror
Mon Jun 5 18:02:48 2017 Resolved mirror to http://anorien.csc.warwick.ac.uk/mirrors/osmc/osmc/download/
Mon Jun 5 18:02:48 2017 Enumerating supported devices
Mon Jun 5 18:02:48 2017 Added the following devices
Mon Jun 5 18:02:48 2017 Vero 4K
Mon Jun 5 18:02:48 2017 Vero 2
Mon Jun 5 18:02:48 2017 Vero
Mon Jun 5 18:02:48 2017 Raspberry Pi 1 / Zero
Mon Jun 5 18:02:48 2017 Raspberry Pi 2 / 3
Mon Jun 5 18:02:48 2017 Apple TV
Mon Jun 5 18:02:48 2017 Checking for updates
Mon Jun 5 18:02:48 2017 Checking for updates by downloading http://anorien.csc.warwick.ac.uk/mirrors/osmc/osmc/download//installers/latest_mac
Mon Jun 5 18:02:48 2017 Acquired mirror file
Mon Jun 5 18:02:48 2017 No new update is available
Mon Jun 5 18:02:58 2017 The user has selected English as their language
Mon Jun 5 18:02:58 2017 The user has selected Raspberry Pi 1 / Zero as their device
Mon Jun 5 18:02:58 2017 Attempting to download device versions file http://anorien.csc.warwick.ac.uk/mirrors/osmc/osmc/download/installers/versions_RBP
Mon Jun 5 18:02:59 2017 Found a build called  2017.04-1
Mon Jun 5 18:02:59 2017 Found a build called  2017.03-1
Mon Jun 5 18:02:59 2017 Found a build called  2017.02-2
Mon Jun 5 18:02:59 2017 Found a build called  2017.01-1
Mon Jun 5 18:02:59 2017 Found a build called  2016.12-1
Mon Jun 5 18:02:59 2017 Found a build called  2016.11-1
Mon Jun 5 18:02:59 2017 Found a build called  2016.10-1
Mon Jun 5 18:02:59 2017 Found a build called  2016.09-1
Mon Jun 5 18:02:59 2017 Found a build called  2016.08-1
Mon Jun 5 18:03:31 2017 The user has selected an online image for Raspberry Pi 1 / Zero with build URL : http://anorien.csc.warwick.ac.uk/mirrors/osmc/osmc/download/installers/diskimages/OSMC_TGT_rbp1_20170504.img.gz
Mon Jun 5 18:03:31 2017 Disabling internal install for device Raspberry Pi 1 / Zero as it does not support it
Mon Jun 5 18:03:32 2017 SD installation selected
Mon Jun 5 18:03:42 2017 Wireless network configured with SSID xxxxx key value xxxxx
Mon Jun 5 18:03:42 2017 Enumerating imageable devices for OSX
Mon Jun 5 18:03:42 2017 New disk device entry created with entry point /dev/rdisk0, 250.1 GB free space and label 
Mon Jun 5 18:03:42 2017 =================================================
Mon Jun 5 18:03:42 2017 Starting to parse /dev/rdisk0 for additional info

Mon Jun 5 18:03:42 2017 MediaName-Line: Device / Media Name: Crucial_CT250MX200SSD1
Mon Jun 5 18:03:42 2017 Protocol-Line: Protocol: SATA
Mon Jun 5 18:03:42 2017 Determined SATA as protocol for /dev/rdisk0
Mon Jun 5 18:03:42 2017 Decided to be a DMG: no
Mon Jun 5 18:03:42 2017 R/O-Line: Read-Only Media: No
Mon Jun 5 18:03:42 2017 parsed/split/simplified readOnly line would have been: No
Mon Jun 5 18:03:42 2017 Determined No as readOnlyMedia for /dev/rdisk0
Mon Jun 5 18:03:42 2017 Decided to be r/o: no
Mon Jun 5 18:03:42 2017 Ejectable-Line: Removable Media: Fixed
Mon Jun 5 18:03:42 2017 Determined Fixed as ejactableProperty for /dev/rdisk0
Mon Jun 5 18:03:42 2017 Decided that /dev/rdisk0 is not writable to us
Mon Jun 5 18:03:42 2017 Parsed device as NON-writable. NOT Appending.
Mon Jun 5 18:03:42 2017 

Mon Jun 5 18:03:42 2017 Finished parsing additional info for /dev/rdisk0
Mon Jun 5 18:03:42 2017 =================================================

Mon Jun 5 18:03:42 2017 New disk device entry created with entry point /dev/rd248.8, Crucial SSD free space and label 
Mon Jun 5 18:03:42 2017 =================================================
Mon Jun 5 18:03:42 2017 Starting to parse /dev/rd248.8 for additional info

Mon Jun 5 18:03:43 2017 Decided that /dev/rd248.8 is not writable to us
Mon Jun 5 18:03:43 2017 Parsed device as NON-writable. NOT Appending.
Mon Jun 5 18:03:43 2017 

Mon Jun 5 18:03:43 2017 Finished parsing additional info for /dev/rd248.8
Mon Jun 5 18:03:43 2017 =================================================

Mon Jun 5 18:03:43 2017 New disk device entry created with entry point /dev/rdisk3, +25.4 MB free space and label 
Mon Jun 5 18:03:43 2017 =================================================
Mon Jun 5 18:03:43 2017 Starting to parse /dev/rdisk3 for additional info

Mon Jun 5 18:03:43 2017 MediaName-Line: Device / Media Name: Disk Image
Mon Jun 5 18:03:43 2017 Protocol-Line: Protocol: Disk Image
Mon Jun 5 18:03:43 2017 Determined Disk Image as protocol for /dev/rdisk3
Mon Jun 5 18:03:43 2017 Decided to be a DMG: yes
Mon Jun 5 18:03:43 2017 R/O-Line: Read-Only Media: Yes
Mon Jun 5 18:03:43 2017 parsed/split/simplified readOnly line would have been: Yes
Mon Jun 5 18:03:43 2017 Determined Yes as readOnlyMedia for /dev/rdisk3
Mon Jun 5 18:03:43 2017 Decided to be r/o: yes
Mon Jun 5 18:03:43 2017 Ejectable-Line: Removable Media: Removable
Mon Jun 5 18:03:43 2017 Determined Removable as ejactableProperty for /dev/rdisk3
Mon Jun 5 18:03:43 2017 Decided that /dev/rdisk3 is not writable to us
Mon Jun 5 18:03:43 2017 Parsed device as NON-writable. NOT Appending.
Mon Jun 5 18:03:43 2017 

Mon Jun 5 18:03:43 2017 Finished parsing additional info for /dev/rdisk3
Mon Jun 5 18:03:43 2017 =================================================

Mon Jun 5 18:03:43 2017 New disk device entry created with entry point /dev/rdisk4, 31.9 GB free space and label 
Mon Jun 5 18:03:43 2017 =================================================
Mon Jun 5 18:03:43 2017 Starting to parse /dev/rdisk4 for additional info

Mon Jun 5 18:03:43 2017 MediaName-Line: Device / Media Name: Built In SDXC Reader
Mon Jun 5 18:03:43 2017 Protocol-Line: Protocol: Secure Digital
Mon Jun 5 18:03:43 2017 Determined Secure Digital as protocol for /dev/rdisk4
Mon Jun 5 18:03:43 2017 Decided to be a DMG: no
Mon Jun 5 18:03:43 2017 R/O-Line: Read-Only Media: No
Mon Jun 5 18:03:43 2017 parsed/split/simplified readOnly line would have been: No
Mon Jun 5 18:03:43 2017 Determined No as readOnlyMedia for /dev/rdisk4
Mon Jun 5 18:03:43 2017 Decided to be r/o: no
Mon Jun 5 18:03:43 2017 Ejectable-Line: Removable Media: Removable
Mon Jun 5 18:03:43 2017 Determined Removable as ejactableProperty for /dev/rdisk4
Mon Jun 5 18:03:43 2017 isEjectable: yes; isDmg: no; isReadOnly: no
Mon Jun 5 18:03:43 2017 Parsed device as writable. Appending.
Mon Jun 5 18:03:43 2017 

Mon Jun 5 18:03:43 2017 Finished parsing additional info for /dev/rdisk4
Mon Jun 5 18:03:43 2017 =================================================

Mon Jun 5 18:03:45 2017 Device selected: 3	/dev/rdisk4	31.9 GB	Built In SDXC Reader
Mon Jun 5 18:03:48 2017 EULA has been accepted
Mon Jun 5 18:03:48 2017 Downloading http://anorien.csc.warwick.ac.uk/mirrors/osmc/osmc/download/installers/diskimages/OSMC_TGT_rbp1_20170504.img.gz
Mon Jun 5 18:03:50 2017 Extracting /Users/roobarb/OSMC_TGT_rbp1_20170504.img.gz
Mon Jun 5 18:03:55 2017 Finished extraction. Going to write image
Mon Jun 5 18:03:55 2017 Requesting confirmation from user
Mon Jun 5 18:04:12 2017 User confirmed
Mon Jun 5 18:04:12 2017 going to start osa
Mon Jun 5 18:04:12 2017 pasting admin script to process do shell script "dd if=/Users/roobarb/OSMC_TGT_rbp1_20170504.img of=/dev/rdisk4 bs=1m conv=sync && sync" with administrator privileges
Mon Jun 5 18:04:12 2017 waiting for finish
Mon Jun 5 18:04:27 2017 osa claims to be done...collect output and verify
Mon Jun 5 18:04:27 2017 Imaging was successful
Mon Jun 5 18:04:27 2017 Image successfully written to device
Mon Jun 5 18:04:27 2017 Deleting the uncompressed image to save space
Mon Jun 5 18:04:27 2017 Creating preseeder
Mon Jun 5 18:04:27 2017 Adding preseed stringd-i target/storage string sd
Mon Jun 5 18:04:27 2017 Adding preseed stringd-i network/interface string wlan
Mon Jun 5 18:04:27 2017 Adding preseed stringd-i network/auto boolean true
Mon Jun 5 18:04:27 2017 Adding preseed stringd-i network/ssid string xxxxx
Mon Jun 5 18:04:27 2017 Adding preseed stringd-i network/wlan_keytype string 1
Mon Jun 5 18:04:27 2017 Adding preseed stringd-i network/wlan_key string xxxxx
Mon Jun 5 18:04:27 2017 Writing preseeder
Mon Jun 5 18:04:27 2017 Mounting the first filesystem on /dev/rdisk4
Mon Jun 5 18:04:27 2017 Trying to umount before we are remounting and writing the preseed.
Mon Jun 5 18:04:28 2017 Mounting /dev/rdisk4s1 to /var/folders/y2/n240prq94134clzffckxsy6m0000gn/T/osmc_mnt
Mon Jun 5 18:04:28 2017 Could not mount /dev/rdisk4s1. Messages are: stdErr: Volume on disk4s1 failed to mount
If the volume is damaged, try the "readOnly" option

 stdOut: 
Mon Jun 5 18:04:28 2017 Could not mount filesystem!

Physically reinserting the card works and mounts the partition:

/dev/disk4 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *31.9 GB    disk4
   1:             Windows_FAT_32 NO NAME                 254.8 MB   disk4s1

Any suggestions?

2

Do you have antivirus software?
Something may be getting a hold on the device and preventing our installer from proceeding.

Also try a reboot if you can

3

It looks like the partition has already been written to. Why not try it in the Pi and see if it boots?

4

AntiVirus - No.
Reboot - No change.

5

So, the MicroSD card boots in my Pi (Pi Zero Wireless) but, as expected, the wireless config wasn’t pre populated.

Looks like I’m actually good to go but it’d be nice to iron out that final step with the installed.

6

It will boot.
We only need to remount the partition to write the preseed.cfg file so that his WiFi works out of the box. If @Roobarb doesn’t mind doing this manually, then I’d just recommend booting up.

7

Yeah, same thing happened to me to this morning…

8

Same here. I tried 3 different SD cards with 2 different ‘setups’ (Mac SD-slot and SD-card reader via USB). All 6 combinations resulted in the ‘could not mount’-error.

I suspected corrupt SD cards, but when I ended up doing a manual installation, everything worked fine.

9

See When will OS X mount error solved? - #7 by sam_nazarko

Feedback much appreciated

Sam