So, my Time Machine drive would not mount after I unmounted it during a period of time when I was offline on purpose. After using Disk Repair multiple times, still did not mount. Used Onyx which found a disk error and told me to restart holding down Command-R. It restarted in a mode I have not seen before and gave me a window with the option to run Disk Utility again.

This time Disk Utility found a bitmap error and a file count error, which it was able to repair. Then I got a window asking me if I wanted to run OSX Fuse, whatever that is. Closed the window and the same application showed up in System Preferences panel when I went to go there to turn on Time Machine. Clicked on it and asked me if I wanted to remove it and I clicked yes. But it is still there.

(TM drive is now mounted)

Command-R got you into your recovery partition, and this is why you needed to get there:


(Doc was last updated in 2-26-2016, so I'm not sure why it doesn't mention recovery partition.)

I haven't got a clue how OSXFUSE got into the picture; as far as I can tell it's a 3rd party d/l that wouldn't even be on your Mac under ordinary circumstances.

How do I get rid of it?

Btw, after I ran Disk Utilty under the other started mode Onyx stopped alerting me of the errors. The disk tested perfectly.

This looks promising:


(I'd search afterwards just to make sure they're on the mark.)

But the better question is how did it get there in the first place?


Yep! That's expected...well, hoped for, anyhow.

I have had Fuse installed as a support utility for another application. I can't say which one of yours required it, but it can appear without directly and consciously installing Fuse.

slolerner found it after running "Repair Disk" in recovery mode preceded by having run OnyX while booted into OS X.

It doesn't seem like something like that ought to be able to happen in recovery mode, but maybe that's just my erroneous impression of the nature of the beast.

Got me beat. :osxfused:

What exactly does Fuse do?

Certainly made things easier.

And please don't ask me what that means.

I meant that it doesn't seem like OSXFUSE should have happened under the circumstances.

Hmm, seems like another piece of "sneaky" software. Glad I use TechTool Pro for my disk repair/maintenance (after I have run Onyx), as I have never seen it.

It means that it is used to allow the Mac to fully support files systems other than Mac OS or FAT, for example NTFS. As I recall Parallels Desktop and other Windows emulator apps install MacFuse or OSXFUSE to allow OS X to read AND write to NTFS formatted disks.

It even occurs to me it might be used on the Recovery Drive(?)

Thanks for that; my best guess would have been no better than a paraphrase of my post.


If that's the case, I wonder what circumstances invoked its appearance in slolerner's instance?

Could I have installed it when I installed special software so I could view my back MRIs?

That's a possibility, particularly because I seem to remember you having mentioned platform problems with the software, but that was a while ago; could oyu have overlooked it for so long?

Wonder if following the steps above to get rid of it will also remove it from the Recovery HD partition? If not, then maybe the Recovery HD partition needs to be deleted/removed, and then "re-installed" again.

For both of my Macs, I have an eDrive bootable partition which one creates after initially installing TechTool Pro. It can perform the same functions as Disk Utility, and also do more useful tasks. One can also use it to restore from a clone backup. It cannot, though, perform an installation of the Mac OS, like the Recovery HD partition can. But, I have that covered, as when I have an issue that requires "external" software, I just boot my Mac from my most recent SuperDuper! backup.

Yes.

Then I'll go with its likely being associated with the MRI software. (Any chance you can find the thread in which it was discussed?)

Just to clarify, did you get the OSXFUSE pop-up when you were still booted into your recovery partition or after you booted back into OS X? (Edit: The presence of OSXFUSE in System Prefs has led me to assume the latter, nor do I think that there's any way for3rd party apps to run in recovery mode.)

Can't remember whether it came up as an a recovery partition but that is probably why it came to my attention.
I remember the Control Panel icon for it looked like a drive.

I'm looking for the thread, I found the one where Grelber suggested I get a "1990-something Ford Taurus bucket seat" at my desk in lieu of surgery.

Found it! Post 33285

It has never even occurred to me that a recovery partition is an "open system" despite its ability to access the Internet via Safari, and an attempt to d/l OSXFUSE into mine just now failed..."insufficient space". (I think it's a pretty fair assumption that a recovery partition is "no write" under any circumstances.)

Me, I'd just forget about it. OSXF is no longer on your boot volume, and if it's on your recovery partition it's there by default.

(Wrong thread. I was thinking of the one in which you described having trouble viewing your MRIs...needing different software.)

If there is any possibility that this "rogue" software could be on the Recovery HD partition, then one can delete/remove it, and then rebuild it again. This link explains how to remove it:

http://osxdaily.com/2011/06/30/deleting-the-mac-os-x-10-7-lion-recovery-hd-partition/

After doing that, this link explains how to rebuild it (note that it assumes one has the "Install OS X whatever" file someplace, whether on the internal drive or somewhere else):

http://www.macworld.com/article/2602951/...-any-drive.html

Note also that one cannot use that software with a Fusion Drive setup.

I have used that gem of software quite a few times, and it works as advertised. In fact, after my last SuperDuper! "Restore all files" to my Mac Mini, there was no Recovery HD partition (SuperDuper! does not backup the Recovery HD partition. Carbon Copy Cloner does). So, I just ran Recovery Partition Creator, and sure enough, I was able to rebuild that partition. Although I do not really need it (have the eDrive partition also), I just wanted to prove that it works.