Hey everyone, new user and modder so I apologise if Im posting in the wrong place or doing something stupid or whatever but Im hoping someone's run into this before because I'm at a dead end.
Got a Xbox 360 Slim, RGH'd, running Aurora (0.7b.2) with DashLaunch 3.21. It came pre-modded like this with a 250GB drive and it's been working flawlessly - 224GB used, boots straight into Aurora every time. No complaints with the original setup at all.
Only issue is I want more space, so I've tried upgrading twice now and hit the exact same wall both times.
First I tried a Lexar NS100 SSD (checked it was on the FATXplorer compatibility list), then when that didn't work I tried a Seagate 1TB 2.5" HDD instead. Same result both times: format the new drive, copy all the content across from the original, pop it into the console internally, and it boots to the standard dashboard instead of Aurora. Storage menu shows it as 0KB free despite having copied roughly 224GB onto it.
Things I've already ruled out (or at least tried to):
Initially I copied everything via FATXplorer by mounting the original, copying to desktop, then mounting the new drive and pasting from the desktop. Got the 0KB/standard dash result from that.
I went back into FATXplorer itself (not just Windows Explorer) and checked the new drive properly - both partitions mount without any errors, correct amount of used space shows up, files are genuinely all there. This came back totally clean on the Seagate, no issues at all
Also double checked the root of the drive, the Aurora 0.7b.2 folder is there with Aurora.xex inside, and it matches exactly what's specified in launch.ini's Default= line. launch.ini itself looks fine too, standard DashLaunch 3.21 config, nothing corrupted that I can see.
Someone also mentioned the extra partitions (System Extended/Auxiliary) that show on the original but not on a fresh format are apparently just generated later by a system update, so that's supposedly a non-issue.
Last thing I tried was the console's own Storage > Transfer Content feature instead of going through FATXplorer at all. Hooked the original drive up via USB-SATA adapter as the source (since it's already occupying the internal bay) and picked the new Seagate as destination. But it got stuck asking me to "Configure Device" with a warning that only 32GB would be usable and the rest would be wasted. Looked like it was trying to format it as USB storage rather than a proper internal drive, so I backed out rather than risk capping it.
So basically: has anyone actually managed a straight internal-to-internal upgrade on an RGH Slim without hitting this? Is there an actual known method that works reliably for this (FATXplorer settings I'm missing, XeXMenu, FTP through Aurora, whatever) or is "boots to standard dash + shows 0KB" a symptom of something specific that I'm just not seeing?
Can post screenshots if that helps. Trying to be careful not to mess with the original drive since it's still my only working copy right now.
Got a Xbox 360 Slim, RGH'd, running Aurora (0.7b.2) with DashLaunch 3.21. It came pre-modded like this with a 250GB drive and it's been working flawlessly - 224GB used, boots straight into Aurora every time. No complaints with the original setup at all.
Only issue is I want more space, so I've tried upgrading twice now and hit the exact same wall both times.
First I tried a Lexar NS100 SSD (checked it was on the FATXplorer compatibility list), then when that didn't work I tried a Seagate 1TB 2.5" HDD instead. Same result both times: format the new drive, copy all the content across from the original, pop it into the console internally, and it boots to the standard dashboard instead of Aurora. Storage menu shows it as 0KB free despite having copied roughly 224GB onto it.
Things I've already ruled out (or at least tried to):
Initially I copied everything via FATXplorer by mounting the original, copying to desktop, then mounting the new drive and pasting from the desktop. Got the 0KB/standard dash result from that.
I went back into FATXplorer itself (not just Windows Explorer) and checked the new drive properly - both partitions mount without any errors, correct amount of used space shows up, files are genuinely all there. This came back totally clean on the Seagate, no issues at all
Also double checked the root of the drive, the Aurora 0.7b.2 folder is there with Aurora.xex inside, and it matches exactly what's specified in launch.ini's Default= line. launch.ini itself looks fine too, standard DashLaunch 3.21 config, nothing corrupted that I can see.
Someone also mentioned the extra partitions (System Extended/Auxiliary) that show on the original but not on a fresh format are apparently just generated later by a system update, so that's supposedly a non-issue.
Last thing I tried was the console's own Storage > Transfer Content feature instead of going through FATXplorer at all. Hooked the original drive up via USB-SATA adapter as the source (since it's already occupying the internal bay) and picked the new Seagate as destination. But it got stuck asking me to "Configure Device" with a warning that only 32GB would be usable and the rest would be wasted. Looked like it was trying to format it as USB storage rather than a proper internal drive, so I backed out rather than risk capping it.
So basically: has anyone actually managed a straight internal-to-internal upgrade on an RGH Slim without hitting this? Is there an actual known method that works reliably for this (FATXplorer settings I'm missing, XeXMenu, FTP through Aurora, whatever) or is "boots to standard dash + shows 0KB" a symptom of something specific that I'm just not seeing?
Can post screenshots if that helps. Trying to be careful not to mess with the original drive since it's still my only working copy right now.
