Looks like my BR http://bugs.debian.org/402511 against lvm-common is
related to this issue.
The issue itself seems to be based in lvm2 and udev.
David Härdeman pointed me to
https://bugzilla.novell.com/show_bug.cgi?id=178321
which may have a (partial) fix for this issue in
Hi!
I have also just experiened this:
device-mapper: table ioctl failed: No such device or address
Fatal: device-mapper: dm_task_run(DM_DEVICE_TABLE) failed
What I did: install etch with root-on-lvm from the rc1 installer.
Boot up. dist-upgrade to newest etch (udev 103, kernel
On Fri, December 8, 2006 4:12, Daniel Burrows said:
On Thu, Dec 07, 2006 at 09:33:33AM +0100, Loïc Minier [EMAIL PROTECTED] was
heard to say:
some trivia first:
- Debian's lilo is patched with an unofficial patch for device-mapper
support which was not updated since mid 2005
- Debian
On Fri, December 8, 2006 10:31, Loïc Minier said:
On Fri, Dec 08, 2006, David Härdeman wrote:
Don't mix up boot-on-raid and boot-on-device-mapper, they are two
different things using different kernel subsystems (md and dm).
Err, md is dm based, right?
Nope, see
Hi,
some trivia first:
- Debian's lilo is patched with an unofficial patch for device-mapper
support which was not updated since mid 2005
- Debian just hits the problem, but it seems to be a common problem if
I look at google queries; see also:
Loïc Minier wrote:
[...]
Could you send a lilo run in verbose mode and your lilo.conf to the
bug? A dmsetup ls would be nice as well.
Ok, so here are lilo.conf, dmsetup ls, and some lilo output:
- lilo-t-v.bad
- lilo-t-v5.bad
- lilo-t-v.ok
Cheers
Harry
boot=/dev/sda3
Package: lilo
Version: 1:22.6.1-9
Severity: grave
My system has a somewhat unusual setup: I'm using lvm on RAID1. Sometime
recently, lilo just quit working:
[EMAIL PROTECTED]:~$ sudo lilo
Warning: COMPACT may conflict with LBA32 on some systems
device-mapper: table ioctl failed: No such
7 matches
Mail list logo
