Looks like it's working:
Not sure why Linux partition names and Xbox partition numbers are so out of sync in their naming convention. Why part50 for partition 1? Why not part01 for partition 1? Although a lot of Linux/C programming array offsets start with 0 for the first element, why 50 not 0?
PartName - Drive Letter - Size (in bytes) - Cluster Size (in bytes) - Xbox Partition Number - Use
part50 – E: - 5,120,024,576 - 16,384 - 1 - Game Saves, Ripped Music [WMA] (DATA)
part51 – C: - 524,288,000 - 16,384 - 2 - System Software (DASHBOARD)
part52 – X: - 786,432,000 - 16,384 - 3 - Game data cache 1
part53 – Y: - 786,432,000 - 16,384 - 4 - Game data cache 2
part54 – Z: - 786,432,000 - 16,384 - 5 - Game data cache 3
(would be nice if one could create tables in messages!)
For software development, partition access is performed via the device name of a particular hard drive partition: \Device\Harddisk0\Partition[Xbox Partition Number 1-7].
\Device\Harddisk0\Partition1, \Device\Harddisk0\Partition2, etc. which can be mapped to a drive letter same as Windows NT which the Xbox OS (Kernel/BIOS) is based upon.
Two more partitions left to format, currently:
part55 – F: - 996,197,400,576 - 65,536 - 6 - Extended Storage
being formatted that’s 996GBs, then
part56 – G: - 996,197,400,576 - 65,536 - 7 - Extended Storage
should be created once F: finishes.
The F and G partitions are going to take some time to be created. Each ~195 times longer than part50, E:, took.