Hi, I need some help clarifying some qs. I purchased an xbox console with 1tb hdd installed from a seller recently but have issues with file transfers from computer to xbox (I could ftp and transfer files but up to a certain point, the xbox would not accept any newer files and starts corrupting my other folder directories). I read some other forums stating issues on file cluster size which should either use 32kb/64kb cluster size. So what I did was I used the xbpartitioner to split the drive to have 460gb each on f and g drive with 32kb cluster. Before I start retransfering my whole data again, I want to confirm if this will definitely work as from my research, I heard that xbox's with duox3 modchip have issues with xbpartitioner and may not actually do the clustering properly eventhough it is sucessful.
Could anyone confirm that duo x3 modchips have issues with xbpartitioner or not?
Also, as I noticed that there is no bios information available or can be checked out under the menu of xbmc or unleashx, I discussed with the seller of the xbox as he mention he did not flash any bios on the duox3 modchip and just left it as it is as there is a stock bios already. Could someone explain on this if this is correct for all duox3 modchips to not have any bios information available or should the xbox rev 1.6 needs to have a bios to flashed on the duo x3 modchip instead of using the factory stock bios. The reason for asking this is because I can't determine which bios revision is installed and I would like to determine what kind of file system support is available (e.g. LBA48 6 or LBA48 67 support is available or not).
Lastly,is there a way to check if the xbox drive is now properly set to use the correct cluster size because when I did the partitioning using xbpartitioner, it does the partitioning,etc but did not show the new info on the new cluster size and I would like a confirmation that this is done correctly by either viewing the cluster size properties somewhere in xbmc,etc or some other way that you can advice checking this out.
Well for starters, I never heard of someone putting a 1tb HD into an Xbox. I have a 500gb, and I thought that was alot...twice as much memory is godlike to me haha.
If I read correctly, you have a 460gb partition! That must be what the problem is. You cannot have more then 137GB partitions for E or F on your Xbox if I remember correctly. My C drive is the default partition size, E is 137GB, F is 137GB, G is remaining 226GB.
I will have to check again, I had a friend install my HD to be honest. I know for a fact though there is a 137gb size limit on certain drives, I or someone else will get back to you asap.
Ya that was wrong. F drive max size is 137GB, dump rest on G drive. My C and E drive combined is less then 10GB. So don't touch your C or E drives, have your F drive with 137GB, then G drive with 863GB.
Thanks for your advice. I managed to get it fixed using xbpartitioner splitting the drive volume to 450gb each for f and g drive using 32kb clusters. After using this, no corruption seems to happen. I found my answers searching some other forums as well. Apparently, anything for drive volumes above 137gb on F, will need to use either 32kb or 64kb clusters to avoid corruption of data.
Glad you figured it out by yourself. As Demonix90 told you corruption begins with any partion over 137gb. Usually it happens when one of the other partitions is completely full. And it looks like you solved the problem the way i always recommend so that's perfect.
