From owner-freebsd-questions@FreeBSD.ORG Tue Aug 12 23:34:34 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2B46F7C3 for ; Tue, 12 Aug 2014 23:34:34 +0000 (UTC) Received: from mail.parts-unknown.org (home.parts-unknown.org [50.250.218.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 028CD26A2 for ; Tue, 12 Aug 2014 23:34:33 +0000 (UTC) Received: from mail.parts-unknown.org (unknown [127.0.0.1]) by mail.parts-unknown.org (Postfix) with ESMTP id 9CB6F598DE21; Tue, 12 Aug 2014 16:34:26 -0700 (PDT) Received: by mail.parts-unknown.org (Postfix, from userid 1001) id 7F11A598DABF; Tue, 12 Aug 2014 16:34:26 -0700 (PDT) Date: Tue, 12 Aug 2014 16:34:26 -0700 From: David Benfell To: Polytropon Subject: Re: operation not permitted on entropy file Message-ID: <20140812233426.GA25757@home.parts-unknown.org> References: <20140810124433.da498898.freebsd@edvax.de> <20140810224038.GD24036@home.parts-unknown.org> <20140811101822.41851cc7.freebsd@edvax.de> <20140811142707.GA10186@home.parts-unknown.org> <20140811171653.b7c60e58.freebsd@edvax.de> <20140811153535.GA30506@home.parts-unknown.org> <20140811183912.ef0f20a6.freebsd@edvax.de> <20140812022709.GA84770@home.parts-unknown.org> <20140812072832.da0166dc.freebsd@edvax.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="u3/rZRmxL6MmkK24" Content-Disposition: inline In-Reply-To: <20140812072832.da0166dc.freebsd@edvax.de> User-Agent: Mutt/1.5.23 (2014-03-12) X-Virus-Scanned: ClamAV using ClamSMTP on home.parts-unknown.org Cc: FreeBSD Questions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Aug 2014 23:34:34 -0000 --u3/rZRmxL6MmkK24 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 12, 2014 at 07:28:32AM +0200, Polytropon wrote: >=20 > The text is kept in the console buffer until reboot. Of > course saving something to /tmp when you have enabled > a cleanup for /tmp isn't optimum. In this case, choices > like /root/fsck.txt or even /fsck.txt (for temporary > storage) would have been okay. >=20 I'm learning more about this. Most of my experience is with Linux so this is where my assumptions come from. First, I didn't know that scroll lock was the secret to being able to scroll back in these text mode terminals; second, I didn't know that the arrow keys were then the appropriate means for doing so; and third, I assumed you had to reboot after playing in single-user mode. > For the next time: You can use mdconfig to temporarily > allocate a RAM disk, then use script to record the whole > console session (including fsck output), afterwards run > "mount -a" and copy the log fron the RAM disk to a more > permanent place. Just in case. This may well be coming. I had roughly 48 good hours. Now, it's crashing again. I suppose I can't be surprised if the remaining memory card has now gone bad (the vendor is sending me replacements for both, despite my saying only one had gone bad). I realized I had a 32GB partition available for use as a swap partition. I had deviated from the default installation by allocating an EFI partition. It's manifestly clear that this is not needed. And it's more than large enough (actually about twice the needed size) for a complete memory dump (I'm presently running on 8GB, but the specification is for 16GB). I've gone in with gdisk and changed that partition's type, so hopefully the next time, I'll actually get a dump. Not that I've figured out what to do with one once I have it. Having changed that file sytem type, it wanted me to reboot. So I did, and while doing so, went into single user mode to do fsck -fy. The first pass was not clean; but all the messages were about stuff at the end. I don't remember it all, but there are something like four things here, including some sort of bit map. It seems to be about at least part of how the file system keeps track of allocated and unallocated blocks. I've already turned off background_fsck, but it seems to do a fast fsck anyway. Right now, at least, that seems undesirable. Is there a way to force it to be more thorough? Thanks! >=20 >=20 >=20 > --=20 > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... --=20 David Benfell See https://parts-unknown.org/node/2 if you don't understand the attachment. --u3/rZRmxL6MmkK24 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJT6qSCAAoJEBV64x4SNmArmGcP/R9UlkrNhMBRXy+/i5gkH+JV mdI0uIY5EQLNiVjbrsDu5hXvrE+dv5rJ6lSQUseiOxOUR2LYWZZp+Q0R3/cDF3WN DtEJR2yH6vR4b/odQCQJH0sAELOnx0/N0OJwy1Oj/cuuQWVhi39SZkA334J+W4fm /zqHwc037vm/acaaozxFBzOx1c8TqavB2+XOwLwNYfh+2cnXy1uWoulrvAU6Ue4O pdYFG2NEy61B+pb2HlShBabsFINwygziK+5nIUCzERpu0Vh+gfjjLpfTsxfjRyYe 4YRXkRPlrpfEzPE/E808S2oUfBVS4Zy2QNoIO8Uotmv/gHW6ZhJushhS5K8BZJ3V QE83u1qIdbiIpTl27PZFm0Fm7/SZCPEZyvnpDq2UdfUcfidLPiW061k+DCQwXuCr w93Q4pFOiNXtTGfBOGy/w1fmSmf2L7+TYtY1iCB6ynPKn3SaNhc39j4VbMV1J+nX a+IFgBvFctDIEnFVeB7/S3wbxM3lqfm52dcHoFrY94QmhVxr370f1Hs3JgVZQWhg B+dRrhe7lZpUM1y1bYKG3LhfxKbcPQ3TMf3mz/IfomJ+dhGGUgVEsCiee9HNbMHW l+tAhn8qS9i1fOQ31w1oxhjosqPw77dieRm2V4sntMWJuHmkzIwulQkEJOXWzYHF 5ldSiSJM/QSj8UDuaWt5 =pTuV -----END PGP SIGNATURE----- --u3/rZRmxL6MmkK24--