From owner-freebsd-bugs@FreeBSD.ORG Fri Jun 25 10:50:51 2004 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C9A916A4CE for ; Fri, 25 Jun 2004 10:50:51 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5EABA43D54 for ; Fri, 25 Jun 2004 10:50:51 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id i5PAoTcI043436 for ; Fri, 25 Jun 2004 10:50:29 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i5PAoTRH043435; Fri, 25 Jun 2004 10:50:29 GMT (envelope-from gnats) Resent-Date: Fri, 25 Jun 2004 10:50:29 GMT Resent-Message-Id: <200406251050.i5PAoTRH043435@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Alexander Weisel Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C79E416A4CE for ; 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 ; 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 ; 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 To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: kern/68313: Installing/Updating to Release 5.2.1 destroys RAID on Promise Controllers (i386, ACPI, SMP) X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jun 2004 10:50:51 -0000 >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: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jun 25 10:50:29 GMT 2004 >Closed-Date: >Last-Modified: >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: >Unformatted: