Re: 2nd Request: SCSIPORT.SYS 0x50 BSD


"System Administrator" <sysadmin@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:464dee67.1032714062@xxxxxxxxxxxxxxxxxxxxxxx
Original Posting: Sat, 12 May 2007 18:23 GMT

I have a Windows 2000 Server based server. The motherboard has an
onboard SCSI controller controlling only a tape drive. There is an
Adaptec SCSI controller in a PCI slot controlling the system drive
(RAID5). I want to add an eSATA controller but the system BIOS will
not support another "SCSI" type device. To get around this, I decided
to disable use of the tape drive as it isn't being used. So, I
uninstalled the onboard SCSI device (two instances) in Windows' Device
Manager, rebooted into the system BIOS and disabled the onboard SCSI
controller. I then double checked the boot device sequence - it was
still pointed to the RAID5 controller and rebooted. I then received a
BSD with 0x50 stop error in scsiport.sys. I attempted to boot into
safe mode per the BSD instructions and still received the BSD 0x50
scsiport.sys stop error. Any ideas on how to resolve this problem?
Thanks.

Additional, 18 May: Windows 2000 Server OS is at SP4 level with all
latest updates

First, disabling the device in Windows would have no effect of boot
order. If you want to disable the on-board SCSI controller, the place to do
it is in CMOS Setup.

It sounds like you may have disabled both SCSI controllers in Windows
and that's why boot is failing. If so, you may have painted yourself into a
nasty corner. If not, disabling the on-board SCSI controller in CMOS Setup
may get you past the problem.

I suspect that even disabling the on-board controller will not fix the
boot order. It's possible that the only way of controlling which add-on
card it boots from will be by moving the cards around. If you're lucky, it
will try to boot from the first "SCSI" card it finds. If you're not lucky,
it will always try to boot from the real SCSI card and never from the SATA
card.

--

- Gary Chanson (Windows SDK MVP)
- Abolish Public Schools




.

Relevant Pages

  • Re: Install Problem at GUI Startup
    ... After completing the install and getting to the "NTLDR Missing" error, ... directory or trying to boot from a directory other than the root. ... How to troubleshoot the "NTLDR is missing" error message in Windows Server ... I am using the non promise controller exactly as you suggest. ...
    (microsoft.public.windows.server.sbs)
  • Re: Can logon my computer
    ... Once you've launched Windows, though, Windows can't ... find the appropriate driver for your boot device. ... The drivers for that controller got trounced and had to ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Hard Drive Change
    ... especially if you move it form fairly old to much newer hardware. ... While it is correct to say that in 100% of cases if the drive controller ... is different Windows will not boot, it is incorrect to say that different ...
    (microsoft.public.windowsxp.general)
  • Re: Change from PATA to SATA harddrive?
    ... There's no reason why the system won't properly boot after you use the Acronis True Image program to clone the contents of your PATA drive to the SATA one. ... Paul is simply incorrect about Windows XP being unable to boot under these circumstances. ... controller changes I have performed have left 2 of the systems unbootable due to the wrong controller driver being loaded. ... If windows loads then your sorted, you may need to download or install the SATA controller drives at this point. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: 2nd Request: SCSIPORT.SYS 0x50 BSD
    ... I did not delete the wrong controllers in Windows. ... Boot order is set in the BIOS and after disabling the onboard SCSI ... controller in BIOS the boot device was still set to the Adaptec ... Once I re-enabled the onboard SCSI controller in BIOS, ...
    (microsoft.public.win2000.hardware)
Loading