evilmurdoc Posted June 1, 2024 Report Share Posted June 1, 2024 So I'm finally upgrading the HD in my second OGXBOX. After initial issues, I was able to get HeXen2018 to load. I went through the process and chose to have the whole ~1TB for the F. After the process was complete and I booted up into UnleashX I noticed the f drive wasn't showing the full space. In fact it's a hell of a lot smaller than expected. Instead of the ~1TB it's showing 123,408.52 MB for the F. I attached a picture below. Thoughts? FYI it's hard modded with a Xenium ICE. Quote Link to comment Share on other sites More sharing options...
NokSueCow Posted June 1, 2024 Report Share Posted June 1, 2024 (edited) Does your bios have LBA48 support? I would format the hdd in FatXplorer and see what happens after that. Edited June 1, 2024 by NokSueCow Quote Link to comment Share on other sites More sharing options...
FrostyMaGee Posted June 1, 2024 Report Share Posted June 1, 2024 19 minutes ago, NokSueCow said: Does your bios have LBA48 support? I would format the hdd in FatXplorer and see what happens after that. From his post on a related thread he’s got an ER on that partition. My guess is that somehow it used the wrong cluster size or something else went slightly awry in the process. Happens sometimes at random. It’s happened to me enough that I check partitions in xbpartitioner every time before I start copying data. Lol Quote Link to comment Share on other sites More sharing options...
evilmurdoc Posted June 1, 2024 Author Report Share Posted June 1, 2024 12 hours ago, NokSueCow said: Does your bios have LBA48 support? I would format the hdd in FatXplorer and see what happens after that. So funny you mentioned that. I don't know what I was doing but I came across the below error. Not sure how to update the BIOS. I didn't see anything on the HeXen CD. Quote Link to comment Share on other sites More sharing options...
evilmurdoc Posted June 1, 2024 Author Report Share Posted June 1, 2024 11 hours ago, FrostyMaGee said: From his post on a related thread he’s got an ER on that partition. My guess is that somehow it used the wrong cluster size or something else went slightly awry in the process. Happens sometimes at random. It’s happened to me enough that I check partitions in xbpartitioner every time before I start copying data. Lol Okay I also noticed the cluster size. I believe when I was originally setting up I saw 16KB and then the second time around I saw 64KB. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.