Bug 105020

Summary:	encrypted partition can't be mounted while installation
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Christian Boltz <suse-beta>
Component:	Installation	Assignee:	Thomas Fehr <fehr>
Status:	VERIFIED FIXED	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Normal
Priority:	P5 - None
Version:	Beta 1
Target Milestone:	Beta 3
Hardware:	Other
OS:	All
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	full y2logs - just search for the quoted lines in y2log ;-) changes needed in RootPart.ycp

Description Christian Boltz 2005-08-16 19:15:46 UTC

I booted 10.0 beta1 DVD to upgrade my existing 9.3 system. 
 
While mounting the partitions, I was asked for the password for my 
encrypted /home partition (created with 9.3). Although I entered the correct 
password, the partition was not mounted - but YaST showed no error message. 
 
The y2log seems to show the problem: 
 
[YCP] RootPart.ycp:556 vfstype:ext3 mntops:acl,user_xattr,noatime 
loop:/dev/loop0 fspath:/home device:/dev/hda6 
[YCP] RootPart.ycp:576 crypt pwd ok:true 
[YCP] Storage.ycp:3686 PerformLosetup format false loop 
$["encryption":"twofish", "loop_dev":"/dev/loop0", 
"partitionName":"/dev/hda6"] 
 
Maybe this is already the problem - IIRC /dev/loop0 is used to 
mount /download/<don't_remember>.iso 
 
[YCP] Storage.ycp:3689 PerformLosetup tmpf /tmp/YaST2-02578-kQWViH/tmpf 
[YCP] FileSystems.ycp:1206 GetLosetupCmd rmmod twofish cryptoloop; modprobe 
loop_fish2; /sbin/losetup -e twofish /dev/loop0 /dev/hda6 -p0 
< /tmp/YaST2-02578-kQWViH/tmpf 
[bash] ShellCommand.cc(shellcommand):78 ERROR: Module twofish does not exist 
in /proc/modules 
[bash] ShellCommand.cc(shellcommand):78 ERROR: Module cryptoloop does not 
exist in /proc/modules 
[bash] ShellCommand.cc(shellcommand):78 Switching to old S.u.S.E. loop_fish2 
compatibility mode. 
 
Hmm - what's up with the modules? (did the on-disk format change again?) 
 
[bash] ShellCommand.cc(shellcommand):78 ioctl: LOOP_SET_FD: Device or resource 
busy 
 
Ah - the device (I guess /dev/loop0) is busy. Anybody wondering? ;-) 
 
[YCP] Storage.ycp:3694 PerformLosetup r $["exit":1, "stderr":"ERROR: Module 
twofish does not exist in /proc/modules\nERROR: Module cryptoloop does not 
exist in /proc/modules\nSwitching to old S.u.S.E. loop_fish2 compatibility 
mode.\nioctl: LOOP_SET_FD: Device or resource busy\n", "stdout":""] 
[YCP] Storage.ycp:3707 PerformLosetup ret false 
 
I'll attach the full y2logs. 
 
 
PS: Déjà vu? See bug 77126 *g*

Comment 1 Christian Boltz 2005-08-16 19:17:11 UTC

Created attachment 46206 [details]
full y2logs - just search for the quoted lines in y2log ;-)

Comment 2 Thomas Fehr 2005-08-17 17:08:45 UTC

I did some changes to yast2-storage that makes update with encrypted loop 
device work again. These changes are contained in yast2-storage-2.12.19.tar.bz2

There are some changes to RootPart.ycp of yast2-update required.

Jiri, I attach these here and sent them via mail. 
Should I add them to subversion or yould you like prefer doing this yourself.

Comment 3 Thomas Fehr 2005-08-17 17:09:18 UTC

Created attachment 46347 [details]
changes needed in RootPart.ycp

Comment 4 Thomas Fehr 2005-08-18 09:04:27 UTC

Change to both yast2-storage and yast2-update are in SVN and STABLE.