I used "fsck -n" and then tried to mount the /crypto/home/cryptofile partition 
container with no luck, same results stating:

# sh cryptfs -m -p /home -f /crypto/home/cryptofile -d /dev/svnd0c
Encryption key:
vnconfig: VNDIOCSET: Device busy
mount_ffs: /dev/svnd0c on /home: specified device does not match mounted device
# mount -f /home
mount: can't find fstab entry for /home.
# mount -f /crypto/home/
mount_ffs: /dev/wd0g on /crypto/home: Device busy
# mount -r /crypto/home/
mount_ffs: /dev/wd0g on /crypto/home: Device busy
#

In a previous mail you said :

just use vnconfig to attach a file to
svnd0, and then do fsck /dev/rsvnd0c (maybe take a backup first?)
OTOH, whether that works may depend on the disklabel on /dev/rsvnd0c,
but at least i do this routinely in a similar script as yours,
before mounting /dev/svnd0c, and it appears to work fine for me

I cant take a backup, and I cant risk loosing the data.. (if not already
lost because of the damage from the improper shutdown cause by the power
break).

Is this method previously mentioned by you still advisable ?
Thank you for your time!

Juha Erkkila <[EMAIL PROTECTED]> wrote: On Mon, Jun 05, 2006 at 04:47:28AM 
-0700, Rott_En wrote:
> Is it a risk to attempt using your recommedation ? Am I risking the
> integrity of my cryptofile container ? It is 90GB big and I dont have
> any auxiliary backup medium so big, taking a backup of it is almost
> out of hope.
> 
> I can't loose the data from this cryptofile, so please tell me if I
> risk using your method of repair.

of course there is a risk, as doing a fsck will modify the vnd-disk
contents.  try first with ``fsck -n'', see fsck(8).  but as it
appears to me, your problem is that as the system was not shut down
cleanly, the crypto disk is in a dirty state, and thus a fsck is
required for its proper operation.  alternatively, you might consider
trying a mount with -f and -r, see mount(8), and see if you can
read its contents.  make sure to use ``vnconfig -k'' first, and see
that you have the right key, otherwise neither will work (but should
still be safe)

Juha
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Reply via email to