#Volume could not be unmounted imac pro how to#
#Volume could not be unmounted imac pro mac os x#
#Volume could not be unmounted imac pro pro#
#Volume could not be unmounted imac pro password#

Is there any normal reason the System HD would unmount/appear unmounted like that? It's a mystery I would like to solve before it claims any other victims.įirst post here, but having gotten great info from this forum even BEFORE we had Jamf, I'm hopping someone has some bright ideas. I can't tell if this is a hardware fault, OSX related, Jamf related, or perhaps a combo.

#Volume could not be unmounted imac pro how to#

If anybody can shed some light on what might've caused this, how to solve without data loss, or anything worth trying or checking into I would greatly appreciate it. Teacher lost her data though.įigured it was a one off fluke that night, but was greeted by an email from a colleague asking if anybody else had seen this the following morning, so now I'm concerned. Ultimately I could get nothing to work but erasing the disk which then mounted it afterward and I could re-install the OS and so far it's running as expected again. Tried First-Aid and it failed, tried using the Terminal to repair the disk, still failed. I attempted to re-mount it but nothing happened. Stumped, I booted into recovery mode, and checked the Disk Utility, only to find that the internal system boot disk was unmounted. Tried several times and made absolutely sure it was being entered correctly.

#Volume could not be unmounted imac pro password#

However, when I entered the password for the local admin account it didn't work. Since she could not get in from there she brought it to me. Instead, the local administrator account appeared there with a space for the password. When it came back up, the usual 'Username/Password' login screen was not there. The teacher was having trouble connecting to the wifi and restarted the machine. Both reports and subsequent symptoms were identical. Can't confirm exact timing but they were within a day of each other for sure. So far this has happened on 2 separate MacBook Airs (2019 model).

I figured I'd put it up here and see if anyone has any insight, so here's the scoop. Of course not on the same machine, but I've been keeping settings from machine to machine, and old stuff gets to accumulate.), but I don't think it will find (and delete/fix) hidden snapshots.Īlso, I'm a fan of Onyx, which usually fixes almost everything and always recovers a lot of disk space, but, this time, even Onyx gets stumped.We recently started using Jamf in our school district and ran into a very weird issue recently that quite frankly I can't explain and a couple hours scouring the internet was of little to no help.

#Volume could not be unmounted imac pro mac os x#

I'm also exploring a bit with DaisyDisk, and finding lots of interesting garbage to delete (note that I've been progressively upgrading Mac OS X since. I wonder if the only way out is going the way of reformatting the SSD disk with HFS+. Time Machine automatic backups are shut down. This time, however, tmutil listLocalSnapshotDates / didn't show anything by contrast, tmutil listLocalSnapshots / gives .-003459 (dataless), but I have no way to delete that (assuming it's even possible to do so). I did tmutil listLocalSnapshotDates / and it did find one local snapshot, which I deleted as per instructions then I tried to run fsck_apfs again (in SU mode), and it failed at the exact spot with the same error message.

#Volume could not be unmounted imac pro pro#

Sadly, it didn't work for me (running 10.13.2 Beta (17C79a) on a MacBook Pro (Retina, 15-inch, Mid 2014)). Targeting the main partition (/dev/rdisk1s1), it'd say that live repairs weren't supported yet.įinally, I'm getting a similar error to what albugna is getting which I have a feeling is related to this. Seemingly no matter what I did, it would say the drive as a whole (ie /dev/rdisk1) was mounted with write access even with the drive completely ejected. Even booting the 10.13 installer from a flash drive, for the life of me, I couldn't get fsck_apfs to even attempt to repair anything. As far as I can tell, fsck_apfs (so by extension, Disk Utility and diskutil) isn't able do any repairs right now because it thinks the APFS drive is perpetually mounted. Still, even with the local snapshots deleted (and automatic backups disabled to prevent new snapshots from being created), I get the same the same 'error 8' in SU or Recovery mode. TM, however, seems to be working fine regardless. Using 'tmutil deleteLocalSnapshots ' to delete all the local snapshots, I no longer get 'Snapshot is invalid.' So Apple has apparently (and so far, poorly) integrated features for TM directly into APFS. This seems to be related to/caused by local Time Machine snapshots.