*** This bug is a duplicate of bug 428435 ***
https://bugs.launchpad.net/bugs/428435
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
*** This bug is a duplicate of bug 428435 ***
https://bugs.launchpad.net/bugs/428435
Hi,
I have the "Waiting for encrypted source device..." message too (32 bit; 9.10
Ubuntu) but not all the time.
- 80% of all boots are normal
- 15% ends with "Waiting for encrypted source device..."
- 5% end
*** This bug is a duplicate of bug 428435 ***
https://bugs.launchpad.net/bugs/428435
This is clearly a duplicate of bug #428435
I had the same error when I started to look into this problem:
/dev/disk/by-uuid/xx----xxx does not exist.
** This bug has been marked a dup
But you can run it as script. I changed it to my needs, and now when i start
the script, it begins, vi opens the file, i change the values manually (could
be done by a script for sure, but doing by hand is shorter than thinking of a
right script), save the file, and the script continues. Reboot
Same problem here, fix also worked for me. Hoping I won't have to do
this for every kernel update though ;)
--
Karmic update "Waiting for encrypted source device..." error
https://bugs.launchpad.net/bugs/446591
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Yes for me it is one volume, too, but the solution works.
I just needed to change in a similar way, and at the end of the rows there was
an additional lvm_... or something, and that stays unchanged.
so it should be something like:
>> There you will see something like
target=sda5_crypt,source=/de
This problem may have pre-dated Karmic. Here is what looks to be the identical
problem:
https://answers.launchpad.net/ubuntu/+question/68158
Note, also that the workaround in the forum link did not work for me. One
difference with my system as compared to the one in the forum link is that on
Maybe this could also help, but i dont know.
"I don't want to suggest any command like "sudo update-initramfs -k all -c"
without knowing exactly what I'm doing, since I don't know if a mistake could
make your encrypted partition totally unaccessible."
(Source: http://ubuntuforums.org/showpost.php
Found a workaround:
http://ubuntuforums.org/showpost.php?p=7159100&postcount=4
With this changes everything working again. initrd is 3 times the size,
but i dont mind the size if its working :)
--
Karmic update "Waiting for encrypted source device..." error
https://bugs.launchpad.net/bugs/44659
Updated today, and have the same problem. With the old jaunty kernel
(2.6.28) i can boot in recovery mode, so i can work a bit, but with
2.6.31 i got the same symptoms here.
--
Karmic update "Waiting for encrypted source device..." error
https://bugs.launchpad.net/bugs/446591
You received this bu
FYI, I have access to the contents of my encrypted root filesystem now
as outline in question 84659 on answers.launchpad.net so I can backup (I
know, should have done that first) and reinstall from scratch if
necessary.
--
Karmic update "Waiting for encrypted source device..." error
https://bugs.
** Summary changed:
- Laptops with encrypted harddisks won't boot after Karmic Update
+ Karmic update "Waiting for encrypted source device..." error
--
Karmic update "Waiting for encrypted source device..." error
https://bugs.launchpad.net/bugs/446591
You received this bug notification because y
12 matches
Mail list logo
