Gosted Drive gets NTOSKRNL.EXE Blue screen on boot

[Guest Jeff Gross]

Hi, I have a customer with a DC running windows 2000 advanced server.

It's an older Pentium 3 rack mount server. Runs great, but the drives

(mirrored) are getting noisy and it seems time to replace the

drives.

 

I ghosted the old maxtor 40 gig drive onto a new Seagate barracuda 60

gig drive. It booted beautifully the first time on the new drive,

then I saw something about a hardware update or something, and then

when I shut down and re-booted, I got the ntoskrnl.exe missing error.

I guess it has something to do with the system recognizing the new

drive hardware and making a change. So I had to put the old mirror

pair back in for now.

 

What the heck is going on? I've never had such difficulty before when

I did this.

 

Any help form anyone whos gone through this would be appreciated.

[Guest Pegasus \(MVP\)]

Re: Gosted Drive gets NTOSKRNL.EXE Blue screen on boot

 

 

"Jeff Gross" <jgross@quonix.net> wrote in message

news:3ca7dd3e-ad5f-4e19-b660-102f0789a40d@t63g2000hsf.googlegroups.com...

> Hi, I have a customer with a DC running windows 2000 advanced server.

> It's an older Pentium 3 rack mount server. Runs great, but the drives

> (mirrored) are getting noisy and it seems time to replace the

> drives.

>

> I ghosted the old maxtor 40 gig drive onto a new Seagate barracuda 60

> gig drive. It booted beautifully the first time on the new drive,

> then I saw something about a hardware update or something, and then

> when I shut down and re-booted, I got the ntoskrnl.exe missing error.

> I guess it has something to do with the system recognizing the new

> drive hardware and making a change. So I had to put the old mirror

> pair back in for now.

>

> What the heck is going on? I've never had such difficulty before when

> I did this.

>

> Any help form anyone whos gone through this would be appreciated.

 

I haven't experienced this problem but I would try the following:

1. After cloning, boot the machine with a Bart PE boot CD.

2. Create a backup copy of the three registry files in

c:\Windows\system32\config. This allows you to recover

quickly from subsequent BSODs.

3. On the first boot, force the driver for the disk controller to

the generic Microsoft controller (Control Panel / System /

Hardware / Device Manager.

[Guest Jeff Gross]

Re: Gosted Drive gets NTOSKRNL.EXE Blue screen on boot

 

Bart Pe didn't work, but here's what I did, I put the original drives

back. They work but the bearings are very loud (an indication that

time is short). I placed the newly ghosted drive into another machine

on the network, so I could compare them side by side, and every single

file was there, file for file, an exact duplicate drive. All the

system and boot files. However putting it back into the server, no

boot.

 

Could it be something in the FAT table or boot sector? Is there some

way to make the drive bootable?

 

 

On Apr 19, 10:14 am, "Pegasus \(MVP\)" <I....@fly.com.oz> wrote:

> "Jeff Gross" <jgr...@quonix.net> wrote in message

>

> news:3ca7dd3e-ad5f-4e19-b660-102f0789a40d@t63g2000hsf.googlegroups.com...

>

>

>

>

>

> > Hi, I have a customer with a DC running windows 2000 advanced server.

> > It's an older Pentium 3 rack mount server.  Runs great, but the drives

> > (mirrored) are getting noisy and it seems time to replace the

> > drives.

>

> > I ghosted the old maxtor 40 gig drive onto a new Seagate barracuda 60

> > gig drive.  It booted beautifully the first time on the new drive,

> > then I saw something about a hardware update or something, and then

> > when I shut down and re-booted, I got the ntoskrnl.exe missing error.

> > I guess it has something to do with the system recognizing the new

> > drive hardware and making a change.  So I had to put the old mirror

> > pair back in for now.

>

> > What the heck is going on?  I've never had such difficulty before when

> > I did this.

>

> > Any help form anyone whos gone through this would be appreciated.

>

> I haven't experienced this problem but I would try the following:

> 1. After cloning, boot the machine with a Bart PE boot CD.

> 2. Create a backup copy of the three registry files in

>     c:\Windows\system32\config. This allows you to recover

>     quickly from subsequent BSODs.

> 3. On the first boot, force the driver for the disk controller to

>     the generic Microsoft controller (Control Panel / System /

>     Hardware / Device Manager.- Hide quoted text -

>

> - Show quoted text -

[Guest Ace Fekay [MVP]]

Re: Gosted Drive gets NTOSKRNL.EXE Blue screen on boot

 

In news:39d5fbc0-8363-4f20-90ca-b929b4d05953@i76g2000hsf.googlegroups.com,

Jeff Gross <jgross@quonix.net> typed:

> Bart Pe didn't work, but here's what I did, I put the original drives

> back. They work but the bearings are very loud (an indication that

> time is short). I placed the newly ghosted drive into another machine

> on the network, so I could compare them side by side, and every single

> file was there, file for file, an exact duplicate drive. All the

> system and boot files. However putting it back into the server, no

> boot.

>

> Could it be something in the FAT table or boot sector? Is there some

> way to make the drive bootable?

>

 

It may be an Int 13 issue with the Ghost image. I saw this in the past with

Compaq servers. We had to use a switch called -FNX with Ghost when Ghosting

up. The command line we used (by memory):

ghost -z9 -split=650 -FNX -auto

 

-z9 = highest compression rate. When choosing one of the default three

compressions settings that show up on the screen, is only -z1, -z2 or -z3.

So -z9 is the highest, but slower ghosting up, but fastest ghosting down.

-split=650 Used to break each .gho segment to 650 megs so we can burn them

and archive them.

-FNX Used this for the compaq servers mentioned. Give it a shot.

-auto = Generates new names for each 650 segment

 

Ghost switches:

http://ghosting.netfirms.com/switchesal.htm

 

If the drive is an IDE drive, you can use the script in the following "Stop"

error article to create a .reg file to force it to enumerate all drive

manufacturer types. Then manually copy the Atapi.sys, Intelide.sys,

Pciide.sys, and Pciidex.sys files. There are about 30 possibly combination

of ide drivers from various manufacturers that it checks. This is normal

when Windows Setup runs the first time, but after that, it won't look for

other types unless forced with reg entries. We found it very useful with

ghosting machines for various classrooms with diferent hardware, laptop to

desktop.

 

You receive a Stop 0x0000007B error after you move the Windows XP system

disk to another computer

http://support.microsoft.com/kb/314082

 

How to move a Windows installation to different hardware

http://support.microsoft.com/kb/249694

 

As immediately dealing with this issue, you can re-run Windows 2003 Setup as

an upgrade. Reboot from the CD, and choose repair. One of the things it

repairs is the boot sector. It will not change the installation; all your

settings and profiles will still be there. It's clean and it works. Cleans

out some bugs too. It would also be helpful if you had an i386 source on the

CD that matches the machine's current service pack level. If not, you'll

have to re-run the service pack setup as well as getting it caught up at

Windows Update.

 

How to Perform an In-Place Upgrade of Windows Server 2003

http://support.microsoft.com/kb/816579/

 

 

--

Regards,

Ace

 

This posting is provided "AS-IS" with no warranties or guarantees and

confers no rights.

 

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,

MVP Microsoft MVP - Directory Services

Microsoft Certified Trainer

 

For urgent issues, you may want to contact Microsoft PSS directly. Please

check http://support.microsoft.com for regional support phone numbers.

 

Infinite Diversities in Infinite Combinations

[Guest Pegasus \(MVP\)]

Re: Gosted Drive gets NTOSKRNL.EXE Blue screen on boot

 

The essence of my suggestion was not really the Bart PE

boot but replacing the current driver for your IDE Controller

with the generic Microsoft driver. Your reply makes no

reference to this technique.

 

 

"Jeff Gross" <jgross@quonix.net> wrote in message

news:39d5fbc0-8363-4f20-90ca-b929b4d05953@i76g2000hsf.googlegroups.com...

Bart Pe didn't work, but here's what I did, I put the original drives

back. They work but the bearings are very loud (an indication that

time is short). I placed the newly ghosted drive into another machine

on the network, so I could compare them side by side, and every single

file was there, file for file, an exact duplicate drive. All the

system and boot files. However putting it back into the server, no

boot.

 

Could it be something in the FAT table or boot sector? Is there some

way to make the drive bootable?

 

 

On Apr 19, 10:14 am, "Pegasus \(MVP\)" <I....@fly.com.oz> wrote:

> "Jeff Gross" <jgr...@quonix.net> wrote in message

>

> news:3ca7dd3e-ad5f-4e19-b660-102f0789a40d@t63g2000hsf.googlegroups.com...

>

>

>

>

>

> > Hi, I have a customer with a DC running windows 2000 advanced server.

> > It's an older Pentium 3 rack mount server. Runs great, but the drives

> > (mirrored) are getting noisy and it seems time to replace the

> > drives.

>

> > I ghosted the old maxtor 40 gig drive onto a new Seagate barracuda 60

> > gig drive. It booted beautifully the first time on the new drive,

> > then I saw something about a hardware update or something, and then

> > when I shut down and re-booted, I got the ntoskrnl.exe missing error.

> > I guess it has something to do with the system recognizing the new

> > drive hardware and making a change. So I had to put the old mirror

> > pair back in for now.

>

> > What the heck is going on? I've never had such difficulty before when

> > I did this.

>

> > Any help form anyone whos gone through this would be appreciated.

>

> I haven't experienced this problem but I would try the following:

> 1. After cloning, boot the machine with a Bart PE boot CD.

> 2. Create a backup copy of the three registry files in

> c:\Windows\system32\config. This allows you to recover

> quickly from subsequent BSODs.

> 3. On the first boot, force the driver for the disk controller to

> the generic Microsoft controller (Control Panel / System /

> Hardware / Device Manager.- Hide quoted text -

>

> - Show quoted text -