ieblj01 Posted May 7, 2021 Report Share Posted May 7, 2021 (edited) I seem to have a lot of issues with my data files on my G partition. Any emulators, games, media, etc., on the F partition work flawlessly. I can copy the same files over to my G partition and it is very hit and miss on whether things will function properly. There are also times when I can have everything working on G, then copy over some files (FTP or FATxplorer) and suddenly, things go wonky even with files that I never touched. My HDD is a Samsung SSD 860 EVO 1TB. So my G partition is quite large (803GB). My F partition is only 120GB. I used AID to prepare/format the drive. My BIOS is the EVOX m8+ CEE FG w/no DVD off the OGXBOX installer 1.5.3 disc. Is it possible that I am using a BIOS that doesn't handle that large G partition very well? Should I be using a different BIOS perhaps? It is very frustrating to work on making a HDD and getting the xbox all set up and then suddenly my files are corrupt for no apparently reason when they work just fine on F. Any insight here is greatly appreciated. Edited May 7, 2021 by ieblj01 Quote Link to comment Share on other sites More sharing options...
KaosEngineer Posted May 7, 2021 Report Share Posted May 7, 2021 Same problem that @Doom87posted about. I believe the larger than 512 GB partition was formatted using 32KB clusters instead of 64KB clusters. Once you write more than 512 GB's of data to partition 7/G drive data corruption occurs. The 32 bit counter used to access the data has overflowed wrapping back to 0 (e.g., FFFFFFFF + 1 = 0) - overwriting data to the start of the partition. Corrupting data previously stored there. Quote Link to comment Share on other sites More sharing options...
ieblj01 Posted May 7, 2021 Author Report Share Posted May 7, 2021 (edited) Thanks Kaos, I believe you may be on to something. I have a 500GB SSD EVO drive that prepared the same way as my 1TB drive that use for testing files before I put them over on the main unit with the 1TB drive. If memory serves, I don't have these issues on the G partition with the smaller HDD. I have another 1TB EVO SSD for another unit, so I am going to check (added photo...you are the man Kaos) the partition as you suggested and redo it with 64KB clusters and see if the problem remains. Thanks for the insight! Edited May 7, 2021 by ieblj01 added photo Quote Link to comment Share on other sites More sharing options...
HDShadow Posted May 7, 2021 Report Share Posted May 7, 2021 (edited) Using AID for the extended partitioning was likely the culprit. I'm pretty sure that even the last official version of that v4.53 used XBPartitioner v1.1 or similar age tool for the formatting. Fine for C, E, X, Y, Z and F if its under 137GiB but anything bigger and it will not use the correct cluster size just as KaosEngineer suggested. After the initial formatting and dash install using AID before doing anything else install and use XBPartitioner v1.3 in Apps to check and format the extended partitions, F and G (6 and 7 as shown by XBPartitioner v1.3). Edited May 7, 2021 by HDShadow Quote Link to comment Share on other sites More sharing options...
ieblj01 Posted May 7, 2021 Author Report Share Posted May 7, 2021 You are 100% correct HDShadow. I checked AID XBPartitioner and it is using 1.1 (and I was using v4.53 as well). I have reformatted G using v1.3 and moving over a ton of files now to verify. Quote Link to comment Share on other sites More sharing options...
ieblj01 Posted May 7, 2021 Author Report Share Posted May 7, 2021 (edited) Son of a #$!@&...that was it! I copied over 100s and 100s of gigs of files over using FATxploer and absolutely everthing is working. That has never happened before. Man, I wish I had brought this up sooner. I wasted weeks of time and effort trying to figure out why my files were corrupted. I am just glad it is resolved! You guys rock Edited May 7, 2021 by ieblj01 Quote Link to comment Share on other sites More sharing options...
Doom87 Posted June 7, 2021 Report Share Posted June 7, 2021 I've got the same problem, damn... Quote Link to comment Share on other sites More sharing options...
MrMajst3r Posted June 8, 2021 Report Share Posted June 8, 2021 There is a bug in XBpartitioner which cause wrong cluster size sometimes. Need to be careful and check cluster size after formatting. I advise formatting with Chimp261812 or XblastOS. These formats extended partitions without issues. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.