boot + lvm ?

Hello,I encounter a problem using lvm and lilo.On standart install, everythings works despite the boot partition is on a logical volum.But when I try to make a custom kernel and then run a lilo, I get the following message:device-mapper: table ioctl failed: No such device or addressFatal: device-mapper: dm_task_run(DM_DEVICE_TABLE) failedHere is my lilo.conf---------------------------------boot=/dev/sdaroot=/dev/mapper/volume_group1-logical_vol2map=/boot/mapdelay=20default=Linuximage=/vmlinuz        label=Linux        read-only        initrd=/initrd.imgimage=/vmlinuz.old        label=LinuxOLD        read-only        optional       
initrd=/initrd.img.oldIt seems that the line "root=/dev/mapper/volume_group1-logical_vol2" is the key of the problem.But how does it works on a standart install.I suppose I am not obliged to make a /boot partition If someone can help me ...Thanks

Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions !
Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses.

0

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

boot + lvm ?

On Tue, Jan 16, 2007 at 02:24:44PM +0100, Stephane Durieux wrote:
> Hello,
>
> I encounter a problem using lvm and lilo.
> On standart install, everythings works despite the boot partition is on a logical volum.
>
> But when I try to make a custom kernel and then run a lilo, I get the following message:
> device-mapper: table ioctl failed: No such device or address
> Fatal: device-mapper: dm_task_run(DM_DEVICE_TABLE) failed

> It seems that the line "root=/dev/mapper/volume_group1-logical_vol2" is the key of the problem.
> But how does it works on a standart install.
>
> I suppose I am not obliged to make a /boot partition
>

I don't know if you can do what you want. On a standard install if you
choose LVM root you have to put /boot into a regular partition. AFAIK
its because bootloaders can't see lvm. Further, the install process
sets up the LVM mapping within the initrd so that the kernel knows
what's where.

On my etch system with separate /boot, my kernel parma is
root=/dev/mapper/system-root
Note: system is the the name of the VG for the system, and root is the
LV for the / directory.

Doug.

--

boot + lvm ?

Le mardi 16 janvier 2007 14:24, Stephane Durieux a écrit :
> Hello,
>
> I encounter a problem using lvm and lilo.
> On standart install, everythings works despite the boot partition is on a
> logical volum.
>
> But when I try to make a custom kernel and then run a lilo, I get the
> following message: device-mapper: table ioctl failed: No such device or
> address
> Fatal: device-mapper: dm_task_run(DM_DEVICE_TABLE) failed
[...]

LVM only installs used to work, with lilo as the bootloader, but since ~kernel
2.6.17+udev, it does not anymore.
Read the full history here :
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=401393

I had the surprise one day, with my workstation, it could not boot after a
kernel upgrade (I was following etch/testing).
I had to repartition an create a separate /boot.
I do that systematically since, 100Mo as the first partition. So that I can
use grub again, which is less dangerous.

boot + lvm ?

On Thu, Feb 01, 2007 at 11:26:55PM +0100, Gilles Mocellin wrote:
> I had to repartition an create a separate /boot.
> I do that systematically since, 100Mo as the first partition. So that I can
> use grub again, which is less dangerous.

I also like having a small RAID-1 /boot and keep it mounted read
only. Works with any bootloader, and fairly reliable.

--
http://bitfolk.com/ -- No-nonsense VPS hosting
Encrypted mail welcome - keyid 0x604DE5DB

Syndicate content