Softmod - lockable HDD upgrade not recognized as locked
Posted: Wed Jul 17, 2019 9:27 pm
Hey guys,
I know this topic has been widely discussed, however I’m having a problem that from I’ve concluded is somewhat unique.
I am upgrading the Original Xbox HDD on my softmodded console.
Softmod performed using SID5.
New HDD to be installed: Maxtor 6L250R0 (lockable)
In summary:
I boot the system with Molex plugged into new HDD via splitter while keeping the original connected to the DVD drive with the IdE cable.
I also make sure the original is in master mode and new HDD in slave mode.
After booting, I select chimp and immediately move the IDE from DVD drive to new HDD.
Scan for IDE devices shows both hard drives. /hda and /hdb. I also take this opportunity to review the new drive, /hdb and see that it is recognized as a lockable drive. Perfect!
So I move on to cloning the drive and proceed with the default selections. The cloning process begins and everything looks good.
Here’s where my issues begin:
I walk away from the cloning process and grab a beer, eat some goldfish, etc. come back and the screen is black. Hmm... as soon as I push a button on my controller I’m back to the Chimp main menus. Strange, did it complete successfully, did it just go to a screen saver ?
I select lock slave drive, and it confirms it was successfully locked. I exit to shell, reinstall new drive and set it to master , and reboot.
I get error code 5.
So I wonder if the screen timeout was an issue, even though code 5 is for a drive that isn’t locked. I repeat the whole process over again, and get the same error code! This time I sat in front of the screen during cloning (took much patience but I had my dog by my side and a beer in my hand) I would periodically tilt the analog stick up and this time, screen does not go black! But after the clone, it goes back to chino main menu automatically. Not sure if chimp has a message that says the clone was completed, or if it simply jumps back to the menu. Nevertheless, I locked the drive again, confirmed, and rebooted with same error code 5.
So my question is, why am I getting an error code 5, when chimp confirms I have successfully locked my new drive?
I’m also considering any alternatives, of simply plugging the drives into my desktop and doing the cloning from there. Any thoughts, or the simplest solution would be greatly appreciated, thank you!
I know this topic has been widely discussed, however I’m having a problem that from I’ve concluded is somewhat unique.
I am upgrading the Original Xbox HDD on my softmodded console.
Softmod performed using SID5.
New HDD to be installed: Maxtor 6L250R0 (lockable)
In summary:
I boot the system with Molex plugged into new HDD via splitter while keeping the original connected to the DVD drive with the IdE cable.
I also make sure the original is in master mode and new HDD in slave mode.
After booting, I select chimp and immediately move the IDE from DVD drive to new HDD.
Scan for IDE devices shows both hard drives. /hda and /hdb. I also take this opportunity to review the new drive, /hdb and see that it is recognized as a lockable drive. Perfect!
So I move on to cloning the drive and proceed with the default selections. The cloning process begins and everything looks good.
Here’s where my issues begin:
I walk away from the cloning process and grab a beer, eat some goldfish, etc. come back and the screen is black. Hmm... as soon as I push a button on my controller I’m back to the Chimp main menus. Strange, did it complete successfully, did it just go to a screen saver ?
I select lock slave drive, and it confirms it was successfully locked. I exit to shell, reinstall new drive and set it to master , and reboot.
I get error code 5.
So I wonder if the screen timeout was an issue, even though code 5 is for a drive that isn’t locked. I repeat the whole process over again, and get the same error code! This time I sat in front of the screen during cloning (took much patience but I had my dog by my side and a beer in my hand) I would periodically tilt the analog stick up and this time, screen does not go black! But after the clone, it goes back to chino main menu automatically. Not sure if chimp has a message that says the clone was completed, or if it simply jumps back to the menu. Nevertheless, I locked the drive again, confirmed, and rebooted with same error code 5.
So my question is, why am I getting an error code 5, when chimp confirms I have successfully locked my new drive?
I’m also considering any alternatives, of simply plugging the drives into my desktop and doing the cloning from there. Any thoughts, or the simplest solution would be greatly appreciated, thank you!