XBOX ONE - How To Install A Bigger Hard Drive !

[wagner4362]

As far as capturing a WIM? You could leave out the /compress flag or use fast instead of max. You could forgo the WIMs and try to move the unallocated space over two partitions, however this generally takes several hours. It could be quicker as there would be less than 10GB on Partition 4, however I'm not sure on an exact time.

Either way, I highly recommend capturing WIMs of partition 1, 3, & 4 as the Xbox One will receive large updates again at some point, and when that happens, Windows will reformat and partition the drive with the partition layout of a 500GB HDD.

• In order to prevent the xbox from doing so, someone needs to figure out how to mount the updater.xvd and possibly how to access the 8GB NAND flash file system, as one of them contains the script that needs to be edited.

Having in mind than my case is not a hdd upgrade, I'm working with the shipped hdd of 1tb just with file system corrupted then already would have solved from beginning isn't?

Each new update/factory reset will change hdd layout back to 500gb?

 

[JW0914]

If you're unit shipped with a 1TB drive, then no, Windows will always format and partition it as a 1TB drive. Windows will only reformat and repartition during an update if it sees an HDD with a partition layout different than what originally shipped with the unit.

I originally had that in my Wiki, however I had to remove it in order to keep the WIM commands and Steps on a single page in an effort to make it more convenient for others. I'll add that tidbit back in when I edit the third page to include a notes section in order to annotate what you mentioned last night.

 

[wagner4362]

So what I doing wrong?

1. Run "sudo python xboxonehdd.py sdc"
2. Run "sudo bash mkxboxfs.sh sdc"
3. Copy OSUDT1 files to System Update partition
4. Unmount mounted partitions
5. Run "sudo python xboxonehdd.py sdc" and typed yes
6. Put back to Xbox One and boot up will fail in ~25%
7. Connect the hard drive to PC and copy OSUDT2 files to folder B
8. Back to Xbox One and got E200 error as I said have deleted some files from folders A and B and booted up but not with the correct hard drive size.

 

[JW0914]

The only way you would have ended up with a 500GB partition layout is if Windows reformatted and repartitioned at step 6. You can verify by looking at the mkxboxfs bash script to verify it did create the 800GB+ user content partition... if it did, then Windows reformatted.

As I stated last night, you need to WIM partitions 1, 3, & 4, re-run the mkxboxfs script, then apply the WIMs back to their respective partitions. Simply follow the steps under the bullet point I mentioned last night

 

[wagner4362]

Just to inform your wiki have some text errors (mkxbox and mkxbox-500gb are bash files instead of python scripts).

 

[JW0914]

There is a possibility you may have a system that doesn't match the versions listed on the Xbox, however if you did, you would have received a 101 error during OSUDT2.

Unfortunately, Microsoft refuses to provide any information for users on this; unless someone discovers a way to mount the updater virtual disk and access the NAND flash filesystem, there's no way to determine why you're seeing what you're seeing. You're not doing anything wrong, as this is being caused by the update scripts contained within the updater virtual disk.

- - - Updated - - -

Just to inform your wiki have some text errors (mkxbox and mkxbox-500gb are bash files instead of python scripts).

Thanks! =] Correction has been pushed.

 

[wagner4362]

Looks correct partitions sizes, I'll do the WIM steps now and see if works.

 

[JW0914]

That's quite odd...

The only thing I can think of is perhaps the consoles that shipped with 1TB drives have a different GUID for the user partition... As that is truly quite odd.

I'll do some research into it when I have some time around noonish

 

[wagner4362]

Applying WIMs...
One thing than I've been noticed is when I run the mkxboxfs.sh (with root rights of course) I get some errors like "cannot identify device sdb1.. sdb2.. sdb3.. sdb4.." or something else, I'm running Ubuntu 16.04 x64 the last version from 8gb usb stick and using a portable external case to plug the hdd in PC, maybe an error in mkxboxfs script? I used an older version of this script I remember and don't appears that errors.

 

[wagner4362]

If not work I don't know what do now. I tried everything and didn't solve. Ubuntu shows User Partition as 800gb+ and Windows in diskmgmt.msc as 800gb+ but in file explorer shows as 300gb+.

 

[wagner4362]

All WIM related steps completed successfully, I'll try when I back home.

 

[JW0914]

Things got a bit hectic and I haven't had time to research it yet, but will tonight.

When you said file explorer, I'm assuming you meant in Windows? Try using diskpart to format partition 2 and see if that fixes whatever the issue.

• Diskpart
  • lis dis
  • sel dis 1
  • lis par
    • sel par 2
    • format fs=NTFS quick label="User Content"

Please take a screenshot of disk management and file explorer open to This PC/My Computer.

As to the mkxboxfs.sh, if you open it in a notepad, all it is is a variable at the top assigning DEV to the correct disk, then 3 commands per partition (I think 3, may be 2). The scripts should be ran by using sudo, not as root (I haven't fully read through the xboxonehdd and gptutil scripts, but I do know certain scripts will not function properly if executed as root vs using sudo; as sudo, while granting su privileges, still keeps permissions as the user.)

Your experience thus far really is perplexing, and has me stumped. Hopefully I'll have some time in an hour or so to do some research into what the cause may be, however I will have time tonight if not.

 

[wagner4362]

After apply WIMs to the hard drive I get E200 error.

Yes, File Explorer from Windows.
I don't understand what you mean after "sel par 2" command. What I do exactly? To format I need to look the script and what next? Please, be more specific.
Yeah I'm getting crazy with that. I need to say than PS4 is much more easier to upgrade hard drive, Xbox is so poor.

 

[JW0914]

After apply WIMs to the hard drive I get E200 error.

Yes, File Explorer from Windows.
I don't understand what you mean after "sel par 2" command. What I do exactly? To format I need to look the script and what next? Please, be more specific.
Yeah I'm getting crazy with that. I need to say than PS4 is much more easier to upgrade hard drive, Xbox is so poor.

Those are diskpart commands, in the order they should be issued. Please post a screenshot showing diskmanagement and file explorer, as it's not possible for Windows to display separate values for partition sizes in file explorer and disk management

The GUIDs you need to ensure are set are:

GUID	Device	Name
A2344BDB-D6DE-4766-9EB5-4109A12228E5	/dev/sdb
B3727DA5-A3AC-4B3D-9FD6-2EA54441011B	/dev/sdb1	Temp Content
869BB5E0-3356-4BE6-85F7-29323A675CC7	/dev/sdb2	User Content
C90D7A47-CCB9-4CBA-8C66-0459F6B85724	/dev/sdb3	System Support
9A056AD7-32ED-4141-AEB1-AFB9BD5565DC	/dev/sdb4	System Update
24B2197C-9D01-45F9-A8E1-DBBCFA161EB2	/dev/sdb5	System Update 2

There's only two explanations at this point for your experience thus far, either the consoles that shipped with a 1TB drive use a different GUID for user content, or it's user error. While there's a decent amount of steps involved, the process is fairly straight forward.

Please also post the detail disk and detail part 2 output from diskpart. For proper command syntax, utilize help followed by the command. The disk has to be selected for detail disk and the partition must be selected for detail part

 

[wagner4362]

Screenshot: http://i.imgur.com/Q4GilzO.png

 

[JW0914]

I've been doing some research since I replied last night to try and figure out what's causing this, and think I may have found a solution.

Issue the following in an admin command prompt/powershell terminal:

1. diskpart

• list volume
• sel vol # [where # equals the volume number of the user content partition]
• extend filesystem
• exit

Refresh the explorer view, and it should now show the correct partition size. If it does not, try removing, then reattaching the disk to the PC.

I'll continue to do some more research until I hear back from you, in case that doesn't solve it.

 

[JW0914]

If that doesn't solve it, please post the output of the following:

• diskpart
  • lis dis
  • sel dis # (where # equals the disk # of the Xbox HDD)
    • detail disk
  • ​sel par # (where # equals the partition number of user content)
    • detail par

Also please post the text output of mkxboxfs.py within

 brackets

 

[wagner4362]

I pull off the hard drive from USB External Case and power it directly to another PC.
Tried the process again, look the output:

[email protected]:~$ sudo python xboxonehdd.py sdf
Disk must have 5 partitions
Create as follows:
    41 GiB NTFS
    831 GiB NTFS
    40 GiB NTFS
    12 GiB NTFS
    7 GiB NTFS
run ./mkxboxfs.sh to create the correct partitions
[email protected]:~$ sudo bash mkxboxfs.sh sdf
Failed to access '/dev/sdf3': No such file or directory
The device doesn't exist; did you specify it correctly?
Failed to access '/dev/sdf4': No such file or directory
The device doesn't exist; did you specify it correctly?

 

[JW0914]

I pull off the hard drive from USB External Case and power it directly to another PC.
Tried the process again, look the output:

[email protected]:~$ sudo python xboxonehdd.py sdf
Disk must have 5 partitions
Create as follows:
    41 GiB NTFS
    831 GiB NTFS
    40 GiB NTFS
    12 GiB NTFS
    7 GiB NTFS
run ./mkxboxfs.sh to create the correct partitions
[email protected]:~$ sudo bash mkxboxfs.sh sdf
Failed to access '/dev/sdf3': No such file or directory
The device doesn't exist; did you specify it correctly?
Failed to access '/dev/sdf4': No such file or directory
The device doesn't exist; did you specify it correctly?

Verify via ls /dev that sdf is the correct disk

 

[JW0914]

I've asked several times for the output of the commands listed in diskpart... please post them. I need the output of detail disk, detail part, and might as well do detail volume as well.

Something within your environment is causing this, however what that specifically is, I have no clue. I've performed the partitioning on 2 separate HDDs, as well have at least 2 other users, with all resulting in a properly formatted 1TB & 2TB HDDs showing correct partition sizes.

I have come across a few technet threads stating issuing the extend filesystem command in diskpart two or three times caused it to finally register as extended, however I'm beginning to suspect this could very well be region related, as more than just language packs are different in Windows from region to region (regardless if it's a PC or an Xbox).

If the diskpart output does not provide any conclusive reasonings for your experience, you're going to have do some research on Google, as this is environment specific.