Doug, That was linux fdisk I was talking about. It only shows the windows partition. sfdisk -l shows four partitions - one windows, and three empty ones, with no start or end cylinders. I'm not sure what that's about. Here's the output for fdisk and sfdisk when that drive is hooked up as slave: fdisk -l Device Boot Start End Blocks Id System /dev/hdb1 * 1 1123 9020466 c Win95 FAT32 (LBA) sfdisk -l Disk /dev/hdb: 1123 cylinders, 255 heads, 63 sectors/track Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls #blocks Id System /dev/hdb1 * 0+ 1122 1123- 9020466 c Win95 FAT32 (LBA) /dev/hdb2 0 - 0 0 0 Empty /dev/hdb3 0 - 0 0 0 Empty /dev/hdb4 0 - 0 0 0 Empty Here's what I tried. I went into yast2 partitioning tool, setup the drive the way I did the first time, wrote down the cylinder numbers, then hit ABORT, so it wouldn't write to the disk. Then ran "parted -i /dev/hdb", then used the cylinder numbers for the "rescue partitions near START and END" function. It scanned, returned no errors, and made no changes. I don't get it, and I'm out of ideas for now. OK, one more idea. Can I use the partition tool to set the partitions again without formatting them, and then be able to access them? Thanks for all your help, Greg doug waud wrote:
Hi again
Gregory Avedissian wrote:
Hi Doug,
I tried fdisk /mbr and it worked easily. As expected, I only have a windows partition (verified by fdisk). I suspect that I'm less than halfway there.
I'm glad you finally tried that! At least the easy part is taken care of so you can now focus on a smaller problem.
I admit to some guessing here, but I would suggest you try both the Windows fdisk (just because I am a bit anal; I don't expect it to know about the linux partitions) and the Linux fdisk. (You may have done this but I can't tell since you say just "fdisk".)
However, once that is working, you can boot into your linux system (by one of the ways I mentioned in an earlier post, and run LILO which is smart enough to leave the Windows part working and simply add the stuff for other things you want to boot (as specified in lilo.conf --- which I assume is OK if it was working earlier and you have not edited it).
No, there's no lilo.conf and never was one on that installation.
Oops! Sorry about that; I misread an earlier email. :-(
There is (was) a grub/menu.lst, which serves the same function, but as far as I understand it, the partition table needs to contain information about linux partitions for either of these to work.
I suspect that is true (can't recall off hand). If so, then remember to pray when you run the Linux fdisk! :-
And do run the linux fdisk, i.e. fdisk /dev/hda and then chose option p (as in *P*rint the partition table. If you get a nice listing, then don't screw around with parted!
I went ahead and booted the rescue system and tried a grub-install /dev/hda, and it returned a message saying that no /dev/root was found.
Maybe I'll try parted again, now that I can find where hda1 ends.
But do try both Windows fdisk and Linux fdisk (with the P option) first!
doug
_______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug