Date: Sun, 1 Jul 2012 11:03:49 -0700 From: Marcel Moolenaar <marcel@xcllnt.net> To: Anton Shterenlikht <mexas@bristol.ac.uk> Cc: freebsd-current@freebsd.org, freebsd-ia64@freebsd.org Subject: Re: init: fatal signal: Segmentation fault Message-ID: <56020E80-DBA0-4D54-BF0C-A5716B657839@xcllnt.net> In-Reply-To: <20120621154010.GA95280@mech-cluster241.men.bris.ac.uk> References: <20120621154010.GA95280@mech-cluster241.men.bris.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 21, 2012, at 8:40 AM, Anton Shterenlikht wrote: *snip* > 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. Why are you forcing a fast boot? Subsequent problems are the result of not making your file system clean. > 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 I don't know if there's a separate problem with init(8) dumping core or the immediate consequence of the above. > How can I recover from this? boot -s and see what happens. If init(8) dies again, use a different init(8) by setting init_path at the loader prompt. SOmething like the following could do the trick: set init_path=3D"/sbin/init.bak" FYI, --=20 Marcel Moolenaar marcel@xcllnt.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56020E80-DBA0-4D54-BF0C-A5716B657839>