Stop 0x00000050 on Boot with eSATA Connected External Drive

[Bob Felton]

Scenario:

-Gateway 6400 Server platform (Pentium III @ 800MHz) running Windows
-2000 Server, SP4
-2GB RAM
-Adpatec RAID controller with SCSI drives providing RAID5 drive,
booting Windows
-Motherboard SCSI controller enabled controlling a tape drive
-System working fine with no issues for many months.

Needed to add additional storage. Acquired an external RAID1 capable
drive enclosure (Sans Digital MS2UT) with both USB and eSATA
interfaces. Acquired Qty 2, 320GB Western Digital SATA drives for use
in the enclosure. Acquired a SIIG eSATA II-150 PCI adapter card for
connecting the external drive to the server via eSATA.

Tested the external drive enclosure on a Windows XP Pro workstation
via the USB interface. Enclosure came up as a RAID1 drive and worked
without problem.

Shutdown the server, installed the eSATA adapter, restarted the
server, and installed the eSATA adapter driver from provided CDROM
when prompted by Windows. Server came up OK with no issues and Device
Manager showing no problems.

With the server up, attached the external drive enclosure to the
server via the eSATA interface and turned the enclosure ON. Windows
detected a new hard drive and installed support for it. Was able to
create a root folder, copy files/folders into the root folder, assign
user permissions to sub-folders, and share the root folder with no
problems.

Problem:

Upon shutdown and restart of the server, a blue screen appeared with
Stop 0x00000050. A second restart attempt resulted in same issue.
Upon a restart with the external drive enclosure turned OFF, the
server booted but into a "previously good state". (Probably due to
the fact that the external drive was no longer accessible.) After the
restart with the external drive enclosure turned OFF, the enclosure
was turned ON. Windows detected the drive and installed support for
it, but it was no longer in a shared state.

With the external drive enclosure connected via the USB interface and
the drive placed into a shared mode, there are no problems encountered
during system boot. System comes up and the external drive is
incorporated into the system as the previously shared drive.

I would like to know how to fix the blue screen boot problem when the
external drive enclosure is connected via the eSATA interface and in
an ON state so that the server will boot, detect and incorporate the
external drive into the system in its previously configured shared
state.

Thanks!

 

[Steve Parry]

Scenario:

-Gateway 6400 Server platform (Pentium III @ 800MHz) running Windows
-2000 Server, SP4
-2GB RAM
-Adpatec RAID controller with SCSI drives providing RAID5 drive,
booting Windows
-Motherboard SCSI controller enabled controlling a tape drive
-System working fine with no issues for many months.

Needed to add additional storage. Acquired an external RAID1 capable
drive enclosure (Sans Digital MS2UT) with both USB and eSATA
interfaces. Acquired Qty 2, 320GB Western Digital SATA drives for use
in the enclosure. Acquired a SIIG eSATA II-150 PCI adapter card for
connecting the external drive to the server via eSATA.

Tested the external drive enclosure on a Windows XP Pro workstation
via the USB interface. Enclosure came up as a RAID1 drive and worked
without problem.

Shutdown the server, installed the eSATA adapter, restarted the
server, and installed the eSATA adapter driver from provided CDROM
when prompted by Windows. Server came up OK with no issues and Device
Manager showing no problems.

With the server up, attached the external drive enclosure to the
server via the eSATA interface and turned the enclosure ON. Windows
detected a new hard drive and installed support for it. Was able to
create a root folder, copy files/folders into the root folder, assign
user permissions to sub-folders, and share the root folder with no
problems.

Problem:

Upon shutdown and restart of the server, a blue screen appeared with
Stop 0x00000050. A second restart attempt resulted in same issue.
Upon a restart with the external drive enclosure turned OFF, the
server booted but into a "previously good state". (Probably due to
the fact that the external drive was no longer accessible.) After the
restart with the external drive enclosure turned OFF, the enclosure
was turned ON. Windows detected the drive and installed support for
it, but it was no longer in a shared state.

With the external drive enclosure connected via the USB interface and
the drive placed into a shared mode, there are no problems encountered
during system boot. System comes up and the external drive is
incorporated into the system as the previously shared drive.

I would like to know how to fix the blue screen boot problem when the
external drive enclosure is connected via the eSATA interface and in
an ON state so that the server will boot, detect and incorporate the
external drive into the system in its previously configured shared
state.

Thanks!

Have you spoken with the device manufacturers/suppliers support people?

 

[Bob Felton]

I sent the same inquiry to Initio support as the adapter card was
identified as an Initio INIC1620 by Windows. They replied I needed to
contact SIIG since Initio only provided the chipset to SIIG. I sent
the same inquiry to SIIG this morning, thus no reply from them as yet.

 

[Bob Felton]

Nothing back from SIIG as yet. Can anyone offer any suggestions?
Thanks.

 

[Bob Felton]

After almost 96 hours I finally get a response from SIIG support:

"Hello,
Yes, we use the INITIO chipset for this card.
Right now, we do not have the update firmware for this card.
You may want to check back with us in a few weeks."

Caveat Emptor, I guess. I sure won't buy any more products from SIIG.
Totally unacceptable tech support.

Anybody know a quality source of PCI eSATA interface cards?

 

[Bob Felton]

I recreated the stop error to discover its source: scsiport.sys. A
Google search discovered that MSKB Article 888321 may apply. The
article says there is a hotfix available for this via a "new"
scsiport.sys file, Version 5.1.2600.2562 dated 11 Nov 2004. The
scsiport.sys file in the server's c:\winnt\system32\drivers folder is
Version 5.0.2195.7059 with a creation date of July 26, 2000 and a
modification date of July 14, 2005. This file appears to be newer
than the hotfix file. Does the hotfix still apply? Is it readily
available for download? Thanks!