XBOX ONE - How To Install A Bigger Hard Drive !

[wagner4362]

Reconnect the drive to the PC, repeat step one in my wiki above and you should be fine. I forget to include the bit about Windows reformatting the drive prior to rebuilding if it sees a partition structure different than what the unit shipped with. When you reconnect the drive to your PC, you should see ~430GB of unused space after partition 5.

If you've already done all that and you're still receiving an error screen: Did you unmount the drive prior to removing from the PC? Did you re-run the xboxonehdd script?

Thanks for the reply, I'll try again and back here to say if worked or not.

 

[JW0914]

quick question pretty sure i've done everything right and original drive still boots up but i was trying to upgrade to a 1tb from a 500 gb and get nothing but a black screen all the files show they are there too....however here is the question would a server drive work....it's not a standard 2.5 inch size its a little bigger i think thats my issue but wanted to see if someone had this issue before.....oh and fyi i've let it sit for 5 or 10 minutes and still black screen

did you follow my wiki?

Its generally best to read the last page of a thread, or at the very least the last 10 posts, prior to posting.

Also, it's not recommended to install a server drive in any console. A server drive's RPMs range from 7200 - 15000 depending on the drive, and even with a 7200 RPM drive, it will result in an enormous amount of extra heat. If you're looking for faster boot and game load times, install an SSHD (numerous independent tests have shown you only gain ~1 second with an SSD over an SSHD).

 

[ndtemple417]

did you follow my wiki?

Its generally best to read the last page of a thread, or at the very least the last 10 posts, prior to posting.

Also, it's not recommended to install a server drive in any console. A server drive's RPMs range from 7200 - 15000 depending on the drive, and even with a 7200 RPM drive, it will result in an enormous amount of extra heat. If you're looking for faster boot and game load times, install an SSHD (numerous independent tests have shown you only gain ~1 second with an SSD over an SSHD).

Yes I did and I used you're guide thanks anyways it's a 7200 rpm drive thanks for your help and input

 

[JW0914]

Yes I did and I used you're guide thanks anyways it's a 7200 rpm drive thanks for your help and input

Your reply isn't clear on whether you fixed your issue...

Please list the files in each partition, and if you haven't read the wiki since last night, please take a look at the wiki on GitHub again, as I realized I left out two steps and added them last night. The only thing that would result in the xbox displaying a black screen would be the 1st sector bits or Windows reformatted the drive. Did you run the xboxonehdd script after copying files?

If the original 500GB drive boots up, all you need to do is wim partitions 1, 3, & 4 and apply each wim to the new drive.

• Skip to Step 3 under If you are installing a drive larger than 500GB, then see WIM Commands

If you didn't read the entire three pages, I encourage to do so, as the wiki does work (both myself and another user used it to successfully rebuild a bare hdd). The only way one could be getting a different result is by not fully reading the wiki.

• The Xbox HDD is fairly simple... partition 4 rebuilds the OS (system files on partitions 1 & 3), with folder A containing the previous update and folder B containing the current update iteration (files needed can be download from the Xbox Support site). Partition 2 can be ignored, as it's content is synced once you sign into Xbox Live, and partition 5 is empty.

Do you have any suggestions on anything I can add to the wiki to make it easier for other users?

 

[JW0914]

Because of the issues being experienced by users using my wiki, I reorganized and reworded portions of it to make it more fluid and clear up some misunderstandings that could occur, especially if one has never done this before.

The newly changed wiki is currently available here & if anyone has any suggestions for additions or re-wordings, please let me know.

 

[ndtemple417]

Your reply isn't clear on whether you fixed your issue...

Please list the files in each partition, and if you haven't read the wiki since last night, please take a look at the wiki on GitHub again, as I realized I left out two steps and added them last night. The only thing that would result in the xbox displaying a black screen would be the 1st sector bits or Windows reformatted the drive. Did you run the xboxonehdd script after copying files?

If the original 500GB drive boots up, all you need to do is wim partitions 1, 3, & 4 and apply each wim to the new drive.

• Skip to Step 3 under If you are installing a drive larger than 500GB, then see WIM Commands

If you didn't read the entire three pages, I encourage to do so, as the wiki does work (both myself and another user used it to successfully rebuild a bare hdd). The only way one could be getting a different result is by not fully reading the wiki.

• The Xbox HDD is fairly simple... partition 4 rebuilds the OS (system files on partitions 1 & 3), with folder A containing the previous update and folder B containing the current update iteration (files needed can be download from the Xbox Support site). Partition 2 can be ignored, as it's content is synced once you sign into Xbox Live, and partition 5 is empty.

Do you have any suggestions on anything I can add to the wiki to make it easier for other users?

Oh I didn't try anything else as i need to get a none 7200 rpm drive however i'll read over your wiki again as it's very helpful and thanks for your time and efforts again by the way

 

[ndtemple417]

@JW0914

Just to be clear all we have to do is copy and paste your wim commands in command prompt with admin rights or powershell correct?

 

[JW0914]

No problem at all =]

You can use a 7200 RPM as a temporary drive, I just wouldn't recommend using one as a permanent drive due to the massive amount of heat they put off, as well as spin up noise. Server drives vary in what advanced features they offer, however they're rarely manufactured with db level or heat output as primary concerns since they're meant to be installed in a server rack with adequate cooling (as many server processors are 115w+, with many, if not most, non-SOC server boards running two on the same board).

Using a 7200rpm drive won't damage the console, but it will result in a noticeable db increase, mainly due to the fan. If you're going to be buying an HDD specific for the console, I'd recommend Seagate's ITB SSHD or WD's different take on the SSHD (they essentially combined a physical SSD with a mechanical drive).

 

[JW0914]

@JW0914

Just to be clear all we have to do is copy and paste your wim commands in command prompt with admin rights or powershell correct?

Yup; It would be just like creating a WIM of your system partition.

• The only caveat I noticed was one isn't able to capture them as ESDs with /compress:recovery, which would have been nice, since ESD utilizes a compression ratio thats ~33% more efficient than WIM.

It's important to not have whichever partition is currently being WIM'ed open in Explorer, as it will result in a failed image.

• The only other thing I noticed is due to the xvd's, you'll get wonky completion percentages during the capture process, with it appearing like it's frozen at times, and others jumping 20 or 30%. It could very well have simply been unique to my environment, but if you do notice it appearing as if it's frozen, don't cancel it and allow it however much time it needs to update the percentage.

 

[ndtemple417]

No problem at all =]

You can use a 7200 RPM as a temporary drive, I just wouldn't recommend using one as a permanent drive due to the massive amount of heat they put off, as well as spin up noise. Server drives vary in what advanced features they offer, however they're rarely manufactured with db level or heat output as primary concerns since they're meant to be installed in a server rack with adequate cooling (as many server processors are 115w+, with many, if not most, non-SOC server boards running two on the same board).

Using a 7200rpm drive won't damage the console, but it will result in a noticeable db increase, mainly due to the fan. If you're going to be buying an HDD specific for the console, I'd recommend Seagate's ITB SSHD or WD's different take on the SSHD (they essentially combined a physical SSD with a mechanical drive).

gotcha and cool....think i'll wait however that seagate 1tb sshd or wd's sshd do they have 2 tb for a decent price as that is what im wanting to go to and is there anyway to make a 3.5 inch fit and could the console handle the voltage

 

[JW0914]

gotcha and cool....think i'll wait however that seagate 1tb sshd or wd's sshd do they have 2 tb for a decent price as that is what im wanting to go to and is there anyway to make a 3.5 inch fit and could the console handle the voltage

For the 2.5" FF, 1TB is as high as SSHDs go with both, and my guess as to the reason why would be drive thickness. Both make a 2.5" FF 2TB mechanical HDD, and if faster load times aren't a priority, that would work for you; Seagate also has a 4TB 2.5" and I believe WD does, or will soon . There's numerous blog posts and videos demonstrating the ~20 - 25 second gain you get by switching to an SSHD for the internal drive, dropping a cold boot time from ~50 seconds to ~30 with an SSHD, with an additional gain of ~2s with an SSD. Game load times increased by ~ 10s with an SSHD over a plain mechanical.

If you need/want more storage than 1TB, I would recommend running a 1TB SSHD for the internal drive, and utilizing an external 2.5" drive via USB3. This ensures you get the boost in speed for load times, while still providing you with a large storage medium.

In regards to a 3.5" drive (I was having this exact conversation with another user on iFixIt the other day) things get a bit grey due to do the licensing agreement with Microsoft for the Xbox One. While the license is a software license only, the way two things in it are worded does provide the ability for interpretation not in the end user's favor. I don't believe it would actually create an issue with Microsoft, but I am curious how Microsoft would interpret such a modification.

I personally wouldn't recommend utilizing a 3.5" drive in a console, as there's too many cons for doing so, from the fact the console wasn't designed for a 3.5" drive, to the fact it will cause more heat, draw more power, and possibly restrict adequate ventilation to the board and processors (if installed internally into the console). This is simply my personal opinion, so if you'd like to try, give it a go and see how it goes. I would recommend a few things however: since the console wasn't designed for a 3.5" drive, you'll need to use a multimeter to determine the voltage on the molex power connector. I would also encourage doing as much research as you can beforehand online to find out if anyone has done so and what results they had.

My personal moto: don't mod something you can't afford to lose or break. If money isn't an issue, wait until June or July when Samsung releases their 2nd gen 850 Evo/Pro series SSDs, which doubles all currently available sizes, with their largest 850 Evo/Pro SSD being their 4TB one (the new sizes will be 256GB, 512GB, 1TB, 2TB, and 4TB all in the 520MB/s read/540MB/s write area with Evos carrying a 5yr warranty & Pros carrying a 10yr)

 

[JW0914]

Just wanted to touch base... were you able to finally rebuild without issues, or are you going to wait until you get a new HDD?

 

[wagner4362]

Hi, I tried the process again and now I see an E200 error after copy OSUDT2 files to folder B.

And yes I've executed the xboxonehdd.py script again typed yes to convert to xbox one hdd and unmounted correctly all partitions before detach the hard drive from PC. What I do now? Copy OSUDT3 files to folder B?

 

[wagner4362]

Seems to work right now!!! After error E200 I deleted all files in folder B and deleted all files in folder A except sosinit.xvd and sostmpl.xvd in folder A, after that I put OSUDT2 files in usb stick and boot up. The update finally finished and now is working perfetly, thank you soo much!!!!!

 

[JW0914]

Seems to work right now!!! After error E200 I deleted all files in folder B and deleted all files in folder A except sosinit.xvd and sostmpl.xvd in folder A, after that I put OSUDT2 files in usb stick and boot up. The update finally finished and now is working perfetly, thank you soo much!!!!!

Out of curiousity, did you have a LAN cable plugged into the Xbox [internet accessible]? I can't remember if I did or did not, and when I have some time in the coming weeks, I'll take mine apart again and rebuild with the opposite of your answer as I'm interested in seeing if I can replicate the results you were getting. If I can replicate them, I can solve them and add notes on what one should do if they run into a specific issue.

It really is rather unfortunate Microsoft doesn't post a wiki on Xbox Support on how to do this, as the Xbox One only has a 1 yr warranty. It would be different if it had a 3 or 5 year, but to not provide something similar to a technet page on how to rebuild Windows on a bare HDD is baffling.

 

[wagner4362]

Out of curiousity, did you have a LAN cable plugged into the Xbox [internet accessible]? I can't remember if I did or did not, and when I have some time in the coming weeks, I'll take mine apart again and rebuild with the opposite of your answer as I'm interested in seeing if I can replicate the results you were getting. If I can replicate them, I can solve them and add notes on what one should do if they run into a specific issue.

Yes with LAN cable.
Now looking inside system the hdd size is showing as I have 500gb and not 1tb, strange:

364,8gb free of 364,9gb

I can fix this in gparted or what?

 

[wagner4362]

I have 466,51gb not allocated. I can resize the User Content partition?

 

[JW0914]

You'll need to perform everything listed under the first bullet point under "Rebuilding OS using OSUDT Downloads" in the Wiki (create WIMs of partitions 1, 3, & 4, then perform the 4 listed steps).

Whenever Windows does an update, if it does not see the partition layout the system originally shipped with, it will reformat the drive and partition it accordingly (in this case, the partition layout of a 500GB drive); also applies to factory resets. This is one of the reasons why I recommend WIMing partitions 1, 3, & 4 to keep as a backup, as the Xbox One will eventually see another major OS update, at which point it will reformat the drive and repartition it.

It's generally quicker and more efficient to capture WIMs of the partitions, then apply those WIMs, than it is to move the unallocated space over 2 partitions. This knocks out two birds with one stone by also leaving you with a backup of the three partitions. Utilizing the max compression flag will result in the capture process taking longer, but provides the most efficient size, however you could use the fast compression flag as well, which would take a little less time. If the max flag is used, you'll end up with a total size of ~5.7GB for all three partitions

 

[wagner4362]

There's another way to do this more faster? I'm out of time now.

 

[JW0914]

There's another way to do this more faster? I'm out of time now.

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.