From owner-freebsd-current@FreeBSD.ORG Thu Jun 21 15:40:12 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 956C81065678; Thu, 21 Jun 2012 15:40:12 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from dirj.bris.ac.uk (dirj.bris.ac.uk [137.222.10.78]) by mx1.freebsd.org (Postfix) with ESMTP id 4D2598FC16; Thu, 21 Jun 2012 15:40:12 +0000 (UTC) Received: from ncsc.bris.ac.uk ([137.222.10.41]) by dirj.bris.ac.uk with esmtp (Exim 4.72) (envelope-from ) id 1ShjUR-0003YS-IN; Thu, 21 Jun 2012 16:40:11 +0100 Received: from mech-cluster241.men.bris.ac.uk ([137.222.187.241]) by ncsc.bris.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1ShjUR-0005du-5q; Thu, 21 Jun 2012 16:40:11 +0100 Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.5/8.14.5) with ESMTP id q5LFeA6V095290; Thu, 21 Jun 2012 16:40:10 +0100 (BST) (envelope-from mexas@bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.5/8.14.5/Submit) id q5LFeAI1095289; Thu, 21 Jun 2012 16:40:10 +0100 (BST) (envelope-from mexas@bris.ac.uk) X-Authentication-Warning: mech-cluster241.men.bris.ac.uk: mexas set sender to mexas@bris.ac.uk using -f Date: Thu, 21 Jun 2012 16:40:10 +0100 From: Anton Shterenlikht To: freebsd-current@freebsd.org, freebsd-ia64@freebsd.org Message-ID: <20120621154010.GA95280@mech-cluster241.men.bris.ac.uk> Mail-Followup-To: freebsd-current@freebsd.org, freebsd-ia64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: Subject: init: fatal signal: Segmentation fault X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2012 15:40:12 -0000 I ended up in state where I can't boot even in single user mode. This is on ia64, but I think this is not very relevant: FreeBSD 10.0-CURRENT #17 r232100: Wed Jun 20 11:17:16 BST 2012 *skip* da2 at mpt1 bus 0 scbus1 target 2 lun 0 da2: Fixed Direct Access SCSI-3 device da2: 320.000MB/s transfers (160.000MHz, offset 127, 16bit) da2: Command Queueing enabled da2: 70007MB (143374738 512 byte sectors: 255H 63S/T 8924C) da0 at mpt0 bus 0 scbus0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 160.000MB/s transfers (80.000MHz, offset 63, 16bit) da0: Command Queueing enabled da0: 17366MB (35566478 512 byte sectors: 255H 63S/T 2213C) da1 at mpt0 bus 0 scbus0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 160.000MB/s transfers (80.000MHz, offset 63, 16bit) da1: Command Queueing enabled da1: 17366MB (35566478 512 byte sectors: 255H 63S/T 2213C) Trying to mount root from ufs:/dev/da2p2 [rw]... WARNING: / was not properly dismounted Jun 21 17:35:34 init: fatal signal: Segmentation fault Setting hostuuid: 0aa09909-35f1-11df-b7f8-00110a31e60a. Setting hostid: 0xc70eae4e. Entropy harvesting: interrupts ethernet point_to_point kickstart. Fast boot: skipping disk checks. mount: /dev/da2p2: R/W mount of / denied. Filesystem is not clean - run fsck.: Operation not permitted Mounting root filesystem rw failed, startup aborted ERROR: ABORTING BOOT (sending SIGTERM to parent)! Jun 21 17:36:06 init: /bin/sh on /etc/rc terminated abnormally, going to single user mode Jun 21 17:36:06 init: fatal signal: Segmentation fault Setting hostuuid: 0aa09909-35f1-11df-b7f8-00110a31e60a. Setting hostid: 0xc70eae4e. Entropy harvesting: interrupts ethernet point_to_point kickstart. Fast boot: skipping disk checks. mount: /dev/da2p2: R/W mount of / denied. Filesystem is not clean - run fsck.: Operation not permitted Mounting root filesystem rw failed, startup aborted ERROR: ABORTING BOOT (sending SIGTERM to parent)! Jun 21 17:36:37 init: /bin/sh on /etc/rc terminated abnormally, going to single user mode Jun 21 17:36:37 init: fatal signal: Segmentation fault This continues indefinitely, I cannot break out of this, except with a cold reboot, which brings me back to this error. How can I recover from this? Thanks -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423