It happened for me. My original report of the issue is here
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581761. I'm
updated and still my ubuntu won't boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: cryptsetup (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
just wanted to add that I am running 15.10 dev branch and have this
issue too
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273261
Title:
Cryptsetup error during boot:
I had this problem too and while it still exists for me I have
identified a workaround that enables my system to boot. My issue was to
do with cryptsetup not accepting my password. This prevents me for
booting and fixing system issues.
Turns out that my password included a special character '@'
It would appear this message comes from:
eval $(fstype $NEWROOT)
on line 295 of:
/usr/share/initramfs-tools/scripts/local-top/cryptroot
It seems to be a timing issue. An extra udev_settle seems to fix it:
udev_settle
eval $(fstype $NEWROOT)
Then rebuild the initramfs:
update-initramfs -u
OK. (It is a shame boot.log is not rotated to retain old versions.)
I fixed my boot issue and I still see the message - I did not need to
reinstall.
BTW In case anyone is here for a boot problem ;-) In my particular case
I installed lxc-android-config without checking what it was because it
The original bug description was about a message that did NOT prevent
booting
However if for some reason you cannot boot but can view boot messages on
a text console then there is a good chance this message will already be
visible and nothing much else. So if you have not looked before you
might
@Jim: I do see your point.
However, for me the boot issue and this message seemed to be connected:
Just like you, I still could boot in recovery mode, WITHOUT seeing this error
message. Since reinstalling everything I have never seen this message again in
the bootlog. Unfortunately, I did not
Same issue. I just upgraded to 3.13.0-44 and I can't fully boot. The
screen gets stuck on the gnome footprint after entering the sda crypt
password. Recovery mode also does not boot. Restarting gnome-session did
not work.
However, I am able to switch to the CLI using Ctrl+Alt+F2. I installed
I can confirm that this happened to me on a fresh install of Ubuntu
14.04.1 LTS via an expert mode install where I didn't really customize
any of the options that allows, on an older Core 2 Duo E6800 based
system with linux-server kernel choice, with triple drive raid 1 on 1TB
msdos partition
Same errors came up after reboot, but it seemed to progress past it
anyway. Here's a boot.log after the updates, still quite clearly showing
the failure to map the partition but seemingly eventually succeeding and
getting past it (rather quickly too, actually):
Begin: Mounting root file system
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273261
Title:
Cryptsetup error during boot: /scripts/local-top/cryptroot: line
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: initramfs-tools (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273261
My laptop ThinkPad L420 had 14.04 Ubuntu with lvm but no encryption.
Now, after doing fresh install to 14.10 with encrypted hard drive, I get
this problem. Probably unrelated issue, but I had to remove splash from
kernel boot parameters even in order to get to the enter
passphrase-part.
--
You
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273261
Title:
Cryptsetup error during boot:
is this issue necessarily a cryptsetup issue, or could lvm2 or even
update-initramfs be responsible for the bug? At least for me, I get the
message, that the volume-group is now active, before the error message.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Tags added: boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273261
Title:
Cryptsetup error during boot: /scripts/local-top/cryptroot: line 1:
can't open /dev/mapper/ubuntu--vg-root: no
I can confirm @shuhoa findings, my 14.04 /13.10 laptop displays the
error, but I can boot and continue after the error. It just displays the
error message, but harmless.
- Either a second cause for displaying the same error message is present (in
all 14.04 and later distro's.)
- Or a different
I have two almost identical installations of Xubuntu, one on my Laptop
with Intel-graphics, one on my Desktop with a Nvidia 9something. I am
not sure, which graphics drivers are installed, but on the Deskop it is
the proprietary one. I don't know of any other differences. When I
upgraded to
Can anyone boot after encountering this issue? I can drop into root
shell in recovery, mount my partition as rw, but I can't be the normal
boot process to go.
Anyone around to help?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So looking at this, I'm not sure if the message is related to the fact
that I can't boot. I have a 14.04 laptop that has the same message but
boots just fine.
What I did notice is that the hard drive indicator light for the laptop
that can't boot stays on after that message (and hangs).
I've
I've seen this message in the boot logs also, after installing a new
system from scratch with encryption enables. But everything is working
for me, system boots and I can log in.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also having this issue with an upgrade to utopic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273261
Title:
Cryptsetup error during boot: /scripts/local-top/cryptroot: line 1:
can't open
I'm seeing this error and a failure to boot on a previously working
Trusty environment upgraded to Utopic.
As a workaround if I drop to text mode with ESC or boot in recovery I
can see the error /scripts/local-top/cryptroot: line 1: can't open
/dev/mapper/ubuntu--vg-root: no such file but can
ApportVersion: 2.14.7-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.10
InstallationDate: Installed on 2014-03-31 (190 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64+mac (20140326)
Package: cryptsetup 2:1.6.1-1ubuntu3
PackageArchitecture: amd64
Also observed on a Thinkpad T440p running 14.04.1 64-bit Xubuntu. The
system previously booted without any issue, but after bringing all
packages up to date today booting results in the missing xubuntu--vg-
root error. Booting into recovery mode and resuming circumvents the
problem. Tried
High: People can't boot their system.
** Changed in: cryptsetup (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273261
Title:
Cryptsetup error during boot:
I just had this happen to me today. I'm on 14.04LTS and it was current
on it's patches as of 10/2/2014. I've been running 14.04LTS on this PC
since it was release and had no problems until today.
I do have another observation to add. I have a laptop and I encrypted
the whole disk. I started
I pulled my problem HD and hooked up with a USB adapter to another
Ubuntu 14.04LTS machine. It recognized the drive and asks for the
password. I put it in then it said the encrypted disk was mounted but
had no file system. :-( Any suggestions? Is the encrypted drive just
corrupted beyond
@Martin R: Installing KDE over the existing installation does not solve
this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273261
Title:
Cryptsetup error during boot:
Worked pragmatically for me, so I didn't do more research on it.. Don't
know anything more either
On Sep 19, 2014 9:41 AM, tadl tadl-ubu...@taufderl.de wrote:
@Martin R: Installing KDE over the existing installation does not solve
this issue.
--
You received this bug notification because you
I am affected by this issue as well on an almost fresh installation
(14.04.1) after about a dozen boot procedures without issues. Now I am
only able to boot in recovery mode.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I figured out for myself that it is a gnome issue. If you install eg KDE
over the existing installation the error disappears.. Seems to be an issue
with the gnome wm
On Sep 16, 2014 3:41 PM, tadl tadl-ubu...@taufderl.de wrote:
I am affected by this issue as well on an almost fresh installation
It's not a gnome issue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273261
Title:
Cryptsetup error during boot: /scripts/local-top/cryptroot: line 1:
can't open /dev/mapper/ubuntu--vg-root: no
It affected me on previously working system. The workaround is to add
'recoverty' to the boot options and then resume boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273261
Title:
Cryptsetup
I can confirm this bug affecting my 14.04. System freezes after entering
password. System is not usable that way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273261
Title:
Cryptsetup error
I have the same issue which appeared suddenly and I can not login to
ubuntu 14.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273261
Title:
Cryptsetup error during boot:
This issue is preventing me from booting into my system. I have a volume
group called CryptVolume and I have a root partition at CryptVolume-Root
and it can't find that after I enter my password to unlock CryptVolume.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Same issue for me on 14.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273261
Title:
Cryptsetup error during boot: /scripts/local-top/cryptroot: line 1:
can't open /dev/mapper/ubuntu--vg-root:
On 14.04 rather
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273261
Title:
Cryptsetup error during boot: /scripts/local-top/cryptroot: line 1:
can't open /dev/mapper/ubuntu--vg-root: no such
Same here on my Lenovo W530. Seems like a related issue: I have press
[Esc] to get to the disc unlock menu, instead of being directed to a
nice dark violet color inteface automatically (which I know should be
the case, as I've seen it happening once or twice). See boot.log
attched.
** Attachment
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cryptsetup (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273261
Title:
I have the same issue
see my boot.log
** Attachment added: boot.log
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1273261/+attachment/3971142/+files/boot.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: boot.log
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1273261/+attachment/3959193/+files/boot.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273261
Title:
44 matches
Mail list logo
