Steve, it's my first time using the board. I think I hit the status
button thinking it linked to the fix. apologies.
--
mountall 0.2.5 and cryptsetup fail to boot when using usplash (encrypted root)
https://bugs.launchpad.net/bugs/456274
You received this bug notification because you are a member
don't change bug status without explanation.
** Changed in: cryptsetup (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: mountall (Ubuntu)
Status: Fix Committed => Fix Released
--
mountall 0.2.5 and cryptsetup fail to boot when using usplash (encrypted root)
https://bu
** Changed in: mountall (Ubuntu)
Status: Fix Released => Fix Committed
** Changed in: cryptsetup (Ubuntu)
Status: Fix Released => Fix Committed
--
mountall 0.2.5 and cryptsetup fail to boot when using usplash (encrypted root)
https://bugs.launchpad.net/bugs/456274
You received this
Hamish, my understanding from comment #18 is that your bug was fixed a
long time ago, prior to the karmic release. So I think this bug should
just be closed as fixed.
There are other bug reports for the other issues users have encountered
that don't relate to cryptsetup for /.
** Changed in: cry
mountall in lucid no longer contains any console handling code of its
own, and entirely uses Plymouth for asking questions (when plymouth
isn't around it just skips failing filesystems).
Provided that cryptsetup also uses plymouth, we can ensure that
arbitration over the current question is handle
** Summary changed:
- mountall 0.2.5 and cryptsetup fail to boot when using usplash
+ mountall 0.2.5 and cryptsetup fail to boot when using usplash (encrypted root)
** Description changed:
+ Note that this bug is (now) just for those with an encrypted root. A
+ workaround that seems to work for
Thanks for sorting it out.
The issue Andreas Lieser an I commented on "can't enter a password for
my encrypted home directory" is now Bug #497682
and "mountall and cryptsetup will fight for the console when not using
usplash" is now Bug #497684
--
mountall 0.2.5 and cryptsetup fail to boot whe
ceg,
"on the second prompt (for /home):" - that's not the configuration
described by the original bug reporter; it should be reported as a
separate bug. (Although it's already known that mountall and cryptsetup
will fight for the console when not using usplash, and there's no way we
can get this
In addition to what Andreas Lieser wrote on 2009-12-06: #34
Splash turned off (workaround), on the second prompt (for /home):
Entering the pw never works for me on the first time. I now just hit
Enter once. Only on the second time the pw is accepted.
--
mountall 0.2.5 and cryptsetup fa
On Wed, 2009-12-16 at 17:25 +, Steve Langasek wrote:
> So why does mountall think it's still waiting for the root filesystem,
> when it's already /running/ from the root filesystem? Does /dev/mapper
> /whisper-whisper_root not match the root filesystem value specified in
> the grub config?
>
This bug report has gotten very muddled, with comments from users with
all different kinds of configurations. Looking at the original
reporter's symptoms:
One or more of the mounts listed in /etc/fstab cannot yet be mounted:
(ESC for recovery shell)
/: waiting for /dev/mapper/whisper-whisper_r
Confirming what Andreas Lieser wrote on 2009-12-06.
cryptsetup of /home broken again
--
mountall 0.2.5 and cryptsetup fail to boot when using usplash
https://bugs.launchpad.net/bugs/456274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: regression-release
** Tags removed: regression-potential
--
mountall 0.2.5 and cryptsetup fail to boot when using usplash
https://bugs.launchpad.net/bugs/456274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
I did a fresh Karmic install 2 weeks ago, too, and I still got this bug.
I have two encrypted filesystem (/ and /home) which should be
automatically be mounted at boot time. When rebooting I got the splash
screen with the following displayed:
Unlocking the disk /dev/sda2 (cryptroot)
Enter passphr
I would just like to add to my comment #24:
I did a fresh install of Kubuntu Karmic yesterday, with similar FS setup (/ on
LVM, swap and /home on dm-crypt+LVM) and everything seems to work now as it
should! I get asked for prompt, if I enter passphrase, boot continues
immediately. If I leave the
I have been successfully using the following work-around. I created a
/etc/init.d/mount-tmp script, appended here. I then made /etc/rcS.d
/S38mount-tmp a symlink to the script.
#! /bin/sh
### BEGIN INIT INFO
# Provides: mount-tmp
# Required-Start: mountall
# Required-Stop:
# Default-Start: S
#
I have the same problema of Stephen Gildea.
swap is ok, while /tmp is never mounted
My /etc/crypttab file:
static-swap_crypt /dev/mapper/static-swap /dev/urandom
cipher=aes-cbc-essiv:sha256,size=256,swap
static-tmp_crypt /dev/mapper/static-tmp /dev/urandom
cipher=aes-cbc-essiv:sha256,size=256,tm
** Changed in: mountall (Ubuntu)
Milestone: ubuntu-9.10 => None
--
mountall 0.2.5 and cryptsetup fail to boot when using usplash
https://bugs.launchpad.net/bugs/456274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
I have a failure with only some of my encrypted filesystems, of which I
have three. Here is my /etc/crypttab file:
sda3_crypt /dev/sda3 none luks
dm5-temp /dev/sda5 /dev/urandom tmp
dm6-swap /dev/sda6 /dev/urandom swap
For sda3, I get prompted for a password, and this filesystem (holding
root
I have a similar experience to Geostar1024 (#25)
At the boot splash (white logo/black background) I get:
One or more of the mounts listed in /etc/fstab cannot yet be mounted:
/: waiting for /dev/disk/by-uuid/
/tmp: waiting for (null)
: waiting for
Press ESC to enter recover
As quickly as my problem appeared, it is now gone. For inexplicable
reasons, my system now boots properly (not that I'm complaining). I
wish everyone else luck in solving their issues with mountall.
--
mountall 0.2.5 and cryptsetup fail to boot when using usplash
https://bugs.launchpad.net/bugs
** Description changed:
--
mountall 0.2.5 and cryptsetup fail to boot when using usplash
https://bugs.launchpad.net/bugs/456274
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
htt
@Hamish
Thanks for your reply. I left mountall waiting for about half an hour,
and observed no disk activity at all. Attached is my fstab. . .
** Attachment added: "fstab"
http://launchpadlibrarian.net/34637768/fstab
--
mountall 0.2.5 and cryptsetup fail to boot when using usplash
https://
@geostar1024
Have you tried just waiting? When mountall says it is waiting, stuff may
continue to happen in the background. Basically, if your disk activity light
stays on, then I would not press Escape, but just wait and see if booting
continues anyway.
Only if the disk activity light goes off a
I'm experiencing a variation on this problem in Karmic (similar to jase
and Krastanov):
When I booted up this morning, mountall informed me that it was waiting
for /home to mount. I pressed ESC which took me to the recovery
console, and then tried running mountall again. This was the result:
sw
There is some improvement with latest updates (1.0 release):
- I enter my passphrase
- I get Recovery Console prompt (press Esc)
- I wait a bit, but my passphrase does not seem to be accepted
- I get new cryptsetup prompt
- I enter passphrase and boot continues
So the only problem seems to be that
I am not sure but it seems that the last two comments are for another
similar bug: Bug #461469
--
mountall 0.2.5 and cryptsetup fail to boot when using usplash
https://bugs.launchpad.net/bugs/456274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The same problem here but without any encrypted partitions or LVM.
** Changed in: usplash (Ubuntu)
Status: New => Confirmed
--
mountall 0.2.5 and cryptsetup fail to boot when using usplash
https://bugs.launchpad.net/bugs/456274
You received this bug notification because you are a member o
I've got a very similar problem, same error reported on boot "...one or
more of the mounts listed in /etc/fstab cannot yet be mounted..." with
the effected drives being my two LVM's which are NOT encrypted.
It all boots up and works ok just get the 'fstab' text (as per post #6)
scrolling in a litt
I did not find a workaround (to get in recovery console and fix my
boot), so I had to revert back to version from the official archive, for
which I have at least a workable workaround.
--
mountall 0.2.5 and cryptsetup fail to boot when using usplash
https://bugs.launchpad.net/bugs/456274
You rece
I have tried 0.2.6~boot1, and it seems it has improved the Recovery
console messages (not apearing anymore), and it also did succeed to
setup dm-crypt device, but then it hangs before it mount my /home. It
may be related to the fact that I have /home on LVM which is on dm-crypt
device.
--
mountal
Since the update to mountall 0.2.6~boot1 my situation appears to have
improved. (I'm afraid I didn't notice whether usplash or cryptsetup were
updated recently).
So I enter the passphrase in usplash, and after that I start getting the
messages from mountall, and I get a lot more than I used to, bu
I can also confirm the bug and I'm having exactly the same behaviour and
setup as Luka (except LVM, not using it).
--
mountall 0.2.5 and cryptsetup fail to boot when using usplash
https://bugs.launchpad.net/bugs/456274
You received this bug notification because you are a member of Ubuntu
Bugs, wh
I can confirm that without usplash, it is possible to enter passphrase
correctly sometime, but not always. I still get Recovery prompt after entering
passphrase, but after couple of retries, it is accepted and boot continues.
Without usplash, Recovery prompt does not reappear each second, but onc
Scott, I have to correct myself: Recovery prompt "steals" input only
after I type passphrase and press Enter and not while typing passphrase.
Even though I have typed passphrase correctly, it did not succeed in
setting up crypt disk. Recovery prompt then repeats about every second
and in between I
>
> Shouldn't usplash stay in the INPUT function until done? That's
> probably the right fix here, make it so usplash ignores/queues further
> commands whilst taking input.
>
> That might help Luka, but would not help me.
Luka (as far as I can tell until they post fstab/mtab) has an unencrypted
r
On Wed, 2009-10-21 at 10:20 +, Luka Renko wrote:
> It looks like that when timeout happens, cryptsetup loose keyboard input
> as it is stolen by mountall ESC/recovery console handling. I suspect
> timout should be somehow disabled until cryptdisks-enable job is running
> (or any other job requ
Luka - so you have a non-encrypted root fs, and only /home is encrypted?
Is that right? Maybe you could post your /etc/fstab and /etc/mtab so we
can see exactly what your set up is.
Also, could you do a test and boot without usplash to see if that solved
the problem (as it did for me). I've put in
I did more testing on my system and it is very hard to type fast enough
that passphrase is accepted by cryptsetup. In most cases, timour
happens, and I get message printed to enter recovery console with ESC.
This message repeats with each keypress (if I try to enter password
again).
If I press ESC
I have the same problem after upgrade to 0.2.5: my /home is on dm-
crypt+LVM and when I type my long password, I get this warning. My
experience is that if I continue typing my password (not getting
distracted), I can get through and my /home is mounted properly. Will
need to do more boots to see i
I have done about 10 boots with usplash on and booting has succeeded
twice, so it is not an entirely consistent failure. I've tried not
pressing Escape and just waiting, but that generally fails, as does
pressing Escape.
Looking through bugs in cryptsetup and usplash, the only similar
sounding one
Oh and in case it is useful here is a fresh mountall debug log
** Attachment added: "mountall.log"
http://launchpadlibrarian.net/34047956/mountall.log
--
mountall 0.2.5 and cryptsetup fail to boot when using usplash
https://bugs.launchpad.net/bugs/456274
You received this bug notification bec
Here is my fstab for comparison with the above message.
** Attachment added: "fstab"
http://launchpadlibrarian.net/34047071/fstab
--
mountall 0.2.5 and cryptsetup fail to boot when using usplash
https://bugs.launchpad.net/bugs/456274
You received this bug notification because you are a member
OK, the text displayed is:
One or more of the mounts listed in /etc/fstab cannot yet be mounted:
(ESC for recovery shell)
/: waiting for /dev/mapper/whisper-whisper_root
/tmp: waiting for (null)
/boot: waiting for /dev/disk/by-uuid/23x
/home: waiting for /dev/disk/by-uuid/d5x
(uuids snip
On Tue, 2009-10-20 at 14:50 +, Hamish Downer wrote:
> I only see the timeout warning after entering the correct passphrase, so
> I press Escape after cryptsetup has finished.
>
Which block device is mountall waiting for?
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
mountall 0.2.5 and
I only see the timeout warning after entering the correct passphrase, so
I press Escape after cryptsetup has finished.
I tried waiting several minutes at the cryptsetup prompt in usplash, and
I saw no warning from mountall. I've also entered the passphrase
incorrectly, and there is still no warnin
Could you confirm when you're actually pressing Escape?
Is it possible that you press it when cryptsetup is asking for a
passphrase, in which case it won't go to mountall but to cryptsetup?
If you've entered your passphrases, do you still see the timeout
warning?
** Also affects: cryptsetup (Ubu
** Summary changed:
- mountall 0.2.5 does not start recovery console after timeout
+ mountall 0.2.5 and cryptsetup fail to boot when using usplash
--
mountall 0.2.5 and cryptsetup fail to boot when using usplash
https://bugs.launchpad.net/bugs/456274
You received this bug notification because yo
48 matches
Mail list logo
