Error 1309
 

Hi,

I'm trying to copy a 9.3 gig file to a maxtor 300 gigb external drive, i've partitioned it 50/50 ntfs/mac, and i'm trying to put hte file on teh mac part of the partition and it get to aroudn 4. gig then comes up with the error code 1309, I've done a search in teh support area, and nothing.

Any Ideas?

Is this drive attached to your Mac (via firewire?) or mounted over a network (what protocol?).

What version of OS X are you running?
What program are you using to copy the file - Finder ?

It sounds like you might be hitting a max file size issue.

It's attached via USB2, I'm using OSX Tiger and i'm using finder.. well drag and dropping the file into the icon for the external drive in finder.

I do have fire wire cable which I could try.

Firewire is reported to be much more reliable than USB for large transfers.

I'll give it a try

Nope, it happens again over firewire.

Okay, I've just looked at hte paritition info in Disk utilities, and seen that it's set as a fat32 parition, and if i remember rightly fat33 has a 4 gig file limitation?

Sounds like i have it set wrong. I need to have the external drive as a window/mac paritaiton, because I still do some of Video caputre on the PC, and i also need to be able to move the dv files created on the mac to the PC for compression.

Any suggestion on how to sort this out?

Error 1309 is a file bounds error.

In other words there is some discrepancy with the file's size or end-of-file marker, or some variation on this I haven't thought of :) My point is this sounds like a read error not a write one i.e the problem lies with the original file.

Can you copy the file to another location without diffculty?

Well, i'm trying transfering it over the network. figured out how to do that... and that should take a few 3 hours.. hence wanting th external drive.

I'll post an update when it's done

More than 4 GBs is a problem for XP - but it should not be a problem for the Mac.

I would add to my previous comment that you should check for file system errors on the FAT32. I could be wrong about the file. I know next to nothing about FAT32 - but I think you're best inspecting the partition from the PC.

I'm going through this same problem with transfering an 18 GB file onto a FAT32 drive from a MAC. Seems like it's at about 4GB that I get the error message. What were the programmers thinking when they created this inferrior file format FAT32? Is NTFS any better? Is there a file size limitation with NTFS?

FAT32 does indeed impose a 4 GB file limit. If you need to copy files bigger than 4 GB, then you need to reformat with NTFS. It will handle terabytes.

But, you won't be able to write to the NTFS partition from the Mac. It will be read-only.

workaround with split & cat
 

You could try using "split" to copy the file a chunk at at time to that FAT32 volume, and later rejoin it with "cat". For example:

(the trailing dot is intentional, but cosmetic. With it, the chunks will get names like mybigfile.foo.aa, mybigfile.foo.ab, etc.)

To restore to your desktop:
See the man pages of split and cat for more info. If the command line turns you off, look around at sites like versiontracker.com for splitter/joiner apps (which basically do the above).

This won't help you actually use your ginormous file on a FAT32 volume, but it's suitable for storage.

The developers of FAT32 were probably about the same place that DOS developers were when they thought that 1 MB of RAM would be all that any PC was going to need and imposed a 640 KB limit on DOS. When FAT32 was written, there WEREN'T any hard drives anywhere close to 1 GB, much less 4 GB files! Were they short sighted? Yeah, maybe. But computer costs were a LOT higher then; 2 GB of RAM and 250 GB of storage were server-level requirements, and server systems could handle that, but not desktops. Video-editing was a specialized need that not everyone with a camcorder could dream of doing. They may have misunderstood how long that standard would be around, or how quickly our needs would change, or both. But by computer standards, it is a relatively old file system which even when it was introduced was inferior to HPFS (which turned into NTFS when IBM and Microsoft broke up their partnership), but was entirely adequate to the needs of the day. I don't think it is really fair to ask what the developers of the standards were doing when they didn't design FAT32 to handle files that wouldn't be common for another decade. You might well ask at the same time why Apple didn't put controllers in ALL of their computers that handled drives larger than 128GB. When those machines were designed, the need for it was certainly not clear. Soon, no doubt, drive manufacturers will produce multi-terrabyte drives and we'll have to re-design the file systems for all of our OSes, I expect.

Joe VanZandt

Some details
 

Thank you stevebr for this nice tool. It works fine, it lasts around 5 minutes to split and 8 minutes to rebuild one single file of 4 Gb.

However you misspell the split command (no dash before 2000m) :

I just came across this thread as I searched the web in vein for this error message which I've unfortunately gotten on my machine (for some reason -1309 isn't listed in the usual MacOS X error message lists).

The circumstances are a bit different from the original poster's situation.

I've connected to a server using AFP (by going to the "Go"-"Connect to server" menu in the Finder and entering afp://address.address.address).
I also need to use VPN to get access to this server, which I have the Cisco VPN client for.

The file is a large (2.9GB) file which starts to download fine. Even with my broadband connection it's estimated to take 2 or 3 hours to complete.
So I wait, and after a while I get that error message which I have a screenshot of here:
http://img232.imageshack.us/img232/5...1309hb9.th.png


I've downloaded other files from the same site (though not as big) and had no problems. I'm running MacOS 10.4.9 on a 1.67GHz Powerbook G4 with an 80GB internal drive. Currently I have around 30 GB of free space left.

As I have an external 400 GB Firewire drive I could try downloading to that drive instead if it should make any difference, but from what I've read here it sounds like the problem lies with the server at the other end and not my setup. That probably means I can't do anything about it.

What's almost as frustrating as getting an error message in the midst of my download (with my last attempt 2GB had been downloaded so far, so it wasn't far from being done), and when I press the "OK" button in the error dialog the partially downloaded file disappears so I have to start all over again.
In case the problem is caused by temporary network glitches, is there a way I can just resume the download? I assume the partially downloaded file will still be located somewhere on my hard drive (as a temporary file perhaps) even though it disappears from its download location (which is the desktop in this case)

For now I haven't pressed "OK" in the error dialog, so the partially downloaded file is still on my desktop.

Trying This Alternative
 

:) Hello everyone!

As I was trying to transfer videos with more than 4 gigs to an external hard drive (160 gigs), I got a 1309 error. I thought it was a simple glitch in my Mac computer since my external hard drive still has tons of space. I tried transferring the files again, but to no avail. So, I went on the internet to conduct some research. I found this site that contained conversations with good information, but I guess there is no solution yet to this problem

I will try to import my videos in iMovie and see if this will help compress the video size to something more manageable without over maximizing the limited space I have left in my hard drive.

Should you know solutions to this kind of error, kindly post in the "Comment" section of my work blog which will benefit other readers. I would surely appreciate all the help! Thanks!

error 1309 solution
 

I have struggled with this problem and have finally found the best solution.

The short answer is to push the files through your home network from the storage location to an NTFS formatted drive (eg Maxtor that has been appropriately reformatted). When you push the files through the network, the OS from either your pc or your mac will handle the files, and the 4 GB limit doesn't apply. You will have to make sure that the maxtor drive is shared on the network so that the mac can see the drive.

The key is that your external drive needs to be NTFS formatted.

One of the hangups is that the mac OS X does not seem to allow recognition and wright access to NTFS formatted drives, so you can't just format the drive and plug it into the mac. Therefore, it has to be pushed over your home network, to a PC that can write to the NTFS formatted drive.

The NAT32 format just simply will not work due to the 4 GB restriction. The Mac OS X extended format will handle files larger than 4 GB, but will not work on a PC.

To format the external hard drive to NTFS on a PC, attach the drive to the PC and right clicking the drive and selecting format and make sure to choose NTFS. This will erase the drive, so beware.

good luck.

error 1309
 

I've read this thread and I'm a bit confused. I'm using iMovie to back up my miniDV camcorder tapes and each tape will be about 18GB when imported with iMovie. I've backed up 4 tapes during the last days. I usually back them up on the computer's hard drive and after working on them a bit, pass them on to an external USB hard drive with 120GB. I still have around 60GB free and the 4 tapes gave me no problem when passing them to the external drive. But now, from out of nowhere, the 5th tape is giving me the error 1309. It is a 18.88 GB file, same as other's average, but when it is around 5 GB copied to the drive I get error code 1309 so I realy don't know what to do. The drive is in FAT32 but remember that even this morning I copied a 18GB file to it... so it seems I cannot find the FAT32 4GB limit that you talk about in this thread, or at least I couldn't...

Regarding my last post, I now understand the problem. It is not the entire size of the .iMovieProject that matters but the size of individual .dv files within it. I noticed I had a 4.6GB .dv file on this last project that was giving me trouble. On the other projects I only had .dv files up to 2GB and as soon as I erased this 4.6GB file and re-imported this footage spliting it into 2 clips (I used the "Limit Clip Size" on iMovie preferences) I was able to send it over to the external drive.

I also had this problems trying to use my iPod 60gb to transfer files of 4gb or more. My iPod is in FAT32 format so that explains the error. In order to fix the issue I have used a File Splitting system (I'm not very good at terminal so I'll let an application do it for me). The following is the application I used to split: http://www.xs4all.nl/~loekjehe/Split&Concat/index.htm

After splitting the file i was able to put the file on my iPod no problem. After putting it on my iPod I transfered it to my Media Center PC and joined the files using the file joiner: http://www.freebyte.com/hjsplit/#win32

I hope this helps some people. I know it surely has helped me.

Btw,

You can easily set up Mac OS X to have reliable write-access to an NTFS-volume (details can be found here http://www.daniel-johnson.org/ )

Download and install MacFuse from http://macfuse.googlecode.com/files/...Core-0.4.0.dmg

Download and install ntfs-3g from
http://homepage.mac.com/danielj7/NTFS-3G.pkg.tar.bz2

To enable automatic remounting of the ntfs-volume to allow write-access, download iMountit from http://www.auf-ex.de/iMountIt.dmg . You can then easily use Automator (an OS X Tiger app) to create a workflow application to open the selected ntfs-partition with iMountit, then set your created Automator app as a login item (drag to the dock, right-click "Open at login" ) to have your ntfs-volume automatically mount as read-write everytime you log in.

Okay I have a Macbook Pro 2.2 GHz Intel Core 2 Duo - 2 GB 667 MHz DDR2 SDRAM and a 200 GB HITACHI external USB2 hard drive.

I would like to say that I had this problem with a 6 gig file - a dmg file that i made as a backup for my leopard because I have just installed it.

I partitioned my external hard drive with 2 parts - one part was 10 gig and the other was the rest of it. (i can now boot the leopard installer off of my external hard drive to install on my other 2 mac's - (family pack)

I had to format it so that I could do that - the 10 gig partition is GUID partition the rest in the other partition is FAT32.

I had no problem puting all my backup files back onto the seconed partition (over 80 gig of files all at once)

THEN I tried to copy the dmg file for leopard to it. BAM I was stuck with the Error -1309.

I was like, well fine!! I'll just put you on a flash drive! And I got the same error.

So it was not my external hard drive format or anything it was the file itself.

I decided to mount the dmg file to my desktop and let it "VERIFY"< ---- LET IT VERIFY!!! (that is if it's a dmg file you are trying to transfer!)

After it verified, I ejected the mounted image and then dragged it over to my external hard drive... IT WORKED!

So if it is a dmg file that you have NEVER verified (alot of people just hit cancel) - verify it by mounting it (window pops up saying verifying ****.dmg or whatever)

Then you should be all set!

Also make sure you have read/write permissions by going to APPLICATIONS/UTILITIES/DISK UTILITY and clicking the First aid on "REPAIR DISK PERMISSIONS for your internal mac hard drive.

For your external hard drive click on Verify Disk and then Repair Disk.

You should be all set to go. This all sounds like alot to do but it's really not. I wish apple would spend the time to not have error codes but the ACTUAL Discription.

The Error Code 1309 isn't even on their error code page - would someone be kind enough to share where they got the information for that code? I just figured it was a read/write error or file error/permissions error.

Anyways what I did worked for me, I hope this helps someone!

FAT32 has a very specific size limit to files. A file saved on a FAT32 drive or partition can be a maximum size of 4 GB minus 1 byte.

There's no way no how no chance that any 6 GB file will ever be saved to a FAT32 partition, no matter what. End of story.

Perhaps you saved it to the other partition which was HFS+ when you got it to save? Or perhaps the file was not really 6 GB. Because verifying the file didn't make any difference.

Further reading: Microsoft: Limitations of the FAT32 File System in Windows XP
(In case you didn't know, FAT32 and other FAT filesystems were developed by Microsoft.)

Trevor

You could always format your FAT32s as NTFS (Back-up First!!!). You might need a linux boot cd or a partition program to partition it. Since Mac OSX does not have native read/write on NTFS, only read, you have to download NTFS 3G. The new version doesn't require MacFUSE, is free, and integrates into finder. NTFS solves most limitations of FAT32, and once you got NTFS 3G, the only excuse for not using it is not having a HD to back-up your FAT32 drive.

Another program that worked well for me was:

http://tc.versiontracker.com/product...litter.zipPif- Splitter

What is especially useful is that it is writing the files directly to the ext. HD I originally wanted to transfer my file to.

Error 1309 solved (partially I think)
 

I just had this error message over and over again, trying to transfer a 7.9 gigs file to a external hard drive, and I only split the file in two and that was it, no more transfer problems. After all, in some cases it may be a file size related problem. Hope this helps.