Known problems

Known Problems

This section describes common problems along with known solutions. Feel free to write us to support@jetico.com

Problem description	Known solution
BestCrypt does not compile
All systems/configurations may be affected	Upgrade to latest BestCrypt for Linux from www.jetico.com/linux.htm
	Make sure that kernel sources are installed
	Make sure that your C compiler is affordable for kernel compilation
	Distribution vendors sometimes provide kernel sources and binaries with different configurations. In order to fix that run following commands from the root of kernel source tree: `[foo@bar]# make mrproper # erase current configuration [foo@bar]# make menuconfig # configure your kernel here [foo@bar]# make dep # update configuration files; not required for 2.6.x kernels`
	Write Jetico Support Team if you could not resolve the problem
Problems loading BestCrypt modules
`"...will taint the kernel..."` message is displayed when loading BestCrypt modules	This message informs that BestCrypt's license is not GPL. It does not affect product functionality. Don't care about this.
BestCrypt modules could not be loaded, `"...unresolved symbols..."` message is displayed	Make sure that your kernel sources and kernel binaries are the same version
	Distribution vendors sometimes provide kernel sources and binaries with different configurations. In order to fix that run following commands from the root of kernel source tree: `[foo@bar]# make mrproper # erase current configuration [foo@bar]# make menuconfig # configure your kernel here [foo@bar]# make dep # update configuration files`
Problems running bctool
`open("/dev/bcrypt0", O_RDONLY): No such file or directory` error messages are displayed.	BestCrypt modules were not loaded. Please load modules by `/etc/init.d/bcrypt start` or `/etc/bcrypt start` command. List of loaded modules is displayed by `lsmod` command.
`mount( ... ): Invalid argument` Error message is displayed when running `bctool mount` command	Wrong filesystem type passed to `bctool mount` command
	Container was not formatted. Format container using `bctool format` command
	Both code page for container's filesystem and default code page are not supported by your kernel. Applies to FAT/VFAT-formatted containers. Add appropriate codepage support to your kernel.
`mount( ... ): No such device` Error message is displayed when running `bctool mount` command	Container's filesystem not recognized. Either filesystem module not loaded or filesystem support is missing in your kernel. Load corresponding module or reconfigure/rebuild your kernel.
`Operation not permitted` or `Permission denied` - style error messages are displayed when trying any container operations.	Your Linux kernel and BestCrypt are built using different compilers. Please install BestCrypt in the same environment as kernel did. Kernel compiler version could be found in `/proc/version` file.
`Can not find free device` - style error messages are displayed when trying any container operations.	BestCrypt drivers are not loaded. `/sbin/lsmod` command will show you list of loaded drivers. Run `/etc/init.d/bcrypt start` or `/etc/bcrypt start` or `/etc/rc.d/init.d/bcrypt start` in order to load BestCrypt drivers.
BestCrypt operations fail on password checking. The same worked ok before (or on other computer).	Since BestCrypt v1.3 initial vector generation procedure is improved to fix security flaw. Older versions of BestCrypt won't recognize records in newer container header and will fail. Take a look at changelog also.
`One or more components of BestCrypt outdated. driver version 23.0`(values may vary) `bctool version 1.3 Please update your current version of BestCrypt` error message is displayed.	Actually, BestCrypt drivers are not loaded. To get rid of false error message please upgrade to BestCrypt v 1.4-2 or newer.
BestCrypt v1.3 does not read older containers correctly. BestCrypt does not read containers created by BestCrypt v1.3 correctly.	Important! BestCrypt v1.3 created incorrect containers and it could damage containers created by earlier versions as well as by BestCrypt for Windows. Please upgrade to BestCrypt v1.4 or newer Please note: before upgrading from v1.3 please backup data from containers created by BestCrypt v1.3, then create new containers using BestCrypt v1.4. Do not use containers created by BestCrypt v1.3 with other BestCrypt versions - this may cause data loss. BestCrypt v1.4 is fully compatible with containers created by BestCrypt versions prior to v1.3.
open(/dev/bcrypt0,O_RDONLY): Permission denied or Can not find free device error is reported on every BestCrypt operation. `/dev/bcrypt*` nodes have 0600 or 0660 access mask.	This error may happen due to conflict with udev system which manages `/dev` entries. Add the following lines to the `/etc/udev/permissions.d/50-udev.permissions` file: `# bcrypt bcrypt*:root:root:0666` Thanks to Hrvoje Horvat for the solution.
	From version 053 onwards, udev does not support "/etc/udev/permissions.d" entries. If you are using udev of version >= 053, you would need to add the following lines to the `/etc/udev/rules.d/udev.rules` file: `# bcrypt KERNEL="bcrypt[0-9]*" NAME="%k", MODE="0666"` Thanks to Venky TV for the solution.
	From version 095 onwards udev rule for BestCrypt devices should look like `KERNEL=="bcrypt[0-9]*" NAME="%k", MODE="0666"` Thanks to Stephen Moehle.
Hangup on large data transfer from/to container
Linux kernels prior to 2.4.17 with ext3 filesystem (including RedHat's 2.4.7)	Upgrade to newer kernel; Kernel 2.6.x + BestCrypt 1.5-7 eliminate this problem 2.4.19+ is highly recommended for 2.4 series.
	Place your containers on ext2 or FAT/VFAT filesystems
Linux kernels prior to 2.4.19 with HIGHMEM enabled on SMP systems	Upgrade to newer kernel; Kernel 2.6.x + BestCrypt 1.5-7 eliminate this problem 2.4.19+ is highly recommended for 2.4 series.
	turn off HIGHMEM support