LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Fedora (http://www.linuxquestions.org/questions/fedora-35/)
-   -   Device-mapper errors FC6 (http://www.linuxquestions.org/questions/fedora-35/device-mapper-errors-fc6-498393/)

cuco76 11-03-2006 04:20 PM

Device-mapper errors FC6
 
Hello!

Anyone seen this before
Code:

ACPI: Power Button (FF) [PWRF]
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com
device-mapper: multipath: version 1.0.4 loaded
device-mapper: table: 253:0: linear: dm-linear: Device lookup failed
device-mapper: ioctl: error adding target to table
device-mapper: table: 253:0: linear: dm-linear: Device lookup failed
device-mapper: ioctl: error adding target to table
device-mapper: table: 253:0: linear: dm-linear: Device lookup failed
device-mapper: ioctl: error adding target to table
device-mapper: table: 253:0: linear: dm-linear: Device lookup failed
device-mapper: ioctl: error adding target to table
device-mapper: table: 253:0: linear: dm-linear: Device lookup failed
device-mapper: ioctl: error adding target to table
EXT3 FS on sda3, internal journal
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds

I just installed FC6 and I am seeing errors on boot but I can't seem to see a log file with what scrolls during boot but dmesg shows these device-mapper errors.

Also curious how to view the boot log file. When i open /var/log/boot.log as root in gedit i see nothing and when i try to view through the gnome log monitor it won't open and a message says that it is an invalid log file??

any thoughts?
thanks!

PTrenholme 11-04-2006 12:53 PM

You might get a clue looking in man dmsetup,although you'll need to look at the initrd internals to see how dmsetup is being called.

I suspect that the mkinitrd run during the setup found a block device that you've since unplugged, and that it configured the device mapper to treat all the partitions on that device as a single, linear, volume.

Perhaps re-running mkinitrd on your working system would eliminate the messages. (Just a guess.)

If you're moving around physical devices, you should probably be using udev to assign them "fixed" places in the /dev tree without regard o the actual physical location of the device.

cuco76 11-07-2006 09:36 AM

Thanks I will check into this when I get back to my machine!

cowboycraig 05-02-2008 08:16 PM

Errors seem OK
 
I get these errors every boot, but my /dev/mapper/mpath* devices are OK.

I think the error is that the device names under /dev that get multipathed change.

So dmsetup and multipath -v2 get confused and log errors. In the end it all works out.

Have not quite worked out if running mkinitrd fixes this. Would be nice if it did. But the device names still may change at boot time.

When I do a multipath -l and look at the devices that make each mpath device the names change. Udev would be the same way, at least on SAN you can bind to the LUN ID, in what ever form that comes.


Craig


All times are GMT -5. The time now is 01:08 AM.