Hello and thank you for your initial reply. I know mount has an issue but svnd accept the cryptofile, so it is a filesystem problem wich a friend of mine had once in the past and fixed but can't remember how exactly.
The data is not lost, I just need a proper fix solution for this as am not sure what to do to mount properly as accesing the cryptofile is ok, it hasnt been damaged. Tobias Weisserth <[EMAIL PROTECTED]> wrote: Hi, On Jun 4, 2006, at 11:07 AM, 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: > > # sh cryptfs -m -p /home -f /crypto/home/cryptofile -d /dev/svnd0c > Encryption key: > mount_ffs: /dev/svnd0c on /home: specified device does not match > mounted device > # > > and then, when trying again : > > # 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 > # Not good. > # 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 OpenBSD's fsck will not acknowledge vnd > filesystems, > # these damaged structures can not reasonably be repaired. Have you read what it says here? This seems logical to me. If the filesystem is corrupted you would have to repair it, but the utilities to repair the filesystem can't access it, because the filesystem is wrapped in encryption which the utility can't read. In my opinion, you're screwed. Anybody else? I hope you have backups ;-) kind regards, Tobias W. Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
