From owner-freebsd-stable@FreeBSD.ORG Thu Jun 29 10:43:40 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 411E116A5B2 for ; Thu, 29 Jun 2006 10:43:40 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.18.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id D33DC44586 for ; Thu, 29 Jun 2006 10:15:21 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 22074 invoked from network); 29 Jun 2006 10:15:16 -0000 Received: from unknown (HELO localhost) (775067@[217.50.129.210]) (envelope-sender ) by smtprelay01.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 29 Jun 2006 10:15:16 -0000 Date: Thu, 29 Jun 2006 12:15:01 +0200 From: Fabian Keil To: Robert Watson Message-ID: <20060629121501.59b81c28@localhost> In-Reply-To: <20060629085650.H9293@fledge.watson.org> References: <20060627175853.765a590e@localhost> <20060628101729.J50845@fledge.watson.org> <20060628235258.3414b074@localhost> <20060628230255.M78211@fledge.watson.org> <20060629021509.13ff7341@localhost> <20060629085650.H9293@fledge.watson.org> X-Mailer: Sylpheed-Claws 2.2.3 (GTK+ 2.8.19; i386-portbld-freebsd6.1) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2006-08-19.asc User-Agent: 321 test Mime-Version: 1.0 Content-Type: multipart/signed; boundary=Sig_UzlQDMNTeq+tJsW5jw6suv9; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: Peter Thoenen , freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.1 Tor issues (Once More, with Feeling) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jun 2006 10:43:40 -0000 --Sig_UzlQDMNTeq+tJsW5jw6suv9 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Robert Watson wrote: > On Thu, 29 Jun 2006, Fabian Keil wrote: >=20 > > I wish I could. The machine died before I read your message. > > > > I was logged in on the serial console running tail > > -f /var/log/messages. Last messages were: > > > > Jun 29 00:42:20 tor kernel: Memory modified after free > > 0xc4275000(2048) val=3Da020c0de @ 0xc4275000 Jun 29 00:42:20 tor > > kernel: Memory modified after free 0xc4055800(2048) val=3Da020c0de @ > > 0xc432a000 Jun 29 00:42:24 tor kernel: ad0: TIMEOUT - WRITE_DMA > > retrying (1 retry left) LBA=3D34263674 Jun 29 00:42:24 tor kernel: > > Memory modified after free 0xc3dff800(2048) val=3Da020c0d > > > > Ctrl+Alt+ESC didn't trigger any reaction, so I caused a reset > > through the ISP's webinterface. Now the system appears to be hosed, > > at least FreeBSD never reaches the login: > > > > PXELINUX 3.11 2005-09-02 Copyright (C) 1994-2005 H. Peter Anvin > > Booting from local disk... > > > > 1 Linux > > 2 FreeBSD > > 3 FreeBSD > > > > Default: 2 > > > > [nothing] > The ATA error above is a bit distressing, as is the fact that it > won't boot. Is "[nothing]" normally the FreeBSD boot loader rather > than nothing? The "1 Linux ..." part already is the FreeBSD boot loader. Normally it goes: PXELINUX 3.11 2005-09-02 Copyright (C) 1994-2005 H. Peter Anvin Booting from local disk... 1 Linux 2 FreeBSD 3 FreeBSD Default: 2=20 FreeBSD/i386 (tor.fabiankeil.de) (ttyd0) login: > I would suggest running some hardware diagnostics to > make sure we're dealing with reliable hardware before continuing so > that we're not chasing both hardware and software problems, since you > can't reliably debug software problems in the presence of hardware > failures. I'll see what the ports collection has to offer (running smartmontools right now) but so far it's the only ATA message I got. > > Probably something which would be easy to resolve with keyboard > > access and a screen, but I think I'm forced to use the > > "RecoveryManager". Unfortunately "recovery" means reinstalling the > > preconfigured GNU/Linux which I than can replace with FreeBSD > > again. If there ever was a core dump it will be gone, and so will > > be kernel.debug. Lucky me. The "RecoveryManager" turned out to be a full featured PXE-booted GNU/Linux system. It allowed me to fetch and replace /dev/ad0s2a (/) through ssh. The system is online again.=20 After fsck -y /dev/ad0s3d (/usr) the whole tor jail is gone, but the rest of this slice seems to be ok, including kernel.debug. I can't fsck /var: [fk@tor ~]$ sudo fsck /dev/ad0s3d ** /dev/ad0s3d ** Last Mounted on /var ** Phase 1 - Check Blocks and Sizes fsck_4.2bsd: cannot alloc 1082190976 bytes for inoinfo but it can still be mounted. No core dump though. Fabian --=20 http://www.fabiankeil.de/ --Sig_UzlQDMNTeq+tJsW5jw6suv9 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEo6gxjV8GA4rMKUQRArnCAJ994MzBZ1Q5E2pTMUjNz2yWXWOB0QCfZg45 +yOvYbzgmREq4vpkkKe01K8= =qRGk -----END PGP SIGNATURE----- --Sig_UzlQDMNTeq+tJsW5jw6suv9--