Todd Walton wrote: > Something definitely strange has happened to me. I recently had > occasion to install a new operating system. This finicky operating > system insisted on being in the first partition of the first disk, but > the partition was way too small. So I deleted the first three > partitions, and then created a new single partition in their place. > Now my partitioning is hda1, 2 (extended), and then 5 through 9. > > But I now find a problem that I believe is related to this. My > partition 9 is out of place. Here's what the table looks like now: > > hda1 0000 - 8025 > hda2 8026 - 30401 [ extended ] > hda5 9850 - 9971 > hda6 9972 - blah > hda7 blah - 25775 > hda8 25776 - 30401 > hda9 8026 - 9849 > > So, "hda9" should really be "hda5", and then 5 through 8 should be > moved up one to become 6 through 9. Could my condensing the first > three have caused this? And regardless of what caused it, is there a > way to fix it?
It's possible you need do nothing (except possibly for fixing up boot loaders and fstabs, etc). The out-of-order partition table entries will cause warnings whenever you use fdisk, but otherwise may work just fine. IMPORTANT: if you do want to get it back to a /normal/ ordering, you probably want to be sure to work with sector-based partition boundaries rather than blocks or cylinders. fdisk -lu will list partition end-points in units of sectors, and the u command within interactive fdisk will also set those units to sectors. In any experimenting, you may wish to avoid booting to any version of Windows until/unless you convince yourself that it won't go _fixing_ things up for you. A reference on Windows partition diddling (including boot.ini fixing, IIRC), that may be worth reading is http://linux.coconia.net/copyingXP.htm ..jim -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
