Print

[xboxjason]

Hey guys. I'm having a very dumb problem occuring with my Xbox. I have a 500GB Seagate drive in it, and I run Xcecuter 4981 and iND-Bios 5003 bioses.

I have all my extra space going to my F partition, no G being used. Well I have approx 198GB free left in my F partition. But I've now have run into a problem. Randomly I cannot put a file/folder into a folder Ex:

/F/GAMES/New Xbox Game/  

If I were to put a file or a folder into that new "xbox game folder", it doesn't copy. Whether I FTP, or DVD2Xbox a game. So it doesn't matter what game I try to copy to my xbox now, or what the name of the game is, but as soon as it trys to go an extra folder deep, it doesn't copy. Like I said this is quite the retarded problem. Anyone know what's up with this? Thanks
~Jason

[Cappi]

If a drive is bigger than 256gigs it will corrupt all data after 256gigs. Reformat your F drive with xbpartitioner and it will format with 32k clusters making data corruption happen after 512gigs.

[Maverick0984]

QUOTE(Cappi @ Jun 18 2006, 05:33 PM)

If a drive is bigger than 256gigs it will corrupt all data after 256gigs. Reformat your F drive with xbpartitioner and it will format with 32k clusters making data corruption happen after 512gigs.

i agree, you need to do exactly what he said.  i had a 400gb last xmas that ran into this problem.

[xboxjason]

QUOTE(Cappi @ Jun 18 2006, 11:33 PM)

If a drive is bigger than 256gigs it will corrupt all data after 256gigs. Reformat your F drive with xbpartitioner and it will format with 32k clusters making data corruption happen after 512gigs.

First of all, thank you so much for your help. I REALLY wish I had known this before, because I just finished copying most of my games to my HD and all of my mp3/videos to the drive.  (IMG:style_emoticons/default/mad.gif) This really sucks that I have to do that again, but oh well at least this problem is solved. I partitioned this drive originally with that "Xbox Hard drive maker" the linux distro one. So I'll grab xbpartitioner and fix this problem. Again, thanks so much for your help guys! (IMG:style_emoticons/default/pop.gif)
~Jason

[dre74]

This must be the problem I am having. I have an xbox with a x3 modchip and I am changing a 250gb hd with a 320 hd, I setup the new hd with x3 configlive. I transferred everything using flashfxp (all night) xbox to xbox on my local network. I could see everything was transfered but shorty after all my apps and emulators disappear, I tried reloading them but they failed, reformatted and repeated process(all night long again) and the same damn problem. So I guess I will try your suggestion. I was ready to send the new hd flying across the room. Thanks

[xboxjason]

Maybe this should be stickied or something, because I've been on the scene for a while and never knew about this either. =b

~Jason

[dre74]

QUOTE(xboxjason @ Jun 20 2006, 12:30 AM)

Maybe this should be stickied or something, because I've been on the scene for a while and never knew about this either. =b

~Jason

Yea this is about the 8th hdd I have set up but never one larger then 250gb, I guess I learned something new today.

[Cappi]

QUOTE(xboxjason @ Jun 19 2006, 04:30 PM)

Maybe this should be stickied or something, because I've been on the scene for a while and never knew about this either. =b

~Jason

I dont know why nobody ever sees these kinds of threads. I post about this problem about 2-3 time per week. But people still keep asking why they have data corruption.

[lenballs]

You also need to use an EvoX M8+ or M8_16+ bios, as Xecuter2 4981 is not compatible with xbpartitioner.

And the limit for corruption when you format F: with 32k clusters is 2Tb or 2000Gb, not 512Gb like Cappi said.

This corruption problem on drives bigger than 256Gb is old news, search and theres heaps of threads about it when nightshade wrote xbpartitioner a couple of years ago.

[xboxjason]

QUOTE(lenballs @ Jun 20 2006, 08:56 PM)

You also need to use an EvoX M8+ or M8_16+ bios, as Xecuter2 4981 is not compatible with xbpartitioner.

And the limit for corruption when you format F: with 32k clusters is 2Tb or 2000Gb, not 512Gb like Cappi said.

This corruption problem on drives bigger than 256Gb is old news, search and theres heaps of threads about it when nightshade wrote xbpartitioner a couple of years ago.

Wait... I used Xbpartioner and I was running X2-4981. Using XBpartitioner, I set all extra space to drive F drive, and it did format my F, and while formating it said something about 32K cluster being set. So now I'm confused... Did it work or no? I remember Xbpartitoner saying something about not being compatible if I wanted to make custom partitions...  O_o I don't think that includes setting all extra space to F.

~Jason

[Cappi]

QUOTE(lenballs @ Jun 20 2006, 12:56 PM)

You also need to use an EvoX M8+ or M8_16+ bios, as Xecuter2 4981 is not compatible with xbpartitioner.

And the limit for corruption when you format F: with 32k clusters is 2Tb or 2000Gb, not 512Gb like Cappi said.

This corruption problem on drives bigger than 256Gb is old news, search and theres heaps of threads about it when nightshade wrote xbpartitioner a couple of years ago.

Do not listen to him, he has absolutely no idea what he is talking about. 2TB is the max size of hard drive you can put into an xbox, but since they dont make any that big it isnt a problem.

[xboxjason]

Kk. well I do know that I used XBpartitioner while running an X2-4981 bios, and Xbpartitioner did format my F partition using 32k clusters. So it worked. Thanks a lot Cappi!  (IMG:style_emoticons/default/pop.gif)
~Jason

[dre74]

Would seting hard drive so that f get 137gb and g gets everything else  solve this problem as well? I am using the latest x3 bios.

[xboxgamer733]

Yes, as long as any partition doesn't go over 256 GB in size, you won't encounter future data corruption.

[dre74]

Thanks xboxgamer.