Solve : NT 4.00 Imaged Drive Problems?

1.	Solve : NT 4.00 Imaged Drive Problems?
Answer» We have a machine that the hard drive was imaged, that image was put on another drive. Now both drives when hooked up SHOW a blue screen stop message. The message is inaccessible_boot_device, along with it in the bug check section are some other numbers. In the driver information section of the screen it shows all the drivers that loaded. In the kernel build number and stack dump section there are other numbers and all along the right side of that it says ntoskrnl. I can't set it up to do a memory dump file so as to look at that, because the hard drive never boots past that screen. Does anyone have any ideas what could be causing the blue stop screen or how to get a memory dump file to READ, for further troubleshooting of the drive?Post the entire BSOD message including the gibberish... What were these machines imaged thru ? ?The drives were attached to a USB DEVICE similiar to a drive toaster. The original was imaged, and that image was put on the second drive. We tried to check if both drives would work and both of them show this same screen. The drives were checked in a computer that isn't the original, but before the drives were imaged the original would boot up completely in this non original computer. [attachment deleted by admin]Quote from: MachTool on October 05, 2009, 09:34:38 PM ...The drives were checked in a computer that isn't the original... This is a drive controller issue, the original having a specific driver instead of the Windows generic driver. I have had this happen to me numerous times with Win2k. "...Windows NT requires a mini-port driver to communicate with the boot controller. If the device driver is corrupt or incompatible with your controller, you can replace it by copying a new driver to the %systemroot%\system32\drivers folder or through the Emergency Repair process. On computers running on a SCSI controller or ATAPI enabled systems, SCSIPORT.SYS and DISK.SYS (Windows NT 4.0 only) device drivers are also required to successfully boot..."Can I find out that information from the Registry the type of driver that was used? Its hard finding information on these computers.NT4.0 was not plug & play and does not automatically find and use the proper drivers, even if they exist in the proper directory. I'm not even sure if it has the capability to do a Repair Install. Repairing anything in NT4.0 usually requires a complete reinstall from the original CD's.It's confusing how the original drive worked in another computer before it was imaged, now that same drive gives the stop screen. I could understand how the imaged drive would give the stop screen. Quote from: MachTool on October 09, 2009, 08:02:57 AM It's confusing how the original drive worked in another computer before it was imaged, now that same drive gives the stop screen. I could understand how the imaged drive would give the stop screen. That's the reason: it's a different computer. Unlikely an identical make and model of computer.I guess I should have clarified that better, this is what I meant. The drives were checked in a computer that isn't the original, but before the drives were imaged the original would boot up completely in this non original computer. How do I get around this problem? Do you know how to make this drive record a memory dump file, so it could be put in a Windows Debugger. It seems like the only way to view the problem is to hook two computers together and troubleshoot it that way. Maybe this: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q125933 or this: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q164471 The FIRST link refers to being able to get to the control panel, is there a way with the disk not being able to boot past the stop screen? Second link says there has to be an ERP made from the system in question, unfortunately it isn't available. http://support.microsoft.com/default.aspx?scid=kb;en-us;Q125933 If you are running Windows NT 4.0, go to the SCSI Adapters option in Control Panel. http://support.microsoft.com/default.aspx?scid=kb;en-us;Q164471 An Emergency Repair Disk from the installation of Windows NT that we are replacing the file on is required for this operation. It is possible to use an ERD from an identical installation of Windows NT on another computer, but this invites unforeseen problems if there is even a minor difference between installations.I'm sorry, I have no more suggestionsThank you for your help Comp_Com. Does anyone else have any suggestions that MIGHT be able to help with our problems? Patio I posted all the Stop screen message, is there anything you might have?

Answer»
We have a machine that the hard drive was imaged, that image was put on another drive. Now both drives when hooked up SHOW a blue screen stop message. The message is inaccessible_boot_device, along with it in the bug check section are some other numbers.
In the driver information section of the screen it shows all the drivers that loaded. In the kernel build number and stack dump section there are other numbers and all along the right side of that it says ntoskrnl.
I can't set it up to do a memory dump file so as to look at that, because the hard drive never boots past that screen.
Does anyone have any ideas what could be causing the blue stop screen or how to get a memory dump file to READ, for further troubleshooting of the drive?Post the entire BSOD message including the gibberish...
What were these machines imaged thru ? ?The drives were attached to a USB DEVICE similiar to a drive toaster. The original was imaged, and that image was put on the second drive. We tried to check if both drives would work and both of them show this same screen. The drives were checked in a computer that isn't the original, but before the drives were imaged the original would boot up completely in this non original computer.

[attachment deleted by admin]Quote from: MachTool on October 05, 2009, 09:34:38 PM

...The drives were checked in a computer that isn't the original...

This is a drive controller issue, the original having a specific driver instead of the Windows generic driver. I have had this happen to me numerous times with Win2k.

"...Windows NT requires a mini-port driver to communicate with the boot controller. If the device driver is corrupt or incompatible with your controller, you can replace it by copying a new driver to the %systemroot%\system32\drivers folder or through the Emergency Repair process. On computers running on a SCSI controller or ATAPI enabled systems, SCSIPORT.SYS and DISK.SYS (Windows NT 4.0 only) device drivers are also required to successfully boot..."Can I find out that information from the Registry the type of driver that was used? Its hard finding information on these computers.NT4.0 was not plug & play and does not automatically find and use the proper drivers, even if they exist in the proper directory. I'm not even sure if it has the capability to do a Repair Install. Repairing anything in NT4.0 usually requires a complete reinstall from the original CD's.It's confusing how the original drive worked in another computer before it was imaged, now that same drive gives the stop screen. I could understand how the imaged drive would give the stop screen. Quote from: MachTool on October 09, 2009, 08:02:57 AM

It's confusing how the original drive worked in another computer before it was imaged, now that same drive gives the stop screen. I could understand how the imaged drive would give the stop screen.

That's the reason: it's a different computer. Unlikely an identical make and model of computer.I guess I should have clarified that better, this is what I meant.

The drives were checked in a computer that isn't the original, but before the drives were imaged the original would boot up completely in this non original computer.

How do I get around this problem? Do you know how to make this drive record a memory dump file, so it could be put in a Windows Debugger. It seems like the only way to view the problem is to hook two computers together and troubleshoot it that way.
Maybe this:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q125933

or this:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q164471
The FIRST link refers to being able to get to the control panel, is there a way with the disk not being able to boot past the stop screen?
Second link says there has to be an ERP made from the system in question, unfortunately it isn't available.

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q125933

If you are running Windows NT 4.0, go to the SCSI Adapters option in Control Panel.

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q164471

An Emergency Repair Disk from the installation of Windows NT that we are replacing the file on is required for this operation. It is possible to use an ERD from an identical installation of Windows NT on another computer, but this invites unforeseen problems if there is even a minor difference between installations.I'm sorry, I have no more suggestionsThank you for your help Comp_Com.

Does anyone else have any suggestions that MIGHT be able to help with our problems?

Patio I posted all the Stop screen message, is there anything you might have?

Solve : NT 4.00 Imaged Drive Problems?

Discussion

No Comment Found

Related InterviewSolutions

Reply to Comment