From owner-freebsd-questions Tue Jan 19 08:42:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA07204 for freebsd-questions-outgoing; Tue, 19 Jan 1999 08:42:53 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from snowcrest.net (mtshasta.snowcrest.net [207.201.33.195]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA07188 for ; Tue, 19 Jan 1999 08:42:50 -0800 (PST) (envelope-from djewett@snowcrest.net) Received: from ws2600 (ppp499.snowcrest.net [209.148.37.147]) by snowcrest.net (8.8.5/8.8.5) with SMTP id IAA06327 for ; Tue, 19 Jan 1999 08:42:42 -0800 (PST) Message-ID: <01f601be43ca$984e36b0$0afea8c0@ws2600> From: "Derek Jewett" Cc: Subject: Re: FreeBSD and the Proliant 1600 HELP!!! Date: Tue, 19 Jan 1999 08:41:41 -0800 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wanted to thank the folks that replied... Turns out it WAS just a controller problem.... I slapped fbsd on our other 1600 and it worked fine, even after running the smartstart garb. Seems like there is a problem with running the smartstart on some systems. I plan to call compaq to see what happened. I have not tried to run it on my 3000's or 5000. and they use the same controller! -----Original Message----- From: Karl Pielorz To: Derek Jewett Cc: questions@FreeBSD.ORG Date: Saturday, January 16, 1999 4:39 PM Subject: Re: FreeBSD and the Proliant 1600 HELP!!! > > >Greg Lehey wrote: >> >> On Saturday, 16 January 1999 at 16:21:17 -0800, Derek Jewett wrote: >> > Is anyone else running fbsd on a proliant 1600 box..? Our has been running >> > for a few weeks now with no problems. Until the other day I ran the >> > smartstart CD on it for the first time since it has always displayed a >> > configuration error at bootup. Now after running the smartstart CD the >> > system bombs at "waiting for SCSI devices to settle". it gives me an ncr0:0: >> > ERROR and several errors after this that I have been unable to capture, but >> > the problem appears to be with the ncr/symbios logic SCSI adapter. >> >> Are you sure the host adaptor hasn't just died? > >The previous 'config error' would be handy, we also have a machine that >displays a Config Error (one of those 'we'll get round to fixing it' types of >errors)... A recent install of -current on that machine (an AST with embedded >Symbios SCSI) nets, > >Jan 14 12:14:43 magpie /kernel: Waiting 15 seconds for SCSI devices to settle >Jan 14 12:14:43 magpie /kernel: (probe6:ncr0:0:6:0): COMMAND FAILED (6 ff) >@0xf070fa00. >Jan 14 12:14:43 magpie /kernel: (probe5:ncr0:0:5:0): COMMAND FAILED (6 ff) >@0xf070e000. >Jan 14 12:14:43 magpie /kernel: (probe4:ncr0:0:4:0): COMMAND FAILED (6 ff) >@0xf070e600. >Jan 14 12:14:44 magpie /kernel: (probe3:ncr0:0:3:0): COMMAND FAILED (6 ff) >@0xf070ec00. >Jan 14 12:14:44 magpie /kernel: (probe2:ncr0:0:2:0): COMMAND FAILED (6 ff) >@0xf070c200. >Jan 14 12:14:44 magpie /kernel: (probe1:ncr0:0:1:0): COMMAND FAILED (6 ff) >@0xf070c800. >Jan 14 12:14:44 magpie /kernel: (probe0:ncr0:0:0:0): COMMAND FAILED (6 ff) >@0xf070ce00. > >At boot-time, but continues OK... > >What exactly does it display as an 'ncr0:0' error? > >-Kp > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message