[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [linux-lvm] mount root filesystem on lvm



Am Son, 2003-05-11 um 04.05 schrieb Manfred Gschweidl:

> when i use "/dev/progs/root" boot up ends with:
> VFS: Cannot open root device "3a00" or 3a:00
> Please append s correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on 3a:00

0x3a is the LVM1 device major.

> when i use "/dev/mapper/progs-root" boot up ends with:
> VFS: Cannot open root device "mapper/progs-root" or 00:00
> Please append s correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on 00:00

Ok, 00:00 means that he didn't find anything there.

> i use the append option for "/dev/mapper/progs-root", because i can't 
> run lilo with it, because lilo says, that it doesn't find the device....

Yep.

It looks like you are currently running on LVM1 but want to switch to
LVM2 after the next reboot, right?

LILO can only look at the device numbers currently in use in /dev, but
when there is no device-mapper device there, he can't find the device
number to use with LVM2.

I don't think you can't activate a volume group at the same time with
LVM1 and LVM2, so you'll have to give it explicitly to the kernel
"command line" on the next reboot.

Before reboot, can you find out what major device-mapper uses? Type "cat
/proc/devices" and search for the line with device-mapper. My kernel is
currently using the major 254, but I don't know if the numbers are
allocated the same way with the 2.4 kernel.

Ok, then you'll have to translate the number to hexdecimal (e.g. using
this command line where you should replace 254 with your major number if
it differs: perl -e 'printf "%02x\n", 254).

After rebooting you interrupt lilo and append root=##00 to the command
line, where ## is the major number in hex (so it looks like "linux
root=fe00"). If he doesn't find the root device, try fe01, fe02, etc...
until he finds the root device. The problem is that you can't know
exactly which minor number the kernel number will assign the volume
without having tested it first.

This should of course only work when the ramdisk has correctly activated
the volume before the kernel tries to mount the root filesystem, there
should be a message printed.

-- 
Christophe Saout <christophe saout de>




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]