Post by: vjreddy12 on December 07, 2003, 03:44:00 PM
Try searching.........and yes it does.
Post by: kilroy1 on December 07, 2003, 10:22:00 PM
There are a couple threads in the backups forum that you should read. One of the threads I started. They have to do with file system corruption if you exceed ~ 250GB on a single partition.
I've asked for someone to make a sticky warning post in these forums, but for some reason no one will.
-Kilroy
Post by: heinrich on December 08, 2003, 04:24:00 AM
| QUOTE (Traian2003 @ Dec 8 2003, 12:09 AM) |
It does.  I believe it's version 2.5.Traian2003 |
what?!?! I think you thinking of SLAYERS 2.5, cause the evox 2.5 BIOS, (notice he asked about a bios) is rather old and def. does not support lba48.
ok, cromwell has supported lba48 for a LONG TIME... at least a year. You can patch the evox bios to support it with xbtool, its not hard to do, and quite frankly, if you cant figure it out, you dont deserve all that hard drive space in your xbox
And you posted this in the evox dash forum, so I am moving to the bios forum...
Post by: Ghettofreeryder on December 08, 2003, 08:16:00 AM
Post by: muddy on December 09, 2003, 07:44:00 AM
Post by: Heykrop on December 09, 2003, 08:01:00 AM
Post by: muddy on December 09, 2003, 09:33:00 AM
Post by: lookformeb on December 09, 2003, 10:25:00 AM
Post by: The Dave man on December 09, 2003, 12:22:00 PM
Post by: Ghettofreeryder on December 09, 2003, 01:13:00 PM
Post by: The Dave man on December 09, 2003, 04:39:00 PM
Post by: NghtShd on December 09, 2003, 05:55:00 PM
| QUOTE (The Dave man @ Dec 9 2003, 09:39 PM) |
| So if I patch EvoX M7, I wouldn't need to create a G: partition, I could just have everything in the F: one? |
That's right. However, if your drive is 300GB or more then you'll want to have it partitioned into F & G, because there is a filesystem problem with partitions over ~280GB. You may also want to use a G partition for the part of the disk over 137GB if you already have a F which goes up to the 137GB limit and you don't want to lose the data on that partition.
Post by: The Dave man on December 10, 2003, 11:52:00 AM
Post by: oz_paulb on December 10, 2003, 07:41:00 PM
| QUOTE (The Dave man @ Dec 10 2003, 09:52 PM) |
| Well, I'm planning my mod for summer 2004, so it's a while off, but I'm getting prepared now so I can do it lickidy split. I have tons of games, and I was going to get a 120GB HDD until I found out all this, so now it seems I'll be getting at least a 200GB one. Someone else told me that that problem with a HDD bigger than 280GB happens at 250GB, is that true? |
It's unclear (to me) exactly where the limit is (250GB vs 280GB).
It seems that most people experiencing corruption have > 280GB drives. But, there have been some reports of issues on 250GB drives. There's reason for me to believe that the problem is on >= 280GB (because of the # of bits used for a cluster #). That's just a guess, though.
I've ordered a 320GB Maxtor drive, and will spend some time trying to track down exactly where the problem is. I think it'll turn out to be 'fixable' by changing the 'cluster' size on the hard drive. That's just a guess, though.
Worst case, I believe it'll work just fine if you split the drive into F: + G: (each partition smaller than the 'limit' (~250GB)).
- Paulb
Post by: The Dave man on December 11, 2003, 03:54:00 PM