Jump to content

Trying to upgrade internal HDD but only showing 120gb...


Recommended Posts

Hey guys, happy new year!

A few months ago I was given an original Crystal Xbox. As someone who has always been on the Sony side of consoles, I admit, I don't know much about Xbox. However I was told that the Xbox was running EvoX (Can be confirmed, when I turn the Xbox on, there is an EvoX icon on the left hand side of the boot screen) and that the Xbox had a modchip inside.

The Xbox has been sitting under my bed for a while and I thought today I would dust it out and upgrade the internal HDD. The IDE hard drive inside the Xbox was only 80GB and I had a spare 250GB IDE hard drive I wasn't using. --

So I went ahead and followed this tutorial: 

 

Basically I downloaded Hexen 2018 > burned the image to a DVD > put the DVD inside my Xbox > replaced the old IDE HDD with the 250GB one > booted into Hexen 2018 > went into Disk Upgrades > From there I followed the process. 

After the files had copied over from the DVD, XBPartitioner 1.3 booted up and I made sure that I set the F drive to the full 250GB.

From there the process was complete. I took the Hexen 2018 DVD out of my Xbox and the UnleashX dashboard popped up. BUT when I look at the drive details on the upper left corner. I can see that there is only around 120gb free on (F:).

Whenever I try to boot XBPartitioner from the dashboard menu, I get the following error:

"LBA48 info not found! Custom Partitions will not work with this BIOS! Update your BIOS to one which supports at least LBA48 version 2."

I done a bit of research and it LOOKS like I need to update my BIOS. But honestly as someone who has no clue what they're doing, this frightens the hell out of me. So that leads me to this post... I'm looking for some help which can preferably be explained in as simple detail as possible, I literally need someone to spoon feed me the steps. I would be so grateful and appreciate it!

EXTRA INFORMATION - If I load into the EvolutionX dashboard I can see the follow details, which might be relevant.

  • BIOS: EvoX M8 (1.6)
  • Kernal: 1.00.5838.01
  • EvolutionX V+3935
Edited by Thakarra
Link to post
Share on other sites

I have found more often than not you need to format partition 6 (and 7 if you have it) twice the 1st time go 10 to 20 gb smaller than max and next time go max less 1gb.

What mod chip have you got?

 

Cheers

SS Dave


Soft modding is like masturbating, It gets the job done but it's nothing like the real thing.

 

Link to post
Share on other sites
Posted (edited)
15 minutes ago, SS_Dave said:

I have found more often than not you need to format partition 6 (and 7 if you have it) twice the 1st time go 10 to 20 gb smaller than max and next time go max less 1gb.

I have tried doing the "Disk Upgrade" from Hexen about 5-6 times now. Still no change.

I can't open XBPartitioner because it throws the error mentioned above.

 

16 minutes ago, SS_Dave said:

What mod chip have you got?

 

 

Also I don't know what chips I have, as I mentioned the Xbox was given to me.

Edited by Thakarra
Link to post
Share on other sites

Go here and download this it leaves Hexen for dead

You can also run Xbpartitioner from the DVD

It could also be a old version of the EvoxM8 and only support up to 137gb, The EvoxM8 on this disk will support up to 2.2tb of HDD

 

Cheers

SS Dave


Soft modding is like masturbating, It gets the job done but it's nothing like the real thing.

Link to post
Share on other sites
9 minutes ago, SS_Dave said:

Go here and download this it leaves Hexen for dead

Sorry to sound like an absolute noob (I am hahaha), but which version should I download? PBL or non-PBL?

Also once I've got this up and running.. Am I using it to reinstall everything to my hard drive (like I was doing with Hexen) or am I using it to flash my BIOS?

Link to post
Share on other sites

I would go the PBL and you could just use the disk to reflash the BIOS and run the Xbpartitioner but I would use it for a complete install.

 

Cheers

SS Dave


Soft modding is like masturbating, It gets the job done but it's nothing like the real thing.

Link to post
Share on other sites
Just now, SS_Dave said:

I would go the PBL and you could just use the disk to reflash the BIOS and run the Xbpartitioner but I would use it for a complete install.

 

Okay, I'll try the complete install first because it seems like the most "safe" option.

However when it comes to flashing BIOS, the whole reason I made this post is because I want advice from a community who know what they're doing, I don't want to flash the wrong thing and brick my console. I've been there and done that before, it's a horrible feeling.

Cheers though! I do appreciate you helping me!

Link to post
Share on other sites
2 minutes ago, Thakarra said:

However when it comes to flashing BIOS, the whole reason I made this post is because I want advice from a community who know what they're doing, I don't want to flash the wrong thing and brick my console. I've been there and done that before, it's a horrible feeling.

That's fair enough and it would be better if more people asked for help over jumping in and breaking it. That makes a lot more work to fix it.

If you are not sure on the modchip I would suggest you open the Xbox and take a pic of the main board then post it here plus while it's open clean the dust out of it.

 

Cheers

SS Dave


Soft modding is like masturbating, It gets the job done but it's nothing like the real thing.

Link to post
Share on other sites

I'd bet the original Evox M8 1.6 BIOS is just a default M8 type.

According to the BIOS features tables I have archived neither Evox M8 or M8+ support LBA48 by default, it has to be "reconfigured" using the EVTool. I think a lot people forget that and other useful/wanted features of the EvoxM8+ BIOS need to be enabled by it in the same way too.

Most versions of EvoxM8+ you find on discs etc have been so configured but if this is an old chip install and/or the BIOS version used to flash it likewise then you have the most likely explanation.

If you get a message about LBA48 and it not being supported by the BIOS then you should believe it and not assume all sorts of other things are wrong that need fixing.

Chances are a simple reflash of the BIOS with any recent EvoxM8+ v1.6 BIOS would solve the problem.

But I'm very much with SS_Dave on the importance of correctly identifying the chip type first and confirming the Xbox version too from any pictures that can be provided.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Similar Content

    • By cOrPsE
      DHCP, PC and Xbox are wired ethernet. All devices in the same room. Basically one day it was fine and the next it wasn't. Its so strange. When I ftp to any xbox from my PC, it maxes out around 1mb on FlashFXP. I have tried from Linux using a different client. Also tried 3 different windows clients. I changed out modems and ethernet NIC. If I setup an FTP from one xbox to another, the speeds between them are great/normal like 11mb. I can take files FROM the xboxs to my PC at the same speed. This is not simply just a 1 xbox issue if you cant tell. Any xbox I hook up, same shit happens. I tried 3 different dashboards. Tried different HDDs obv. The only thing I can think of is around the time this started happening, I did the forza multiple screen thing through DHCP. However my setup has completely changed since then, and new xboxs too. I am really lost on what this could be. I feel like i have covered every single base, but problem persists. This has happened to me in the past and 2 things fixed it. One time, I changed the ethernet cable. Tried that this time, didn't work. It specifically happened after a windows update way back so i reverted to an old version and that fixed it. However trying linux I feel has ruled that out. /shrug
    • By Skrumpkin
      Hi,
      I have a hard modded OpenXenium chip with a 1 TB WD Blue HDD.  I have everything set up and I am trying to get more than 200 GB - with more than  > 200 GB left on a partition.  Filezilla is not letting me do that.  I am just trying to transfer the titles.  They are all HDD ready for transfer but they do not go through at a certain point.  They  all become failed transfers.  The bios I am using is unleashed x from the OGXBOX installer.  It was not flashed by the program but was transferred by my network.  It is a CEE bios.   I switch dashboard sometimes.  The only one that I have on there that is not preinstalled is Emulation Station. I had used the DVDmulleter to get the bios necessary.  The HDD has been partitioned correctly having being split from F to G the remaining left.  I am fairly new to this and any advice to help would be beneficial.
    • By KpCollins
      All Xbox's I mention are Tsop'd 1.0,1.1& 1.4 .I'm receiving the errors above, this is only with the sata HDD and a convertor I got off ebay. I have one in another tsop xbox and it runs fine
       
      So I have 3 convertors, all are the same and 1 runs just fine. The other 2 give the error codes above.
      The one working is using the original Xbox's IDE Cable with a slow 5400rpm 2tb Drive. Works flawlessly
      The other 2 Tsop xboxs ( 1.0 & 1.4 ) do not want to accept the Sata Drives, Their original Stock HDD with UNleashX Dahboard works fine on both.
      All drives are set to unlocked
      the 1.4 runs EvoM8+
      The 1.0 Run x2 5035? Think thats right. - Same as the 1.1 that works.
       
      I've read this could be an issue with the Sata Adaptor, IDE Cable only being 40wire, Drives or Both.
       
      Its worth mentioning I've tried a few different hdd's with the same issue on all Sata's. I can get Hexen2020 to boot on both but Hexen also struggles to read the drives.
      On the 1.4 I backup the Eeprom to the HDD and it will boot but to the Xbox Dash and as soon as I try with the UnleashX Dash I get the errors again.
       
      I am close to ordering an 80wire ide cable to try see if this resolves it, Failing that The more expensive adaptor for IDE made by Star tech which i'd wished to avoid.
       
      1 more thing, the IDE to Sata Adaptors being set to Master gives the error. Without the Pin in cable select does nothing but freeze on the Blob Screen
      Slave mode causes it to freeze also.
       
      Any advise is really appreciated.

Board Life Status


Board startup date: April 23, 2017 12:45:48
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.