On Tue, Jun 06, 2006 at 01:46:15PM -0700, Rott_En wrote:
Hello again.
I am not able to fix the issue, but here is the disklabel, maiby it
can help you figure out a solution.
...
If I change unused to 4.2BSD fsck reports serval errors like
SuperBlocks are missing. Any advice is highly
On Tue, 6 Jun 2006, Rott_En wrote:
Hello again.
I am not able to fix the issue, but here is the disklabel, maiby it can help
you figure out a solution.
# disklabel svnd0
# /dev/rsvnd0c:
type: SCSI
isk: vnd device
label: fictitious
flags:
bytes/sector: 512
sectors/track: 100
On Sun, 4 Jun 2006, Rott_En wrote:
Hello
I had a power failure yesterday morning and because of that my server went
down because of no battery present.
When trying to mount the crypto partitions, I have figured out its not
possible anymore because a set of 2 errors, as follows:
#
Hello again.
I am not able to fix the issue, but here is the disklabel, maiby it can help
you figure out a solution.
# disklabel svnd0
# /dev/rsvnd0c:
type: SCSI
isk: vnd device
label: fictitious
flags:
bytes/sector: 512
sectors/track: 100
tracks/cylinder: 1
sectors/cylinder: 100
cylinders:
Hello
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
Original message
Date: Mon, 5 Jun 2006 04:47:28 -0700 (PDT)
From: Rott_En [EMAIL PROTECTED]
Subject: Re: Crypto Partition Problem
To: misc@openbsd.org
Hello
Is it a risk to attempt using your recommedation ? Am I risking the integrity
of my cryptofile container ? It is 90GB big
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
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
On Mon, Jun 05, 2006 at 01:01:34PM -0700, Rott_En wrote:
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
On Mon, Jun 05, 2006 at 01:01:34PM -0700, Rott_En wrote:
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
On Sun, Jun 04, 2006 at 02:07:22AM -0700, Rott_En wrote:
# Important Note: Under OpenBSD's current encrypted vnd filesystem
# implementation, when a system with a mounted, encrypted vnd filesystem
# is shutdown uncleanly, the encrypted vnd filesystem's structures get
# damaged and, since
Juha Erkkila wrote:
i don't think this is true. 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
12 matches
Mail list logo
