Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem RESOLVED
On Wed, 2005-08-31 at 17:26, Robert Slade wrote: > On Wed, 2005-08-31 at 00:21, Vizion wrote: > > On Tuesday 30 August 2005 13:31, the author Robert Slade contributed to > > the > > dialogue on- > > Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: > > > > >On Tue, 2005-08-30 at 21:20, Vizion wrote: > > >> On Tuesday 30 August 2005 13:22, the author Robert Slade contributed to > > >> the dialogue on- > > >> > > >> Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: > > >> >On Tue, 2005-08-30 at 20:10, Vizion wrote: > > >> >> On Tuesday 30 August 2005 12:05, the author Robert Slade contributed > > >> >> to the dialogue on- > > >> >> > > >> >> Proliant 5000 sever Fbsd 5.4 (re)boot problem: > > >> >> >Hiya, > > >> >> > > > >> >> >I've been working on this beasty on and off for some time. It's a > > >> >> >Quad > > >> >> >processor 1 Gbyte of memory and 5 scsi drives using the 2p raid > > >> >> >controller setup as 2 raid arrays + 1 spare. > > >> >> > > > >> >> >The machine works fine with 5.4 release #0 with the supplied generic > > >> >> >kernel. > > >> >> > > > >> >> >The problem(s) I have been having are: > > >> >> > > > >> >> >1. When I recompiled the Kernel with SMP support, I get random > > >> >> > reboots. It also fails to boot sometimes failing at the point after > > >> >> > waiting for the scsi drives to settle. I get some error codes and > > >> >> > Fbsd fails to find the boot device. > > >> >> > > > >> >> >2. I CVSuped to 5.4 release #2 and recompiled the Kernel with SMP > > >> >> >support. This does to boot at all. It gets as far as the waiting 15s > > >> >> > for scsi devices to settle, then (appears to) reset the scsi > > >> >> > controller and immediately tries to access the drives (does not > > >> >> > wait). I have tried recompiling with scsi_delay set to 3 (30s) > > >> >> > with no change. > > >> >> > > > >> >> >I have checked dmesg and message logs but there is nothing related to > > >> >> >the problem(s) there. > > >> >> > > > >> >> >I have gone back to the 5.4 release #0 single processor kernel for > > >> >> >now > > >> >> >which is a shame as the machine is slow without the multi processor > > >> >> >support. > > >> >> > > > >> >> >The only thing out of the ordinary I have noted is a tx underunn -- > > >> >> >increasing threshold to 512 bytes message which appears related to > > >> >> >running kde remotely via vncserver and tinync. > > >> >> > > > >> >> >Any ideas, I can send conf files etc if needed. > > >> >> > > > >> >> >Thanks > > >> >> > > > >> >> >Rob > > >> >> > > >> >> What are your bios setting? > > >> >> My guess is that you have not made the right setting using the > > >> >> siftware > > >> >> and configuration utilities > > >> >> david > > >> > > > >> >David, > > >> > > > >> >Thanks. The BIOS setting appear ok - OS type is set as UNIX (Small disk > > >> >geometry) and the machine passes all the diagnostics. > > >> > > > >> >Rob > > >> > > >> I cannot remember - but I have sneaking notion that you need to set it as > > >> linux > > > > > >Tried that too :-). I think that the problem is that with 5.4 release #2 > > >it is trying to access that scsi drives immediately then inducing the > > >kernel panic for 15s. Rather than inducing the panic 1st. > > > > > >Rob > > > > > > > Did you follow my suggestion and search the HP resources with freebsd and > > your > > model. I have had the same problem myself I am pretty certain it was fixed > > by changes using the Proliant Essrntial Foundation Pack.. but my memory may > > not be accurate. > > david > > David, > > I did update the system and controller ROMs whne the machine was running > windows. I have been on the HP site and as far as I can tell I have the > latest. > > Rob For the record, lucking under SCO Unix is an update to the Raid Controller firmware which fixes the problem. You do need Dos or Windows to create the self booting disks. Only disk 1 is needed for the SMART 2P controller. The update appears to be only listed under SC Unix though. Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem
On Wed, 2005-08-31 at 00:21, Vizion wrote: > On Tuesday 30 August 2005 13:31, the author Robert Slade contributed to the > dialogue on- > Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: > > >On Tue, 2005-08-30 at 21:20, Vizion wrote: > >> On Tuesday 30 August 2005 13:22, the author Robert Slade contributed to > >> the dialogue on- > >> > >> Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: > >> >On Tue, 2005-08-30 at 20:10, Vizion wrote: > >> >> On Tuesday 30 August 2005 12:05, the author Robert Slade contributed > >> >> to the dialogue on- > >> >> > >> >> Proliant 5000 sever Fbsd 5.4 (re)boot problem: > >> >> >Hiya, > >> >> > > >> >> >I've been working on this beasty on and off for some time. It's a Quad > >> >> >processor 1 Gbyte of memory and 5 scsi drives using the 2p raid > >> >> >controller setup as 2 raid arrays + 1 spare. > >> >> > > >> >> >The machine works fine with 5.4 release #0 with the supplied generic > >> >> >kernel. > >> >> > > >> >> >The problem(s) I have been having are: > >> >> > > >> >> >1. When I recompiled the Kernel with SMP support, I get random > >> >> > reboots. It also fails to boot sometimes failing at the point after > >> >> > waiting for the scsi drives to settle. I get some error codes and > >> >> > Fbsd fails to find the boot device. > >> >> > > >> >> >2. I CVSuped to 5.4 release #2 and recompiled the Kernel with SMP > >> >> >support. This does to boot at all. It gets as far as the waiting 15s > >> >> > for scsi devices to settle, then (appears to) reset the scsi > >> >> > controller and immediately tries to access the drives (does not > >> >> > wait). I have tried recompiling with scsi_delay set to 3 (30s) > >> >> > with no change. > >> >> > > >> >> >I have checked dmesg and message logs but there is nothing related to > >> >> >the problem(s) there. > >> >> > > >> >> >I have gone back to the 5.4 release #0 single processor kernel for now > >> >> >which is a shame as the machine is slow without the multi processor > >> >> >support. > >> >> > > >> >> >The only thing out of the ordinary I have noted is a tx underunn -- > >> >> >increasing threshold to 512 bytes message which appears related to > >> >> >running kde remotely via vncserver and tinync. > >> >> > > >> >> >Any ideas, I can send conf files etc if needed. > >> >> > > >> >> >Thanks > >> >> > > >> >> >Rob > >> >> > >> >> What are your bios setting? > >> >> My guess is that you have not made the right setting using the siftware > >> >> and configuration utilities > >> >> david > >> > > >> >David, > >> > > >> >Thanks. The BIOS setting appear ok - OS type is set as UNIX (Small disk > >> >geometry) and the machine passes all the diagnostics. > >> > > >> >Rob > >> > >> I cannot remember - but I have sneaking notion that you need to set it as > >> linux > > > >Tried that too :-). I think that the problem is that with 5.4 release #2 > >it is trying to access that scsi drives immediately then inducing the > >kernel panic for 15s. Rather than inducing the panic 1st. > > > >Rob > > > > Did you follow my suggestion and search the HP resources with freebsd and > your > model. I have had the same problem myself I am pretty certain it was fixed > by changes using the Proliant Essrntial Foundation Pack.. but my memory may > not be accurate. > david David, I did update the system and controller ROMs whne the machine was running windows. I have been on the HP site and as far as I can tell I have the latest. Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Proliant 5000 sever Fbsd 5.4 (re)boot problem
On Wed, 2005-08-31 at 07:01, Ted Mittelstaedt wrote: > >-Original Message- > >From: [EMAIL PROTECTED] > >[mailto:[EMAIL PROTECTED] Behalf Of Vizion > >Sent: Tuesday, August 30, 2005 4:21 PM > >To: freebsd-questions@freebsd.org > >Cc: Robert Slade > >Subject: Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem > > > > > >Did you follow my suggestion and search the HP resources with > >freebsd and your > >model. I have had the same problem myself I am pretty certain > >it was fixed > >by changes using the Proliant Essrntial Foundation Pack.. but > >my memory may > >not be accurate. > > Yeah, what a awful design! You have to load an entire full-blown > Windows install just to update the microcode in the SCSI raid > controller. I saw they had done this the last time I setup a > Compaq server and nearly barfed. > > You can still firmware update the machines' BIOS with a bootable > floppy but that's it. To get anything else, helo Windows! > > At least you get the satisfaction of scratching it off once you've > done the update. > > Ted > -- Thanks Ted & David, The HP site does not turn up anything about FreeBSD and the Proliant. However I have found out that the Smart-2 family controllers do have an update. There is a Linux version of the flash utility so I'll try that first. Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Proliant 5000 sever Fbsd 5.4 (re)boot problem
>-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] Behalf Of Vizion >Sent: Tuesday, August 30, 2005 4:21 PM >To: freebsd-questions@freebsd.org >Cc: Robert Slade >Subject: Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem > > >Did you follow my suggestion and search the HP resources with >freebsd and your >model. I have had the same problem myself I am pretty certain >it was fixed >by changes using the Proliant Essrntial Foundation Pack.. but >my memory may >not be accurate. Yeah, what a awful design! You have to load an entire full-blown Windows install just to update the microcode in the SCSI raid controller. I saw they had done this the last time I setup a Compaq server and nearly barfed. You can still firmware update the machines' BIOS with a bootable floppy but that's it. To get anything else, helo Windows! At least you get the satisfaction of scratching it off once you've done the update. Ted -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.10.17/85 - Release Date: 8/30/2005 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem
On Tuesday 30 August 2005 16:21, the author Vizion contributed to the dialogue on- Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: >On Tuesday 30 August 2005 13:31, the author Robert Slade contributed to the >dialogue on- > > Is this any use: http://ezine.daemonnews.org/23/cpqraid.html -- 40 yrs navigating and computing in blue waters. English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after completing engineroom refit. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem
On Tuesday 30 August 2005 13:31, the author Robert Slade contributed to the dialogue on- Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: >On Tue, 2005-08-30 at 21:20, Vizion wrote: >> On Tuesday 30 August 2005 13:22, the author Robert Slade contributed to >> the dialogue on- >> >> Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: >> >On Tue, 2005-08-30 at 20:10, Vizion wrote: >> >> On Tuesday 30 August 2005 12:05, the author Robert Slade contributed >> >> to the dialogue on- >> >> >> >> Proliant 5000 sever Fbsd 5.4 (re)boot problem: >> >> >Hiya, >> >> > >> >> >I've been working on this beasty on and off for some time. It's a Quad >> >> >processor 1 Gbyte of memory and 5 scsi drives using the 2p raid >> >> >controller setup as 2 raid arrays + 1 spare. >> >> > >> >> >The machine works fine with 5.4 release #0 with the supplied generic >> >> >kernel. >> >> > >> >> >The problem(s) I have been having are: >> >> > >> >> >1. When I recompiled the Kernel with SMP support, I get random >> >> > reboots. It also fails to boot sometimes failing at the point after >> >> > waiting for the scsi drives to settle. I get some error codes and >> >> > Fbsd fails to find the boot device. >> >> > >> >> >2. I CVSuped to 5.4 release #2 and recompiled the Kernel with SMP >> >> >support. This does to boot at all. It gets as far as the waiting 15s >> >> > for scsi devices to settle, then (appears to) reset the scsi >> >> > controller and immediately tries to access the drives (does not >> >> > wait). I have tried recompiling with scsi_delay set to 3 (30s) >> >> > with no change. >> >> > >> >> >I have checked dmesg and message logs but there is nothing related to >> >> >the problem(s) there. >> >> > >> >> >I have gone back to the 5.4 release #0 single processor kernel for now >> >> >which is a shame as the machine is slow without the multi processor >> >> >support. >> >> > >> >> >The only thing out of the ordinary I have noted is a tx underunn -- >> >> >increasing threshold to 512 bytes message which appears related to >> >> >running kde remotely via vncserver and tinync. >> >> > >> >> >Any ideas, I can send conf files etc if needed. >> >> > >> >> >Thanks >> >> > >> >> >Rob >> >> >> >> What are your bios setting? >> >> My guess is that you have not made the right setting using the siftware >> >> and configuration utilities >> >> david >> > >> >David, >> > >> >Thanks. The BIOS setting appear ok - OS type is set as UNIX (Small disk >> >geometry) and the machine passes all the diagnostics. >> > >> >Rob >> >> I cannot remember - but I have sneaking notion that you need to set it as >> linux > >Tried that too :-). I think that the problem is that with 5.4 release #2 >it is trying to access that scsi drives immediately then inducing the >kernel panic for 15s. Rather than inducing the panic 1st. > >Rob > Did you follow my suggestion and search the HP resources with freebsd and your model. I have had the same problem myself I am pretty certain it was fixed by changes using the Proliant Essrntial Foundation Pack.. but my memory may not be accurate. david >___ >freebsd-questions@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-questions >To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- 40 yrs navigating and computing in blue waters. English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after completing engineroom refit. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem
On Tue, 2005-08-30 at 21:20, Vizion wrote: > On Tuesday 30 August 2005 13:22, the author Robert Slade contributed to the > dialogue on- > Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: > > >On Tue, 2005-08-30 at 20:10, Vizion wrote: > >> On Tuesday 30 August 2005 12:05, the author Robert Slade contributed to > >> the dialogue on- > >> > >> Proliant 5000 sever Fbsd 5.4 (re)boot problem: > >> >Hiya, > >> > > >> >I've been working on this beasty on and off for some time. It's a Quad > >> >processor 1 Gbyte of memory and 5 scsi drives using the 2p raid > >> >controller setup as 2 raid arrays + 1 spare. > >> > > >> >The machine works fine with 5.4 release #0 with the supplied generic > >> >kernel. > >> > > >> >The problem(s) I have been having are: > >> > > >> >1. When I recompiled the Kernel with SMP support, I get random reboots. > >> >It also fails to boot sometimes failing at the point after waiting for > >> >the scsi drives to settle. I get some error codes and Fbsd fails to find > >> >the boot device. > >> > > >> >2. I CVSuped to 5.4 release #2 and recompiled the Kernel with SMP > >> >support. This does to boot at all. It gets as far as the waiting 15s for > >> >scsi devices to settle, then (appears to) reset the scsi controller and > >> >immediately tries to access the drives (does not wait). I have tried > >> >recompiling with scsi_delay set to 3 (30s) with no change. > >> > > >> >I have checked dmesg and message logs but there is nothing related to > >> >the problem(s) there. > >> > > >> >I have gone back to the 5.4 release #0 single processor kernel for now > >> >which is a shame as the machine is slow without the multi processor > >> >support. > >> > > >> >The only thing out of the ordinary I have noted is a tx underunn -- > >> >increasing threshold to 512 bytes message which appears related to > >> >running kde remotely via vncserver and tinync. > >> > > >> >Any ideas, I can send conf files etc if needed. > >> > > >> >Thanks > >> > > >> >Rob > >> > >> What are your bios setting? > >> My guess is that you have not made the right setting using the siftware > >> and configuration utilities > >> david > > > >David, > > > >Thanks. The BIOS setting appear ok - OS type is set as UNIX (Small disk > >geometry) and the machine passes all the diagnostics. > > > >Rob > > I cannot remember - but I have sneaking notion that you need to set it as > linux Tried that too :-). I think that the problem is that with 5.4 release #2 it is trying to access that scsi drives immediately then inducing the kernel panic for 15s. Rather than inducing the panic 1st. Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem
On Tue, 2005-08-30 at 20:10, Vizion wrote: > On Tuesday 30 August 2005 12:05, the author Robert Slade contributed to the > dialogue on- > Proliant 5000 sever Fbsd 5.4 (re)boot problem: > > >Hiya, > > > >I've been working on this beasty on and off for some time. It's a Quad > >processor 1 Gbyte of memory and 5 scsi drives using the 2p raid > >controller setup as 2 raid arrays + 1 spare. > > > >The machine works fine with 5.4 release #0 with the supplied generic > >kernel. > > > >The problem(s) I have been having are: > > > >1. When I recompiled the Kernel with SMP support, I get random reboots. > >It also fails to boot sometimes failing at the point after waiting for > >the scsi drives to settle. I get some error codes and Fbsd fails to find > >the boot device. > > > >2. I CVSuped to 5.4 release #2 and recompiled the Kernel with SMP > >support. This does to boot at all. It gets as far as the waiting 15s for > >scsi devices to settle, then (appears to) reset the scsi controller and > >immediately tries to access the drives (does not wait). I have tried > >recompiling with scsi_delay set to 3 (30s) with no change. > > > >I have checked dmesg and message logs but there is nothing related to > >the problem(s) there. > > > >I have gone back to the 5.4 release #0 single processor kernel for now > >which is a shame as the machine is slow without the multi processor > >support. > > > >The only thing out of the ordinary I have noted is a tx underunn -- > >increasing threshold to 512 bytes message which appears related to > >running kde remotely via vncserver and tinync. > > > >Any ideas, I can send conf files etc if needed. > > > >Thanks > > > >Rob > > > What are your bios setting? > My guess is that you have not made the right setting using the siftware and > configuration utilities > david David, Thanks. The BIOS setting appear ok - OS type is set as UNIX (Small disk geometry) and the machine passes all the diagnostics. Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem
On Tuesday 30 August 2005 12:05, the author Robert Slade contributed to the dialogue on- Proliant 5000 sever Fbsd 5.4 (re)boot problem: >Hiya, > >I've been working on this beasty on and off for some time. It's a Quad >processor 1 Gbyte of memory and 5 scsi drives using the 2p raid >controller setup as 2 raid arrays + 1 spare. > >The machine works fine with 5.4 release #0 with the supplied generic >kernel. > >The problem(s) I have been having are: > >1. When I recompiled the Kernel with SMP support, I get random reboots. >It also fails to boot sometimes failing at the point after waiting for >the scsi drives to settle. I get some error codes and Fbsd fails to find >the boot device. > >2. I CVSuped to 5.4 release #2 and recompiled the Kernel with SMP >support. This does to boot at all. It gets as far as the waiting 15s for >scsi devices to settle, then (appears to) reset the scsi controller and >immediately tries to access the drives (does not wait). I have tried >recompiling with scsi_delay set to 3 (30s) with no change. > >I have checked dmesg and message logs but there is nothing related to >the problem(s) there. > >I have gone back to the 5.4 release #0 single processor kernel for now >which is a shame as the machine is slow without the multi processor >support. > >The only thing out of the ordinary I have noted is a tx underunn -- >increasing threshold to 512 bytes message which appears related to >running kde remotely via vncserver and tinync. > >Any ideas, I can send conf files etc if needed. > >Thanks > >Rob > What are your bios setting? My guess is that you have not made the right setting using the siftware and configuration utilities david -- 40 yrs navigating and computing in blue waters. English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after completing engineroom refit. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
