I may be wrong, but it is my understanding that the 'Halt on errors' in the
system BIOS is for while the system is coming up (when the BIOS is coming
up). These are errors like when you have no video card, no keyboard, or
harddrive errors). Setting 'halt on errors' to 'none' will usuallly allow a
system to come up if it has no keyboard attached (or is attached to a
keyboard switch that does not emulate the keyboard port) or probably the
most common reason related to raid is that you want the system to still come
up when a drive fails on a raid system -- if it is not set, the BIOS will
not allow the system to boot when a drive has failed (which is contrary to
the point of RAID).
HTH,
--Bryan
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of root
> Sent: Monday, January 17, 2000 12:02 AM
> To: Eric Enockson
> Cc: [EMAIL PROTECTED]
> Subject: Re: loose cables on external raid device
>
>
> Eric Enockson wrote:
>
> >
> > hello, I have an external raid scsi device with
> > a loose cable. It would come loose and things would freeze
> > up on the machine, and then i would push it back in and
> > the system would come back. Now however i get somewhat
> > random operating system crashes. At least i think they're o/s
> > crashes, but they aren't the usual kernel crashes with messages
> > sent to the console. The machine just freezes up and won't except
> > any input. I check all the cables and none are loose.
> > I am wondering if having cables being taken off and put
> > back on for a running system like this will corrupt random files
> > or cause some general weirdness.
>
> Hello Eric,
>
> is it possible that the BIOS switch "Halt on all errors" is
> enabled? Try
> to experiment a bit with this, propably you will get other hang up
> messages then.
>
> Regards Wolfgang Magin
>
