Closed as per verification of release notes.
** Changed in: ubuntu-release-notes
Status: Confirmed = Fix Committed
** Changed in: ubuntu-release-notes
Status: Fix Committed = Fix Released
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You
** Branch linked: lp:ubuntu/gutsy/evms
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: ubuntu-website
Status: Confirmed = Invalid
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
** Branch linked: lp:ubuntu/gutsy/evms
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Steve i put this at the wiki:
Upgrading from EVMS 6.06 LTS Systems
*
Since 7.10, EVMS support was dropped by upstream and moved to
Universe in Ubuntu. Users from previous LTS Release should be aware of
this issue and act accordingly as suggested at
https://wiki.ubuntu.com/Evms and
Andres,
Can you please propose some language to use in the release notes for
describing this issue? The 8.04 release notes are otherwise unlikely to
get much additional attention at this point.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You
Maybe this can be addressed at the release notes. So i'm adding it to
the wiki so the admins out there upgrading from 6.06 to 8.04 can take
this into account beforehand.
https://wiki.ubuntu.com/HardyReleaseNotes
Also i'm adding the ubuntu website tasks to update the website.
** Changed in:
Just to be clear -
This bug is *not* fixed. Upgrading via command line and completely
breaking a working system is not very cool. System critical bugs that
are open for years doesn't bother me half as much as serious bugs
erroneously marked as fixed...
--
Device-mapper errors: dm-linear,
2009/2/10 Christian Gunning icos.atr...@gmail.com:
Just to be clear -
This bug is *not* fixed. Upgrading via command line and completely
breaking a working system is not very cool. System critical bugs that
are open for years doesn't bother me half as much as serious bugs
erroneously
Same as 'PETIT Aymeric' here...
Just upgraded a server from dapper to hardy, after which the /backup couldn't
be mounted... same device-mapper errors.
After removing evms and a reboot, it worked again.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You
I had the same (udevd) problem after upgrading kubuntu 6.06 to 8.04 on PPC.
Removing evms and reboot helped.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
I had the same (udevd) problem after upgrading xubuntu 6.06 to 8.04 (although
the problem might already have occurred with 6.06)
removing evms and stop, restart udevd helped.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug
Hi,
I have do apt-get dist-upgrade on a server (without any X environment, so I
can't use update-manager) and I must to remove evms manually to fix the issue.
To remove first reduce LogLevel to 3 (using the sysrq key (alt+sysrq+3))
then update the path with the main binary directory (export
If you read the first post you will see:
[This issue is fixed by removing evms: just type sudo apt-get remove
evms in a console.]
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs,
On 21/12/2007, Richard Kleeman [EMAIL PROTECTED] wrote:
If you read the first post you will see:
[This issue is fixed by removing evms: just type sudo apt-get remove
evms in a console.]
But that does not fix the issue. The issue is that unless you file a
duplicate of this bug and get to read
So, if apt-get dist-upgrade is no longer considered a supported method
or the right way of upgrading, what are users to do when the update
manager chokes on a package that corrupted on download and has to be
killed? That happened to me. After a bit of fighting with dpkg, I
could get apt-get
I don't usually like to add a me too comment to bugs but I think this
one is rather important and I want to add my almost insignificant voice
-- happened on one of my production servers yesterday during a
dist_upgrade to Gutsy. The purge of evms worked fine and the killall
udevd made the machine
Scott Remnant posted a wiki entry on the situation:
https://wiki.ubuntu.com/Evms
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs
** Description changed:
[This issue is fixed by removing evms: just type sudo apt-get remove
evms in a console.]
In gutsy the new 2.6.22-4-generic kernel produces the following error
message repreatedly:
May 19 10:10:16 richard-desktop kernel: [ 227.338011] device-mapper: table:
I'm confused as this bug still affects users who need evms to operate
their raid.
Are there any other options for users in this case? If not, the bug
needs to be reopened.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification
I have exactly the same problem since the latest kernel update with my
Kubuntu gutsy installation:
kernel [ 2185.818660] device-mapper: table: 254:1: linear: dm-linear: Device
lookup failed
25.11.2007 11:40:34 zalas kernel [ 2185.819148] device-mapper: ioctl:
error adding target to
It's explained at the beginning of the bug description. I updated it so
it is more explicit, but *please* always read carefully at least the
description if not the complete thread before asking for help. Thanks
for caring about that, though.
** Description changed:
- [This issue is fixed by
Sorry about that. Thanks. Luther
- Original Message -
From: Milan [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, November 25, 2007 3:07 PM
Subject: [Bug 115616] Re: Device-mapper errors: dm-linear, lookup failed
It's explained at the beginning of the bug description. I updated
I don't know. My system is operational, but I don't know what has been
updated and what has not. Sorry I can' help you. Luther
- Original Message -
From: Hagy Hag [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, November 25, 2007 2:46 PM
Subject: [Bug 115616] Re: Device-mapper
I agree with the posters who mention that if the good old method of
upgrade apt-get dist-upgrade is no longer supported for some
functions, a note should be added to apt packages or elsewhere. I
just upgraded my machine and had the same error. I too have been
upgrading for several versions now.
I have another question, evms successfully removed here, however if I do
a locate evms here is the result:
/var/lib/dpkg/info/evms.list
/var/lib/dpkg/info/evms.postrm
/var/lib/dpkg/info/libevms-2.5.list
/var/lib/dpkg/info/libevms-2.5.postrm
/var/log/evms-engine.log
/var/log/evms-engine.1.log
try a purge maybe?
it's the underscore character on the package in aptitude...
_J
On Nov 5, 2007 5:10 AM, Cimmo [EMAIL PROTECTED] wrote:
I have another question, evms successfully removed here, however if I do
a locate evms here is the result:
/var/lib/dpkg/info/evms.list
I initialled installed v 6.06, upgraded to 7.04 (Feisty) several months
ago and was running well, yet after update and upgrade to 7.10 this
morning I had the above reported problem even after removing evms, i.e.
I cannot boot into 2.6.22 but 2.6.20. Not sure what's happenning. Mine
is a Dell GX260
I *tried to* upgrade using the instructions at
http://kubuntu.org/announcements/7.10-release.php#upgrade
page.
The installer crashed so I resorted to the good ol' 'apt-get dist-upgrade'
method I've used since my
Debian times. It has always worked before quite well.
In case there is a single
On 30/10/2007, Scott Hilleard [EMAIL PROTECTED] wrote:
Wait, sorry, that wasn't intended as a personal insult, thats his
launchpad username!!! I was directing the comment at him and didn't mean
it as an insult at all! :)
Ah, I was looking from my mailbox, and it looks like my spam filter
On 29/10/2007, Scott Hilleard [EMAIL PROTECTED] wrote:
foolishchild, did you upgrade before or after the release of Gutsy?
Personal insults aren't going to solve the problem.
It might be that it works if the Single Correct Upgrade Procedure is
followed. But this is a very specific and narrow
Wait, sorry, that wasn't intended as a personal insult, thats his
launchpad username!!! I was directing the comment at him and didn't mean
it as an insult at all! :)
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification
In my opinion the only possibility is that these people have explicitly
chosen to not remove obsolete software when asked by the installer.
At least in my case this is simply not true. I did use update-manager
and did agree to remove all absolute packages. There are other reports
above which
I had this problem. Thankfully I found this bug report.
I did NOT choose not to remove obselete software - in fact I was careful
to remove obselete software. I also made sure my feisty system was
totally up to date before starting.
My system has evolved from dapper drake thru edgy, eisty, gutsy,
foolishchild, did you upgrade before or after the release of Gutsy?
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
I don't want to be boring, but is it possible that update-manager
crashed before it finished all the updates he wanted to perform? It's
what happened to me: it took some time before I realize that it hadn't
finished but had discretely crashed. Just an idea - chastise me telling
that apt does not
yeah Milan that happened to me, but I had restarted it in text mode and
finished.
I still thinking all people with problems didn't uninstall obsolete packages...
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because
Just reporting I saw these exact errors on dmesg after updating to 7.10
today
[ 615.757307] device-mapper: ioctl: error adding target to table
[ 615.769759] device-mapper: table: 254:2: linear: dm-linear: Device lookup
failed
--
Device-mapper errors: dm-linear, lookup failed
Just confirming that removing evms cured this. Another symptom I was
seeing is that my CD tray (a.k.a. cup holder) would only open half way
and close again when this problem was present.
Also for the record I just used the update-manager GUI for my upgrade.
--
Device-mapper errors: dm-linear,
guys stop spamming and confirming, this bug is known at 100%.
If you upgrade from supported tool then evms will be automatically removed (I
saw that it's removed in a Feisty-Gutsy upgrade) if you are not using official
upgrade method then don't expect that all will work.
So stop spamming and
Sorry Cimmo, but you're wrong. A number of people have confirmed that
this bug still happens on Gutsy upgrades, EVEN WHEN using the upgrade-
manager to perform the upgrade. In fact Alex, whom you responded to,
was using the official upgrade method when he ran into the problem.
This bug should
Just out of interest... did the people who upgraded using the update-
manager, but still suffered the problem, apply all updates to Feisty
before upgrading to Gutsy? If the update-manager was fixed to remove
evms in an update, then I can see the problem potentially occuring for
Feisty users
Scott Hilleard ha scritto:
Just out of interest... did the people who upgraded using the update-
manager, but still suffered the problem, apply all updates to Feisty
before upgrading to Gutsy? If the update-manager was fixed to remove
evms in an update, then I can see the problem potentially
I upgraded about a week before release, using update-manager -d, and
agreed for packages to be removed. I checked the list, and don't
remember evms being on it.
--Max
On 29/10/2007, Cimmo [EMAIL PROTECTED] wrote:
So, ATTENTION ATTENTION to all people that had this bug:
- please describe which
For the sake of not being totally useless here's what I recall of this
story, this happened on mom-in-law machine, so there's nothing more I
can contribute, being in other city as of now.
I have been testing gutsy alpha, beta and final on that machine. Always
using the update-manager GUI for the
Upgraded a box to 7.10 today, it originally ran 6.06, then it was
upgraded to 6.10 and 7.04. All by using apt-get and aptitude. On boot I
get a root shell and the continuous error spewing makes it difficult to
use that shell.
I browsed trough this thread and if I've read it correctly what this
Same here. Just dist-upgraded to Gutsy and got unbootable system as a
result with this error. It was unable to mount my /home. This is a very
bad bug as it probably breaks the upgrade for many people. The package
could be removed automatically in dist-upgrade in case it's not needed
and causes
Please read the thread above before commenting. evms is removed if the
standard and recommended method for upgrading feisty (i.e. upgrade-
manager) is used.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are
As noted in my duplicate report #156157, I encountered this problem when
upgrading a server not a workstation -- I upgraded the workstations with
upgrade-manager as is recommended and had no problem. The server I
upgraded with do-release-upgrade which is the recommended mechanism for
upgrading a
I had the same error when upgrading to gusty. My laptop had a feisty
version upgraded from drapper. I am going to remove evms to confirm the
workarround.
To upgrade I use the command update-manager -d -c, this because when
opening the upgrade manager it did not detected the availability of the
I also had this problem. I upgradet from feisty using the Update
Manager, but it stopped at mpd (still having problems there), so I never
finished the upgrade. I rebooted, got this error, freaked out, and
removed evms after googling the error text on my cell phone. I've never
installed evms
I have the problem on a new upgrade, I had to type this command to the
blind :
aptitude remove evms
(because too much error messages scrolled)
I had already this problem when I upgrade from Feisty to Gutsy Beta.
--
Device-mapper errors: dm-linear, lookup failed
Me to. Upgrade to gutsy via dist-upgrade (N times).
2.6.20 works with gutsy, 2.6.22 does not.
1) It generates annoying Device-mapper errors: messages
2) it does not mount /dev/sda1 to /windows/c automatically (and mount -a does
not help too)
3) after apt-get remove evms it fails to boot because
Just upgraded edgy-feisty-gutsy in a single day (machine was
originally installed as dapper), and this is still a problem. In my case
/home was not mounted...which meant that users couldn't log into a
graphical shell. I'm glad for the Kubuntu failsafe mode (and it's good
that I had a 2nd computer
So to re-cap again. I believe the situation is:
If you do the upgrade via to Gutsy the GUI tool System - Administration
- Update Manager all is well.
If you do the upgrade using apt-get this will not remove evms for you
and you are likely to be in trouble, You have to remove evms yourself.
sudo
I removed evms (#apt-get remove evms) e reinstalled it again (#apt-get
install evms) and the error vanished !
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
I upgraded from Feisty to Gutsy last night. As with the Dapper-Edgy-Feisty
upgrade it didn't go entirely smoothly, but I soon got it to finish the job.
Then today I noticed that I can't mount one of my logical partitions
(thankfully just a media storage partition) and this appears to the be the
Upgraded to Gutsy with `update-manager -d` on Monday 15th (two days ago)
and I'm getting this. EVMS was not removed, but AFAIK I don't use it.
I'm booting fine with my Feisty kernel. I've upgraded all the way from
Breezy or Hoary, but I may have skipped a release somewhere (I know this
is a BAD
Just another me too.
Tried to upgrade using the GUI (suggested) method for Kubuntu 7.04,
failed on debconf packages and never worked right since then. Ended up
having to upgrade via sudo apt-get -f install and sudo apt-get dist-
upgrade a couple times. Then it worked but upon reboot it gave the
Just another follow up. Today, I upgraded to gutsy, from feisty, on a
machine that has seen several upgrades in the past, and I still hit this
bug. Removing evms fixes the problem, it seems.
On the plus side, wireless networking now works much better for my
card:-)
--
Device-mapper errors:
I just upgraded from Feisty to Gutsy RC tonight, and I still ran into
this problem. My system couldn't mount any of my partitions other than
/ (so no /home, etc.) and I was getting errors spewing to the log file
and udev stealing tons of CPU. At first I ran /etc/init.d/udev stop to
get back the
Jan: you are incorrect, evms is the cause of the errors you are seeing
because it is repeatedly attempting to create devmapper devices for a
block device already claimed.
It is correct behaviour that you cannot create devmapper block devices
for an already claimed block device.
** Changed in:
I can confirm that this is not yet fixed in update-manager on Feisty. I
upgraded my main system to the Gutsy release candidate last night (using
update-manager -d) and evms was not listed for removal. When the 2.6.22
kernel was booted this bug appeared with a vengeance preventing a boot.
the
The fix for this has been accepted for gutsy, with the following
changelog:
update-manager (1:0.81) gutsy; urgency=low
[ Jonathan Riddell ]
* DistUpgrade/DistUpgradeViewKDE.py:
- Add word wrap to quesiton dialogue
[ Michael Vogt ]
* DistUpgrade/DistUpgradeControler.py:
- make
Here is mine (after apt-get removal of evms and reboot in gutsy):
/dev/sda5 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
/sys on /sys type sysfs (rw,noexec,nosuid,nodev)
varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755)
varlock on /var/lock
For the folks that still saw this problem during the RC upgrade, can you
attach the output of mount? The only way I see that evms would be
left out of the removal list is if evms is listed in your active
mounts. (Additionally, I've been unable to reproduce this problem --
evms gets uninstalled
Just to follow up on Paul Smith's comment, I just (2 hours) did a tidy-
out of unused packages, cleaned/flushed package cache, a full update of
7.04 followed by update-manager -d and didn't intervene in any package
removals. Same issue. This is not yet fixed as far as I can see. The
fix listed
Keybuk mvo: installed feisty, made sure universe was enabled and installed
evms
upgraded to gutsy
evms was *not* removed
mvo Keybuk: the reason that evms got not removed in your case was that you
had packages depending on it and the upgrader is trying to be too clever.
thanks for catching
Based on the recent comments that the fix doesn't solve the problem, I'm
reopening the bug since it seems to be a problem for those people who
are not using update-manager to update.
However, worryingly, it also still seems to be a problem for those who
*are* using update-manager. If the project
Matthew East , may be the common point for people having the problem is
that their system has dist-upgraded multiple times to follow ubuntu
version since dapper as opposed to a fresh edgy system going to gutsy.
This is my case here since I've been dist-upgrading a few versions on
this machine.
I
Interestingly my laptop started life with Edgy and has been dist-
upgraded to Fiesty and then Gutsy using aptitude and hasn't suffered
this issue at all! I used update-manager -d to upgrade my AMD64 desktop
which did suffer the problem. As people are getting the problem with
both apt and
You could be right - my systems started with 5.10 and they both had this
problem during upgrade. A friend of mine who started with 6.10 did not
have this problem during upgrade to gutsy. By the way for one system I
used aptitude, for the other adept's update manager.
--
Device-mapper errors:
Un-milestoning and Un-assigning this bug.
evms is unsupported (and effectively unmaintained by upstream, who have
not yet provided a version that actually works with the vanilla 2.6
kernel).
Our preferred solution is to ensure evms is removed on upgrade.
** Changed in: evms (Ubuntu)
If evms never worked with the 2.6 kernel, then why did Dapper ship with
it installed and enabled by default (I have just verified it was on the
Dapper based desktop we have here at work). This upgrade bug appears to
mainly be affecting people that ran dapper (or earlier) at some point in
the past
** Also affects: update-manager (Baltix)
Importance: Undecided
Status: New
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Also affects: update-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: baltix
Sourcepackagename: update-manager = None
** Changed in: baltix
Status: New = Invalid
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You
I too have used update-manager -d for several Ubuntu versions in
sequence. I did never actively install evms and was not aware of its
existence. Only when the update to Gutsy left me with an unbootable
system (with the latest 2.6.22 kernel, 2.6.20 allowed me to boot and fix
the system). I can
I have added update-manager to the affected packages list since this
*appears* to be a bug there. Any comment by this package maintainer
greatly appreciated.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you
I wrote earlier that I suffered this bug when updating an IBM T30 laptop
from Feisty to Gutsy. What I omitted to say was that this laptop had
undergone a number of online updates prior to this one. I do not
remember which version I started with but it has probably only had on-
line updates since
Thanks Kees. That should solve this problem for nearly all users.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
ok may i sum ?
EVMS were previously installed by default on early Ubuntu version
(anterior to Feisty)
This project is no longer installed by default
This project is no longer maintain by it author
This bug is fix, i guess that update-manager will ask you to remove EVMS since
all unsupported
The update-manager in beta did not have the rules to remove evms. It
does currently, so this issue from an upgrade perspective should be
fixed now.
** Summary changed:
- Device-mapper errors: dm-linear, lookup failed
+ Device-mapper errors: dm-linear, lookup failed [fixed after beta]
**
Gaëtan - you have it exactly right.
I've summed up the situation in more detail here:
https://wiki.ubuntu.com/Evms
This hopefully explains why we've chosen to drop support for and remove
evms, and what the underlying problem is that causes this bug.
I've also confirmed that updating from dapper
Okay let's sum this up. This problem occurs:
Quote:
May 19 10:10:16 richard-desktop kernel: [ 227.338011] device-mapper: table:
254:1: linear: dm-linear: Device lookup failed
May 19 10:10:16 richard-desktop kernel: [ 227.338017] device-mapper: ioctl:
error adding target to table
People point
przemjaskier,
As Scott previously mentioned, the evms project is no longer maintained and the
patch they suggested does not seem to work for everyone if at all.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because
I did the on-line upgrade from Feisty to a Gutsy beta on an IBM T30
Laptop that I only use for web browsing. It displayed this problem
straight away, very high CPU utilisation.
The resource tab of the System Monitor program charts CPU utilisation
and made it obvious that CPU was being wasted
Scott,
Sorry to be a pain but I am confused about this bug. It seems upgrades
to Gutsy beta from Feisty are not removing evms. Will this change when
the distro goes live i.e. will the changes of July 10 in update-
manager which cause evms to be removed come into effect when the distro
is
I have just been hit by this bug upgrading my AMD64 desktop from Feisty
to Gutsy. Booting the old kernel and using aptitude to remove the evms
package then rebooting fixed the issue. My desktop started off running
Dapper and has over time been dist-upgraded to each new version of
Ubuntu. I have
Sorry, should have provided some additional info. I'm running amd64 and
I used the update manager to perform the upgrade. I accepted all
proposed changes in the update manager process. I don't know what evms
is so I wouldn't have installed it manually (I have been doing upgrades
since 6.06). I
Scott,
I am a bit concerned about this bug. The fix has been released (latest gutsy
update of evms) but people with current gutsy are still reporting this as an
issue. Should people check the version of evms and confirm the fix is not
working?
--
Device-mapper errors: dm-linear, lookup failed
On Mon, 2007-10-08 at 13:53 +, Richard Kleeman wrote:
I am a bit concerned about this bug. The fix has been released (latest
gutsy update of evms) but people with current gutsy are still
reporting this as an issue. Should people check the version of evms
and confirm the fix is not
I used update-manager -d to update my system from 7.04 to 7.10 beta on
the 3rd of Oct. The upgrade process asked me to confirm the deletion of
a lot of packages what I did. Nevertheless evms was not removed and my
system didn't boot with kernel 2.6.22-12 after the upgrade. Luckily
2.6.20-16 was
Hmmm here is the changelog entry for upgrade-manager
- mark evms as obsolete if it is not in use
10 July 2007
And it has switched from main to universe(for fresh installs)
Wonder why this change didn't work for Manfred?
--
Device-mapper errors: dm-linear, lookup failed
Scoot I did update -d from a fully up to date 7.04 system and agreed
to all deletions, but evms was still there.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Please explain me something. AFAIK removing evms criples some
functionality related to automounting - according to some comments in
this (and related) bug report. If so, why removing evms is an accepted
way of resolving this issue?
--
Device-mapper errors: dm-linear, lookup failed
Just did an upgrade to gutsy from 7.04 ( 1 hour ago) and had the same
problem. Removing evms fixed it.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
This does not seem to be fixed, on gutsy beta I have the latest evms:
ii evms 2.5.5-26ubuntu1
Enterprise Volume Management System (core)
ii evms-ncurses 2.5.5-26ubuntu1
Enterprise
After upgrading to from 7.04 to gutsy, I couldn't boot with 2.6.22-12 and -13.
I only got repeated messages scrolling on the screen: 'device-mapper: table:
254:7: linear: dm-linear: Device lookup failed'.
2.6.20-16 booted fine.
After changing /etc/evms.conf (exclude = [ * ] in sections
Got this one, too. In addition to flooding dmesg it also locked up my
dvd-drive and prevented mounting my secondary HD. Tried also using
vanilla kernel 2.6.23-rc9 but the same thing happened with that as well
(not so surprising after reading the evms url above).
Removing evms magically fixed the
I have a current install of Gutsy, and I am experiencing this same
behaviour on a Compaq Presario 2190 Laptop.
stopping udevd stopped the flood of dmesg notices
removing evms stopped it all together.
Although, I'm sure this stuff was installed on purpose, I'm waiting for
a proper solution..
1 - 100 of 155 matches
Mail list logo
