Maxtor 80 gb not useable as bootdisk???

[12move]

Hi there,

Please, can anyone help me?

Because of a new (2nd-hand) pc (Siemens Scenic 800, Pentium III, 450 mhz,
128 mb, 8 gb) I have removed the 10 gb WesternDigital and the (2 weeks old)
80 gb Maxtor harddisks from my previous pc and replaced them with the 8 gb
that came with the new pc (it went in the old one).
Since all Bios-settings regarding IDE-drives are "Auto" (on both pc's) I
expected to just connect and continue working (aside from all the new
devices, which would be detected automatically).
The 10 gb worked as expected, but the Maxtor 80 gb drive ("Master" on
Primary IDE and boot disk) starts out to boot Windows 2000 (progressbar at
the bottom), displays the logoscreen, and then:BOOM!!
A STOP error (blue screen) with "INACCESSABLE_BOOT_DEVICE".
At the moment, I have disconnected the 10 gb and have already done some 15
to 20 setup's of both Windows 2000 and Windows XP in all kinds of different
ways. Booted with the OS cd, booted from MSDOS floppy, loaded cdrom driver
and started "E:\I386\winnt.exe". I even tried all kinds of settings in the
BIOS setup.
The strange thing is, that the disk itself is recognised perfectly. When I
boot from the 10 gb (there was still an old NT4 installation on it) I could
see the full drive and could even copy files to and from it.
Except, when I want to boot from this Maxtor 80 gb, problems occur. Even
stranger: on my previous pc I already used this drive as bootdisk! With
Windows 2000 in a 5 gb partition (C and next to it (almost empty) a 75 gb
partition.
This previous pc was a Packard Bell Pentium at 200 mhz. A plain Pentium, at
least 5 or 6 years old! No problems at all using this Maxtor as bootdisk
with Windows 2000 on it! And now, in a much more recent pc (max 3 years)
this disk will not boot anymore. I thought it had to do with a BIOS <->
harddrive geometry translation problem, so I deleted all partitions and
started from scratch (partitioning, formatting). But I keep getting the same
message!
In the Windows XP setup process the message is: "UNMOUNTABLE_BOOT_VOLUME".
The BIOS in the new pc is: PhoenixBios Version 4.06 Rev. 1.06.1107.

This problem always occurs when the setup process reboots for the first time
and wants to boot from the new installation to resume the setup process. So
far, it has not been able to complete any setup!

PLEASE HELP! I am already fighting this thing for two days or so. I am
going out of my mind trying to figure out what is going wrong.

Thanks for youre reply.

Frank

f (dot) wienk (at) 12move.nl
(notation to avoid spam. just type the dot (.) and the at-symbol (@).)

 

[Dave Patrick]

This article may help you.

How to Move a Windows Installation to Different Hardware
http://support.microsoft.com/directory/article.asp?ID=KB;EN-US;Q249694

 

[Dave Patrick]

You didn't mention the error and or the drive controller (possibly SCSI,
ultra DMA, raid, or ATA100), but you may need to boot the Windows 2000 setup
disks or CD-Rom and *F6* very early and very important (at setup is
inspecting your system) in the setup to prevent drive controller detection,
and select S to specify additional drivers. Then later you'll be prompted to
insert the manufacturer supplied Windows 2000 driver for your drive's
controller in drive "A"

If you wait and then S to specify additional drivers, then it may be too
late as Windows 2000 Setup at this point may have already assigned the
resources your drive's controller is wanting to use.

 

[Frank]

Hi there,

(Sorry about the displayed name. Before now, I hadn't setup my
profile-info correctly in my news-software. The original problem came
from me, anyhow....)

Patrick,
thanks for the reply, but it isn't about 'moving' the OS, at least not
anymore.
Because of all the problems, I completely re-partitioned and formatted
the 80 gb drive and did a clean install of Windows 2000 (and tried XP
too, for that matter).
I keep getting the same STOP error during the first reboot in the
setup-process:
"INACCESSABLE_BOOT_DEVICE", or (in XP): "UNMOUNTABLE_BOOT_VOLUME".

I tried partitioning/formatting in many different ways:
during the W2000-setup, with MSDOS fdisk/format (C: as FAT16, less
than 2 gb), using the Maxtor Max-BlastII software, I downloaded the
latest MaxBlast III from www.maxtor.com.
I even downloaded and performed a Flash update on the Phoenix BIOS:
from v4.06 rev. 1.06.1107 to v.4.06 rev. 1.16.1107. This came from
www.fujitsu-siemens.com.
The motherboard modelnr is D1107. It's a Siemens Scenic 800. By now, I
found out that it is actually a Scenic 860 (some german
Siemens-related site said that a 800 with a D1107 motherboard and a
PIII on 450 mhz is called a "860".)
I am really going mad here. I called the shop where I bought this
Maxtor drive (only two weeks ago!) and explained the problem. I asked
if it could be solved with a separate ATA-133 board, but he couldn't
be sure. He said it should also work in the current situation.
I someone would say: "with an ATA-133 board your problem is 100% fixed
for SURE", then I will buy this thing this very minute! But all I hear
is that I shouldn't have this problem in the first place, so I don't
know anymore.

During IDE recognision at boot time, the BIOS does a perfect job with
the message:
"Harddisk 1 Maxtor 6Y080L0".

When I boot from another harddisk, there are no problems at all! I can
see the whole 80 gb. Just the booting from it don't work!

PLEASE HELP!!

Thanks very much!

Frank Wienk
f.wienk(at)12move.nl






Op Tue, 1 Jul 2003 20:15:37 -0600 schreef "Dave Patrick"

 

[Frank]

Patrick,

One other thing that came in mind. At a certain time, my other (10 gb)
harddisk was still connected and used it as bootdisk. (It still has an
old NT4 installation on it.) At that time, I could see the complete
80gb disk in the explorer right away, copy files to and from it, no
problems at all and I did NOT have to load any special drivers or
anything.
Does this matter or is the Windows driver-need completely different
when used as bootdisk?

Just thought I should mention this little detail.

Greetings,

Frank Wienk
f.wienk(at)12move.nl

 

[Dave Patrick]

You need a driver for the drive controller. Nothing to do with the drive
itself.

 

[Dave Patrick]

Either from the drive controller, pc, or mother board manufacturer.