B*gger its got the partition table

  • Thread starter Thread starter David Lindsay
  • Start date Start date
D

David Lindsay

I have just got a virus (Baphometh) thats hit the partition table. This
stops the disk from booting. Whats the best way to clean the partition
table so I can re-boot the machine?

Thanks.
 
David said:
I have just got a virus (Baphometh) thats hit the partition table. This
stops the disk from booting. Whats the best way to clean the partition
table so I can re-boot the machine?

baphometh alone shouldn't stop the machine from booting, however if you
tried to remove it using fdisk /mbr that will render the disk
unbootable as the partition table (the real one) is no longer where
it's supposed to be... if that's what you've done you might want to
look here http://vil.nai.com/vil/content/v_10250.htm to see what all
the virus has done and maybe get some ideas on how to recover...
otherwise i suggest you try using the av that identified the virus to
remove the virus... you did create recovery boot disks for that
product, did you not?
 
kurt wismer said:
baphometh alone shouldn't stop the machine from booting, however if you
tried to remove it using fdisk /mbr that will render the disk
unbootable as the partition table (the real one) is no longer where
it's supposed to be... if that's what you've done you might want to
look here http://vil.nai.com/vil/content/v_10250.htm to see what all
the virus has done and maybe get some ideas on how to recover...
otherwise i suggest you try using the av that identified the virus to
remove the virus... you did create recovery boot disks for that
product, did you not?

Thanks for the reference. Now I have started writing a copy of the boot
record on the c disk just in case (with backups of course)
I do have boot disks, avast found it but failed to remove it,
unfortunately. In fact I found avast totally useless at virus removal.
 
Useless info, in Baphomet's case.
to see what all

And if he didn't, then what? Lose the drive's content?
Thanks for the reference. Now I have started writing a copy of the boot
record on the c disk just in case (with backups of course)
I do have boot disks, avast found it but failed to remove it,
unfortunately. In fact I found avast totally useless at virus removal.

Boot virus damage should ALWAYS be addressed as disk/disaster recovery. You
don't mention under what OS your system runs, but from losing boot ability,
seems that the real damage was caused by whatever you used to attempt removing
the virus, especially AV.

Read the thread below, it explains why you should avoid AV when dealing with
boot infectors in general, and Baphomet in particular:
http://groups.google.com/groups?&[email protected]

If you haven't reformatted the drive yet, then you may restore boot ability and
recover the content of the drive by aid of RESQDISK, from www.invircible.com.
All you need is to pick the original (uninfected) MBR from sector 0/0/2 (CHS
notation) and rewrite it to 0/0/1.

RESQDISK is free for the above purpose.

Regards, Zvi
 
Zvi Netiv said:
If you haven't reformatted the drive yet, then you may restore boot ability and
recover the content of the drive by aid of RESQDISK, from www.invircible.com.
All you need is to pick the original (uninfected) MBR from sector 0/0/2 (CHS
notation) and rewrite it to 0/0/1.

RESQDISK is free for the above purpose.
Thanks Zvi very useful info. I appreciate your help.
 
Zvi said:
Useless info, in Baphomet's case.

did you actually read the page in question, zvi? or is that a boiler
plate response driven by an "i know better than anyone when it comes to
bsi's" attitude?

the page describes where (which sector) the original mbr can be found -
hardly useless info...
And if he didn't, then what? Lose the drive's content?

no, if he didn't then he should try to find a clean system on which to
make some... my interpretation of his response was that that won't be
necessary, however...
 
kurt wismer said:
did you actually read the page in question, zvi?

Yes, I read the page before posting and maintain my statement: accurate and
useless.
the page describes where (which sector) the original mbr can be found -
hardly useless info...

It suggests no means or method to restore the MBR. Moreover, that particular
info drowns in noise ...

My guess is that what caused the problem is something of the sort you advised,
i.e. trying to get rid of the virus with AV.
no, if he didn't then he should try to find a clean system on which to
make some...

Some what? Make AV recovery boot disks? On a different system? Do you realize
how bad that advice is?
my interpretation of his response was that that won't be
necessary, however...

Why? Since Baphomet modifies the MBR's partition table, and he also lost boot
ability, then the only conclusion is that he ruptured the boot chain and is
stuck with a ruined partition table. You offered no useful advice how to
recover from that.

Regards, Zvi
 
Zvi said:
Yes, I read the page before posting and maintain my statement: accurate and
useless.

we seem to be in disagreement over the nature of usefulness...
It suggests no means or method to restore the MBR. Moreover, that particular
info drowns in noise ...

i see... so if it's not a panacea, if it doesn't answer *all* the
questions, it is useless in your opinion...

[snip]
My guess is that what caused the problem is something of the sort you advised,
i.e. trying to get rid of the virus with AV.

and my guess is that it was more likely the generic (and wrong) 'fdisk
/mbr cleans bootsector viruses' advice...
Some what? Make AV recovery boot disks? On a different system? Do you realize
how bad that advice is?

what i realize is that you like to express the opinion that
conventional anti-virus products can never do a good job at removing
boot sector infectors, and do an especially bad job at removing those
that relocate the partition table...

do you realize that you have never convinced me that the aforementioned
opinion is an accurate representation of reality? you've never put
forward a compelling explanation for the supposed impotence you charge
conventional av's with...

av vendors being a competitive sort, and mbrs relocated by *known*
viruses being easy to find after a successful clean boot, you'd think
that if there was mass impotence in the industry at any time then each
of those vendors would be falling over each other trying to solve their
problem and thereby gain a competitive advantage over the rest... did
they all fail? were they all idiots? did they collectively decide to
not compete with each other over such a feature? i'm sorry but somehow
it just does not ring true...

the text
"I do have boot disks, avast found it but failed to remove it,
unfortunately."

suggests that making recover boot disks for his av have already been
done so he won't have to go and find a clean system on which to make
some...
Since Baphomet modifies the MBR's partition table, and he also lost boot
ability, then the only conclusion is that he ruptured the boot chain and is
stuck with a ruined partition table. You offered no useful advice how to
recover from that.

the text

"Thanks for the reference. Now I have started writing a copy of the
boot record on the c disk just in case (with backups of course)"

suggests that he is, in fact, capable of reading and manipulating the
sectors in question...
 
kurt wismer said:
[snip]
It suggests no means or method to restore the MBR. Moreover, that particular
info drowns in noise ...

i see... so if it's not a panacea, if it doesn't answer *all* the
questions, it is useless in your opinion...

The reference is useless because of the opposite, as it doesn't answer the only
question that matters: How to recover the lost partition and boot ability.
[snip]
My guess is that what caused the problem is something of the sort you advised,
i.e. trying to get rid of the virus with AV.

and my guess is that it was more likely the generic (and wrong) 'fdisk
/mbr cleans bootsector viruses' advice...

This is a possibility too in Baphomet's case, although I don't think that this
is what happened, since the OP didn't mention FDISK, but he mentions having
tried AV. Besides, you twist things: I don't recommend FDISK /MBR as a
standard solution to BSI (and certainly didn't recommend it here, although you
make it sound as if I did), FDISK is far from being a panacea, and FDISK /MBR
isn't part of InVircible, although you make it sound like it is. ;)
what i realize is that you like to express the opinion that
conventional anti-virus products can never do a good job at removing
boot sector infectors, and do an especially bad job at removing those
that relocate the partition table...

I realize the Pavlovian conditioning in regard of FDISK /MBR and boot infectors,
regardless of the circumstances, and whether relevant to the case or not. ;-)
do you realize that you have never convinced me that the aforementioned
opinion is an accurate representation of reality? you've never put
forward a compelling explanation for the supposed impotence you charge
conventional av's with...

I realize that your ideas haven't progressed a bit since FIDONET. ;) Quite
fossilized and formalistic ones for such a young fellow.
av vendors being a competitive sort, and mbrs relocated by *known*
viruses being easy to find after a successful clean boot, you'd think
that if there was mass impotence in the industry at any time then each
of those vendors would be falling over each other trying to solve their
problem and thereby gain a competitive advantage over the rest... did
they all fail? were they all idiots? did they collectively decide to
not compete with each other over such a feature? i'm sorry but somehow
it just does not ring true...

Attempting the removal of boot infectors with conventional AV is like playing
Russian roulette, as sometimes is FDISK /MBR. Whether you like it or not, FDISK
/MBR has higher success scores when dealing with boot infectors compared to AV,
while the latter has killed far more drives in the process. Deal with that.
Besides, I am no partisan of FDISK /MBR either. ;)

As to why that is, the simple answer is that AV products aren't tested, nor
certified, for properly fixing virus damage, only on detection and mostly on
*correct identification* in virus zoo tests. That simple! Fact that the AV
that David used identified Baphomet, but (probably) screwed up on its removal.

[snip]
the text

"Thanks for the reference. Now I have started writing a copy of the
boot record on the c disk just in case (with backups of course)"

suggests that he is, in fact, capable of reading and manipulating the
sectors in question...

It doesn't suggest anything of the sort. If anything at all, the above suggests
that the poster is clueless and could use some real help. As an old timer here
you should know that "writing to C" does not imply that he can access sector
0/0/2 which is outside the reach of the OS, and that backing up the boot
record(s) to C is like writing on ice, as the C drive won't be accessible with a
corrupted boot chain.

Regards, Zvi
 
I realize that your ideas haven't progressed a bit since FIDONET. ;) Quite
fossilized and formalistic ones for such a young fellow.

Zvi, Reading this article makes me think you've been taking courses
in diplomacy! Are you planning to go into politics?

Regards, Dave Hodgins
 
Zvi said:
The reference is useless because of the opposite, as it doesn't answer the only
question that matters: How to recover the lost partition and boot ability.

clearly the idea of breaking a difficult problem into smaller simpler
problems - and conversely building up an answer to a difficult problem
from the answers to simpler sub-problems - is something you don't
ascribe to...
[snip]
My guess is that what caused the problem is something of the sort you advised,
i.e. trying to get rid of the virus with AV.

and my guess is that it was more likely the generic (and wrong) 'fdisk
/mbr cleans bootsector viruses' advice...

This is a possibility too in Baphomet's case, although I don't think that this
is what happened, since the OP didn't mention FDISK, but he mentions having
tried AV.

it wouldn't be the first time someone brought a virus problem to the
group without listing (or in some cases even having) a complete set of
the procedures attempted so far...
Besides, you twist things: I don't recommend FDISK /MBR as a
standard solution to BSI (and certainly didn't recommend it here, although you
make it sound as if I did), FDISK is far from being a panacea, and FDISK /MBR
isn't part of InVircible, although you make it sound like it is. ;)

?? maybe it's an issue of english not being your native tongue, but i
made no reference to your product nor your advice... i fail to see
where you're drawing these inferences...

the generic and wrong 'fdisk /mbr cleans boot sector viruses' advice is
in reference to the generic and wrong advice that has been floating
around the internet and other forums for as long as i can remember...
part of the background noise of bad advice, if you will... any
long-standing participant in av forums should be able to remember a
variety of instances when the advice has popped up - it's why there's a
section in the alt.comp.virus faq against warning against fdisk /mbr...

[snip]
I realize that your ideas haven't progressed a bit since FIDONET. ;) Quite
fossilized and formalistic ones for such a young fellow.

well, you know what opinions are like, don't you...
Attempting the removal of boot infectors with conventional AV is like playing
Russian roulette, as sometimes is FDISK /MBR. Whether you like it or not, FDISK
/MBR has higher success scores when dealing with boot infectors compared to AV,
while the latter has killed far more drives in the process. Deal with that.

deal with what? an assertion with no supporting evidence? should i take
your word as an authority in spite of your vested interest?

there are voluminous examples of conventional av's removing bsi's
properly archived for posterity by google groups...
Besides, I am no partisan of FDISK /MBR either. ;)

never said you were...
As to why that is, the simple answer is that AV products aren't tested, nor
certified, for properly fixing virus damage,

not true... some tests/certifications do involve virus removal... not
vtc or virus bulletin, perhaps, but others do... i seem to recall a
certain someone (whom shall remain nameless) shilling for icsa (i
think) certs. on that very basis...

[snip]
It doesn't suggest anything of the sort. If anything at all, the above suggests
that the poster is clueless and could use some real help. As an old timer here
you should know that "writing to C" does not imply that he can access sector
0/0/2 which is outside the reach of the OS,

he doesn't say he's "writing to C"... in fact he doesn't actually say
where he's writing anything - chalk it up to ambiguous grammar if you
like...

perhaps he didn't express what he's doing as accurately as you would
like... perhaps he does indeed think of physical and logical drives
interchangeably and therefore calls his first physical disk "C"... but
if he's writing a copy of the boot record then he must have read it
from somewhere, and if he can read it from where it is and write it to
where it's supposed to go what more do you want?

at any rate, i've given him the benefit of the doubt (clue-wise) that
you apparently would rather not give him... whatever - to each their own...
 
Back
Top