On 30 Jan 2004 02:02:31 -0800,
(E-Mail Removed) (dandandan) wrote:
>Rod,
>
>Thanks for your advice.
>
>I ran findpart. It didn't work.
>
>One line of output was writen to the screen immediately:
>
>Disk: 2
>Cylinders: 9964
>Heads: 255
>Sectors: 63
>MB: 78160
>
>Then, there was a long pause. The hard drive was spinning at a
>constant rate but nothing else happened. I went out and came back 5
>hours later and it was the same so I switched the computer off.
>
>Anyway, the disk was set up in the simplest way - just the one
>partition.
>
>I think the problem is that the NAV restored an old mbr (presumanbly
>restored from an NAV folder?) and this was for my old 6gb drive not
>the new 80gb drive. When NAV recognised that the mbr had changed (of
>course it had, i had changed the hard drive), it suggested it could be
>due to virus activity and as I suspected a virus anyway i leapt in
>there without thinking... Of course the restored mbr didn't know what
>the 80gb drive was so it could not boot. So then it tried to boot to
>the floppy, the CD etc until eventually it booted from the old mbr on
>the D: drive (the old 6GB drive). So today I have a situation where
>the 6gb drive is C: and the 80gb drive id d:. The directory of files
>on D: shows nothing and the OS incorrectly recognises d: this also as
>a 6gb drive.
>
>I have ordered a new 80gb (exact same model) and I will get it
>formatted in exactly the same way as mine was. Hopefully this will
>give me the correct mbr for my 80gb drive. Am I talking sense here?
>
>Thanks
You can do this:
findpart tables fp-a.txt
and insert (not attach) the output here. This will only print the
partition tables.
If only the MBR is damaged, a finding from the boot sector of the
first (and in this case only) partition, should be shown immediately.
It is difficult to say how long time a full search without findings
will take, but it should be less than 5 minutes for a 78160 MB disk
before a message "None found" is printed. After that a FAT search will
be run.
If the partition is an NTFS partition, and the boot sector damaged,
and the original geometry was another, Findpart will not find the NTFS
backup boot sector, which is in the very last sector of the partition.
You can do:
findpart 2 heads 240 fp-b.txt.
and give this 7 minutes:
findpart 2 fp-c.txt
If the partition was a FAT partition, you can do:
findpart findfat 2 0 4 fp-d.txt
Findpart can be interrupted with Ctrl-break. If it should be the case
that bad sectors are present, that will delay or stop the search.
It is unlikely that copying a MBR from another disk will recover a
partition, which Findpart cannot find, since then the partition itself
is damaged. The method should be to figure out what happened, or copy
data to another disk using recovery tools.
--
Svend Olaf