On Thu, 2004-12-02 at 15:11 +1100, Michael Mansour wrote: > > On Thursday 02 December 2004 09:27, Michael Mansour > > wrote: > > > # fdisk -l /dev/sda > > > > > > Disk /dev/sda: 9056 MB, 9056904704 bytes > > > 255 heads, 63 sectors/track, 1101 cylinders > > > Units = cylinders of 16065 * 512 = 8225280 bytes > > > > > > Device Boot Start End Blocks > > Id > > > System > > > /dev/sda1 * 1 13 104391 > > fd > > > Linux raid autodetect > > > /dev/sda2 1037 1101 522112+ > > 82 > > > Linux swap > > > /dev/sda3 14 407 3164805 > > fd > > > Linux raid autodetect > > > /dev/sda4 408 1036 5052442+ > > 5 > > > Extended > > > /dev/sda5 408 774 2947896 > > fd > > > Linux raid autodetect > > > /dev/sda6 775 905 1052226 > > fd > > > Linux raid autodetect > > > /dev/sda7 906 1036 1052226 > > fd > > > Linux raid autodetect > > > > > > Partition table entries are not in disk order ... snip > Either way, I'm still interested to know how to fix > the partition table issue, since this was really the > only issue with the upgrade. > > Michael. fdisk /dev/sda, then enter x for expert mode. Select f to fix partition order, then w to commit changes to disk. You probably want to print (p) the partition table before writing to disk. Before you reboot, you must edit all /etc/fstab, /etc/raidtab entries to point to the correct partition. You will also need to update the (hdx,x) entries in /boot/grub/grub.conf. Once everything is edited, have a rescue CD handy just in case. Kevin Freeman
