Date: Tue, 29 Jun 2004 23:00:41 GMT From: "Alexander Weisel" <alex@schubduese.de> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/68313: Installing/Updating to Release 5.2.1 destroys RAID on Promise Controllers (i386, ACPI, SMP) Message-ID: <200406292300.i5TN0fde014652@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/68313; it has been noted by GNATS. From: "Alexander Weisel" <alex@schubduese.de> To: <freebsd-gnats-submit@FreeBSD.org> Cc: Subject: Re: kern/68313: Installing/Updating to Release 5.2.1 destroys RAID on Promise Controllers (i386, ACPI, SMP) Date: Tue, 29 Jun 2004 22:57:10 -0000 I did some research on the problem - i found out that one of my disks shows up an ICRC error. I'd love to provide some output, but i successfully destroyed my working system trying to make boot the 5.2.1 Release. Here are some hints on what happened: While booting on 5.1, i see some ICRC errors on one device. There are a few retries and then the device is falling back to PIO4. All is working normally. I upgraded to 5.2.1 kernel via source and tried to boot it. As far as i can remember, some CRC errors showed up too. But instead of falling back to PIO, i can remeber an 'ABORT' message and then immediately the message 'ERROR: array corrupt' and then 'device temporarily not available'. The raid configuration is destroyed at this moment. There seems to be a serious problem in error handling in such a case. I can accept to switch cabling/harddisk, but i think that freebsd should not run amok and kill raid configurations. Same raid config is working with very good performance and without any problems under windows2k, FBSD 4.10 and 5.1 (i only see the ICRC error on 5.1). So i doubt that there is a real problem with the hardware.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200406292300.i5TN0fde014652>