From owner-freebsd-geom@FreeBSD.ORG Tue Jan 20 17:08:32 2009 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C40A0106566C for ; Tue, 20 Jan 2009 17:08:32 +0000 (UTC) (envelope-from alekar2009@gmail.com) Received: from mail-gx0-f33.google.com (mail-gx0-f33.google.com [209.85.217.33]) by mx1.freebsd.org (Postfix) with ESMTP id 6F73C8FC12 for ; Tue, 20 Jan 2009 17:08:32 +0000 (UTC) (envelope-from alekar2009@gmail.com) Received: by gxk14 with SMTP id 14so1897652gxk.19 for ; Tue, 20 Jan 2009 09:08:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=kUyM6ob+G8eX87DkPvTCX6RFVPOYo4tlaZGWkIYc9w0=; b=nSDpSLEsSjRpRAa/97cnMAKE/WO6JSENVaPhaWtN+0cqZV4kQTmDP/DigD/EFUkjq+ PuBmSsSZ4D5S5YJA6qdMeokP0o7B0grBqYMSxWyk7hsb+5/cL2NCavjjGlicDxAxNOPH Lj6M/XS2Rw9U32w3lI66OUExyGWAhbV6r4P+o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=eSid4+I87o6hA396bPnP10oJpIZ59mnytg7SQFpINVhp5XuWsoTqon9cJ6xlDG+RIv cqV6Qy2wPHtkhecsypSOXGVCf1R8bfQbLYOE2nXK2mWaOFX6vTPf3i98Fg57tmaBn0Ij dMl78nESSksux0TkRuAH0jOByio+eH+0fvTtQ= MIME-Version: 1.0 Received: by 10.151.147.10 with SMTP id z10mr8931982ybn.102.1232470519051; Tue, 20 Jan 2009 08:55:19 -0800 (PST) Date: Tue, 20 Jan 2009 18:55:19 +0200 Message-ID: <700ff07a0901200855oaf6eaccpf2693bcf791269e6@mail.gmail.com> From: Alex Karpovic To: freebsd-geom@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: GELI problem... Oh, I mean disaster X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2009 17:08:33 -0000 Hello everyone, I am a long-time user of geli encryption, but just today I faced a problem, connected probably to some hardware malfunction, and I am in need of good advice now. I have a SATA drive, encrypted as whole with GELI. Booting is performed via usbflash drive. Today I tried to add an old IDE hdd, but when I turned my box on, loud clicking sound informed me that the hdd is physically broken. OK, turned computer off right after memory test, removed IDE hdd, and tried to boot as usual. However, GELI is unable to recognize my encrypted SATA now! I do bi-weekly backups, but in current situation it won't save me. I did a lot of work recently, and deadline is so near, that I cannot recreate all that is lost. Therefore, my first question is evident: taking into account the situation, is it possible that the damage is reversible? I know there's little hope, but maybe it is just a signature, which could be re-written? Second question is to feed my brain: what is the technical nature of my problem? Before that, I never expirienced a damaging of good SATA caused by attaching of bad IDE. Alex