Problems booting 2.6.31 on Fedora 8

Problems booting 2.6.31 on Fedora 8

[Ben Greear]

I'm having troubles booting 2.6.31 on Fedora 8.  The same kernel
boots fine on F11, but on F8, it cannot find the root logical volume.

One thing I notice is that F11 uses root=/dev/mapper... and F8 uses
root=/dev/VolGroup00/LogVol00 in grub.  It's not clear to me what
the value of mapper should be...is there some way to figure this
out from an older kernel (2.6.29) that boots fine?

I'm using a kernel config based on the one in F11.

My grub entry looks like:

title SERIAL 2.6.31
         root (hd0,0)
         kernel /ct2.6.31.img ro root=/dev/VolGroup00/LogVol00 console=ttyS0,38400
         initrd /initrd-ct2.6.31.img


sr 0:0:1:0: Attached scsi generic sg0 type 5
scsi 2:0:0:0: Direct-Access     ATA      Maxtor 6L080M0   BACE PQ: 0 ANSI: 5
registered taskstats version 1
   Magic number: 9:307:694
Initalizing network drop monitor service
sd 2:0:0:0: [sda] 160086528 512-byte logical blocks: (81.9 GB/76.3 GiB)
sd 2:0:0:0: Attached scsi generic sg1 type 0
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
  sda: sda1 sda2
sd 2:0:0:0: [sda] Attached SCSI disk
Freeing unused kernel memory: 1292k freed
Write protecting the kernel read-only data: 6036k
Red Hat nash version 6.0.19 starting
Mounting proc filesystem
Mounting sysfs filesystem
Creating /dev
Creating initial device nodes
Sinput: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input4
etting up hotplug.
Creating block device nodes.
Loading pata_acpi.ko module
Waiting for driver initialization.
Loading ata_generic.ko module
Making device-mapper control node
Scanning logical volumes
   Reading all physical volumes.  This may take a while...
   No volume groups found
Activating logical volumes
   Volume group "VolGroup00" not found
Trying to resume from /dev/VolGroup00/LogVol01
Unable to access resume device (/dev/VolGroup00/LogVol01)
Creating root device.
Mounting root filesystem.
mount: could not find filesystem '/dev/root'
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Booting has failed.


Thanks,
Ben


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

Re: Problems booting 2.6.31 on Fedora 8

[Nikita V. Youshchenko]

> I'm having troubles booting 2.6.31 on Fedora 8.  The same kernel
> boots fine on F11, but on F8, it cannot find the root logical volume.
>
> One thing I notice is that F11 uses root=/dev/mapper... and F8 uses
> root=/dev/VolGroup00/LogVol00 in grub.  It's not clear to me what
> the value of mapper should be...is there some way to figure this
> out from an older kernel (2.6.29) that boots fine?

I've recently faced a very similar problem, trying to boot some "modern" 
kernel on debian etch system.

It was solved by putting more recent lvm2 binary into initrd.

Re: Problems booting 2.6.31 on Fedora 8

[Joseph Fannin]

On Fri, Sep 18, 2009 at 10:55:52AM -0700, Ben Greear wrote:
> I'm having troubles booting 2.6.31 on Fedora 8.  The same kernel
> boots fine on F11, but on F8, it cannot find the root logical volume.
>
> One thing I notice is that F11 uses root=/dev/mapper... and F8 uses
> root=/dev/VolGroup00/LogVol00 in grub.  It's not clear to me what
> the value of mapper should be...is there some way to figure this
> out from an older kernel (2.6.29) that boots fine?

Possibly /dev/mapper/VolGroup00-LogVol00 .

--
Joseph Fannin
jfannin@gmail.com

Re: Problems booting 2.6.31 on Fedora 8

[Ben Greear]

On 09/18/2009 11:48 AM, Nikita V. Youshchenko wrote:
>> I'm having troubles booting 2.6.31 on Fedora 8.  The same kernel
>> boots fine on F11, but on F8, it cannot find the root logical volume.
>>
>> One thing I notice is that F11 uses root=/dev/mapper... and F8 uses
>> root=/dev/VolGroup00/LogVol00 in grub.  It's not clear to me what
>> the value of mapper should be...is there some way to figure this
>> out from an older kernel (2.6.29) that boots fine?
>
> I've recently faced a very similar problem, trying to boot some "modern"
> kernel on debian etch system.
>
> It was solved by putting more recent lvm2 binary into initrd.

The LVM2 mailing list gave me another answer:

Compile with
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y


This will likely not work on later distributions, but seems to work
fine for Fedora 8, at least.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com