I'm running Leopard 10.5.8 on my Dual G4 MDD. I have an external USB 1.4 TB hard drive that is partitioned with two 512-GB FAT32 volumes and has, therefore, over 300 GB of space available at the end. I'm trying to create a third partition using fdisk. Here's how the drive shows up as it is now:
I figured out that, allowing for the same gap (65536) between partition 2 and 3 as exists between 1 and 2, the starting address for the third partition should be 2181431356. But here's what I get when I try to edit the third entry in the partition table, first using that calculated value and then using the default (by pressing Return):
At first I thought that the problem was that this version of fdisk couldn't deal with large numbers, but then I tried entering small numbers, including 0, and got the same 'out of range' message.
Does anybody have any idea how to get around this?
BTW, I actually dumped the existing MBR as text using 'fdisk -d' and edited it. I was thinking I could use 'fdisk -r' to load the edited table, but it seems dangerous if I make a mistake. Moreover, I don't even know if it would alter the two existing partitions in any way -- something I definitely don't want to do!
Code:
fdisk: 1> print
Disk: /dev/rdisk3 geometry: -5415437/4/63 [-1364690128 sectors]
Offset: 0 Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: 0B 1023 254 63 - 1023 254 63 [ 33816636 - 1073741824] Win95 FAT-32
2: 0B 0 0 0 - 0 0 0 [1107623996 - 1073741824] Win95 FAT-32
3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unusedI figured out that, allowing for the same gap (65536) between partition 2 and 3 as exists between 1 and 2, the starting address for the third partition should be 2181431356. But here's what I get when I try to edit the third entry in the partition table, first using that calculated value and then using the default (by pressing Return):
Code:
fdisk: 1> edit 3
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
Partition id ('0' to disable) [0 - FF]: [0] (? for help) 0b
Do you wish to edit in CHS mode? [n] n
Partition offset [0 - -1364690128]: [-2113601476] 2181431356
'2147483647' is out of range.
Partition offset [0 - -1364690128]: [-2113601476]
'-2113601476' is out of range.
Partition offset [0 - -1364690128]: [-2113601476]At first I thought that the problem was that this version of fdisk couldn't deal with large numbers, but then I tried entering small numbers, including 0, and got the same 'out of range' message.
Does anybody have any idea how to get around this?
BTW, I actually dumped the existing MBR as text using 'fdisk -d' and edited it. I was thinking I could use 'fdisk -r' to load the edited table, but it seems dangerous if I make a mistake. Moreover, I don't even know if it would alter the two existing partitions in any way -- something I definitely don't want to do!