From owner-freebsd-hardware@FreeBSD.ORG Thu Aug 14 00:03:06 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 99AD437B401 for ; Thu, 14 Aug 2003 00:03:06 -0700 (PDT) Received: from nsdv.konzoom.net (nsdv.konzoom.com [217.8.32.240]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E5E143F93 for ; Thu, 14 Aug 2003 00:03:05 -0700 (PDT) (envelope-from fredde@konzoom.net) Received: by nsdv.konzoom.net (Postfix, from userid 1017) id 48BDB10A6D; Thu, 14 Aug 2003 09:03:03 +0200 (CEST) Date: Thu, 14 Aug 2003 09:03:03 +0200 From: Fredrik Lindberg To: freebsd-hardware@freebsd.org Message-ID: <20030814070303.GA33216@nsdv.konzoom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: Re: [SOLVED] RAID 5 array on Promise SX6000 failing after fsck at boot X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Aug 2003 07:03:06 -0000 Acctually you don't need to do that. :) I got it running by installing 5.1-RELEASE running UFS2 instead of UFS I really can't understand the problem with 4.8-RELEASE. According to the cvs repository there has been no big changes to fsck in the 5.x branch. My other theory is a acpi-releated issue which "solved itself" because of the acpi support in 5.x (however I can't see how that should affect anything) but ACPI was enabled in the motherboards bios during my tests with 4.8-RELEASE (never though of disable it). Perhaps somebody with better knowledge of acpi could confirm or decline this. Anyway, thanks for your time! Fredrik Lindberg > > It may take a few days. > > The only way I know of getting the firmware version is by rebooting. > I'll try and do that tonight. > > -- Scott > > Fredrik Lindberg wrote: > >>Thanks for your reply! >> >>Could you please provide me with the firmware-version of your Promise >> SuperTrack SX6000? >>I suspect it *might* be a such issue. >> >>Thanks alot! >> Fredrik >> >> >> >> >>>Fredrik, >>> >>>Sorry to hear you're having trouble with your Promise SuperTrak >>> SX6000. >>> >>>I've been using one for about a month now, and haven't seen the >>> problem you reported. >>> >>>I know that I've run fsck, because I've had to power-cycle the system >>> a couple of times due to other issues that I've had with the >>> contoller. >>> >>>Sorry I can't recommend a solution. >>> >>>Here's my setup: >>> >>>FreeBSD 4.8-RELEASE >>> >>>pstpci0: mem >>>0xf4000000-0xf43fffff irq 20 at device 1.1 on pci3 pst0: 572204MB >>> [72945/255/63] on pstpci0 >>> >>> >>># See the fstab(5) manual page for important information on automatic >>> mounts # of network filesystems before modifying this file. >>># >>># Device Mountpoint FStype Options Dump >>> Pass# /dev/ad0s1b none swap sw >>> 0 >>> 0 /dev/ad0s1a / ufs rw >>> 1 >>> 1 /dev/ad0s1f /usr ufs rw >>>2 2 /dev/ad0s1e /var ufs rw >>> 1 2 /dev/acd0c /cdrom cd9660 ro,noauto >>> 0 0 /dev/pst0s1e /export ufs rw >>> 1 2 proc /proc procfs rw >>> 0 0 >>> >>># /dev/pst0s1e: >>>type: ESDI >>>disk: pst0s1 >>>label: >>>flags: >>>bytes/sector: 512 >>>sectors/track: 63 >>>tracks/cylinder: 255 >>>sectors/cylinder: 16065 >>>cylinders: 72944 >>>sectors/unit: 1171861362 >>>rpm: 3600 >>>interleave: 1 >>>trackskew: 0 >>>cylinderskew: 0 >>>headswitch: 0 # milliseconds >>>track-to-track seek: 0 # milliseconds >>>drivedata: 0 >>> >>>8 partitions: >>># size offset fstype [fsize bsize bps/cpg] >>> c: 1171861362 0 unused 0 0 # >>> (Cyl. 0 - 72944*) e: 1171861362 0 4.2BSD 2048 16384 >>> 89 >>> # (Cyl. 0 - 72944*) >>> >>> >>> >>>-- Scott >>> >>> >> >> >> >> >> ----- End forwarded message -----