mray(mra) please could you list the steps your friend took to
resolve the issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481536
Title:
"cryptsetup: unknown fstype, bad password or
** Changed in: cryptsetup (Ubuntu)
Milestone: ubuntu-17.01 => ubuntu-17.02
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481536
Title:
"cryptsetup: unknown fstype, bad password or options?"
** Changed in: cryptsetup (Ubuntu)
Milestone: None => ubuntu-17.01
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481536
Title:
"cryptsetup: unknown fstype, bad password or options?" error
A a skilled friend of mine had a look at my issue and found out that the
UUID of my bootable partition got mixed up. after setting things
straight in a textfile where this gets looked up my problem was gone and
I could boot normally again. Sorry for not being able to provide better
terminology,
I'm on Ubuntu 16.04, added the ppa and updated my cryptsetup package
(even did dpkg-reconfigure) but run into the same problem still. Do I
need to do something else?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attached is a new revision (v4) of the patch, this time targeted to
Xenial (16.04) instead of Wily (15.10).
Changes from v3 to v4:
* restore activate_vg() (which runs 'lvm vgscan' and 'llvm vgchange
-a y') because Xenial's lvm2 package no longer includes udev rules
that run those
FYI, lvm2 2.02.133-1ubuntu8 dropped the udev rule that runs 'lvm vgscan;
lvm vgchange -a y', so cryptsetup must still run those commands in
scripts/local-top/cryptroot. In other words, they can't be dropped as
proposed in comment #15.
--
You received this bug notification because you are a
I have the same problem with Kubuntu 14.04.4 Trusty Tahr. The common LTS
updates yesterday contained 2:1.6.7-Ovanir1~14.04(trusty) which replaced
2:1.6.1-1ubuntu1 (trusty). While boot I get the message "cryptsetup: unknown
fstype, bad password or options?" although the password was correct.
I'm attaching another revision of the patch (v3).
Changes from v2:
* skip calls to udev_settle() if the device of interest already
exists
* don't assume the unlocked device will appear after udev_settle()
(sleep until the device appears, if necessary)
* wait for the LVM logical
>> The patch looks good to me, except I wonder whether the call to
>> udev_settle() between the two blkids should be moved up to just
>> after $cryptopen (see attached patch). Thoughts?
>
> Since there was not already a udev_settle call there, I assumed (but
> did not verify) that cryptsetup
I uploaded Steve's patch to my PPA:
https://launchpad.net/~rhansen/+archive/ubuntu/bug1481536
I haven't tested it yet. The patch looks good to me, except I wonder
whether the call to udev_settle() between the two blkids should be moved
up to just after $cryptopen (see attached patch). Thoughts?
On Fri, Dec 04, 2015 at 03:51:50AM -, Richard Hansen wrote:
> I uploaded Steve's patch to my PPA:
> https://launchpad.net/~rhansen/+archive/ubuntu/bug1481536
> I haven't tested it yet. The patch looks good to me, except I wonder
> whether the call to udev_settle() between the two blkids
This problem is caused by a race condition, which is why only some
people are experiencing it.
At /usr/share/initramfs-tools/scripts/local-top/cryptsetup line 322, the
setup_mapping() function in the cryptroot script calls the activate_vg()
function, which runs 'lvm vgchange -a y'. At line 340,
Thanks for the analysis and patch, Richard. I think you've put your
finger on the problem. However, I see that there's only one code path
where we call vgchange without already calling udev_settle afterward A
proper fix for this should eliminate unnecessary calls to udevadm settle
that would
** Changed in: cryptsetup (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481536
Title:
"cryptsetup: unknown fstype, bad
The attachment "Patch for /usr/share/initramfs-tools/scripts/local-
top/cryptroot" seems to be a patch. If it isn't, please remove the
"patch" flag from the attachment, remove the "patch" tag, and if you are
a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message
Hello, i hope my first post is helpful.
After some debugging i figured out where this error message "cryptsetup:
unknown fstype, bad password or options?" in my case comes from.
The point is that i am having a LVM Partition which holds several
logical volumes which need to be mounted (at least
In my comment #11 i did some mistake in "3)"
I copied the wrong command for changing the use_lvmetad parameter temporarily.
I missed the "-i" for sed.
To not confuse someone here is the corrected part:
# Replace use_lvmetad=1 with use_lvmetad=0
sed -i -E
I have the same issue as the OP on Ubuntu 15.10 Desktop AMD64. It spits out
"cryptsetup: unknown fstype, bad password or options?" after the correct
passphrase is entered then proceeds to boot normally. I thought it was just me,
because I have a LUKS-encrypted LVM setup that might be different
I have the same issue as the OP and Johny Rogers. System boots
successful and notifies me cryptsetup was successful but first it
displays the unkown fs type, bad option password message. This started
happening after upgrading lubuntu to wily.
--
You received this bug notification because
After entering the password encryption sends me the Emergency mode. Here
you enter "systemctl default" and can enter the desktop Ubuntu 15.10.
Now I'm trying to fix the bug with "sudo dpkg --configure -a"
//Sorry for my bad english
--
You received this bug notification because you are a member
I'm also experiencing this. I noticed the following in my
/var/log/boot.log:
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Reading all physical volumes. This may take a while...
Found volume group
This also occurs on Ubuntu MATE 15.04 running cryptsetup 1.6.6-5ubuntu2
(versus the ubuntu1 in the original report).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481536
Title:
"cryptsetup:
I also ran into this problem. I was able to fix it by looking at my
dmesg and realizing that the proprietary ati drivers don't work with the
4.X kernel. I had the ones from ATI installed so when it'd try and boot
up it'd get past the encryption but then the driver would crash.
I solved this by
I had this after upgrading to wily four days ago. I get the error
message as above for Johnny Rogers, but then the system hangs and will
go no further... my workaround is to boot up in recovery mode which
gives asks for my password then gives this message (about 20 times):
remove ioctl on
** Description changed:
Since upgrading to cryptsetup-1.6.6-5ubuntu1 to replace
cryptsetup-1.6.1-1ubuntu7 today on my Ubuntu Wily 15.10 installation, I
have been receiving an error message at boot time after entering my
passphrase to unlock the LUKS partition. I noticed that at the same
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/1481536
Title:
I've gotten this message as well for Kubuntu Wily, but I didn't have
issues unlocking it. I first get the prompt screen for cryptsetup to
enter password, I then enter correct password for it, I then get:
"Unknown Fstype, bad password or options?" Then it gives message
"sda5_crypt setup
** Summary changed:
- cryptsetup: unknown fstype, bad password or options? error decrypting LUKS
volume at boot
+ cryptsetup: unknown fstype, bad password or options? error unlocking /
decrypting LUKS volume at boot
--
You received this bug notification because you are a member of Ubuntu
29 matches
Mail list logo
