From nobody@FreeBSD.org  Fri Jun 25 10:40:55 2004
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id C79E416A4CE
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 25 Jun 2004 10:40:55 +0000 (GMT)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A895843D2D
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 25 Jun 2004 10:40:55 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.11/8.12.11) with ESMTP id i5PAcwV3036778
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 25 Jun 2004 10:38:58 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.11/8.12.11/Submit) id i5PAcwM4036776;
	Fri, 25 Jun 2004 10:38:58 GMT
	(envelope-from nobody)
Message-Id: <200406251038.i5PAcwM4036776@www.freebsd.org>
Date: Fri, 25 Jun 2004 10:38:58 GMT
From: Alexander Weisel <alex@schubduese.de>
To: freebsd-gnats-submit@FreeBSD.org
Subject: Installing/Updating to Release 5.2.1 destroys RAID on Promise Controllers (i386,  ACPI, SMP)
X-Send-Pr-Version: www-2.3

>Number:         68313
>Category:       kern
>Synopsis:       Installing/Updating to Release 5.2.1 destroys RAID on Promise Controllers (i386,  ACPI, SMP)
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jun 25 10:50:29 GMT 2004
>Closed-Date:    Tue Aug 24 17:22:52 GMT 2004
>Last-Modified:  Tue Aug 24 17:22:52 GMT 2004
>Originator:     Alexander Weisel
>Release:        5.2.1
>Organization:
explido Software GmbH&CoKG
>Environment:
FreeBSD 5.2.1-RELEASE FreeBSD 5.2.1-RELEASE #0: Mon Feb 23 20:45:55 GMT 2004 root@wv1.btc.adaptec.com:/usr/obj/usr/src/sys/GENERIC i386

Standard boot kernel of ISO image.
>Description:
When trying to install FreeBSD 5.2.1 via CD, system shuts down with a SIG 11 panic message. After rebooting system comes up with destroyed raid configuration.
System is a Tyan S2466 with two Athlon MP and Promise Fasttrak TX2000, with two raids (2x2 drives raid 0) configured. First raid has a Windows installation, on the second one i want to install FreeBSD.

The magic moment is during normal setup via sysinstall. Right after configuring the disk slices and after 'newfs' is executed, i can see the 'copying files' screen come up for a second and a messagebox, too, with the message 'SIG 11 - Automatic Shutdown'. After reboot, as said, raid is destroyed and must be rebuilt.

Further problem: When trying to do a binary upgrade from a Release 5.1 installation (which is working btw.) i get a kernel panic with message 'lost mount' right at the point when system is 'checking file system integrity' after choosing/making new slices.
>How-To-Repeat:
Fresh installation:
1. Insert installation CD (ISO image from FTP server)
2. Boot from CD
3. Make sure, ACPI is on and SMP is activated, too
4. Choose normal installation
5. Set up disk slices, package configuration and so on
6. Choose any boot loader config, doesn't matter
7. Hit ok to start making filesystems
8. When system tries to copy files, system automatically reboots and raid is destroyed.

Update:
1. Make sure you have a running 5.1 Release
2. Boot from 5.2.1 install CD.
3. Choose 'binary upgrade'
4. Choose existing slices and mountpoints.
5. When system says 'checking filesystem integrity' right after accepting configuration, kernel panics with message 'lost mount'.
6. As above, aber hitting reset button system comes up with destroyed raid configuration.

>Fix:
None.
>Release-Note:
>Audit-Trail:

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.
 

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, 6 Jul 2004 22:00:32 -0000

 Update:
 Took apart and reassembled every pice of my system to find the problem. Tried
 all combinations of disk combos on different controllers and found only this:
 one older drive was ATA REV 4, the other REV 5.
 
 Drives are on a different bus (ata1 , other drive ata2), both as slaves.
 Master drives are identical.
 
 Only in this configuration the error occurred. I replaced both drives and all
 is going well. On same cables, so this is not the prob this time :)
 Looks like a very mystic mirror, but most likely faulty and/or old hardware
 was the cause.
State-Changed-From-To: open->closed 
State-Changed-By: arved 
State-Changed-When: Tue Aug 24 17:22:10 GMT 2004 
State-Changed-Why:  
Close this PR, According to submitter: 
"most likely faulty and/or old hardware was the cause." 

http://www.freebsd.org/cgi/query-pr.cgi?pr=68313 
>Unformatted:
