So I have recently fitted a 2TB sata hdd to my original xbox all tho I'm not 100% certain the hdd partitioned in 64k clusters like it's supposed to be or not so I took some pictures to post up here in hopes that someone can tell me rather it did or did not go as planned. XBpartionter F:\ and G:\ split 50/50 but there is an ER for some reason The 1k file to transfer to test proper clusters Partition sizes before test file transfer Partition sizes after the transfer (both reduce to 949,815.89) The guide I was following for my results is here: https://www.xbmc4xbox.org.uk/forum/viewtopic.php?t=649 The only part I did not follow was using both xbpartitioner 1.0 and 1.1 because 1.3 reportingly solved the bugs in the previous versions. Also I used the hexen 2017 disc for the setup of the new hdd, Information such as the change log and things like that for this version of hexen can be located here: http://www.theisozone.com/forum/viewtopic.php?f=31&t=66976 My two major concerns with the way things ended up is the 2 ER which I assume means error signs in xbpartitioner and the fact that the math for checking the cluster size does not seem to be adding up as the guide says it should because the 1KB file should use up 64KB of hdd space if I'm not mistaken. So if anyone can tell me if things are right here or not I would greatly appreciate it, and if I did something wrong that you can see please correct me. I really don't want to get over the data limit and have things start corrupting or overwriting on me.
Use Chimp 261812 and format your extra partitions. ( does the proper cluster size and stuff ) That will format them properly. Load XBP after and the er should be gone.
Hmm see I thought chimp was just for softmod hdd clones......this is exactly why I made this thread because so much of the information out there is out dated and it's a long process to sort threw everything to get to current t information that is still valid to even accomplish what your after for 1 task. When I first started this process the xbox would detect the blank hdd but would not let me assign a G drive unil I told xbpartitioner that it was there made the partition then started the new hdd process over again evolutionx then detected and gave me the G drive option after making the partition.
An interesting thought here....if I'm not mistaken the E:\ drive is the one that stores what? Music and game saves?? By default it's made to be 4,878.97 MB (roughly translates into about 5GB) would it hurt anything to increase that size so I can have more space for game saves? I know I can only have if I recall correct 249 items inside each folder (in this case the TDATA and UDATA) but I suppose all of this depends on the average size of a retail game save as well
Which I kind of do.....just gotta quix it over lol......I'm now having some sort of issue with the controllers somehow.....I made a thread about that as well.....need to get it sorted out so I can proceed working on my projects
I generally run XBP1.3 twice to verify that the format of the extended partitions is using the correct cluster size. If not, ER, is visible write and format the partitions again. Reboot the Xbox and run XBP1.3 again. Most times, the second execution of the XBP's write & format process shows that the correct cluster size is in use. To tell if the 1KB file uses 1 cluster (e.g., 64KB, 32KB) when written to the drive, check its directory entry. The size shown for test.txt should be 1 cluster. A cluster is the minimum space allocated on the HDD for a file and depends upon the cluster size used for that partition. A file will occupy an entire cluster when its size is less than 1 cluster. Files are broken down into cluster sized chunks and stored to the HDD. If the file is not exactly divisible by the cluster size, there will be one final cluster allocated for the portion left up to ((cluster size) - 1) bytes in length.
This. I've also found that sometimes G: wouldn't even be available until I ran XBP1.3 a second time. There shouldn't be any need to run Chimp (perhaps there is a benefit, but when I did this upgrade, I had not used Chimp nor had I any issues for years). No need to increase E: size. Just checking: did you upgrade to an ATA133 cable? I believe 24 inch ATA133 cables are still available (without this, you may run into speed issues and crashes; the difference is very noticeable). Also, be aware that the Xecuter3 BIOS does not play well with 2TB hard drives (X2 5035 and IND BIOS 5003/5004 are fine in my experience) - if using X3, do not change the "Use saved partition table" option in X3 config live, or else the system will not boot and you'll have to unplug the HDD to be able to access X3 config live and change the option again. Furthermore, after the system was powered off and unplugged for a while, I remember needing to power on the system the video cable disconnected to give the HDD time to spin up, or else it would timeout and give an error (I believe 7). Also, if you need a custom jewel, let me know I hope this helps!
Ya the ata cable is upgraded and I ran chimp to eliminate the err it for some reason takes care of it I think I'm running the last X2 bios on this x2.3 + B chip. Now a custom jewel does in fact interest me I was unaware they were still around anymore lol. On a side note and probably something I should open another thread for I seem to be having difficulties installing an X3 I have just received......my guess it I need to go over the solder joints again with the soldering iron as it worked fine before I removed the motherboard for further alterations to the machine.......I'm getting inconsistent boot ups and having to twist the chip or reposition it a little to eliminate the problem
Definitely reflow the solder joints. There were countless reported symptoms just like yours (though mostly when used with the solderless adapter) when the X3 was released in 2004.
Dont know if I should hijack this thread, but I've just put a 1.5TB disk into a XBOX v1.6 with an X3 chip. Formatting went fine in XBP 1.3 (64bit clusters are fine) but as soon as I reboot, I can see in the X3 bios that E: is 127GB and G is something like 1.2GB. This obviously is not correct and I suspect it is because of the X3 BIOS overwriting the values read from disk or something. If I go into the filemanager in the X3 bios, its also wrong. XBP 1.3 still shows it correct, as is any other 3rd party file manager, but if I try to copy files, it goes all haywire. I have another Xbox with a DuoX2 chip it in that I'm going to try with as well, but I wanted to verify with you guys that the X3 does not like large disks as its too smart for its own good. Thanks!
Is there not a setting in the x3 config menu to enable the partition table? ( I know some of the advanced chips with custom menus has this option )
From X3 BIOS menu select: Disk Tools -> New Hard Drive Setup -> Use Saved Partition Table = ? ( Disabled or Enabled ) Select the menu item and Press (A) to toggle the setting. Set to Enabled then press (B) a couple times to return to top-level menu. Cold Reboot and check the sizes. There are also two other menu items: (should not be needed as you've already setup the drive with XBP1.3) Click Here To Set LBA48 Option Prepare and Format New Drive It's smart enough to format the HDD for you. I'm not sure if it supports 64KB clusters but I think it does (have not verified). I've always used XBP1.3. My current Xbox with X3 modchip is the first time I've used an X3. The system's a pre-owned console I bought at Goodwill. It was never flashed with X3 BIOS. It had 3 256KB BIOSes flashed: evox.m8plus.fc.137.bin, FlashBIOS 3.0.1 and FlashBIOS 3.0.3. And, the backup BIOS boots FlashBIOS 3.0.1. The 2MBs (8 banks) are now flashed with X3 3294 (1MB), m8plus67 with Quick IGR, iND-BiOS 5004.67 (actually iND-BiOS.Beta.Feb-11-05.67), X2 4983.67 and FlashBIOS 3.0.1.
That was indeed it. Thanks a lot! I had to set it to Enabled and the X3 happy read the partition table from the disk instead of forcing its own. It took me a while to respond because the Xbox drove me nuts. I had put it all together again with the old disk. On inserting the new 1.5TB disk, I could not get the Xbox to write to it. Trying to boot from DVD to Hexen or Slayer just hung the whole thing. I tried different disks and different SATA->ATA adapters but nothing helped. Finally I replace the IDE cable with an 80 pin one instead of the original 40 and it started working. I thought that was a semi myth, but yeah, remember to replace your IDE cables folks... =) And yes, I had to format them twice in XBP 1.3, with a reboot in between, to get it to "hold".
If I buy the parts(https://www.xbmc4xbox.org.uk/forum/viewtopic.php?t=649) for my sata hdd(in the image), will it work?
Yes, 80-wire 40-pin IDE cable and a compatible IDE to SATA adapter. I generally shy away from using a GREEN WDC drive. If you do, find the old WDC utility to disable the green features.
Green drives park their heads very very often and is a point of failure. You can disable the feature to make the green drives act like the other wd drives and gain a vast improvement in expected life time.
