From owner-freebsd-stable@FreeBSD.ORG Sat Apr 1 03:03:12 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 14DF716A41F for ; Sat, 1 Apr 2006 03:03:12 +0000 (UTC) (envelope-from groundedforlife@verizon.net) Received: from smtp101.vzn.mail.dcn.yahoo.com (smtp101.vzn.mail.dcn.yahoo.com [209.73.179.139]) by mx1.FreeBSD.org (Postfix) with SMTP id 6E81243D46 for ; Sat, 1 Apr 2006 03:03:11 +0000 (GMT) (envelope-from groundedforlife@verizon.net) Received: (qmail 68372 invoked from network); 1 Apr 2006 03:03:10 -0000 Received: from unknown (HELO ?192.168.1.47?) (groundedforlife@verizon.net@71.116.82.146 with plain) by smtp101.vzn.mail.dcn.yahoo.com with SMTP; 1 Apr 2006 03:03:10 -0000 From: Napoleon Dynamite To: freebsd-stable@freebsd.org Date: Fri, 31 Mar 2006 19:02:44 -0800 User-Agent: KMail/1.8.2 References: <200603311634.35583.groundedforlife@verizon.net> <200603311821.32454.groundedforlife@verizon.net> <442DEAFF.6030001@optim.com.ru> In-Reply-To: <442DEAFF.6030001@optim.com.ru> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <200603311902.45304.groundedforlife@verizon.net> Subject: Re: Can't mount encrypted drive 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: Sat, 01 Apr 2006 03:03:12 -0000 I restored /etc/gbde/ad0s2c, and the problem remained. I double checked gdb= e=20 in the kernel, and it is in there. I had a bad shutdown earlier this week a= nd=20 backup up everything right after that. This problem came out of nowhere this morning. I had no problems at all wit= h=20 gdbe at all until today. I have all the data encrypted by gnupg on normal=20 files, so I will just remake the encrypted partition from scratch. Thank you very much for your help. Eric Buchanan El Vie 31 Mar 2006 06:52 PM, Nikolay Mirin escribi=C3=B3: > Well, then the only idea I have from my own experience, that either key > file /etc/gbde/ad0s2c, or the whole disk partition are corrupted. > If you have a backup of /etc/gbde/ad0s2c, I'd try it. > Also checking disk surface may not hurt. > > > Did the problem emerge after the upgrade or just from like nowhere? > > It seems to me, that you may not have gbde support activated in you kerne= l. > I'd double check on that too. > > > I am using gbde intensively, but all partitions I have are located on > physically mirrored or RAID-5 disks. > I never had such problems for almost then a year of production servers up > and running. I mean like one beautiful morning it won't attach for any > reason. > > But once the filesystem was badly corrupted, but I dumped it and then > rebuilt from the scratch. Lots of inodes were lost, but they were not > critical and most of missing files were in the latest backup anyway. > >