I have this issue of "open: Permission denied Error locking counter"
when trying to mount my home folder from a live sesion. I used the guide
on https://help.ubuntu.com/community/EncryptedPrivateDirectory.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
I have similar symptoms on a natty installation (upgraded), see #796755.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/561390
Title:
LVM - /var failed to mount during boot
To manage notifications a
I have an ubuntu 10.04 server with text mode and find out the following output:
cat /var/log/syslog | grep device-mapper
Apr 7 11:57:58 server01 kernel: [ 30.590688] device-mapper: table: 251:2:
crypt: Device lookup failed
Apr 7 11:57:58 server01 kernel: [ 30.590869] device-mapper: ioctl: er
I hope that i'm not the only one that realized that Scott was saying
"idiot" to himself, am i?
The comment on the commit log was supposed to make fun of himself,
there's no CoC issue here ;)
--
LVM - /var failed to mount during boot
https://bugs.launchpad.net/bugs/561390
You received this bug no
http://bit.ly/aro1lo
--
LVM - /var failed to mount during boot
https://bugs.launchpad.net/bugs/561390
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
https://lists.ubuntu.com/mail
Hi,
This is a bugreport not a discussion forum.
If you have a complain about the behavior of any ubuntu developer I'm
pretty sure there are better ways than this one.
--
LVM - /var failed to mount during boot
https://bugs.launchpad.net/bugs/561390
You received this bug notification because you
"Idiot" word was the only reason why I opened this page. This is very
unprofessional...
--
LVM - /var failed to mount during boot
https://bugs.launchpad.net/bugs/561390
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
The "idiot" message showed up in the Update Manager yesterday in Lucid.
Whatever the reasons are (code or humour) this is embarrassing for the
Ubuntu community and for a professional product. The way it shows up it
looks like a clear breach of the Ubuntu Code of Conduct. I would suggest
editing the
I have to agree with the sentiment of Kelsey. Regardless of how bad the
original code was, it does not warrant the sort of written statement
that appeared in the changelogs. Please keep in mind the Code of
Conduct that you have signed and treat everybody with respect.
In particular, these change
On Thu, Oct 07, 2010 at 07:05:36AM -, Kelsey Thornton wrote:
> "Some idiot thought it'd be a good idea if device mapper didn't respond
> to "add" events, like those during boot. Take their change out back and
> shoot it in the head. LP: #561390."
Unless the kernel has been customised, udev
This is the relevant file portion:
# What idiot thought this was a good idea?
#ACTION=="add", ENV{STARTUP}!="1", NAME="", GOTO="dm_end"
I suppose you had no idea. Please do some research before jumping the
gun.
--
LVM - /var failed to mount during boot
https://bugs.launchpad.net/bugs/561390
You
Description of bug fix:
"Some idiot thought it'd be a good idea if device mapper didn't respond
to "add" events, like those during boot. Take their change out back and
shoot it in the head. LP: #561390."
You are publicly calling a fellow developer an idiot... I think this is
extremely unprofes
Could this bug be affecting mounts on a Coraid SR1521 AoE etherdisk too?
See bug report: https://bugs.launchpad.net/bugs/575053
Thanks,
/mysteron
--
LVM - /var failed to mount during boot
https://bugs.launchpad.net/bugs/561390
You received this bug notification because you are a member of Ubunt
On Sat, 2010-05-01 at 10:25 +, teeedubb wrote:
> I seem to be having a similar issue, although with a mdadm raid 5 array.
> I get the screen stating 'the disk for/mnt/md0 is not ready yet or not
> present'. If i press M and try 'mount -a' it states that 'special device
> /dev/md0 does not exis
I seem to be having a similar issue, although with a mdadm raid 5 array.
I get the screen stating 'the disk for/mnt/md0 is not ready yet or not
present'. If i press M and try 'mount -a' it states that 'special device
/dev/md0 does not exist'. If I try 'mdadm --assemble --scan' it states
'no devices
Hi.
I came from bug #557909.
It seems to be solved after I perform a simple upgrade.
Thank you Scott.
Regards
--
LVM - /var failed to mount during boot
https://bugs.launchpad.net/bugs/561390
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
On Tue, 2010-04-27 at 09:10 +, Carlos Perelló Marín wrote:
> Hmm, today, I rebooted a server we have with Lucid and got this exact
> problem, even with latest package that is supposed to fix it.
>
Please run "dpkg-query -W dmsetup" and report the version returned.
Scott
--
Scott James Remna
Hmm, today, I rebooted a server we have with Lucid and got this exact
problem, even with latest package that is supposed to fix it.
I rebooted it again and it booted without problems, so It smells like
this bug is not completely fixed... (root partition is on a LVM2
partition).
--
LVM - /var fa
well for some reason the UUID for /data was wrong in my fstab (no idea
how this could have been as i had done nothing to it before this and i
thought the whole point of a uuid was that it was unique to that device)
have changed the uuid listed and now works fine.
--
LVM - /var failed to mount dur
this is what my fstab currently contains:
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See
was having the same problem here with /data refusing to mount at boot
added your ppa and updated.
dpkg-query -W dmsetup
shows:
dmsetup 2:1.02.39-1ubuntu4
dpkg-query -W mountall
shows:
mountall2.15~ppa1
however when i boot i still get message to skip or go to maintenance
shell but if i
Just tried uploaded packages, problem seems to be gone ! Thanks
--
LVM - /var failed to mount during boot
https://bugs.launchpad.net/bugs/561390
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
This bug was fixed in the package lvm2 - 2.02.54-1ubuntu4
---
lvm2 (2.02.54-1ubuntu4) lucid; urgency=low
* Some idiot thought it'd be a good idea if device mapper didn't respond
to "add" events, like those during boot. Take their change out back
and shoot it in the head. L
On Mon, 2010-04-26 at 03:29 +, Ali Onur Uyar wrote:
> I upgraded the device-mapper packages from your PPA repo and I've done
> some testing.
>
> I've done five reboots and one shutdown-restart cycle for testing
> without any boot problems so far; seems like things have definitely
> gotten muc
Hi Scott,
I upgraded the device-mapper packages from your PPA repo and I've done
some testing.
I've done five reboots and one shutdown-restart cycle for testing
without any boot problems so far; seems like things have definitely
gotten much better; congratulations. :-)
All LV device nodes have r
** Changed in: lvm2 (Ubuntu Lucid)
Milestone: None => ubuntu-10.04
** Changed in: lvm2 (Ubuntu Lucid)
Status: Triaged => Fix Released
** Changed in: lvm2 (Ubuntu Lucid)
Status: Fix Released => Fix Committed
--
LVM - /var failed to mount during boot
https://bugs.launchpad.net/b
In my PPA you'll find a new dmsetup package, could you try it out and
see whether it makes things better or worse?
sudo add-apt-repository ppa:scott/ppa
sudo apt-get update
sudo apt-get upgrade
Check you have dmsetup 2.02.54-1ubuntu4~ppa1
dpkg-query -W dmsetup
Then reboot.
--
LVM - /v
Thanks to the contributed debugging information, I think I've tracked
down this bug. Since mountall had a bug where it was overflowing
events, I think that may have diluted the debugging information at
first, and that has now been fixed.
The remaining bug is in lvm itself.
** Changed in: mountal
On Mon, 2010-04-26 at 00:36 +, Ali Onur Uyar wrote:
> boot.log.recshell - /var/log/boot.log from recovery shell.
>
Unfortunately it looks like this has the contents from the *previous
boot* (since it shows the boot completing); could you finish booting,
and then attach the "new" /var/log/boot
On Mon, 2010-04-26 at 00:36 +, Ali Onur Uyar wrote:
> The filesystems that fail to get mounted are always the ones on LVM with
> the device files that have root:disk ownership.
>
Do the filesystems that *do not* get mounted have different ownership?
> The /dev/shm permission problem is corre
Ali: I don't suppose you can grab "dmesg" output as well?
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
LVM - /var failed to mount during boot
https://bugs.launchpad.net/bugs/561390
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Hi Scott, I will be glad to help as much as I can.
I am sending you the following information in the attached zip file:
udevadm_info.recshell - Output of 'udevadm info --export-db' in recovery shell.
boot.log.recshell - /var/log/boot.log from recovery shell.
udev.recshell - /var/log/udev from reco
Ali: thanks for your debugging work so far.
Could you boot up to the recovery shell, and then run:
udevadm info --export-db
Capture the output, and attach it to this bug (along with the boot.log
and udev log of the same boot)
status incomplete
Scott
--
Scott James Remnant
sc...@ubuntu.com
On Sat, 2010-04-24 at 16:36 +, Ali Onur Uyar wrote:
> ** Attachment added: "boot.log"
>http://launchpadlibrarian.net/45203739/boot.log
>
Would I be correct that, on this boot, it was /opt that was not mounted?
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
LVM - /var failed to mount
On Sat, 2010-04-24 at 16:36 +, Ali Onur Uyar wrote:
> I am sending the boot.log, but I there is no /var/log/udev on this box.
> How can I activate logging for udev?
>
If boot fails, and you have /var on a separate partition, this can often
be found as /dev/.udev.log -- please attach that
Sco
Given the fact that the mounting of partitions and the boot process
still fails half the time can the status of the issue be updated?
--
LVM - /var failed to mount during boot
https://bugs.launchpad.net/bugs/561390
You received this bug notification because you are a member of Ubuntu
Bugs, which
I've done some more testing trying to isolate the bug. I generated
copies of the boot.log and udev log files in the recovery shell, to
leave out log entries from the boot process after leaving the recovery
shell.
The /etc/fstab contains the following file systems:
/dev/mapper/vg0-lvRoot/
Oops, sorry /var/log/udev was sitting there, but I had not seen it... I
am attaching the log for udev for the same boot attempt...
** Attachment added: "udev"
http://launchpadlibrarian.net/45203998/udev
--
LVM - /var failed to mount during boot
https://bugs.launchpad.net/bugs/561390
You recei
* I have upgraded to mountall 2.14 from PPA, but the boot still fails in
more the attempts. The bug is kind of tricky, because after the
upgrade, it seemed as if the issue was fixed, but in subsequent boots
the problem reappeared.
* The bug does not apply only to /var, but it can be any other
fil
** Attachment added: "udev log with mountall 2.14"
http://launchpadlibrarian.net/45125007/udev__561390_mountall2.14
--
LVM - /var failed to mount during boot
https://bugs.launchpad.net/bugs/561390
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
2.13 didn't work for me, but after trying out 2.14 from the PPA it
booted up cleanly. I'm attaching the boot.log with --debug and
/var/log/udev.
What Happened:
System booted and stuck at mounting /var and /local/mnt, continued booting
after pressing S to skip
What I did:
Added PPA and upgraded t
If you are still having problems, please:
* make sure you have mountall 2.14~ppa1 installed (from my PPA)
* edit /etc/init/mountall.conf and add --debug to the exec line
* reboot
* attach /var/log/boot.log to this bug, along with /var/log/udev
--
LVM - /var failed to mount during boot
https:
>From what I see, the ppa build fixes the buffer to listen to udev.
However, the udev logs don't even list the missing devices
(/var/log/udev) which makes us think that udev itself doesn't know about
the device.
lvscan, however, sees it fine.
--
LVM - /var failed to mount during boot
https://bug
scott: just tried 2.14~ppa1 but it doesn't fix the issue (which we
believe to be also a dupe of bug #527666 and bug #540155). We keep
getting random LVM mount issues at boot.
--
LVM - /var failed to mount during boot
https://bugs.launchpad.net/bugs/561390
You received this bug notification becaus
The bug 527666 is still not fixed, and the two bugs seem to related. I
upgraded to mountall from the PPA, but I still have problems randomly,
getting some filesystems on LVs mounted. The issue does not seem to
occur consistently, because I have upgraded two laptops to Lucid and
only one exhibits th
Tried the PPA over in bug #567910, still get problems
I am getting tempted to have ago at this myself.
May I suggest a fix for mountall to get this thing from being a show
stopper?
This whole thing could be avoided if a mount for the file system read
from fstab is tried. If this fails, th
I was also affected by this bug for about a week. Continuing to wait for
/home to be mounted did not seem to work (for about 5 minutes, at least)
so i did the same thing than Thierry Carrez.
My /home partition is under LVM on top of a software RAID 1.
I tried it three time with this mountall. It
** Changed in: mountall (Ubuntu)
Status: Incomplete => Fix Committed
--
LVM - /var failed to mount during boot
https://bugs.launchpad.net/bugs/561390
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
Hey folks,
I have a random hunch on this one. In my PPA you'll find a new mountall
package, could you try it out and see whether it makes things better or
worse?
sudo add-apt-repository ppa:scott/ppa
sudo apt-get update
sudo apt-get upgrade
Check you have mountall 2.14~ppa1
dpkg-query
Same here, but sometimes everything works (about half the time):
I have /home under LVM:
/dev/cassini/cassini-home /home ext4errors=remount-ro 0 1
The boot process (sometimes) hangs with the following message:
The disk drive for /home is not ready yet or not present.
Continue to wait;
*** This bug is a duplicate of bug 527666 ***
https://bugs.launchpad.net/bugs/527666
** This bug has been marked a duplicate of bug 527666
Waiting for /some/partition [SM]
--
LVM - /var failed to mount during boot
https://bugs.launchpad.net/bugs/561390
You received this bug notification b
I am experiencing exactly the same problem since I upgraded to Lucid two
days ago.
Seems to be related to the following issue in Lucid:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/527666
The boot process hangs with the following message:
The disk drive for /xxx is not ready yet or not
Could you please describe what you mean by "failed to boot".
You say that you see a message about the filesystem, what is that
message? (Please copy it exactly)
If the message offers you to wait, what happens if you wait?
What happens if you press each of the keys?
** Changed in: mountall (Ubu
** Attachment removed: "Desk 1_001.png"
http://launchpadlibrarian.net/43910639/Desk%201_001.png
** Attachment added: "debug.log.txt"
http://launchpadlibrarian.net/44039351/debug.log.txt
--
LVM - /var failed to mount during boot
https://bugs.launchpad.net/bugs/561390
You received this bug
Same here for /home on LVM, here is the mountall --debug log
** Attachment added: "saved.log"
http://launchpadlibrarian.net/44017195/saved.log
--
LVM - /var failed to mount during boot
https://bugs.launchpad.net/bugs/561390
You received this bug notification because you are a member of Ubuntu
55 matches
Mail list logo
