(noperiph:sym0:0:-1:-1):SCSI BUS reset delivered. -- HP Netserver LH3r

From: Etienne Ledoux (etienne_at_unix.za.org)
Date: 06/25/03

  • Next message: Matthew Seaman: "Re: (noperiph:sym0:0:-1:-1):SCSI BUS reset delivered. -- HP Netserver LH3r" 
    To: freebsd-stable@freebsd.org, questions@freebsd.org
Date: Wed, 25 Jun 2003 16:14:07 +0200

    Ok i fixed my subject a bit.

    Well I've tried FreeBSD (4.4, 4.8, 5.0), SuSE Linux 8.1, Redhat 9.0.
    All these operating systems fail to detect the hdd and when trying to load the
    scsi drivers for it it gives timeout errors (redhat & suse).

    FreeBSD gives: (noperiph:sym0:0:-1:-1):SCSI BUS reset delivered.
                            (noperiph:sym1:0:-1:-1):SCSI BUS reset delivered.

    This made me think that it might be a problem with the hardware configuration.
    I've got two exactly the same machines. Both give exactly the same error.

    I changed the scsi configuration on one machine. Trying different settings. No
    change. (except for the few times where my changes disabled the hdd and it
    couldn't find any OS). I installed the FreeBSD putting the drives into
    another HP server (which btw also happens to be a Netserver LH3r), and
    putting them back afterwards. Booting of the cd gives the same error.

    What does the error: "(noperiph:sym0:0:-1:-1):SCSI BUS reset delivered"
    actually mean ? What is FreeBSD actually complaining about ?

    I would assume that these HP servers (we have inhereted a few of them) would
    use the same type of hardware. The server I'm trying to install this on is a
    HP cluster server which has an external Raid Storage (which is currently
    disconnected from the servers). The servers themselves are HP Netserver
    LH3r's. The standalone server I used to do the install on is also a HP
    Netserver LH3r. The only noticeable difference between the standalone server
    and the server in the cluster is that the standalone server has a single
    processor and the cluster servers are dual processor. I've removed the SCSI
    card which is used to connect the server to the external Raid Storage and the
    installation still gives the same error.

    Now I could start to think that the hardware might be busted, but these
    servers were still running Redhat 7.1 a few days ago.

    If I want to try using the NCR driver (mentioned below), How would I go about
    doing that ?
    What else could I try.

    Maybe if I understood the error((noperiph:sym0:0:-1:-1):SCSI BUS reset
    delivered) a little better, I could try a few other things.

    hints/tips/anything appreciated.

    Another weird thing I noticed:
    - While another guy was installing FreeBSD on an HP pizzabox he also got this
    error: "(noperiph:sym0:0:-1:-1):SCSI BUS reset delivered", but it continued
    to boot and he was able to install the box. hmmmmm ?

    e.

    On Tuesday 24 June 2003 20:23, you wrote:
    > On 2003-06-24 15:33 +0200, Etienne Ledoux <etiennel@datapro.co.za> wrote:
    > > Greetings
    > >
    > > I'm trying to install FreeBSD on a HP Cluster Server. But when I boot
    > > with the CD's ( 4.4, 4.8 & 5.0 ), it will boot all the way upto "Wait 15
    > > seconds for SCSI devices to settle" and then it immedialty give the
    > > following message:
    > >
    > > (noperiph:sym0:0:-1:-1):SCSI BUS reset delivered.
    > > (noperiph:sym1:0:-1:-1):SCSI BUS reset delivered.
    > >
    > > After this the machine is basically unresponsive/dead.
    > >
    > > Any idea what could be causing this and what I could do to fix it ?
    >
    > Depending on the SCSI chip you may want to try the NCR driver
    > instead of the SYM driver. (The SYM driver is an enhanced
    > version of the NCR driver, but I've heard before, that the NCR
    > driver may work in (the extremely few) situation where the SYM
    > driver fails).
    >
    > Please send a boot message log and complete error messages and
    > I'll see whether they help ...
    >
    > Regards, STefan

    _______________________________________________
    freebsd-stable@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"

  • Next message: Matthew Seaman: "Re: (noperiph:sym0:0:-1:-1):SCSI BUS reset delivered. -- HP Netserver LH3r"

    Relevant Pages

    • Re: Shared Printer
      ... Brother HL1430 can not used on the SBS server box and client workstations. ... driver must be installed on the computers. ... If you try to install the drivers from the Brother CD-ROM into a Windows ...
      (microsoft.public.windows.server.sbs)
    • Re: Printing issue in XP over Remote Desktop VPN
      ... You will need to install the driver on the remote machine only if you are ... So your saying I should install the print drivers on the machine I'm ... Look for Terminal Server event ... Print Terminal Server Applications to Local Printer ...
      (microsoft.public.windowsxp.print_fax)
    • Re: Printing issue in XP over Remote Desktop VPN
      ... I am trying to remote to another XP machine. ... So your saying I should install the print drivers on the machine I'm ... Look for Terminal Server event ... a driver that is not available on the Windows 2000 Server. ...
      (microsoft.public.windowsxp.print_fax)
    • Re: Dude !! Never Buy a Dell !!!
      ... Sounds like when you "converted" from Home to Server, you didn't install the ... go to Dell site, download the Driver, and then when installing the Driver, ... it complains, that the CD drive is missing, Darn, thing.. ...
      (microsoft.public.windows.server.general)
    • Re: Server 2003 32-bit Queue with XP Pro 64-bit
      ... server OS and was successful in adding the drivers for the printer to the ... now when I go to the x64 XP Pro ... The driver files you are installing should also be engineerd for Server 2003 ... open the inf for the device driver you are attempting to install. ...
      (microsoft.public.windowsxp.print_fax)