LC2000-U3 scsiport.sys stop error during boot with 220mx jukebox.

[noka]

LC2000-Ultra 3 w/NetRAID 1M
Win2000 SP3
(2) 9.1GB (9100mx) standalone drives
Want to replace standalones w/220mx jukebox

System boots and works fine with the two standalone drives (connected in series). Not using NetRAID SCSI but another external SCSI connector (separate SCSI bus) that connects to on-board SCSI.

If the two standalone drives are disconnected and the 220mx jukebox is connected, during bootup there is a Blue Screen stop error indicating IRQL_NOT_LESS_OR_EQUAL, and SCSIPORT.sys. At this time, I have no further details on the BSOD data.

I know the standalone drives are fast/narrow SCSI and the jukebox (externally) is wide. Do they both use SCSIPORT.sys? Because it is strange that the standalone drives allow the system to boot and run perfectly fine.

Another thing. The jukebox was brand new (firmware 5.14) and another one did the same thing.

LC2000-U3 BIOS is 4.06.04.RM.

NetRAID BIOS is G.xx.xx (can't remember now). Tried to upgrade to H.02.01 but it failed. So we just rebooted system. Maybe unrelated problem.

Anybody have a clue?

[Eugeny Brychkov]

In addition to MO drive, which has SCSI Id and seen by controller jukebox has another non-standard device, autochanger (robot) which also has SCSI Id and seend by controller. Raid controllers DO NOT support autochanger devices (support disk devices only). This is the first idea. The second is that there's a) SCSI Id conflict (check juke's internal devices SCSI Ids), b) SCSI bus in unterminated OR terminated with incorrect terminator (SE with SE term and LVD with LVD term). If SCSI controller's and juke's interfaces do not match (SE and LVD) then you may need SCSI adapter cable and tune SCSI card's bios to work with juke
Eugeny

[noka]

We know the LC2000-Ultra 3 and 220mx work together (other systems work). The terminator used is the one that comes with the 220mx standard. The SCSI ID's are AC=4, DR1=5 and DR2=6. But we also tried the default 3,4,5, just to be sure. No conflicts as nothing else is on this SCSI bus, except the on-board SCSI controller. We are not using the RAID controller for jukebox.

[Eugeny Brychkov]

This makes things easier. Then problem either in software (drivers) or hardware.
Please compare SCSI drivers to that working machine. Check juke's config to be the same as on that working one. When powering server up make sure there're no WORM disks in the MO drives.
Finally, try connecting this juke to that working server. If it will bluescreen, then problem is in juke and cables/teminator (if you will not replace them)
Eugeny

[noka]

- SCSI drivers "should" be the same but will check. Quite frankly, I'm not sure what driver we should be using.

- Juke's config is factory defaults, except for SCSI ID's mentioned above.

- No WORM media, we don't use WORM.

- Tried 2nd jukebox on same server (new cable/terminator); same problem. Want to try one of the jukes on working server but it's a bit of a logistical problem. Working pair is a few thousand miles away!
:-(

[meloni]

ji,
in the bios of the lc2000, be sure to have selected the correct boot order(HDD), and also the correct boot device, in fact you have to select" pciRaid controller" as first.
also I would suggest to check the internal scsi cable, and to disable domain validation in the scsi bios and fix the scsi transfer. try aslo selecting 8 bit communication instead of wide.

[noka]

We found incorrect SCSI driver. Thanks to all who responded with advice!