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: 1830146 total sectors: 183014656 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 16 partitions: # size offset fstype [fsize bsize cpg] c: 183014656 0 unused 0 0 # Cyl 0 -1830146* # If I change "unused" to 4.2BSD fsck reports serval errors like SuperBlocks are missing. Any advice is highly welcomed, as before. Thank you. Juha Erkkila <[EMAIL PROTECTED]> wrote: 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 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 > # 1. please don't top post, trim your lines under 80 2. RTFM. in this case those are: vnconfig(8), fsck(8), mount(8) 3. AFTER figuring out what these will do, try these: $ vnconfig -k svnd0 /crypto/home/cryptfile (type the correct key) $ fsck /dev/rsvnd0c $ mount /dev/svnd0c /home don't blame me if it breaks. 4. consider not using a single, huge, encrypted vnd, for data that matters 5. toss away the cryptfs-script: it doesn't do fsck, if doesn't back out from errors, it forces mounts even when it should not Juha Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
