Can't mount encrypted drive
Nikolay Mirin
nik at optim.com.ru
Sat Apr 1 02:53:21 UTC 2006
Well, then the only idea I have from my own experience, that either key file
/etc/gbde/ad0s2c, or the whole disk partition are corrupted.
If you have a backup of /etc/gbde/ad0s2c, I'd try it.
Also checking disk surface may not hurt.
Did the problem emerge after the upgrade or just from like nowhere?
It seems to me, that you may not have gbde support activated in you kernel.
I'd double check on that too.
I am using gbde intensively, but all partitions I have are located on physically
mirrored or RAID-5 disks.
I never had such problems for almost then a year of production servers up and running.
I mean like one beautiful morning it won't attach for any reason.
But once the filesystem was badly corrupted, but I dumped it and then rebuilt from the scratch.
Lots of inodes were lost, but they were not critical and most of missing files were in the latest backup anyway.
Napoleon Dynamite said the following on 31.03.2006 20:21:
>El Vie 31 Mar 2006 05:56 PM, Nikolay Mirin escribió:
>
>
>>1) Are sure you have not just mistyped you password?
>>2) Does the file /etc/gbde/ad0s2c still exist?
>>3) Does the device /dev/ad0s2c still exist?
>>4) Did you include gbde in you new kernel config or do you have the
>>up-to-date kernel gbde module compiled.
>>
>>
>>
>1) I am sure I typed it right, and I tried about 100 times. I have it
>memorized and haven't changed it recently
>2) it is still there
>3) yes it exists
>4) it is in my new kernel configuration
>
>
>>What does it respond when if you run
>>
>>gbde attach /dev/ad0s2c -l /etc/gbde/ad0s2c
>>
>>and type you password.
>>
>>
>>
>>
>
>After I type this, I get a blank line, and this is the output of it and
>ls /dev:
>gbde attach /dev/ad0s2c -l /etc/gbde/ad0s2c
>Enter passphrase:
>thanatos# ls /dev
>acd0 ad5s3a agpgart dspW0.0 net stderr ttyv7
>acpi ad5s3c apm dspW0.1 net1 stdin ttyv8
>ad0 ad5s4 ata dspr0.1 net2 stdout ttyv9
>ad0s1 ad5s4c atkbd0 fd net3 sysmouse ttyva
>ad0s1a ad5s4e audio0.0 fd0 net4 ttyd0 ttyvb
>ad0s1b ad5s4f audio0.1 fido network ttyd0.init ttyvc
>ad0s1c ad6 bpf0 geom.ctl nfs4 ttyd0.lock ttyvd
>ad0s2 ad6s1 console io nfslock ttyp0 ttyve
>ad0s2c ad6s1a consolectl kbd0 null ttyp1 ttyvf
>ad0s4 ad6s1b ctty klog pci ttyp2 ums0
>ad5 ad6s1c cuad0 kmem pf ttyv0 urandom
>ad5s1 ad6s1d cuad0.init log ppi0 ttyv1 usb
>ad5s1a ad6s2 cuad0.lock lpt0 ptyp0 ttyv2 usb0
>ad5s1b ad6s3 devctl lpt0.ctl ptyp1 ttyv3 xpt0
>ad5s1c ad6s4 devstat mdctl ptyp2 ttyv4 zero
>ad5s2 ad6s4c dsp0.0 mem random ttyv5
>ad5s3 ad6s4d dsp0.1 mixer0 sndstat ttyv6
>
>I have had the encrypted partition for about five months with no problems
>until today. Thank you for your help.
>
>Eric Buchanan
>_______________________________________________
>freebsd-stable at freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
>
>
More information about the freebsd-stable
mailing list