Bug 148124

Created attachment 66424 [details]
Copy of the yast2 logs from an attempt to create a cryptfs

Maby this was fixed for 10.1. Please try if it works with 10.1 Beta 3 first.

> I see other reports of this claiming 'fixed' but no Suse 10 system that I can
> find is functional in this regard.

Which bug reports (id's) are you referring to?

Thomas: What does this error mean? Can you take care of that, maby the logfiles contain something useful.

There is some iso loopback mounted (/suse10/iso/suse10.iso). Setting up the crypto loop then fails because loop0 is busy. Steven where comes the loop mount of /suse10/iso/suse10.iso from?

It appears the loopback mount was causing the issue.  This loopback is a copy of the suse 10 distribution disk mounted from an iso.  By moving this to another loop device it resolved the issue.

The only issue here really is that we didn't move to the next loopback device when one was in use during the creation of the encrypted partition.

The question is where did this loop mount come from? Your old fstab? Did you set it up manually? When did you do that? During installation?

Please answer that so we can reproduce and have a chance to fix it.

It came from my own fstab (reproduced below).  I typically copy the iso to my disk and loop mount it to feed it to yast as a DVD source.  This is being done by several of my co-workers which explains why none of us could get this to work.  

Here's the fstab as it was:
/dev/hda1            /                    ext3       acl,user_xattr        1 1
/dev/system/home     /home                ext3       acl,user_xattr        1 2
/dev/system/opt      /opt                 ext3       acl,user_xattr        1 2
/dev/system/srv      /srv                 ext3       acl,user_xattr        1 2
/dev/system/tmp      /tmp                 ext3       acl,user_xattr        1 2
/dev/system/usr      /usr                 ext3       acl,user_xattr        1 2
/dev/system/var      /var                 ext3       acl,user_xattr        1 2
/dev/system/virtual  /virtual             ext3       acl,user_xattr        1 2
/dev/system/suse10   /suse10              reiserfs   acl,user_xattr        1 2
/dev/system/swap     swap                 swap       defaults              0 0
proc                 /proc                proc       defaults              0 0
sysfs                /sys                 sysfs      noauto                0 0
usbfs                /proc/bus/usb        usbfs      noauto                0 0
devpts               /dev/pts             devpts     mode=0620,gid=5       0 0
/dev/cdrecorder      /media/cdrecorder    subfs      noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
/dev/dvdrecorder     /media/dvdrecorder   subfs      noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
none                 /subdomain       subdomainfs noauto         0 0
/suse10/iso/suse10.iso /suse10/dvd        iso9660    loop,rw               0 0


Also, please note that removeing the loop entry allowed me to create the encrypted partition but, after I put the entry back the encrypted parition no longer automounted.  I also tried a loop=/dev/loop1 form hoping to skip over the loop device without success.

Correction, it does work when I put my loop entry back.  It simply timed out waiting for a response which is absolutely normal.

This bug still exists in 10.1 beta6 - I can't create an encrypted file :-(
(I didn't test with a real partition)

Before you ask: I don't use any loop device currently. (My encrypted /home is not mounted, I let it timeout at boot.)

To reproduce:
- start the YaST2 partitioner
- create a cryptoloop file with the following settings:
  - enter a pathname for the cryptoloop file
  - check "create loop file"
  - check "format"
  - set a mountpoint
  - let the other options on default settings, click OK
  - enter a password
  - in the main dialog, click "apply"

Created attachment 72313 [details]
y2logs from 10.1 beta6

I emptied the logs before running YaST - therefore, it shouldn't be too hard to find your way in the logs ;-)

I think I found and fixed the problem, it was caused by the facted that you
did not provide the crypto password for /home during system startup.
YaST2 tried wrongly to losetup your encrypted partition on /dev/hda6 and of
course failed since it did not have the password.

Problem should be fixed with RC1.