🚀 go-pugleaf

In article <5man9d$1c6@sjx-ixn10.ix.netcom.com>,
Hugh McCurdy <hmccurdy@ix.netcom.com> wrote:
>[Posted and mailed]
>
>In article <frobozz-2505971859100001@slbri2p64.ozemail.com.au>,
>	frobozz@ozemail.com.au (Adam Eberbach) writes:
>> I have accidentally repartitioned a hard disk using fdisk and if it's
>> possible I have to reverse the actions. 
>> 
>The trick is going to be figuring out where the old partitions started and
>stopped.  If you know that, you can use *Linux* fdisk to reverse the
>actions and put it back.
>
>I had a virus eat my partition table once.  Since I didn't know much about
>viruses, and since I have a record of my partition layout, I did as I 
>suggested and was back up.
>
>If you don't know where the partition started and stopped, you are going to
>need to look for the parition headers.  I don't remember what they look
>like.  What I'd do, is get a different hard disk and partition it.  Then
>look to see what the headers look like.
>
>Note: when you think you have properly marked a Linux file system, use
>fsck -n (no updates) to see if you really have.  This implies that you have
>a working Linux system loaded to another drive on the computer (or have
>a rescue floppy with fsck).
>-- 
>Hugh McCurdy

I had an interesting adventure with Solaris 2.5.1. The hardware:
PPro 180
64M mem
3.1g EIDE disk
Diamond 3d 2000, 2m video card


I had initially partitioned the disk into 3 separate 1 gig partitions:
two primaries and 1 extended.  The system already had NT on the first
1gig, and linux on the 3rd gig.  I needed to port some software to
Solaris 2.5.1 and proceeded to put it on the 2nd 1gig partition. It turns
out that the out-of-the-box Solaris 2.5.1 for x86 did not 1) handle a
3.1g ide disk properly or 2) support the Diamond 3d 2000 card. I had
to download 8 floppies worth of driver updates. After applying all the
updates I proceeded to run the Solaris equivalent of fdisk to partition
the disk. Being a paranoid sort, I thought it would be a good idea to
boot linux and run linux fdisk to make sure that the Solaris partition
program didn't mess anything up.  Good thing I did that! Solaris
had messed up the partition info (made the Solaris partition overlap
Linux by a little). Fortunately I had written down all the partition
info before I started (and the Linux extended partition had about 6
logical partitions within it). Using fdisk I was able to restore the
linux partition info. I then went back and install Solaris and had no
further problems. So, to reiterate what someone else said: if all you
did was repartition your disk, all the original data is still there --
just repartition to your original configuration.

--peter gross
pag@probita.com