Tanmoy said:
Thanks for your support. I feel this is a tech group and one should not
be too much bothered with minor grammatical mistakes.
Yes, that is the easy way out. My post that apart from the typo addresses
the context of the typo plus the usability of sudhlog.dat you did not
answer:
Tanmoy said:
That was a typographical mistake. I guess everyone could make out its
not rott but root. Regarding the issue of Partition locations, agreed
its known but how does a layman restore it? assuming he/she does not
know how to edit physical sectors manually. Moreover the structrure of
Boot Record is not known, so I asked for the SUHDLOG.DAT file.
Hi.
Yes, you are right, it's just, we see here (this thread) a living example of
what could happen if you're not exact and to the point with the instructions
you give. And in that light, not even getting a simple thing as a filename
right doesn't add to the confidence. Yes indeed the bootrecord appears to be
lost, and I very much doubt if that's the only component that's damaged; the
partition table EPBR was trashed, the boot sector as well, no FAT was found
so part of the first FAT at least is damaged as well. And because of that I
doubt if knowing what the boot sector looked like will do much good. If this
were up to me, I'd try the recover the last logical and recover data from
the first logical partition using a file recovery tool. You could even
redefine the partition to make it a little easier on the tool of your
choice.
As far as I understand the files you refer to are created during setup. If
the partitioning changed since that there's not too much use for those
files. In fact data has been lost more than once because of those files and
the restoration of partition tables and boot sectors from those files.
Because of that I'd never rely on them. IMO it's better to scan a disk,
analyse the results of the scan, and plan and perform interventions based on
at analysis.
Does one know how to use the information as it is presented by Findpart?
Yes, that's the question. Either you know, or you don't. The latter seems to
be the case more frequently, and in those cases 99 out of 100 times Svend
has to come to the rescue. Svend recently indicated that he's slowing down a
bit, or has to slow down a bit, because there's so many requests for help
that he fears he may not be able to maintain the high quality of his
support. Svend has a reputation to keep up ;-). It is also because of this
reputation, so it seems, that people trust him blindly to resolve an issue,
or at least that he knows where and when to stop so it doesn't turn into a
bigger mess. I know what Svend is capable of (as anyone that visits this
group on a regular basis probably). If Svend created a batch file to fix my
disk I'd not have too much trouble running that. No offense intended, but
you I don't know, so that's a bit more difficult. F'Nut (alias Folkert) I do
know and I'd never let him touch my disk, before you know it, you have 'free
space partitions' (don't ask me, only he knows) all over the place.
Anyway ... There are tools available that are able to resolve many of the
issues that can be resolved with the help of Findpart and Svend in a safe
manner. Tools that allow about ordinary users to solve issues even when they
don't know how to edit a disk and without indepth knowledge on partition
table and boot sector structures. Tools that only require the user to select
the correct disk and the partitions that need repair.
If people do not want to use those (often commercial) tools then they either
need to be patient or take some risks. I suggest they first clone the victim
disk or practice on a dummy disk.
