Without a copy of the /etc/crypttab in question, this bug is impossible
to confirm or work on. Closing as invalid.
** Changed in: cryptsetup (Ubuntu)
Status: Incomplete => Invalid
--
[Karmic] cryptsetup not accepting filesystem type ext4
https://bugs.launchpad.net/bugs/479129
You receive
** Tags added: regression-release
** Tags removed: regression-potential
--
[Karmic] cryptsetup not accepting filesystem type ext4
https://bugs.launchpad.net/bugs/479129
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
I don't have them anymore; I solved by reinstalling / and /home in 2
different partitions with different passwords; in /etc/crypttab there's a
rule for taking the password of /home from a file...
Not a clean way, but it works.
Also, a friend of mine, tried to mount from SysRescue the whole partitio
Claudio Moretti writes:
> Maybe, but it sounds strange to me: I set up disks during installation,
> should'nt Ubuntu installer take care of this?
it *should*.
please still attach your /etc/crypttab and /etc/fstab to this bug.
--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4
--
[Karmic
Maybe, but it sounds strange to me: I set up disks during installation,
should'nt Ubuntu installer take care of this?
On Sat, Nov 28, 2009 at 16:06, mejo wrote:
> seems like you're using plain dm-crypt encryption, and cryptdisks checks
> for a valid
> filesystem but doesn't find one.
>
> please
seems like you're using plain dm-crypt encryption, and cryptdisks checks for a
valid
filesystem but doesn't find one.
please paste your /etc/crypttab and /etc/fstab for more information.
** Changed in: cryptsetup (Ubuntu)
Status: New => Incomplete
--
[Karmic] cryptsetup not accepting fi
