moving (and losing?) partitions with cfdisk
Ok, I've drawn a map of your disc, both presumed before and
after, and I think I know what cfdisk did.
Before you did anything, you had either three or four
entries in your PT, it's hard to tell, as cfdisk is
not actually showing your PT. But anyway, you had
Primary Bootable Win95 FAT32 (hda1)
Primary Bootable Linux ext3 (hda2) /
Extended
Inside the extended you had two logical partitions
(*) Linux swap (hda6)
(*) Linux ext3 (hda5) /home
What happened is that the extended partition got it's
bottom end moved down, from the bottom of what was hda5
to the beginning of the disc, and two more partitions
were created inside the new extended partition space.
Nothing of the original partitions got copied or moved.
There should have been no need to overwrite anything in
any of the existing partitions. Ok. The first sector of
each partition inside a logical partition contains its
"geometry" (BPB). Creating partitions causes writes to
the beginnings of new partitions. But I don't see any
need to write to the beginning of partitions clobbering
anything in the middle of the existing partitions. (This
geometry stuff is why I mentioned saving the first sector
of each partition. Your grub update overwrote the first
sector, possibly, of one of the partitions.)
Do you have GRUB installed into the MBR? I guess so.
Your new setup looks like it preserves all the old
partitions intact, just expanded the extended.
So it looks like the names of the partitions are:
New Old Type
=== === ====
hda1 hda1 Win95
hda2 hda2 ext3 (/)
hda5 ----
hda6 ----
hda7 hda5 ext3 (/home)
hda8 hda6 swap
Hmm. I can't see anything wrong. That partition should not have
been touched at all. I don't see that anything needed to be
written except to these disc addresses
0 new PT
63 geometry of new logical partition
9184517 geometry of new logical partition
I don't see why any other writes needed to be done.
Even if the grub update overwrote one of the partition
beginnings, it shouldn't clobber the FS, since the FS
should be *after* GRUB.
Hmm. I'm going to have to ponder, but I can't explain
why you have problems with the mount. Have you tried
a direct mount, not using the fstab entry? Possibly
the fstab is messed up. What is in there now?
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
Reply to: