SDB:Error in /etc/cryptotab after Updating to SUSE LINUX 9.2

From openSUSE

Version: 9.2

Symptom

After updating to SUSE LINUX 9.2, mounting encrypted partitions is no longer possible. Your machine freezes after you enter the password during the boot process.

Cause

Due to a bug in YaST, the device is not entered in the file /etc/cryptotab. Normally, the second column of this file should contain the device name for the encrypted partition (e.g., "/dev/hda5") or, in case you have not encrypted a whole partition but only a container file, the path to this file. However, during the update this value (device or file name) was wrongly replaced by duplicating the value of the first column:

/dev/loop0  /dev/loop0      /data                reiserfs   twofish    noatime

Solution

First, continue booting the Linux system by pressing ENTER when prompted to enter the password for "/dev/loop0". The boot process should be resumed.

Then edit the file with an editor of your choice and correct it. For this purpose, open a shell (e.g., xterm or konsole) and log in as root by entering the command "su -" in the shell.

Open the file /etc/cryptotab with a text editor and replace the value in the second column with the device name of your encrypted partition or the crypto file. In our example:

/dev/loop0  /dev/hda5      /data                reiserfs   twofish    noatime

Save the file and enter the following command to mount the crypto file system:

/etc/init.d/boot.crypto start

After entering the password, you should be able to access the encrypted data.

SDB:Using the Crypto File System

SDB:Repairing a Crypto File System