Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 02 Sep 2004 15:04:10 +0200
From:      "Poul-Henning Kamp" <phk@phk.freebsd.dk>
To:        "=?iso-8859-1?Q? " Stefan=20Krau=DF " ?=" <ilsa.gold@web.de>
Cc:        freebsd-geom@freebsd.org
Subject:   Re: problem reattaching GBDE-encrypted slice 
Message-ID:  <1670.1094130250@critter.freebsd.dk>
In-Reply-To: Your message of "Thu, 02 Sep 2004 11:14:24 %2B0200." <1255564800@web.de> 

next in thread | previous in thread | raw e-mail | index | archive | help
In message <1255564800@web.de>, =?iso-8859-1?Q? "Stefan=20Krau=DF" ?= writes:
>Hi all,
>
>like some other guys on this list (have seen this in the archive)
>I have a problem with an already running GBDE-encrypted slice. I
>used this slice for about 3 months without any problems. The slice
>(=ad0s3a) is about 38 GB in size and about 16 GB of this were free
>to use (see fdisk and bsdlabel output at the end of this mail).
>Yesterday I just put about 9-10GB of data on this slice and everything
>seems to work just fine. After rebooting this morning I'm not able
>anymore to attache the slice to gbde. I ente r the password, no
>error message or something similar appears but I get now *.bde-device
>file under /dev. The lock-file is dated to somewhere in Feb 23, and
>I'm absolutely sure that I entered the right password (just tried
>this about 50-times ;-)).

This is weird.  It sounds like the master key sector has been
destroyed on the disk.

I've been running with GBDE on my laptop since I wrote it and I
have never seen anything like this, so I am somewhat convinced
that it is not a bug in GBDE, but I am also not ruling it out.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1670.1094130250>