*** This bug is a duplicate of bug 115616 ***
https://bugs.launchpad.net/bugs/115616
pieje wrote:
> *** This bug is a duplicate of bug 115616 ***
> https://bugs.launchpad.net/bugs/115616
>
> I had exactly the same problem after upgrading to Gutsy.
>
> This is what is happening:
> It seems evms is trying to mount a harddisk that is already being mounted by
> the kernel..and thus fails with an error "device lookup failed" or similar.
>
> How to solve it:
> Edit /etc/evms.conf and add in the exclude fields the names of your harddisks.
> Ie in my case I got sda1 and sda2. So I placed sd* to exclude them all.
> I rebooted and laptop was working normal again.
>
Pieje,
Maybe there could be an option in evms to identify active mounts and
either ignore them or execute the remount option to re-attach the
filesystem to the /dev/evms counterpart.
Someday I hope to learn how to use the EVMS bad block relocation
feature. I was once burned pretty bad by an IDE hard drive in a mail
server where the server would lock up hard when trying to read from a
bad block.
Oh, and it might be preferable to identify the filesystems by uuid
instead of by /dev/sda1. I've heard that the discovery order of
/dev/sd* devices is not something that you can count on to be in the
same order every time. You can see these identifiers at /dev/disk/by-uuid/
-Joe Baker
--
device-mapper: ioctl: error adding target to table
https://bugs.launchpad.net/bugs/124641
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
