win2000 inaccesible_Boot_Device

Printable View

April 5th, 2006, 04:17 PM
.:front2back:.

win2000 inaccesible_Boot_Device

Howdy.

Well i was fiddling around with partitionmagic8.0 and i was copying the win2000 partition onto a new drive..
->old drive 40Gb->Copy to->200Gb drive..

Well i did the wizard thing, restarted like it said to, and now i'm getting this damned blue screen and this is what it's spitting back at me now..

Quote:

***STOP:0x0000007B (0xEB81F84C, 0xC000000E, 0x00000000, 0x00000000)***
Inaccesible_Boot_Device

System=p4 2.6Ghz
Ram=1Gb
Os=Windows2000 professional
Hdisk=40Gb, (Was trying to copy it over to the new 200Gb)

Anyhow i'm pretty much wanting to know if i can just throw in the windows 2000 CD and just do a Recovery thingy like you can in WindowsXP.?
And if not then how can i fix the windows on the 40Gb and NOT loose the data on the drive..
I've tried doing a system restore, after the Bios dissapears press F8 a few times, then choosing last known good config. recieve error message.
Tried booting into safemode, recieve error message.
also I've just tried using knoppix but it is not doing anything..

And i cannot even acess a Dos prompt with a WindowsME boot disk,,

Any and all ideas will be much appreciated.

cheers
F2B..
April 5th, 2006, 04:27 PM
SirDice

Is the 40Gig still primary master? And the 200Gig primary slave? Or secondary master?

Switch them around (physicly)..

Part.Magic probably copied everything including which drive (set to prim. master) to boot from..
April 5th, 2006, 04:27 PM
Nokia

Is the new HDD showing up in the BIOS?
April 5th, 2006, 04:48 PM
.:front2back:.

Quote:

Originally posted here by SirDice
Is the 40Gig still primary master? And the 200Gig primary slave? Or secondary master?

Switch them around (physicly)..

Part.Magic probably copied everything including which drive (set to prim. master) to boot from..

Ok just checked, the 40Gb is still primary master, and the 200GB is secondary slave.
got the 40Gb jumper set to Master, the 200Gb set to slave. have tried trying one drive at a time as master, but i get the error screen on 40Gb, and with the 200Gb it just sit's on the Bios menu, but it detects it when it's set to either master or slave..

Quote:

Originally posted here by Nokia
Is the new HDD showing up in the BIOS?

New HDD is showing up in the Bios, it says it's there, but it won't budge past the BIOS screen, when it's connected by it'self.

cheers
f2B
April 5th, 2006, 05:14 PM
Nokia

It maybe worth running a fix mbr on it to see if it PM has corrupted it in someway.

When you say you have tried setting each as master - is this without a slave connected?
April 5th, 2006, 05:22 PM
.:front2back:.

Quote:

Originally posted here by Nokia
It maybe worth running a fix mbr on it to see if it PM has corrupted it in someway.

When you say you have tried setting each as master - is this without a slave connected?

Howdy.

Yes, i have disconected 200Gb leaving 40Gb as master, powered up,BIOS detects it as primary master, i then get the error message, so i power down, disconnect 40Gb, i then connect the 200Gb set jumper to master, power up and it just sits on the BIOS screen and refuses to go from there, it detects it as primary master.

cheers
f2B
April 5th, 2006, 05:28 PM
Nokia

OK then, if your BIOS is detecting it ok, and is POST'ing ok but you are getting the trouble when it passes over to the hard drive I would say it is almost certainly a problem with the boot record.

The option you mentioned earlier about repairing the installation could be your best bet - I would start with the MBR first!

Try the "chkdsk" and "fixmbr" commands from the repair console..
April 5th, 2006, 05:59 PM
.:front2back:.

Howdy.

Ok just did chkdsk /p this is what the report gave me

Quote:

c:\WINNT>chkdsk /p
Volume created 03/31/06 04:56p
The Volume Serial Number is f887-8fd3
CHKDSK is checking the volume....
CHKDSK is performing additional checking or recovery...
The volume appears to contain one or more unrecoverable problems.
39061412 kilobytes total disk space.
6053672 Kilobytes are available.

c:WINNT>

the fixmbr option says the following.

Quote:

This computer appears to have a non-standard or invalid master boot record.
FIXMBR may damge your partition tables if you proceed.
This could cause all the partitions on the current hard disk to become inacessible.
If you are not having problems accessing your drive, do not continue.

Are you sure you want to write a new MBR?

So should i write a new MBR..

i had an idea, though what if i just threw in a windowsXP disc, and just updated to winxp, i know there is an option to maintain settings programs installed, files etc, would/could that possibley fix the damn drive.?

cheers
f2B
April 5th, 2006, 06:20 PM
Nokia

Probably not as it would be presented with the same errors as Windows 2000 is now, it either woukd not install or have to overwrite data on your HDD.

Is this output for the 40GB or the 200GB drive?
April 5th, 2006, 06:23 PM
.:front2back:.

Howdy.,

This is the output for the 40Gb.
The 200Gb won't let me get past the BIOS screen when it's set as master..

cheers
F2B
April 5th, 2006, 06:36 PM
morganlefay

Sounds like the 200 mb drive is flucked up somehow...physically...

Maybe a bent pin on the connecter....

Can you try it in another machine as slave???

MLF
April 5th, 2006, 06:38 PM
foxyloxley

the fixmbr always puts out that 'warning'

I feel you need to fixmbr and to do it when the 200GB is set as master
IMHO natch
April 5th, 2006, 06:42 PM
.:front2back:.

Howdy.

No physical damage to the 200Gb drive, i set the jumper on it to slave, and put it in my suse box and it is detected at Bios, suse load ups, and i can see the drive, but it will not let me mount it.

cheers
f2B
April 5th, 2006, 06:45 PM
morganlefay

What kinda of cable are you using???

Is there a difference in the 2 boxes??

:confused:

MLF
April 5th, 2006, 06:51 PM
.:front2back:.

Howdy.

It's just a normal cable IDE cable {I think that's the word for it, i'm to tired to think. }
One box is
32bit, <-Suse10.0
while the other is
64bit<-windows box
April 5th, 2006, 07:13 PM
rcgreen

I would put the 200g drive in alone, set as primary master.
Boot from the windows install cd and partition the drive.
then you could stop, reinstall the old drive as primary master,
200g as slave whatever, and try to fix the problems on the
40g drive. Like others have said, the MBR on the 200g is
messed up. that's why you can't mount it under linux.

I would consider the practice of copying a partition to
another drive to be an experimental method.
Prolly better to install from scratch.
:cool:
April 5th, 2006, 07:23 PM
morganlefay

You know maybe partition Magic has a limit on the harddrive size it can recognize\copy to...and the 200 gig threw it off...which then mucked everything up

As suggested by rc ...try setting up a partition first...then use the partition magic to copy the os/??

Hopefully you can recover the 40 gig drive

Just thoughts :(

MLF
April 5th, 2006, 07:38 PM
SirDice

Quote:

Originally posted here by .:front2back:.
No physical damage to the 200Gb drive, i set the jumper on it to slave, and put it in my suse box and it is detected at Bios, suse load ups, and i can see the drive, but it will not let me mount it.

Looks like the drive is borked.. Or perhaps the BIOS cannot handle disks that large..

Since it's not working right now.. Have you tried just a quick 'n dirty w2k install on it?
April 6th, 2006, 06:10 AM
.:front2back:.

Howdy.

well i ended up recovering the contents of the 40Gb drive. And the 200Gb drive has been returned to the shop that it was purchased from. And i was given a replacement. :)
I took the drive into a local computer shop, Anyhow it took 'em from 9:30Am until 2Pm in the afternoon, but they used some program and were able to copy all the needed data over to a temp drive for me.

Anyhow i don't think that i will be touching that damned partition magic anymore..

greenies to all those that helped :)

cheers
f2B