** Description changed: - Binary package hint: gvfs + Some encrypted partitions which were created with older versions of + cryptsetup (< 1.0.7) are not detected anymore in karmic. The problem is + that older cryptsetup does not properly clean the superblock of the + partition and this might leave bogus filesystem signatures. - An encrypted external harddrive is not mounting automatically any more - (e.g. like in 9.04). + Karmic is more precise on these signatures and gets confused when + multiple filesystem signatures are found from single partition and + refuses to automatically do anything. - It mounts after unlocking it over the terminal with "cryptsetup - luksOpen". - - ProblemType: Bug - Architecture: i386 - Date: Sat Sep 12 16:46:16 2009 - DistroRelease: Ubuntu 9.10 - HotplugNewDevices: /dev/sdb /dev/sdb1 - HotplugNewMounts: - - Package: gvfs 1.3.6-0ubuntu1 - ProcEnviron: - LANG=de_DE.UTF-8 - SHELL=/bin/bash - ProcVersionSignature: Ubuntu 2.6.31-9.29-generic - SourcePackage: gvfs - Symptom: storage - Uname: Linux 2.6.31-9-generic i686 + This might manifest itself as simply as an encrypted external harddrive + not mounting automatically any more (e.g. like in 9.04) or more severely + like full encrypted root filesystem not found after standard + distribution upgrade from jaunty to karmic.
-- luks encrypted partition not detected or mounted automatically https://bugs.launchpad.net/bugs/428435 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
