Public bug reported:

I have the following setup:
/boot unencrypted
/ and swap in LVM over encryption with luks
/data encrypted with key stored on / (no LVM, filesystem is directly created on 
/dev/mapper/data

/etc/crypttab contains this line:
data /dev/sdb /sdb.key size=...,cipher=...,hash=...,noearly

The noearly is necessary because the key /sdb.key is in an LVM
partition.

Now, on boot I always get the message
"Serious errors were found while checking the disk drive for /data" Ignore, 
Skip or Manual recovery

I always press "I" because everything works just fine. I don't know yet what 
causes mountall to think that there's a problem, but a manual fsck on 
/dev/mapper/data shows that there is no problem. So I assume it has something 
to do with the block device appearing rather late in the bootup?
/etc/fstab looks like this:
UUID=9d44a5d2-9b21-40f4-9799-6f51d221810b /data            ext4  defaults       
   0       2

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: mountall 2.42ubuntu0.2
ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
Uname: Linux 3.5.0-21-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.6.1-0ubuntu9
Architecture: amd64
Date: Fri Dec 21 11:34:56 2012
InstallationDate: Installed on 2012-11-07 (43 days ago)
InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1)
MarkForUpload: True
SourcePackage: mountall
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: mountall (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug quantal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1092853

Title:
  mountall fails to handle "noearly" crypt disk correctly and displays
  error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1092853/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to