Mount of MacFuse image fails with error "no mountable file systems"

[GoogleCodeExporter]

What steps will reproduce the problem?

1. install MacFuse 0.1.7 and NTFS-3G 1.516
2. Force mount of an external HD wich wasnt automatically mounted, as
descibed in this faq:
http://shadowofged.blogspot.com/2007/03/ntfs-3g-for-mac-os-x.html#faq-nomount.
The forced mount will also fail.
3. Uninstall NTFS-3G running the installation package. Uninstall MacFuse by
 deleting the files listed in issue 36.
4. Try to mount any instalation package of MacFuse

What is the expected output? What do you see instead?

Successful mount of the instalation package. Error message: no mountable
file systems

What version of the product are you using? On what operating system?

first version instaled 0.1.7. Mount of versions 0.1.7, 0.1.9, 0.3.0 fail.
Mac OS X 10.4.9

Please provide any additional information below.

I installed version 0.1.7 and tried to uninstall using the steps described
in issue 36. I couldnt manage to build the script, pasting the code in the
ScriptEditor. (I am a newbie in Mac Os or Unix as I said, but I am an
experienced Windows user)

Nevertheless I moved all the files listed to the trash, but I could have
missed some. Therefore I'd like to have a tip on how to build and run a Script.

The  error I am getting is that when I try to mount file
MacFUSE-Core-0.3.0.dmg it fails with the message: no mountable file
systems. Versions 0.1.7 and 0.1.9 also fails with the same message.

The issue started after I downloaded and installed MAcFuse Core 0.1.7 and
NTFS-3G after reading the following article:
http://www.lifehack.org/articles/lifehack/how-to-read-and-write-ntfs-windows-par
tition-on-mac-os-x.html

As after installation my external harddrive was recognized by the system
but wasnt mounted, I followed the support on NTFS-3G on this page:
http://shadowofged.blogspot.com/2007/03/ntfs-3g-for-mac-os-x.html, again
with no success.

My guess is that the versions 0.1.7 of MacFuse and 1.516 of NTFS-3G are
incompatible.

Thanks for any help,

Matheus

Original issue reported on code.google.com by matheus....@gmail.com on 25 May 2007 at 12:14

[GoogleCodeExporter]

MacFUSE 0.1.7 is very, very obsolete. You really shouldn't be using it.

Please don't report usage issues with obsolete MacFUSE versions and/or specific 
MacFUSE file systems as "bugs" 
here. This ticket system is only for tracking bugs/issues with MacFUSE itself. 
Use the macfuse-devel mailing list 
instead for such things.

Try rebooting and installing the latest version of MacFUSE (0.3.0 at this 
time). It should take care of uninstalling 
the previous version--you don't need to write any scripts to uninstall things. 
The articles you're reading sound 
like the're either obsolete or incorrect, or perhaps both.

Original comment by si...@gmail.com on 25 May 2007 at 1:42

[GoogleCodeExporter]

Still not able to mount any MacFUSE Core image even after rebooting.

Moving the discussion to MacFUSE-devel mailing list:
http://groups.google.com/group/macfuse-devel/browse_thread/thread/248ea1ee92f129
1c

Original comment by matheus....@gmail.com on 26 May 2007 at 12:57

[GoogleCodeExporter]

You're talking about not being able to mount the MacFUSE installer dmg--did you 
try redownloading the dmg?

Original comment by si...@gmail.com on 26 May 2007 at 1:11

• Changed state: Invalid

[GoogleCodeExporter]

Hi, I have installed MacFUSE 0.3.0 and eventually ended up with the "No 
mountable
file systems" error with 50% of all .dmg files failing. It sounds like the 
thing I
have in common with the initial commenter is the usage of the Lifehack page's
terminal code possibly written for an obsolete version of MacFUSE. But for all 
I know
it could be an interaction problem between ping_diskarb deployment in Terminal 
and
the new MacFUSE.

Is it possible that the following code deploys ping_diskarb in a detrimental 
way now
that MacFUSE apparently handles an aspect of this automatically? I can mount 
the .dmg
using a third-party program like Toast but not with the Finder/Disk-mounter. 
When I
do so with Toast, it asks for a system-password as though there is an underlying
permissions issue.

I do not know if this is a problem/interaction with MacFUSE, NTFS-3g, etc. or 
if this
interaction with the Terminal code below constitutes buggy behavior. I 
apologize if I
am submitting this comment to the wrong forum.

Here is the code:

# Create symlink for mount_fusefs: sudo ln -s
/System/Library/Filesystems/fusefs.fs/mount_fusefs /usr/bin/mount_fusefs
# Create a new directory: mkdir /Volumes/Windows
# Mount the NTFS volume: sudo /usr/local/bin/ntfs-3g /dev/disk0s2 
/Volumes/”Windows”
-o ping_diskarb,volname=”Windows”

If this code is partially to blame, it is unfortunate that the Lifehack page 
comes up
so high in a Google search of MacFUSE and NTFS-3g as other people may have 
similar
problem and no recourse.

Original comment by supp...@natewerks.com on 26 May 2007 at 7:50

[GoogleCodeExporter]

I share the same sentiments of all. Firstly Google should NOT let the lifehack 
page score higher than Singh's 
page if Singh's the official one. Secondly, great if we can all upgrade to 
0.3.0 - what is the issues of publishing 
the manual way of removing 0.1.7, and for that matter all the versions? 
Thirdly, the main issue here is that even 
with uninstall MacFuse, it does not solve a more severe issue - how to 
uninstall ntfs-3g cleanly from the system.

Original comment by jkm...@gmail.com on 27 May 2007 at 3:41

[GoogleCodeExporter]

Found the problem - NTFS-3G. If you have followed the lifehack.org way and 
installed MacFUSE Core 0.1.7 and 
NTFS-3G, you are stuck with the 0.3.0 DMG that Singh is distributing.

You need to manually remove NTFS-3G from the different directories as 
superuser, the uninstall scripts in 
NTFS-3G distribution does not do a thorough job. 

Then the DMG for 0.3.0 will mount as per normal :-)

Original comment by jkm...@gmail.com on 27 May 2007 at 5:21

[GoogleCodeExporter]

Many many thanks JK! I was not sure how to track down the individual 
files belonging to the NTFS-3G distribution so I attempted to run the 
NTFS-3G Uninstaller with "sudo" (read somewhere that the uninstaller 
is "broken").  

Didn't appear to work until I reinstalled MacFUSE 0.3.0 
and then reinstalled NTFS-3G  ;)  ...I navigated to the NTFS-3G disk 
image directory (which I was able to mount; Toast would probably be 
able to mount it as well) and finally ran this in termiinal "\

sudo ./Uninstall.command / NTFS-3G

I restarted to be safe and was once 
again able to mount .dmg files. 

perfect timing! THANK YOU 

Original comment by supp...@natewerks.com on 27 May 2007 at 7:26

[GoogleCodeExporter]

After manually removing the folder /System/Library/Filesystems/NTFS-3G.fs it 
worked.

Thank you all for helping me solve this issue!

Original comment by matheus....@gmail.com on 28 May 2007 at 2:22

[GoogleCodeExporter]

> Firstly Google should NOT let the lifehack page score higher than Singh's 
> page if Singh's the official one.

I don't see how Google's supposed to do that.

> Secondly, great if we can all upgrade to 0.3.0 - what is the issues of 
publishing 
> the manual way of removing 0.1.7, and for that matter all the versions?

If you install the MacFUSE 0.3.0 package available from *this web site*, it 
should upgrade you from any 
previous MacFUSE version downloaded from *this web site*. You're involving 
packages from other web sites 
though.

The "manual way" is published, and has been published for a long time. The 
problem is not with publishing it, 
the problem is with people not reading it. Did you look at the FAQ on this web 
site? There's a question "How 
can I uninstall MacFUSE Core?"

> Thirdly, the main issue here is that even  with uninstall MacFuse,
> it does not solve a more severe issue - how to uninstall ntfs-3g cleanly from 
the system.

And it also does not make coffee.

Since the MacFUSE package available from this web site doesn't include ntfs-3g 
to begin with, why, and how, 
should it know about uninstalling ntfs-3g or whatever else cleanly from the 
system?

Anyway, *MacFUSE* does nothing to impair your systems's disk image mounting 
capabilities.

Original comment by si...@gmail.com on 29 May 2007 at 5:34