Hi,
 
In fact, I don't really believe in a hardware problem like a false contact on a temp sensor.
I also noticed that a boot time, it stays blocked at "waiting 15s for scsi device to settle" during arround 10 min what would indicate that it's more an OS / driver problem.
In my previous mail, I indicated that it runs under 4.2-stable, in fact it was 4.2-release. I updated the system to 4.3-rc2, which has a mly driver code 5 month older (2001-03) than on 4.2-release (2000-10). I'm waiting to see what will happen.
 
thanx for your help
 
--
-------------------------------
-->
[EMAIL PROTECTED]
-------------------------------
----- Original Message -----
From: "Lawrence Sica`" <[EMAIL PROTECTED]>
To: "julien" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; "cristophe baillon" <[EMAIL PROTECTED]>
Sent: Tuesday, May 22, 2001 6:52 PM
Subject: Re: mylex raid card problem on 4.2-stable

> At 12:34 PM 5/22/2001 +0200, julien wrote:
> >Hi all,
> >
> >We have a quite disapointing problem with a mylex 170 card, which causes
> >a system crash every 6 hours.
> >This card is installed in a VA Linux 2240 with 4 18GB drives, configured
> >in a single RAID 5 pack, running a FreeBSD 4.2-stable system.
> >We have to notice that this system ran during 4 months without any
> >problem, and that we have many other servers running this configuration
> >without any kind of problem.
> >
> >The kernel output says :
> >mly0: enclosure 1 temperature sensor 0 failed
> >mly0: enclosure 1 temperature sensor 0 ok
> >mly0: enclosure 1 temperature sensor 0 failed
> >mly0: enclosure 1 temperature sensor 0 ok
>
> I don't know much about the mylex cards but have you checked the temp
> sensor in the enclosure it mentions?  Have you checked to see if maybe it's
> faulty or something?
>
>
> --Larry
>
> Lawrence Sica
> -------------------------------------------------------------
> Systems Administrator - Interactivate, Inc.
>
[EMAIL PROTECTED]
> http://www.interactivate.com
> --------------------------------------------------------------
>
>
> To Unsubscribe: send mail to
[EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
>

Reply via email to