Print

[TheGink]

Nice! This was my first experience with Chimp and with upgrading the xbox HD. Was quick and easy with Chimp2618 and the simple instructions. Went pretty fast too. Then I added a bunch of stuff to the new F: partition and decided to clone it all to a different HD because the first one I used was too noisy for a media center.

Still easy, but whereas C: and E: cloned at an average of 15MB/s, F: cloned at about 4MB/s, so 5 minutes to clone C: and E:, 2 hours to clone F: Oh well, next time I'll know.

Speaking of next time, I've got another xbox, as of yet unmodded, so I'd like to softmod and upgrade the HD. But since I'm just basically setting it up the same as my first, is it possible to use Chimp2618 to clone the HD from my modded xbox to another drive, then use the newly cloned drive in a different xbox?

Would this just be a matter of pulling the EEPROM from the second xbox and using that EEPROM in the locking stage after cloning?

Thanks so much for the great tool!

[TheGink]

Well, cloning extended partitions didn't work for me. After 2 hours cloning the F: partition, it's blank. C and E cloned fine, xbmc starts right up, but the F: partition is completely blank. Guess I'll FTP it all down from the old drive and back up to the new one.

Being able to clone C and E to upgrade a drive in such little time is still pretty sweet!

[ldotsfan]

QUOTE(TheGink @ Sep 13 2010, 11:23 AM)

Would this just be a matter of pulling the EEPROM from the second xbox and using that EEPROM in the locking stage after cloning?

You'll need to softmod the second xbox first to obtain the eeprom. The softmod package will need to be kernel version neutral - ie generic fonts for Ndure if the second xbox's kernel version differs from the source xbox.

Check my sig for another alternative - the zeroizing key method. If you are still keen on chimp2618, you'll need ftp access to copy eeprom.bin to /tmp in order to lock with chimp2618.

It has been a while but I did test the extended partition cloning feature before concluding the testing chapter. No idea why it didn't work for you though  

[TheGink]

Cool, thanks for the tips. I'll check out the zeroizing info and decide how I'm going to attempt this. I'd sorted out that I'd need to go through the softmod process at least to the point of being able to do an EEPROM backup, then moving that EEPROM to the /tmp location on the source drive where Chimp will be able to find it to lock. Didn't consider the kernel version and such though. Good to know.

I'm not sure why F didn't clone either, it certainly acted like it was working. I'll probably give it another go when I try this whole clone for a different xbox setup, maybe it was just a one time glitch.

[TheGink]

For the sake of info I'll add that it turns out I didn't just end up with an empty, non-cloned F: partition, but something else went basically wrong in the process, and I eventually figured out that I could no longer transfer files over around 11MB in size to the new F: partition. File Manager would fail it, and my FTP program would fail, then leave a file of the correct name of exactly 32MB size in the target directory. Strange.

Maybe because I cloned from a 60GB to an 80GB hd? So the F: partition had to increase in size as well as clone?

Dunno. Fortunately I could just fire up Chimp2618 on the new drive and use Format Extended Partitions on Master to reformat the F: partition and now it's good as new and my files are transferring back over to it smooth as butter.

[ldotsfan]

QUOTE(TheGink @ Sep 15 2010, 04:49 AM)

Maybe because I cloned from a 60GB to an 80GB hd? So the F: partition had to increase in size as well as clone?

I thought about the cloning process again and referred to the development thread. It seemed that I had wrongly formatted the target hdd to its full size - with a matching partition table and File Allocation Tables - FAT for the new sized extended partition(s) early in the cloning process and during the actual cloning, the partition table entries were adjusted but nothing was done for the FAT so there was residue large size FATs for the smaller extended partition now cloned to the target hdd overlapping with the FATs cloned over - this might explain the 32Mb bug.

This should be trivial to fix but will require some time - especially testing. I hope I get some time to fix it soon in the future - until then please do not use the buggy extended partition cloning feature in the tool.

[Spc 4]

ldotsfan, I do not know if this has anything to do with some of other peoples problems, but I found out If I have XDSL running  I can not get MUGEN to work, and vice versa. If I just have one instance of Linux running I never run into problems. ( linuxboot.cfg ) in the E directory. Just a hunch, and I'm probably off, but just a hunch.

[Terry_Bogard]

QUOTE(kodec @ Aug 22 2010, 05:27 AM)

Here were the steps I took:
1.  Download the LUD iso and burn to CD (http://sourceforge.net/projects/xboxhdm2/files/LUD/LUD-v1.01.iso.zip/download)
2.  Prepare target hdd for hot swap by providing it an external power source (used a USB/IDE kit for this part) and setting the mode to slave.
3.  Boot up the LUD disc.
4.  In the gentoox linux loader, select Chimp.
5.  Wait for booting initrd [ok] message and then immedicately performed hot swap of IDE cable from DVD drive to target hdd.  Default setting in the config file allows for only 10 secs.  If you see "Starting Chimp" before you are done, then you are too late and will need to start from Step 3 again.
6.  Verify both drives were detected using option 1 (Scan).
7.  Select option to clone master to slave.
8.  Wait for completion of cloning process.
9.  Back on the menu, select Lock Slave drive and lock the drive from the motherboard.
10.  Back on the menu, select shutdown.
11.  Move IDE cable back to DVD drive.
12.  Set target hdd to Master mode.
13.  Connect original hdd IDE connector to target hdd.  
14.  Disconnect power cable from original hdd and plug into target hdd.  (Note:  I didn't do this initially and was still using the USB kit power source.  This resulted in Error 07 upon boot up.  When I switch to using the original hdd power cable, the target hdd came up normally).
15.  Boot up Xbox again with LUD disc.  Select Chimp.
16.  Select option to format master drive extended partitions.  I am using a 500 gb drive so I selected the option to put everything after 137 gb to the G drive.
17.  After partitioning is finished, shutdown again and remove LUD disc.
18.  Boot up again. The xbox should now boot up normally as before as it had with the original hdd.
Thanks Idotsfan for making this fantastic tool for us 1.6 owners!
-kodec

Kodec, have a few questions regarding how to create a 137 GB partition from 500 GB HDD using Chimp.

1.) Can it be accomplished with a soft-modded Xbox? (no "mod chip")

2.) How simple is it? If it's not too much trouble could you or somebody else here run me through the process? I just formatted my new HDD with Chimp and am about to lock it. Your guide works best, thanks in advance.

My compliments to ldotsfan for the simplified version.