T
ToasterKing
I wonder if someone could please give me any advice on a mysterious
SCSI problem I'm having.
It seems some data loss is occuring, and I'm not exactly sure why. I
was unable to install Windows 2000 Professional directly to the drive,
because read/write errors would occur, manifested as blue screens,
unreadable data that was just written, and the volume or partition map
becoming corrupt. Also, booting from the Windows 2000 setup floppies
resulted in a BSOD with a STOP error before the install would start.
BIOS didn't support booting from a CD, so that was out. Thinking maybe
the setup program just didn't support the controller well, I ended up
booting an older version of Windows on an IDE drive, doing a clean
install of Win2000 on that same drive, and then "cloning" that drive to
the SCSI drive using a shareware utility called XXCOPY.
Now, Windows 2000 is bootable from the SCSI drive, and I've been trying
to set it up. Unfortunately, the problems still occur. I get the
following errors in the System log in the Event Viewer:
disk: The driver detected a controller error on \Device\Harddisk0\DR0.
amsint: The driver detected a controller error on \Device\Scsi\amsint1.
amsint: The device, \Device\Scsi\amsint1, did not respond within the
timeout period.
ntfs: The file system structure on the disk is corrupt and unusable.
Please run the chkdsk utility on the volume C:.
The timeout error always occurs at the same point in startup, after the
desktop appears and before tray programs load. After heavy disk writes
(copying large files, installing updates or programs), the ntfs error
will sometimes appear and Windows becomes unreliable. At that point,
the disk is flagged as dirty and Windows checks and fixes the disk,
sometimes resulting in lost files.
Some details:
I'm attempting to set up Windows 2000 Professional SP2 on an HP Vectra
XU 5/90c. This machine has an internal and external SCSI bus via an
on-board AMD SCSI controller chip. The number on the AMD chip is
AM79C974KC. This chip is a combination SCSI-2 controller and 10-BaseT
Ethernet NIC. The drive I am using with it is a Seagate ST410800N,
which is a full-height 9GB SCSI hard drive, and I'm using it on an
internal bus. It is set up with one NTFS partition. The chain IS
terminated properly, with an active terminator at the end of the ribbon
cable. I've tried a different terminator and a different cable. This
machine has worked fine with a different SCSI drive on Windows 95, and
this Seagate ST410800N drive has worked fine on another machine (a
Macintosh). I'm using the default driver installed by Windows 2000
(AMD PCI SCSI Controller/Ethernet Adapter). I've been unable to find a
different one.
Would it be worth my while to find and try a different SCSI adapter?
Or is there something else I may have overlooked?
Thank you kindly,
TK
SCSI problem I'm having.
It seems some data loss is occuring, and I'm not exactly sure why. I
was unable to install Windows 2000 Professional directly to the drive,
because read/write errors would occur, manifested as blue screens,
unreadable data that was just written, and the volume or partition map
becoming corrupt. Also, booting from the Windows 2000 setup floppies
resulted in a BSOD with a STOP error before the install would start.
BIOS didn't support booting from a CD, so that was out. Thinking maybe
the setup program just didn't support the controller well, I ended up
booting an older version of Windows on an IDE drive, doing a clean
install of Win2000 on that same drive, and then "cloning" that drive to
the SCSI drive using a shareware utility called XXCOPY.
Now, Windows 2000 is bootable from the SCSI drive, and I've been trying
to set it up. Unfortunately, the problems still occur. I get the
following errors in the System log in the Event Viewer:
disk: The driver detected a controller error on \Device\Harddisk0\DR0.
amsint: The driver detected a controller error on \Device\Scsi\amsint1.
amsint: The device, \Device\Scsi\amsint1, did not respond within the
timeout period.
ntfs: The file system structure on the disk is corrupt and unusable.
Please run the chkdsk utility on the volume C:.
The timeout error always occurs at the same point in startup, after the
desktop appears and before tray programs load. After heavy disk writes
(copying large files, installing updates or programs), the ntfs error
will sometimes appear and Windows becomes unreliable. At that point,
the disk is flagged as dirty and Windows checks and fixes the disk,
sometimes resulting in lost files.
Some details:
I'm attempting to set up Windows 2000 Professional SP2 on an HP Vectra
XU 5/90c. This machine has an internal and external SCSI bus via an
on-board AMD SCSI controller chip. The number on the AMD chip is
AM79C974KC. This chip is a combination SCSI-2 controller and 10-BaseT
Ethernet NIC. The drive I am using with it is a Seagate ST410800N,
which is a full-height 9GB SCSI hard drive, and I'm using it on an
internal bus. It is set up with one NTFS partition. The chain IS
terminated properly, with an active terminator at the end of the ribbon
cable. I've tried a different terminator and a different cable. This
machine has worked fine with a different SCSI drive on Windows 95, and
this Seagate ST410800N drive has worked fine on another machine (a
Macintosh). I'm using the default driver installed by Windows 2000
(AMD PCI SCSI Controller/Ethernet Adapter). I've been unable to find a
different one.
Would it be worth my while to find and try a different SCSI adapter?
Or is there something else I may have overlooked?
Thank you kindly,
TK