Tuxera NTFS could not mount /dev/disk2s1 at....

Hi
I Have just bought an Apple MacBook MC207. I have an Ext HDD which was formatted on Vista and I was able to view files, but not able to write to the HDD. I researched and found Tuxera, and thought this would enable me to write to the HDD. After installation though I am now unable to even read the HDD let alone write to the HDD.
I also researched the error on the website and followed the instructions on how to remove the program, but it hasn't worked.
Here is the error:
Tuxera NTFS could not mount /dev/disck2s1 at /Volumes/New Volume because the following occured:
CBCIO activated with:
cp.fildeds=3
cp.blockSize=524288
cp.items=32
cp.mode=1
WARNING: ReadFully - I/O error while reading from
file (5: 'Input/output error')
WARNING: failed at: pread(3, 0x600000, 518656,
3220701184);
WARNING: bytesRead=0
ntfs_attr_pread_i: ntfs_pread failed: Input/output
error
Failed to read $AttrDef, unexpected length (-1 !=
2560).
_ntfs_volume_release(): Inode 4 still have 1
references.
Failed to mount ' /dev/rdisk2s1': Inout/output error
NTFS is either inconsistent, or there is a hardware
fault, or it's a
SoftRAID/FakeRAID hardware.
etc etc
If anyone can help then it would be greatly appreciated! Many thanks in advance.
Riksta

Joined: Sat Oct 06, 2007 09:24
Posts: 530

Re: Tuxera NTFS could not mount /dev/disk2s1 at....

Hi,

Could you please post the error message that you get when trying to uninstall? Or if you aren't getting any, then please describe what happens when you press the uninstall button in the preference pane.

Have you checked your drive with chkdsk in Windows, following the instructions in the FAQ?
It seems that there's some inconsistency with the $AttrDef file, and hopefully it can be fixed by chkdsk.
Regards,
- Erik

Re: Tuxera NTFS could not mount /dev/disk2s1 at....

Hi,
After using my purchased Tuxera NTFS 2010.1 for a few weeks with it working perfectly, Tuxera NTFS just started displaying an error dialog about every 2 seconds. This is happening regardless whether the only NTFS volume is mounted or not and whether Windows XP is running in VMWare Fusion or not. The only way that I can stop the error dialogs was to uninstall Tuxera NTFS.
See attached screen shot of Tuxera NTFS error dialog.
My system is the following:
MacPro 3.1,1 (2 x Xeon processors, 8 cores)
OS: 10.6.2
Memory: 18GB
Internal Disks: Bay 1 = 300GB, Bay 2 = 1TB, Bay 3 = 1TB, Bay 4 = 2TB
One volume named 'DHD4-NTFS' (320GB) is the second partition on the 2TB drive (see attached screen shot). There are no other NTFS volumes on my Mac except 2 VMWare Fusion Virtual Disks inside the Window XP virtual machine.
Thank you,
Don
There have been no recent software updates.
Anyone know what might be happening?

Re: Tuxera NTFS could not mount /dev/disk2s1 at....

I have this problem in MacOS X.
Tuxera NTFS could not mount /dev/disk2s1
at /Volumes/Untitled because the following problem occurred:
CBCIO activated with:
cp.fildes=3
cp.blockSize=524288
cp.items=32
cp.mode=1
cp.flushInterval=1000
$MFTMirr does not match $MFT (record 0).
Failed to mount '/dev/rdisk2s1': Input/output error
NTFS is either inconsistent, or there is a hardware fault, or it's a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very
important! If the device is a SoftRAID/FakeRAID then first activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
for more details.

Joined: Sat Oct 06, 2007 09:24
Posts: 530

Re: Tuxera NTFS could not mount /dev/disk2s1 at....

Hi,

Have you checked your NTFS drive in Windows with 'chkdsk /f' as suggested in the error message, and in the FAQ? Does this fix your issue?
Please see the following URL for information about running 'chkdsk': http://support.microsoft.com/kb/315265
Regards,
- Erik

Re: Tuxera NTFS could not mount /dev/disk2s1 at....

I too am having the same problem. I have almost given up on this product. It worked for a few weeks and now nothing.
I have tried this with numerous drives all to no avail.
Is there anyone out there with a solution other than running chkdsk with windows. I don't believe every drive I have would be problematic including the last one I checked which worked initially and 3 months later it doesn't even though I haven't used the drive since then!?!

Joined: Sat Oct 06, 2007 09:24
Posts: 530

Re: Tuxera NTFS could not mount /dev/disk2s1 at....

Are you sure you are having the same problem? Many people think that it's the same problem just because the drive won't mount, but the exact wording of the error message does matter.
If you are a Tuxera NTFS for Mac customer, then please feel free to contact our dedicated support email (see your activation email), where we'll be happy to troubleshoot your setup to find out what the problem is.
Regards,
- Erik

Joined: Tue Dec 02, 2008 02:48
Posts: 7

NTFS-3g volume RAW in Vista, strange in OSX

Hi,
I have an external 1tb usb-drive, which has been formatted as NTFS. Previously it has worked well, but since this morning it wouldn't work in Vista. Explorer says the volume is corrupt, Disk Management says it's RAW but chkdsk works just fine. Just can't access the files in any way.
Also, in OSX 10.5.5 the drive works file most of the time, but occasionally it freezes. In Disk Utility it shows up as disk3s1 and doesn't show the partitions real name. When it's mounted, it's in /Volumes/Untitled instead of /Volumes/Teranen.
Manually mounting in the right dir gives this:

(ignore the pid file, not running as su)
Still, the drive gets mounted, and in the right directory as long as it's not removed or the system isn't rebooted.
The first problem is the most severe, as I would like to access my files in both OSX and Vista (otherwise i'd just format it as HFS).
Any ideas?

Joined: Sat Oct 06, 2007 09:24
Posts: 530

When the drive gets mounted as Untitled instead of whatever your real volume label is, it's usually because of some conflict between what ntfs-3g and ntfsprogs (which is used for label retrieval) thinks is a mountable volume.
Szaka has promised to integrate a ntfs-3g.label utility which will remedy that issue in the future.
However, your drive doesn't seem to be in mint condition..
When you say that 'the drive freezes'.. that makes me think you have a hardware error. It also seems really odd that Vista can run chkdsk on the volume, but not mount it.
I think you should back up your important data and run a disk test with 'badblocks' booting from some Linux live CD. If bad sectors are found, get the drive replaced.

Thanks for the reply. I doubt that this is a hardware issue since the drive is just about 1 week old Buffalo DriveStation, but i'll run badblocks asap. If I find no bad blocks i'll get back to this matter, otherwise i'll just have to get it replaced.

Joined: Sat Oct 06, 2007 09:24
Posts: 530

How did you create the NTFS volume?
Even though the NTFS-3G file system bundle can create NTFS volumes (using mkntfs) I would usually prefer to have Windows create the volume. It also eliminates the possibility that you have chosen a non-MBR partition table.
But.. as you had it working earlier, I guess that's not the issue.
Have you ever unplugged your drive without properly unmounting it first (..which is done in Windows by choosing 'Safe Remove Hardware' or in Mac OS X by clicking the eject button next to the volume)?
The issue with Vista not recognizing a drive that passed through chkdsk without issues should be reported to Microsoft, because that's not what you would expect..

I created the volume with OSX Disk Utility and made sure it was MBR. Then I used TeraCopy in Vista to transfer files to the new volume, so yes, it worked in the beginning.
I have disconnected the drive without properly unmounting it in Vista, but after this I booted back to Vista and ran chkdsk to allow normal automount with ntfs-3g and no errors were found. Since then I haven't removed the disk while the pc has been on.
I checked the volume on Ubuntu Livecd and it's recognized properly and mounted in /mnt/Teranen as it should be. GParted shows the volume correctly as NTFS but in mount it is of type 'fuseblk', but I think this is normal.
I'll set it to run badblocks during the night, since it's a 8,5h job.

So I think the disk is physically fine, as I thought. But could the problem be in the MBR or partition table? Just throwing ideas around..

Joined: Sat Oct 06, 2007 09:24
Posts: 530

You could do some forensic investigation on your MBR.. Linux utilities like GParted should be able to give you info on that.
But.. since you have had it working previously, I wouldn't bet too much on any problem with the MBR.
What do you see when you start up 'Administrative Tools'->'Computer Management' (an MMC snapin) in Vista and browse to 'Disk Management'? What does Vista say about the drive and which volumes are on it?

Quick answer in a hurry: Gparted shows the disk OK, diskmgmt.mmc shows a RAW volume after a long seek time on the drive. Every time I try to use the disk in Vista it seeks for about a minute and then shows an error or RAW-volume, except chkdsk. Posted the question also on Microsoft TechNet, no answers yet.

Joined: Thu Jan 15, 2009 03:53
Posts: 8
Location: Texas

Hello Folks..just joined the forum.. Comment for Unsound.
My external 500GB USB Seagate drive was prepared under WinVista with it's Disk Mgr, which pretty much provided an NTFS partition and 465GB of space availability. After installing MacFUSE and NTFS-3g on my Mac with OS X 10.4.11 I connected my Seagate drive, NTFS-3g mounted my drive without any problems whatsoever, immediately I began copying files from my Mac internal HDD over (music, video files etc) as backup. Now here's the catch.
1) I was really hoping I would be able to move freely between my Mac and my Vista environments, this would solve many issues for me at this point in time. Nevertheless, once it finished copying everything (a 2 day process) I decided to check it out on my Vista PC.. Big time surprise!!!
2) ON Vista my drive mounts, yeah it does but unreadable pretty much same symptom couple of the guys here in the forum have mentioned. I checked the drive it's fully operational but shows as RAW. I then moved back to my Mac, and it mounts and shows all my files.. that's a relief.
What I thought and correct me here please, that we would be able to port between both environments, to my surprise when I checked my new drive with Disk Utility (Mac OS) it says that my drive is MAC OS X Journaled.. since when ? I never formatted the drive on my Mac in the first place, since then I've only been able to mount read/write on my Mac..
Is there a way I can gain access to my NTFS filesystem ? what would you recommend ?
Thanks
George

Joined: Sat Oct 06, 2007 09:24
Posts: 530

Hi George,

I really can't help you here. If your drive is really HFS+ formatted all of a sudden (Mac OS Extended (journaled)), then someone must have done something to make that happen. This does not happen automatically, ever.
Did you have anything on the drive before you connected it to your mac? In that case, can that data still be accessed?

Could you post a screenshot from the 'Info' window in Disk Utility for the affected drive (select the affected volume and click the 'info' button)? Or you could copy-paste the text in that window to a forum post..
Also what happens when you type , with X and Y substituted for the drive/partition numbers of the affected drive.

Joined: Thu Jan 15, 2009 03:53
Posts: 8
Location: Texas

Thanks for the reply !.. to be honest when I unpacked the drive I plugged it to my Vista laptop, it ran the utility that comes in the drive and prepared it NTFS simple as that, no other files except for the ones installed by the manufacturer. I played with it for a while, noticed that on my MAC the drive wouldn't mount not even with the native NTFS support 10.4 supposedly has that's when I googled and came across you guys with MacFUSE and NTFS-3g. Before I even started my copy process, I screwed up the drive couple of times, meaning I forced a format on Mac OS X, took one hell of a time, then when it mounted it almost took 16GB out of my drive, then I said no wayyy!..took it back to my laptop and reformatted however I could, finally got back control of the drive and with Windows console applet used the disk management utility and reformatted, so at the end I put it back as original with 465GB capacity, filesystem was NTFS..
I'l check back with you tomorrow on this.thanks

Joined: Sat Oct 06, 2007 09:24
Posts: 530

You say that you forced a format on Mac OS X at some point, so did you choose NTFS-3G as the on disk file system? (I don't think you can do that in Disk Utility in 10.4, so I suspect that you chose some other file system, such as Mac OS Extended)
This just might be a really weird problem, involving dual file system structures.. meaning that even though formatted as NTFS, old HFS+ structures are still there and recognized by Mac OS X.
What kind of partition system do you have on the drive? MBR/GPT/none?

Joined: Thu Jan 15, 2009 03:53
Posts: 8
Location: Texas

Sorry for misleading you on that one, I meant that before actually finding these apps (MacFUSE and NTFS-3g) I had played with the drive on both environments, thus rendering unusable the drive, nevertheless recovered it and reformatted to full NTFS again as like in the very beginning. THen I stumbled across these apps and followed to the letter how it is done.
Strange thing is , and reason of my post is that supposedly we can plug/unplug from either environment right ? I mean the drive will or should always be NTFS in my case, well..to my surprise something changed, and I didn't tweak any settings whatsoever, bottom line is that my once NTFS formatted drive now says it's a Mac OS X Journaled drive and obviously I can't see it on Windows Vista. I would start all over again , just that I have to reverse my 120GB copy

Joined: Thu Jan 15, 2009 03:53
Posts: 8
Location: Texas

Unsound here's the info you asked me for yesterday.
Name : FreeAgent
Type : Volume
Disk Identifier : disk2s3
Mount Point : /Volumes/FreeAgent
File System : Mac OS Extended (Journaled)
Connection Bus : USB
Partition Type : Apple_HFS
Writable : Yes
Universal Unique Identifier : B4FCE920-C7C7-32AF-B6C8-229287445B6E
Capacity : 465.6 GB (499,973,603,328 Bytes)
Free Space : 345.4 GB (370,845,032,448 Bytes)
Used : 120.3 GB (129,128,570,880 Bytes)
Number of Files : 23,412
Number of Folders : 2,761
Owners Enabled : No
Can Turn Owners Off : Yes
Can Be Formatted : Yes
Bootable : Yes
Supports Journaling : Yes
Journaled : Yes
S.M.A.R.T. Status : Not Supported
Disk Number : 2
Partition Number : 3
I notice it say Apple_HFS, but I didn't prepare this drive on my Mac, I am positively , 100% sure, I prepared this drive in Vista as an NTFS system..what I'm gonna do is move my files back and start from scratch, I'll try keep documented all steps.

Joined: Sat Oct 06, 2007 09:24
Posts: 530

Well, it certainly is HFS+ formatted now. :) I'm not sure how you got there, but that's the current situation. You could try to load your drive with HFSExplorer (http://hem.bredband.net/catacombae) in Windows to verify again that it is HFS+.
The disk's identifier is disk2s3 .. this implies that you also have disk2s2 and disk2s1.. what are those? You can type 'diskutil list /dev/disk2' in the Terminal to get a full listing of your partitions.

Joined: Thu Jan 15, 2009 03:53
Posts: 8
Location: Texas

I already did try with HFS Explorer , but all I can do is extract.. I need to write to my new drive rather than pull out of it. Reason I'm being picky is because I have an old G4, these are USB drives so you can imagine how slow it is transfering files from one to the other, instead on my Dell XPS it takes a couple of hours but not 45hrs as how it shows now when I started the copy again.. I hava antother external drive a WD 160GB..but the big type, bulky..it's the one with the media center on it.
Q: Does NTFS-3g rely on MacFUSE? I think I read it did, but wanted to confirm
G. :lol:

Joined: Sat Oct 06, 2007 09:24
Posts: 530

Well, either way you don't seem to have any choice right now but to move everything off your drive, reformat it in Windows, and when you attach your newly formatted drive to the Mac, make sure that it displays as an NTFS-3G drive in Disk Utility before you transfer any of your files to it.
Yes. (When it's running in Mac OS X at least.. in Linux, BSD, Solaris, it's just called FUSE)

Joined: Thu Jan 15, 2009 03:53
Posts: 8
Location: Texas

Unsound:
This is really weird..after moving back all my files, I deleted the partition and reformatted my external drive in Windows Vista this puts me back on an NTFS partition of 465GB.. I checked that MacFuse was installed , re-installed the beta version I had v2.0.2 and now it says v2.1.4 , also re-installed NTFS-3g and ran the enable scripts which are provided on the TOOLS folder.
Guess what?.. my drive came back with all the files I had copied onto it, weird huh?.. it had same folders and the same amount of gigs being ocupied.. now how can that be? I also ran Disk Utility and it showed me my drive , again as a OS X Journaled drive, Apple HFS format.. this I don't get, confused, totally..
What I will try now is the reverse. I will try to format on my Mac this drive using MS-DOS filesystem, this would probably create it as FAT32, once it's done I'll check on my laptop and see how Windows is seeing this drive, should be FAT32.. lastly, I'll try a low level format to make sure I've blown away any potential partitions therein.
I'll check back with you later if you have any other thoughts.
BTW, my iMac is:
G4 , 800Mhz, 60GB internal HDD, 1GB RAM , 15' Screen
Running Mac OS X 10.4.11 up to date.

Joined: Tue Sep 04, 2007 17:22
Posts: 1286

Hi
You should check your partition id. For NTFS it is 07, for HFS it should be AF.
Regards
Jean-Pierre

Joined: Sat Oct 06, 2007 09:24
Posts: 530

Have you considered the possibility that your hard drive may be haunted by ghosts? :)

You should try to zero every sector of the drive, which will take a lot of time, and then create a NTFS file system in Windows, and then see what your Mac has to say about it. If it still claims that there is an HFS+ partition on the drive we should consider that Disk Utility might be providing false information on the mounted file system.
Maybe zeroing the drive is what you mean by doing a 'low level format' (as far as I know, modern hard drives can't do what is traditionally called a 'low level format'..).

Just so you know, I haven't been able do to any testing whatsoever of NTFS-3G on PowerPC macs, since I don't have access to one.
That said, I haven't yet got any PowerPC specific bug reports yet.
BTW, I agree with Jean-Pierre.. the MBR partition signature might have been falsely set to an incorrect partition type at some point, but that still doesn't explain the strange fact that OS X is able to mount the drive as HFS+ successfully when there is an NTFS file system on the drive.
Good luck.
- Erik

Joined: Thu Jan 15, 2009 03:53
Posts: 8
Location: Texas

Ok..I'm gonna try this now..
1) In Windows , I'll use the Computer Management app, and run Disk Management
2) Delete partition
3) Create Partition NTFS , default block size
4) Format and put as ACTIVE Healthy partition
Let's see now what OS X has to say about this!..
BTW: I did the previous on my Mac using Disk Utility and managed to create a FAT32, both operating system seem to understand the partition created in that format , however beats the purpose of this investigation.. I'll report later how it goes with the mentioned above.
Thanks guys

Joined: Thu Jan 15, 2009 03:53
Posts: 8
Location: Texas

Erik,
FINALLY! Per my last comment, seems like it is now working as it should..had to perform a low level format on the drive , took a while because didn't choose the quick format, but was worth the wait..i'm copying my files again from my Mac to the external.. I wanted to share a screenshot but couldn't post it.. dunno gotta check my profile maybe..
Cheers
George :D

Joined: Sat Oct 06, 2007 09:24
Posts: 530

That's great to hear. The weird things that happened are still a mystery though.
I can only guess that you somehow managed to keep the HFS+ structures intact even though the drive was formatted to NTFS, and that you didn't use any partition system at all, or had the wrong partition type set for the NTFS partition. Thus the Mac had to probe for all kinds of partition systems, and HFS+ always comes before NTFS in the probe order.
Formatting the entire drive, using the slow method which zeroes every sector of the drive must have finally erased all traces of the HFS+ structures.
It's the only theory that I can come up with.
Anyway, the important thing is that it works now. :)
Cheers,
- Erik