Bitlocker killed my computer - no really!

G

Guest

Well actually I did, but I wouldn't have done without Bitlocker. And its
broke really bad; I suppose that when something is as secure as Bitlocker,
when it breaks its gonna break properly otherwise its not really doing its
job is it. And how properly has it broken it? Well, my computer can no
longer find its hard disk - that's how bad it is.

Here's how it happened...

1) I have Ultimate, so ran the Bitlocker setup (Toshiba M400). During the
process it set up a new drive, "S" with a couple of Gig leaving my "C" drive
with its 78 Gig or there abouts.

2) Ran TPM from the BIOS and switched Bitlocker on, but as per my earlier
topic, couldn't get it to properly work even with the latest BIOS. My
experience was similar to the one found by Daniel Robinson -
http://labs.itweek.co.uk/2006/11/vista_bitlocker.html (even though his is a
Dell)

3) So decided to switch off TPM and Bitlocker, which went fine. Then I went
into a Disk Management Console (found under the Computer Management Console)
and this is where it went horribly wrong.

4) I wanted to reclaim the disk space "S" was taking up, so tried to delete
the volume, but clever computer wouldn't let me because it was the "Active
Partition". So that's easily sorted isn't it, set "C" to the active
partition - no problem - now right click the "S" volume and delete it.
Ignore the little warning that cropped up (okay maybe I should have read it)
click OK, then reboot and now what ...

5) Windows doesn't load. Oh well, that's a nuisance I'll have to reinstall
Vista which is a bit of a pain, because it means reinstalling XP first since
I purchased the upgrade version of Ultimate. Only XP won't find a hard
drive. Now I start to sweat and shake. Put the Vista disk in and ask it to
repair my computer - what's the message? "Err, I can't find a Hard Drive,
are you sure you have one David?" Yes, Yes Yes.

6) I know lets try any of my windows XP disks ... nope none of them can't
find a hard drive.

7) Finally phone one of my senior developers (I'm supposed to be an IT
Manager you know). Listen to him giggle down the phone and hear him mutter
something about lost the master boot record, so perhaps on Monday he can
install Linux so that they can completely trash the hard drive and then we
can start again. About his only hope is that my BIOS can still see an 80 Gig
hard drive so it should be possible.

Oh well that's my weekend pretty much wrecked, and I suppose I'll have to
endure Tablet withdrawal symptoms. Wait a minute ... unless one of you good
people has any idea?

David L.


UPDATE:

Well - 6 hours later (and 3 hours sleep later) and things haven't improved
much.

Someone suggested doing fdisk from DSL Linux, but my lack of knowledge of
all thing Linux, meant that although I managed to boot froma Linux CD as much
as I tried I couldn't get fdisk -l to give me back anything. But then maybe
I hadn't got a root terminal, etc, etc. Of course equally, maybe fdisk
didn't work because the hard drive is well and truly trashed.

So found a couple of bootable CD iso's on the web and felt more comfortable
with these. One is made by LSoft which had a couple of free utilities. One
of these is KillDisk designed to wipe everything from the disk. It did say
that the disk will be still usable but you'd need a utility to create
partitions, format drive etc, etc. using something like fdisk. So left it to
do its work which took a couple of hours.

After that I burned PartitionLogic iso to disk which builds partitions, etc.
and guess what ... it doesn't find any hard drives to create, shrink, delete
partitions on.

If the boys on Monday who know what they're doing can't find my disk (I'm
sure its here somewhere), then I guess it really is a new hard drive!

Oh well.
 
R

Russ

Boot XP or cd, select the first repair you see, at the command prompt, type
in FIXMBR or FIXBOOT, you may have to use some switch eg FIXMBR /DEVICE
/HARDDISK 0 (use HELP if need be), but I'm sure just FIXMBR. If that doesn't
work, you could get your hands on a 98 boot disk if you have a floppy drive,
if not borrow one or create a 98 boot cd. At the command prompt, I think
its, <command prompt>FDISK /MBR C:
 
R

Richard Urban

If you want to run the DOS version of fdisk with the /mbr option, you had
better have only the drive you want to repair connected as the master on
IDE1. Otherwise you may fdisk the wrong drive.

--


Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!
 
L

Len Mattix

Let me say first off that I know nothing about bitlocker! However, have you
considered turning the TPM back on and trying to reinstall the OS? That
appears from your messages the only variable that you haven't mentioned.
Will it make a difference, I don't know... maybe worth a try?

Len
 
G

Guest

If wores comes to worse, you can always go to your hard drive manufacturers
website, and download the hard disk utility. Writing 0 to the drive generally
will fix all that ailes you.
 
S

Saucy

dfeifer said:
If wores comes to worse, you can always go to your hard drive
manufacturers
website, and download the hard disk utility. Writing 0 to the drive
generally
will fix all that ailes you.


Zero-fill - it's the only way to fly.
 
K

Kerry Brown

This will also erase the Toshiba diagnostic or restore partitions if they
are still on the drive. Erasing track 0 may be the solution but it should
only be done if all the ramifications are known before hand. Some OEM
computers have a special non-standard boot sector so you can press a key
during the POST to access the system restore partition. If this is the case
then you need a special utility from the computer manufacturer to restore
this non-standard boot sector. Zero filling the drive may actually make
matters worse.
 
R

Russ

I'm sorry I thought I C:\ in the command line, I don't imagine he would have
2 hard drives, both set master, a little confusing at boot up would you say?
 
S

Saucy

Russ said:
I'm sorry I thought I C:\ in the command line, I don't imagine he would
have 2 hard drives, both set master, a little confusing at boot up would
you say?


Both might be masters of their channels.
 
R

Richard Urban

That is exactly what happened to me a couple of years ago. I wanted to fdisk
/mbr my secondary master and ended up running it on the primary master. That
is the default and can not be changed. Lessen learned.

--


Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!
 
R

Russ

Unless you boot to your secondary master or for some reason disabled your
primary master in bios and your secondary master happen to have os installed
on it, I can't see this being an issuse, the computer is going to boot to
the primary master, if for some reasons it has been configured wrong, ie,
you have 2/3/4, they would all have to be masters to make such an error.
 
R

Richard Urban

I was dual booting. I was using a third party boot manager. Each operating
system was seen as Drive C:. Each operating system was on a primary DOS
partition on it's own drive. If I had made certain that the drive I wanted
to fdisk /mbr was the only drive attached it would have been applied to the
"correct" drive.

I was just issuing a warning that if you don't take precautions that
something similar may happen to you, or someone else. Take the warning - or
not. No skin off my nose.

--


Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!
 
D

Dale

You guys are missing the point. He states that even his BIOS cannot see the
drive. If the BIOS cannot see it, it isn't there even for FDISK.

As I have said before, BitLocker is not for the faint of heart. It requires
expertise in implementation, in locking down policies, in management of
keys, and it requires non-encrypted backup of your data so that when it
fails - and it will fail, either by itself or with the help of a user, you
can recover your data from backup and start over.

Where others have complained that BitLocker is not available in Home
versions, this is why.

Dale
 
C

cquirke (MVP Windows shell/user)

You guys are missing the point. He states that even his BIOS cannot see the
drive. If the BIOS cannot see it, it isn't there even for FDISK.

Good point - only a PnP OS may do better, and DOS mode with a PnP
manager may create an access that FDisk may not be able to use.
As I have said before, BitLocker is not for the faint of heart. It requires
expertise in implementation, in locking down policies, in management of
keys, and it requires non-encrypted backup of your data so that when it
fails - and it will fail, either by itself or with the help of a user, you
can recover your data from backup and start over.
Where others have complained that BitLocker is not available in Home
versions, this is why.

I quite agree - I don't want it anywhere near my PC, even as an
optional add-on. What if some malware invokes it to protect itself?

Hence the nickname "botlocker"; locks in the bots so that you can't
detect and clean them from orbit (off-HD boot) <g>

It's great for some corporate settings, I can see that - where it's
more damaging for the wrong eyes to see data than to lose it forever.

But for the rest of us, it's like having a self-destruct button in the
center of our forehead, wired to a shotgun cartridge cemented into the
roof of our mouths. No ^%$#n' thanks.


--------------- ---- --- -- - - - -
Saws are too hard to use.
Be easier to use!
 
D

Dale

cquirke (MVP Windows shell/user) said:
Good point - only a PnP OS may do better, and DOS mode with a PnP
manager may create an access that FDisk may not be able to use.



I quite agree - I don't want it anywhere near my PC, even as an
optional add-on. What if some malware invokes it to protect itself?

Hence the nickname "botlocker"; locks in the bots so that you can't
detect and clean them from orbit (off-HD boot) <g>

It's great for some corporate settings, I can see that - where it's
more damaging for the wrong eyes to see data than to lose it forever.

But for the rest of us, it's like having a self-destruct button in the
center of our forehead, wired to a shotgun cartridge cemented into the
roof of our mouths. No ^%$#n' thanks.

That must be why it is only included in Enterprise and Ultimate - not even
in Business.
 
C

cquirke (MVP Windows shell/user)

(about BitLocker)
That must be why it is only included in Enterprise and Ultimate - not even
in Business.

Yep - a very wise decision IMO, tho if using Ultimate, I'd want to be
sure it wasn't left lying around for malware to enable.


--------------- ---- --- -- - - - -
Saws are too hard to use.
Be easier to use!
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top