Jump to content
OGXbox.com

Boot the XboxHDM version of XBoxHDM23USB on real hardware?


 Share

Recommended Posts

I want to copy large amounts of data from one Xbox OG HDD directly to another by connecting them both on a PC with two P-ATA channels.

With the older XboxHDM 1.9 and 2.2a (which are essentially Linux distro's supporting FATx booted from CD) I can mount the F-partition of both drives using "mount -t fatx /dev/hda55 /media/source" & "mount -t fatx /dev/hdc55 /media/dest". But the problem is that these versions show corrupted file names.

But with XboxHDM23USB all the file names are correct. I can even use both of my drives if I launch it manually. But because it's running in QEMU the copying is very slow 😔

Now the FATx driver is in the kernel and 1.9 and 2.2a uses the same kernel. Only 2.3USB has a newer kernel, maybe that's where the problem is. So I wanted to boot this 2.3USB version on real hardware.

I took the "kernel" and "initrd.gz" and tried booting it using ISOLINUX and PXELINUX, but it just stuck at "Uncompressing Linux... Ok, booting the kernel.".

How can I make the kernel and initrd.gz from XBoxHDM23USB booting on real hardware?

 

With 1.9 and 2.2a on real hardware all filenames are corrupted:
spacer.png


With 2.3USB it works, but is very slow because it runs in QEMU:
spacer.png

spacer.png

 

But I can't get the 2.3USB version to boot on real hardware using ISOLINUX of PXELINUX:
spacer.png

Link to comment
Share on other sites

45 minutes ago, Megoosa said:

I want to copy large amounts of data from one Xbox OG HDD directly to another by connecting them both on a PC with two P-ATA channels.

With the older XboxHDM 1.9 and 2.2a (which are essentially Linux distro's supporting FATx booted from CD) I can mount the F-partition of both drives using "mount -t fatx /dev/hda55 /media/source" & "mount -t fatx /dev/hdc55 /media/dest". But the problem is that these versions show corrupted file names.

But with XboxHDM23USB all the file names are correct. I can even use both of my drives if I launch it manually. But because it's running in QEMU the copying is very slow 😔

Now the FATx driver is in the kernel and 1.9 and 2.2a uses the same kernel. Only 2.3USB has a newer kernel, maybe that's where the problem is. So I wanted to boot this 2.3USB version on real hardware.

I took the "kernel" and "initrd.gz" and tried booting it using ISOLINUX and PXELINUX, but it just stuck at "Uncompressing Linux... Ok, booting the kernel.".

How can I make the kernel and initrd.gz from XBoxHDM23USB booting on real hardware?

 

With 1.9 and 2.2a on real hardware all filenames are corrupted:
spacer.png


With 2.3USB it works, but is very slow because it runs in QEMU:
spacer.png

spacer.png

 

But I can't get the 2.3USB version to boot on real hardware using ISOLINUX of PXELINUX:
spacer.png

One word for you.... 

FATXPLORER. 

That app will let you mount XBox drives directly in windows if they are unlocked OR you can supply the eeprom or hdd key from the console. 

https://fatxplorer.eaton-works.com/

This is the go to way to manage xbox hdd's in 2025. Make a QOL change and start using it :)

Link to comment
Share on other sites

19 minutes ago, nikeymikey said:

One word for you.... 

FATXPLORER. 

That app will let you mount XBox drives directly in windows if they are unlocked OR you can supply the eeprom or hdd key from the console. 

https://fatxplorer.eaton-works.com/

This is the go to way to manage xbox hdd's in 2025. Make a QOL change and start using it :)

I don't want to use FatXplorer because it only supports Windows 10 and newer. I'm a Linux user.

Also, PC's I have with two P-ATA channels are too old to run Windows 10. Connecting it with a USB-PATA adapter would require 2 sets of adapters and my PC's only have USB2.0, which is slower then native P-ATA.

I found this too, but compiling it on Debian 10, it skips some parts, ending without the fatxfs executable for mounting...
https://github.com/mborgerson/fatx

 

Edited by Megoosa
Link to comment
Share on other sites

4 minutes ago, Megoosa said:

I don't want to use FatXplorer because it only supports Windows 10 and newer. I'm a Linux user.

Also, PC's I have with two P-ATA channels are too old to run Windows 10. Connecting it with a USB-PATA adapter would require 2 sets of adapters and my PC's only have USB2.0, which is slower then native P-ATA.

I found this too, but compiling it on Debian 10, it skips some parts, ending without the fatxfs executable for mounting...
https://github.com/mborgerson/fatx

 

Ah well ok... If you insist on using Linux then you are out of luck and will have to stick with the old hacky XBHDM etc. Surely you could just borrow a windows pc with a couple of vacant SATA ports and get the job done super quick. If you had windows you would be done and dusted and moved on to your next project by now.... just saying ;)

Link to comment
Share on other sites

49 minutes ago, nikeymikey said:

Ah well ok... If you insist on using Linux then you are out of luck and will have to stick with the old hacky XBHDM etc. Surely you could just borrow a windows pc with a couple of vacant SATA ports and get the job done super quick. If you had windows you would be done and dusted and moved on to your next project by now.... just saying ;)

My hard drives are P-ATA, not S-ATA. There are not much Windows 10 PC's with two P-ATA channels.

Link to comment
Share on other sites

Where can I borrow a Windows 10 PC with two P-ATA channels? How many of those exist?

I have a lot of PC's and the fastest one with 2 P-ATA channels is a Pentium 4 socket 478 with 2GB RAM. Definitely too slow to run Windows 10.

My Core2Duo and Athlon II systems only have 1 P-ATA channel. And the Core i5's have none.

Link to comment
Share on other sites

I only have one set of P-ATA to USB2.0 interface. And I have a Promise Ultra133 TX2 PCI card with 2 P-ATA channels, but not supported in Windows 10.

If the only option is to install Windows 10 and buy another adapter set, I'll use the slow FTP method instead...

I don't really like the idea to need modern tech/equipment to do something for a classic console. Something as little as file transferring. Also, I don't like modern tech (like modern PC's/phones/consoles/cars) at all.

 

Link to comment
Share on other sites

1 hour ago, Kalpi said:

Ide to usb adapters exist, as do ide to sata boards. As do PCI or pcie to ide. Mountain out of a molehill here.

>Core i5

There you go, fire 10 on to that and get some usb adapters

Exactly what I was going to say. 

9 minutes ago, Megoosa said:

I only have one set of P-ATA to USB2.0 interface. And I have a Promise Ultra133 TX2 PCI card with 2 P-ATA channels, but not supported in Windows 10.

If the only option is to install Windows 10 and buy another adapter set, I'll use the slow FTP method instead...

I don't really like the idea to need modern tech/equipment to do something for a classic console. Something as little as file transferring. Also, I don't like modern tech (like modern PC's/phones/consoles/cars) at all.

 

Oh well. You asked for help and you have been advised the absolute best way to do what you are trying to do in 2025. If you don't want to take that option and get the job done in less than half the time it then that's your choice. Seems like you are cutting your nose off to spite your face. 

Link to comment
Share on other sites

On 1/21/2025 at 9:28 AM, Megoosa said:

With the older XboxHDM 1.9 and 2.2a (which are essentially Linux distro's supporting FATx booted from CD) I can mount the F-partition of both drives using "mount -t fatx /dev/hda55 /media/source" & "mount -t fatx /dev/hdc55 /media/dest". But the problem is that these versions show corrupted file names.

What size is the F partition on the drive(s)?  The older kernel most likely only supports LBA28 - max hard drive size of 137GBs, not the newer LBA48 patch - more like LBA32 - not full LBA48 support.

Link to comment
Share on other sites

1 hour ago, KaosEngineer said:

What size is the F partition on the drive(s)?  The older kernel most likely only supports LBA28 - max hard drive size of 137GBs, not the newer LBA48 patch - more like LBA32 - not full LBA48 support.

The source drive with the games is 80GB so the F is around 70GB.

The destination drive is 250GB and when mounted "df -h" showed the right amount of space.

But even with only the 80GB connected, all the file names and directory structure are corrupted with the older version.

Link to comment
Share on other sites

8 hours ago, Megoosa said:

The source drive with the games is 80GB so the F is around 70GB.

The destination drive is 250GB and when mounted "df -h" showed the right amount of space.

But even with only the 80GB connected, all the file names and directory structure are corrupted with the older version.

Strange.

 

I've removed your duplicate edited post.

Link to comment
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
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
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.

 Share

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.