Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

reverting to 500gb? #9

Open
truvine7133 opened this issue Dec 21, 2016 · 12 comments
Open

reverting to 500gb? #9

truvine7133 opened this issue Dec 21, 2016 · 12 comments

Comments

@truvine7133
Copy link

i was using this to replace the original hard drive, which was removed by another person. i know for a fact that it is a 2 tb s model, but when i put in a two terabyte, it formats back to 500gb on the console. coiuld i be doing something wrong? i run the xboxonehdd. py script first ( in sudo) then the mkxboxonefs.sh file, then xboxonehdd again. i use the OSU update file as well, to recover the system

@alexisblack
Copy link

alexisblack commented Dec 21, 2016 via email

@truvine7133
Copy link
Author

that, i understand, but the coding is a bit above me, unless i dedicate a few days to learn what i need to know to edit it. i have an original xbox 2tb hard drive and i recorded the partition info off of that. would cloining that work?

You need to change the script i belive to partition to the correct sizes

On Wednesday, December 21, 2016, truvine7133 @.***> wrote:
i was using this to replace the original hard drive, which was removed by
another person. i know for a fact that it is a 2 tb s model, but when i put
in a two terabyte, it formats back to 500gb on the console. coiuld i be
doing something wrong? i run the xboxonehdd. py script first ( in sudo)
then the mkxboxonefs.sh file, then xboxonehdd again. i use the OSU update
file as well, to recover the system


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#9>, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAyuLV-IpgSJKQ4Ep3TdfC8-uVgLYomgks5rKVOxgaJpZM4LTIK4
.

@alexisblack
Copy link

alexisblack commented Dec 22, 2016 via email

@alexisblack
Copy link

alexisblack commented Dec 22, 2016 via email

@truvine7133
Copy link
Author

I believe so, theoretically it should work. Take a look at what the author told me in my issue I had awhile ago. If you are installing a drive larger than 500GB: - Format with the proper layout of a 500GB drive (remaining free space after partition 5). - Once the OS rebuild finalizes successfully and you're taken to the Xbox Home Screen,shut down the xbox completely via the menu (it needs to be fully shut down, not put into standby). - Copy all files from all partitions into separate folders on a separate HDD - One could also use the WIM commands below <#6 (comment)> to capture, then apply, a WIM to the applicable partitions - Reformat the Xbox One internal drive & partition it via the the script provided - Copy all files back to their respective partitions - Once reconnected to the Xbox One, it should boot and display the correct size for free space. - If you receive an error after reinstalling, you need to rerun the xboxonehdd script, or use dd, to flip the HDD's 1st sector bits.

the problem is that im not trying to go higher that the original, im trying to put the same size as the original. perhaps the scrypt isnt set up for the 2tb one s

@truvine7133
Copy link
Author

truvine7133 commented Dec 30, 2016

i think i found part of the issue. sometimes, the scripts do not create the correct partition sizes

@alexisblack
Copy link

alexisblack commented Jan 1, 2017 via email

@truvine7133
Copy link
Author

It does mention drives larger than 500gb, but only in the context of replacing one in a device that originally had a 500gb drive with one that is larger,since the mkxboxfs-500gb.sh script formats the drive to the 500gb file system's exact sizes to pass the initial update and fix. I've used the standard script to successfully work on both 500 and 1tb drives but it appears not to work correctly for 2tb drives, perhaps not leaving adequate free space

@truvine7133
Copy link
Author

grabbing the drives i needed, i was able to get the exact hard disk partition sizes, and looking into the mkxboxfs.sh file, i can modify it to make the exact sizes needed. i can upload the script to juvenal to make it easier for future users to get it done.

@beren12
Copy link

beren12 commented Jan 5, 2017

Can you attach the patch/file here or make a pull request?

@truvine7133
Copy link
Author

truvine7133 commented Jan 5, 2017

I had made a clone with a two terbyte a while ago, and recently, ive been working on the one terabytes, which have been acting up for me with this script as well. my usb drive glitched out and i lost the two terbyte partition size document, so i need another one to come by for me,, but the one terabyte drive is as follows:

Temp Content

44023414784 bytes

User Content

838592364544 bytes

System Support

42949672960 bytes

System Update

12884901888 bytes

System Update 2

7516192768 bytes

I would have modded the mkxboxfs.sh script, but that script goes by megabytes, and this needs to be perfect. i wasn't sure if i could make it copy correctly., also, i probably need to switch the bits after, since the xboxonehdd.py script wont work on this one

@JW0914
Copy link

JW0914 commented Jan 30, 2017

In order for this to be verified, someone would need access to three different consoles that came with a 500GB, 1TB, and 2TB HDD natively, however this is what I assume is happening:

  • On the WinRE xVHD, scripts reside to auto partition a drive once connected to the an Xbox One, and the only way a console with a native 1TB or 2TB drive would autoformat to a 500GB layout is if the WinRE virtual disk was inadvertently used from the original 500GB consoles during manufacturing.
  • When a PC or game console is manufactured, the drives are deployed with Windows prior to ever being installed in the device. The device may or may not be powered up after HDD installation, depending on how SCCM or MDT has configured the Windows deployment.
    • Due to this, it is possible 1TB and 2TB drives are being deployed to consoles with NAND that contains the WinRE VHDs for the original 500GB consoles.

In regards to the Xbox One HDD Python script, it is written to provide partitions 1, 3, 4, & 5 with the same sizes every time and whatever space is left over is used for partition 2.

I wrote a wiki to make this easier on users, and while it's a bit dated as I haven't re-written it since Microsoft switched how they're pushing updates (i.e. OSUDT steps are no longer the same), the core steps will work.

  • I highly recommend anyone upgrading or replacing their console's HDD to take the time and take WIM backups of the partitions on the original drive, as well as the replacement once it's fully up and running.
    • Partition 2 should not be imaged, unless one does not have reliable internet access or speeds <30mpbs, as the resulting WIM, even with max compression, will be roughly the same size as the data being backed up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants