From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 16:01:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 91B6E16A4CE for ; Fri, 23 Jul 2004 16:01:38 +0000 (GMT) Received: from afields.ca (afields.ca [216.194.67.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37FE643D39 for ; Fri, 23 Jul 2004 16:01:38 +0000 (GMT) (envelope-from afields@afields.ca) Received: from afields.ca (localhost.afields.ca [127.0.0.1]) by afields.ca (8.12.11/8.12.11) with ESMTP id i6NG1buO048425; Fri, 23 Jul 2004 12:01:37 -0400 (EDT) (envelope-from afields@afields.ca) Received: (from afields@localhost) by afields.ca (8.12.11/8.12.11/Submit) id i6NG1bxY048424; Fri, 23 Jul 2004 12:01:37 -0400 (EDT) (envelope-from afields) Date: Fri, 23 Jul 2004 12:01:37 -0400 From: Allan Fields To: Eugene Message-ID: <20040723160136.GC31615@afields.ca> References: <20040722200612.2685A16A4EF@hub.freebsd.org> <4100947E.30805@web.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="i9LlY+UWpKt15+FH" Content-Disposition: inline In-Reply-To: <4100947E.30805@web.de> User-Agent: Mutt/1.4i cc: freebsd-current@freebsd.org Subject: Re: did gbde on swap destroy some boot sectors? (and cdrom did not boot and pppoe broken in xl-driver) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Fri, 23 Jul 2004 16:01:38 -0000 --i9LlY+UWpKt15+FH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 23, 2004 at 06:30:54AM +0200, Eugene wrote: > what can be more evil than a crash? I agree. > the system didnt came up again... what i saw was "F1 FreeBSD"... and=20 > that it was... at first i guessed my keyboard is ugly, changed it,=20 > booted and such actions... nothing... > > ok... so lets try to fix and boot from cd... -current cd in drive... but= =20 > [..]=20 > so now i was surprised the boot floppy pack of -current worked fine...=20 >=20 > ok... im in with a fixit floppy and tried to boot the /-partition...=20 > doesnt work... to mount /usr works fine... ok... lets try mount -f on=20 > /... works fine... ok... >=20 > but i dint find a way to fix the bootloader or whatever was trashed...=20 > so i endet up reinstalling it, lost my disklabels...a nd because it was= =20 Easier done directly with disklabel and/or boot0cfg. > 6 am and i was tired i did newfs when readding the disklabels *g*...=20 > last but not least... the gbde lock file was lost that way, so my other= =20 > partitions are useless now too... and i have much free hard drive space= =20 > now :-)) Unfortunately, you're not alone in having this occur.. :( If anything is currently very important on disk and you haven't newfs'ed the gbde partition, dd to another drive or pull this drive; with faint hope someday you will be able to get it back (but not holding your breath). The more likely case is the lock file still intact, but that may not be so. Read back in lists for similar situation w/ lost lock-file. [Obligatory post-mortem analysis:] The first thing to remember in situations like this is: optimally, don't write to the disk until you spend time dding/dumping specific areas in interest or carefully consider all possible cases. (Probably biggest data loss is the cascading of problems due to being rushed/tired, which has happened to many of us..) It can't be stressed enough how important it is to keep lock-selector file backup on another disk. When one file lost is the whole file system, it makes the case for extra prudence. The other idea is store this on a removable media such as flash, not in root partition. =46rom the Handbook (-- people have fair warning for this): The gbde init command creates a lock file for your gbde partition that in this example is stored as /etc/gbde/ad4s1c. Caution: gbde lock files must be backed up together with the contents of any encrypted partitions. While deleting a lock file alone cannot prevent a determined attacker from decrypting a gbde partition, without the lock file, the legitimate owner will be unable to access the data on the encrypted partition without a significant amount of work that is totally unsupported by gbde(8) and its designer. Perhaps the handbook should now explicitly list making a lock-selector file backup to floppy in procedure for gbde init? > but now what happened? why couldnt it boot again?! the last thing i did= =20 > was enabling gbde encryption on my swaps... and swap are the first label= =20 > on each of the 3 drives... >=20 > i suspect gbde on swap broke something... > > im i wrong or can someone check this please? It's definitely something to look at.. I can't imagine why this should happen, except disklabel issue: where was the swap located and what letter? Did it happen the same on 3 drives? If no, were the disklabels the same? > Eugene --=20 Allan Fields, AFRSL - http://afields.ca 2D4F 6806 D307 0889 6125 C31D F745 0D72 39B4 5541 --i9LlY+UWpKt15+FH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQFBATZf90UNcjm0VUERAlATAJ9fJyq3so/RbWr3LPwnCMu4hzoxLwCgt6Nb oUdNqKVtVCGvHGZ/Ju8gtw0= =IL6m -----END PGP SIGNATURE----- --i9LlY+UWpKt15+FH--