Tuxera Ntfs Could Not Mount Because The Following Problem Occurred

Posted : admin On 30.03.2020
View unanswered posts View active topics It is currently Sun Apr 12, 2020 01:31

NTFS-3G could not mount - unclean shutdown

Moderator: unsound



Page 1 of 1
 [ 8 posts ]
Previous topic Next topic
AuthorMessage

Joined: Wed Dec 31, 2008 03:41
Posts: 2
NTFS-3G could not mount - unclean shutdown
'NTFS-3G could not mount /dev/disk3s1 at /Volumes/Untitled because the following problem occurred:
$LogFile indicated unclean shutdown 0, 0)'..(etc)
I have done all of the following:
  1. Installed the latest:
    - MacFUSE-2.0.3,2
    - NTFS-3G_1.5130u2-stable-catacombae
    - Developer Tools xcode312_2621
  2. Added '/dev/rdisk3s1 /Volumes/Untitled ntfs-3g force 0 0' to the /etc/fstab file
  3. Attempted to run 'mount -t ntfs-3g -o force /dev/disk3s1 /Volumes/Untitled'
  4. Run the strip command:
    sudo strip -arch ppc -no_uuid -S /Library/Filesystems/fusefs.fs/Support/fusefs.kext/Contents/MacOS/fusefs
    (BTW fuse.fs is not located in Library/Filesystems, not System/Library/Filesystems)

The old NTFS-3G worked just fine. I don't understand the point of the dialog instructions on how to force if it simply doesn't work. I get the 'could to mount' error every time and I am absolutely going nuts.
Someone please help.


Wed Dec 31, 2008 03:55

Joined: Tue Nov 21, 2006 23:15
Posts: 1648
The Windows taskbar always has an icon for external drivers, called 'Safely Remove Hardware'. Use it then NTFS-3G will mount the drive. The error means that you may lost data last time when you used Windows because you didn't follow Microsoft's instructions how to safely remove external disks.
If you don't have Windows anymore then type
sudo mkdir '/Volume/NTFS'
sudo /usr/local/bin/ntfs-3g -o force /dev/disk3s1 /Volume/NTFS


Wed Dec 31, 2008 12:00
I managed to get this drive to Windows system and unmounted it 'safely'. However, this is one of the very things I use NTFS-3G for: to access and backup a faulty Windows NTFS drive.
So, two things for you, as Lead Developer:
  1. Why are the instructions you posted to me above not what is in the dialog that appears, instead of what simply does not work? (And has caused MANY entries across the internet because of it.)
  2. Why not create a button option in said dialog, to just do it? (OK, Cancel, and Force)


Wed Dec 31, 2008 21:01

Joined: Sat Oct 06, 2007 09:24
Posts: 530
I'm actually responsible for that dialog, as I'm developing the Mac OS X glue that integrates NTFS-3G into Mac OS X.
The suggestion is interesting, but currently the dialog only exists to give the user some feedback as to why an inserted drive isn't mounted. It only displays the stdout and stderr output from ntfs-3g. It's implemented in an extremely unflexible way, by simply telling SystemUIServer to display a message.
It's a better option than silently ignoring the failed mount, but I agree that it would be even better if the user could interactively choose to force a mount, though it would require some development effort to realize that functionality..
There is a problem with this though.. Making it easier to mount a drive that wasn't unmounted properly could encourage bad/unsafe behaviour from the user, ultimately leading to data loss and unhappy users (it's really their own responsability, but still.. we shouldn't encourage this practice).
A big part of this issue is that it should be easier to remove a drive properly and cleanly from Windows.
Operating system environments often have various visual aids to help users to cleanly unmount drives, such as eject buttons next to removable drives and special icons to indicate which drives are removable.
Microsoft does provide a right-click menu option to eject drives, and lists them as removable when you look at drive details, but there is no eject button or icons that differentiate the drive from internal drives.
On top of that, it's often completely impossible to remove a drive from Windows cleanly because some process has opened a handle to a file on the drive, and there is no way of 'force' unmounting the drive and invalidate that open handle.


Fri Jan 02, 2009 09:12

Joined: Sat Oct 06, 2007 09:24
Posts: 530
Another thing to note is that the instructions, as returned when ntfs-3g fails to mount, doesn't fully apply to Mac OS X.
For instance: /etc/fstab is not used on Mac OS X.. it doesn't even exist on my Mac OS X system.. so that instruction is completely unsupported. I may add some conditional code around those lines in the future to prevent them from being displayed.


Fri Jan 02, 2009 09:22
I just got this same message on a maxtor external HD straight out of the box--it never had been unsafely unmounted to anything.
What can I do?
--eric


Wed Jan 21, 2009 00:55

Joined: Sat Oct 06, 2007 09:24
Posts: 530
What can I do?

You can run chkdsk /f on the drive on a Windows system and try again.
- Erik


Wed Jan 21, 2009 03:57
What can I do?

You can run chkdsk /f on the drive on a Windows system and try again.
- Erik

Difficult to do if you don't have a functioning one handy.
This is what I've found that works (cribbed from a post I found on this subject)
make a directory in /Volumes called NTFS
then run the following command:
sudo ntfs-3g /dev/diskXsY /Volumes/NTFS -olocale=en_US.UTF-8,force,auto_xattr,defer_auth,defer_permissions,volname='NTFS'
Where X and Y are the disk and partition numbers; the error message you get from the automounter contains this information. It will be something like /dev/disk3s1
This works to get dirty but still mountable NTFS volumes to mount, good for data recovery and such.
It probably ends up having issues back in Windows, but in general they're just going back in the box for a reformat and re-install of windows, so for our purposes this works well.


Wed Jan 21, 2009 23:38
Page 1 of 1
 [ 8 posts ]


Who is online

Users browsing this forum: No registered users and 10 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Original forum style by Vjacheslav Trushkin.

Unable to mount an external HDD on Mac. Tuxera NTFS could not mount /dev/disk1s2 at /Volumes/JoeBob because the following problem occurred. May 01, 2014  Hi, I'm newish here and have just got my self a 2010 Macbook Pro (first Mac ever:-)) im trying to get the Mac to read my external hard drive but having a problem getting it to how up. It is formatted in NTFS thats why im using NTFS-3G as was told that it should work. Once i plug the drive in and after about 1/2mins i get this message. NTFS-3G Could not mount Mac Applications. Justin, Your problem is that the filesystem on the LEXAR is possibly corrupted, so.

Omnisphere Hardware Synth IntegrationOmnisphere is the only software synth in the world to offer a Hardware Synth Integration feature. This remarkable innovation transforms over 65 well-known hardware synthesizers into extensive hands-on controllers that unlock Omnisphere’s newly expanded synthesis capabilities.

Tuxera Ntfs Could Not Mount Because The Following Problem Occurred Today

Everything you need to know about Tuxera NTFS for Mac. Everything you need to know about Tuxera NTFS for Mac. Everything you need to know about Tuxera NTFS for Mac. Dec 30, 2018 I just purchased the My Passport backup unit on November 30, 2018 from Target. The unit is not recognized on my PC. When I plugged it into my MacBook Pro, the following message appeared. What is it telling me? Tuxera NTFS Tuxera NTFS could not mount /dev/disk2s1 at /Volumes/My Passport because the following problem occurred: CBCIO activated with: cp.fildes=3 cp.blockSize=524288 cp.items=32 cp.

This allows very large files to be loaded very quickly, but it slows down RX’s waveform displays.Waveform interpolation order: If you zoom into the waveform so that individual samples become visible, RX will display an upsampled analog waveform as well as the individual digital samples. Tones at set frequencies or at a custom frequency can be used as test tones, as can white or pink noise. Higher values yield more accurate analog waveforms at the expense of CPU usage.Brightness: Adjusts the general brightness of the RX interface, allowing you to make RX more readable on your specific display.Floating window opacity: Changes the opacity for RX’s floating windows. The interpolation order controls the quality of upsampling. NoteRX will automatically display an analog waveform when zooming in at extreme zoom levels.Offload waveform calculations: When enabled, RX’s waveform display will be computed in the background. Izotope rx 6 torrent.

Tuxera Ntfs Could Not Mount Because The Following Problem Occurred In Excel

View unanswered posts View active topics It is currently Sun Apr 12, 2020 01:31

Tuxera NTFS could not mount (on OS X)

Moderator: unsound



Page 1 of 1
 [ 12 posts ]
Previous topic Next topic
AuthorMessage

Joined: Sun Jul 11, 2010 13:34
Posts: 6
Tuxera NTFS could not mount (on OS X)
I installed ntfs-3g-2010.5.22-macosx apparently successfully. However, whenever I start the computer (a Mac running OS X 10.6.4), I get the following error message:
'Tuxera NTFS could not mount /dev/disk1s1 at /Volumes/Elements because the following problem occurred:
/Library/Filesystems/fusefs.fs/Support/fusefs.kext failed to load -(libkern/kext) link error; check the system kernel logs for errors or try kextutil(8).
the MacFuse file system is not available(71) _nfts_volume_release(): Inode 9 still have 1 references.'
MacFuse appears to be installed. At least it appears on 'System Preferences'.
What is bad is that my external disk is not even visible after installing ntfs-3g.
I would appreciate any help you could give me.
Josep M.


Sun Jul 11, 2010 18:27

Joined: Sat Oct 06, 2007 09:24
Posts: 530
Re: Tuxera NTFS could not mount (on OS X)
Hi,
If you need to quickly get back your NTFS drives you can just disable NTFS-3G from the NTFS-3G preference pane in System preferences (Apple menu->System preferences->NTFS-3G).
It seems that MacFUSE is broken, or you're trying to use the software with an unsupported configuration such as the newer non-standard fully 64-bit kernel.
If you think that MacFUSE is broken, then try the following procedure:
There is an icon for MacFUSE in System preferences as well (or at least there should be one). Please click it and select 'Remove MacFUSE'. Then reinstall NTFS-3G (which will install MacFUSE with it if you don't deselect MacFUSE when installing). It's possible that this procedure fixes the problem.
Regards,
- Erik


Mon Jul 12, 2010 06:36
Hi. Thanks for the prompt response.
It seems that MacFUSE is broken, or you're trying to use the software with an unsupported configuration such as the newer non-standard fully 64-bit kernel.

I'm running my iMac in 64-bit mode. I did'nt know this was non-standard, though. Somewhere I have seen that there is a mixed mode so that apps that require 32-bit mode will run 32-bit and the OS as well as apps that can take advantage of the 64-bit processing will run in 64-bit mode. I haven't been able to figure out how to do this. As far as I can see the system gives me a choice between the two modes. It would be a bit unfortunate if you have to have a slower system in order to be able to use NTFS drives.
If you think that MacFUSE is broken, then try the following procedure:
There is an icon for MacFUSE in System preferences as well (or at least there should be one). Please click it and select 'Remove MacFUSE'. Then reinstall NTFS-3G (which will install MacFUSE with it if you don't deselect MacFUSE when installing). It's possible that this procedure fixes the problem.

Thanks for the tip. One thing I'm not clear about. I installed MacFUSE separately because it was my impression that you needed to do that with the free NTFS-3G version (as opposed to the comercial Tuxera-NTFS version which installed MacFUSE automatically). So if I install ntfs-3g-2010.5.22-macosx.dmg, this takes care of installing MacFUSE for me?
Again, thanks a lot for your help.
JM


Mon Jul 12, 2010 10:16

Joined: Sat Oct 06, 2007 09:24
Posts: 530
Re: Tuxera NTFS could not mount (on OS X)
Hi. Thanks for the prompt response.
It seems that MacFUSE is broken, or you're trying to use the software with an unsupported configuration such as the newer non-standard fully 64-bit kernel.

I'm running my iMac in 64-bit mode. I did'nt know this was non-standard, though. Somewhere I have seen that there is a mixed mode so that apps that require 32-bit mode will run 32-bit and the OS as well as apps that can take advantage of the 64-bit processing will run in 64-bit mode. I haven't been able to figure out how to do this. As far as I can see the system gives me a choice between the two modes. It would be a bit unfortunate if you have to have a slower system in order to be able to use NTFS drives.

This is a common misunderstanding. You do not have to do anything with your computer in order to do 64-bit computing and take advantage of the capabilities of your 64-bit processor. The stock kernel is a hybrid 32/64-bit kernel, fully capable of running 64-bit applications and giving them a 64-bit address space. The fully 64-bit kernel (RELEASE_X86_64) is to be used with systems that have more than 32 GiB of memory (the hybrid kernel cannot address more than 32 GiB), like the Xserve rack servers. For other systems it does not offer any signficant advantage (in general 64-bit code will use more resources because of the larger pointers needed, so it could even be slower) except perhaps in very special cases..
We are working on bringing support for the fully 64-bit kernel to our products, but in fact most people shouldn't use it yet (it's mostly for server use at this time).
If you think that MacFUSE is broken, then try the following procedure:
There is an icon for MacFUSE in System preferences as well (or at least there should be one). Please click it and select 'Remove MacFUSE'. Then reinstall NTFS-3G (which will install MacFUSE with it if you don't deselect MacFUSE when installing). It's possible that this procedure fixes the problem.

Thanks for the tip. One thing I'm not clear about. I installed MacFUSE separately because it was my impression that you needed to do that with the free NTFS-3G version (as opposed to the comercial Tuxera-NTFS version which installed MacFUSE automatically). So if I install ntfs-3g-2010.5.22-macosx.dmg, this takes care of installing MacFUSE for me?

Yes, both NTFS-3G and Tuxera NTFS for Mac come bundled with MacFUSE to make installation as easy as possible.
Regards,
- Erik


Mon Jul 12, 2010 10:26
Hi Erik and thanks a lot for your prompt and informative reply.
This is a common misunderstanding. You do not have to do anything with your computer in order to do 64-bit computing and take advantage of the capabilities of your 64-bit processor. The stock kernel is a hybrid 32/64-bit kernel, fully capable of running 64-bit applications and giving them a 64-bit address space. The fully 64-bit kernel (RELEASE_X86_64) is to be used with systems that have more than 32 GiB of memory (the hybrid kernel cannot address more than 32 GiB), like the Xserve rack servers. For other systems it does not offer any signficant advantage (in general 64-bit code will use more resources because of the larger pointers needed, so it could even be slower) except perhaps in very special cases..

OK, as you say the misunderstanding must be pretty common because I've read in many forums and sites (some of them looked like they were run by people who knew what they were talking about) that things run generally faster if you are in the 64-bit mode. I only have 8GB of ram so according to what you say I should be in the default 32-bit mode. But just see this sample of what I was talking about:
http://macperformanceguide.com/SnowLeopard-64bit.html
If you note, they do claim that 64-bit apps will run faster. I cannot find other links now where they claim that the whole system will in general faster and more efficient. Perhaps they were talking about previous versions of OS X and now things have improved?
JM


Mon Jul 12, 2010 19:59

Joined: Sat Oct 06, 2007 09:24
Posts: 530
Re: Tuxera NTFS could not mount (on OS X)
OK, as you say the misunderstanding must be pretty common because I've read in many forums and sites (some of them looked like they were run by people who knew what they were talking about) that things run generally faster if you are in the 64-bit mode. I only have 8GB of ram so according to what you say I should be in the default 32-bit mode. But just see this sample of what I was talking about:
http://macperformanceguide.com/SnowLeopard-64bit.html
If you note, they do claim that 64-bit apps will run faster. I cannot find other links now where they claim that the whole system will in general faster and more efficient. Perhaps they were talking about previous versions of OS X and now things have improved?
JM

The main difference would be between 64-bit and 32-bit user space applications. CPU intensive applications are supposed to spend most of their time in user space so any difference in performance between kernels would be hard to notice. The comparison that you linked to confirms that only for very specialized applications there's any noticeable difference at all.. but if you want to squeeze out that last 1-2% of a video rendering session you may be helped by the 64-bit kernel.
There is a reason that Apple don't turn on the fully 64-bit kernel by default, and it's simply that they don't consider it necessary until the machine can support more than 32 GiB of memory. The hybrid kernel is more compatible with legacy software too, and any difference in performance is marginal, so for the vast majority of people it's the right choice at the moment.. but yes we are planning a release that supports the fully 64-bit kernel, though no release date is known yet.
Regards,
- Erik


Mon Jul 12, 2010 20:54
OK dokey. I'll follow your advice, which sounds pretty sensible. I can always logon in 64-bit mode when I need to do those big rendering jobs.
JM


Mon Jul 12, 2010 21:07
I didn't remember about this but Apple itself contributes to the confusion we were discussing. I went to change the mode back to 32-bits and I see a message that says 'When your computer is restarted, it will run the following version of the Mac OS X kernel:
32-bit (slower, uses less memory, better compatibility)
64-bit (faster, uses more memory, some older kernel extensions will not load)


Mon Jul 12, 2010 21:26

Joined: Sat Oct 06, 2007 09:24
Posts: 530
Re: Tuxera NTFS could not mount (on OS X)
I didn't remember about this but Apple itself contributes to the confusion we were discussing. I went to change the mode back to 32-bits and I see a message that says 'When your computer is restarted, it will run the following version of the Mac OS X kernel:
32-bit (slower, uses less memory, better compatibility)
64-bit (faster, uses more memory, some older kernel extensions will not load)

Is that really a message printed by Apple? As far as I know there's no built in 'switching' feature in Mac OS X. You have to either edit the NVRAM settings, the boot config file, or press '6' and '4' while the computer is booting to get the fully 64-bit kernel if you are not using any third party 'switching' app.


Mon Jul 12, 2010 21:30
Is that really a message printed by Apple? As far as I know there's no built in 'switching' feature in Mac OS X. You have to either edit the NVRAM settings, the boot config file, or press '6' and '4' while the computer is booting to get the fully 64-bit kernel if you are not using any third party 'switching' app.

You are totally right. This message is from an app called SixtyFour Switcher. I just wasn't thinking when I said it was from Apple.
JM


Mon Jul 12, 2010 22:42
I am running into the exact same problem on a stock hexacore Mac Pro I just bought.
I don't even know how to switch the kernel between 32 and 64-bit modes, so it appears that Apple is now preinstalling kernels in 64-bit mode. What is the fix?


Sat Sep 18, 2010 07:08

Joined: Sat Oct 06, 2007 09:24
Posts: 530
Re: Tuxera NTFS could not mount (on OS X)
Hi,
I am running into the exact same problem on a stock hexacore Mac Pro I just bought.
I don't even know how to switch the kernel between 32 and 64-bit modes, so it appears that Apple is now preinstalling kernels in 64-bit mode. What is the fix?

The latest release candidate of Tuxera NTFS for Mac supports the fully 64-bit kernels. You can grab it from here:
http://www.tuxera.com/products/tuxera-ntfs-for-mac/
We would love to have your feedback on how the driver works for you under the 64-bit kernel.
If you would prefer not to run a 'release candidate', you can switch to the 32/64-bit hybrid kernel with a simple click of a button using an application called K64Enabler:
http://timesoftware.free.fr/k64enabler/
I hope this helps.
Regards,
- Erik


Sat Sep 18, 2010 08:27
Page 1 of 1
 [ 12 posts ]


Who is online

Users browsing this forum: No registered users and 10 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Original forum style by Vjacheslav Trushkin.