xboxscene.org forums

Author Topic: G Drive Not Displayed Correctly  (Read 367 times)

suiicidalpenguin

  • Archived User
  • Newbie
  • *
  • Posts: 9
G Drive Not Displayed Correctly
« on: February 26, 2006, 12:33:00 PM »

I just accidentally posted the same thing, i just updated mine as well and drive G is not displayed correctly for me as well it seems to be a problem in the config is what i am assuming (something is pointing to the wrong thing)
Logged

The Third Man

  • Archived User
  • Full Member
  • *
  • Posts: 147
G Drive Not Displayed Correctly
« Reply #1 on: February 26, 2006, 12:34:00 PM »

QUOTE(kapdon @ Feb 26 2006, 02:10 PM) View Post

I just upgraded my hdd from 160 to 320 and I had read that your bios had to support "partition 6 takes 137 / partition 7 takes rest" otherwise files could get corupted when hdd started getting full. I re-did my bios using evtool_1.0.9 and evox m8+, ftp to my xbox and flashed using evox, formatted my entire drive and formatted a "G" drive. everything looked fine.  I then updated my Unleashx dash to V0.39.0222a Build 572 and now when in Unleash and I press Y to view system info it displays my G drive as " Drive G: Total: ng Orange Free: 174,130.78 MB"  is this a bug in the latest Unleash build or did I do something wrong?


It sounds like you did everything right. I don't know what that "ng Orange" is all about, but 174 GB is the right size for the G partition on a 320 GB hdd with that BIOS configuration. I wouldn't worry about it.
Logged

Jezz_X

  • Archived User
  • Hero Member
  • *
  • Posts: 2893
G Drive Not Displayed Correctly
« Reply #2 on: February 26, 2006, 12:35:00 PM »

what are you saying is wrong the size ?? or the ng orange bit
because 320gig drive - 174 for G and minus 137 for F leaves about 10 gig which is what the original HD will have in a,c,x,y,z so size is right
Logged

kapdon

  • Archived User
  • Newbie
  • *
  • Posts: 4
G Drive Not Displayed Correctly
« Reply #3 on: February 27, 2006, 04:32:00 PM »

nevermind, i just rolled back to a previous version of unleash and decided to wait until the next release to update my dash.
Logged

rgtaa

  • Archived User
  • Hero Member
  • *
  • Posts: 604
G Drive Not Displayed Correctly
« Reply #4 on: March 07, 2006, 02:59:00 PM »

I am also having the same problem with the WD 320 ....with same error code.
The problem i have is that when I scan games ... it locks up in game menu about 20 to 30 games in... I tryed the latest version.  I was useing Unleashx0.38.0515A when the problem started ...I figured I'd update to latest one ... but same problem.
I'm glad others are getting the same ng/orange message on G drive  ... because that's the reason i'm in this room.
I had to switch to xbmc as main dash since scaning games Freezes on me.

We are all problably talking about the same drive : western digital 320 hard drive ... right?

I was nervous thinking I'd have to re-format the drive (after hours of loading stuff on it ) ... but if it is a config problem I'll check back in week and see if there is fix.
Logged

X_Cheat3R

  • Archived User
  • Jr. Member
  • *
  • Posts: 56
G Drive Not Displayed Correctly
« Reply #5 on: March 07, 2006, 03:26:00 PM »

I have had a similar problem on 3 xboxes that I have upgraded from previous versions of UnleashX.  The area that is supposed to display the free space on G continues to flash back and forth some strange data - it never settles.  Along with this, it causes the video previews to only play for about 3 seconds before restarting.  

I have tried EVERYTHING to resolve these issues - including a full uninstall of UnleashX including UDATA and cache - but the issue does not go away.

I have not had this problem with any that I install the new version on originally, and I have successfully upgraded several others without problems - so it seems to be somewhat random.

I posted more details about this in the official pinned thread~!

Hope we can get this figured out soon!

]
  • [
Logged

brutalboy

  • Archived User
  • Newbie
  • *
  • Posts: 9
G Drive Not Displayed Correctly
« Reply #6 on: March 09, 2006, 12:00:00 PM »

Any update on this problem. This is a only display bug and i can corrupt data?

Thank
Logged